epic: branding-agent - Plan unified Markdown branding #33

Epic Summary

Define the parent specification and delivery plan for category-aware Markdown headers, footers and badges in the .github repository. This is AI Ops planning work, not proof that a unified runtime agent has been implemented. Keep template design and schema detail in the linked children; track remaining implementation separately.

Linked Child Issues/Stories/Tasks/PRs

• [AI Ops] Design footer/header/badge templates for unified branding agent #46 — template design, closed; [AI Ops] Schema update for unified branding agent (category, tags, badges) #49 — schema/config design, closed.
• PR spec: Issue #33 - Comprehensive parent specification for unified branding agent #537 merged the parent specification. Verify its current location: the path cited in that PR was not found on develop.
• Confirm subsequent implementation and validation links before claiming delivery of the branding system.

Milestones & Timeline

GitHub milestone: v1.1. Parent planning sign-off follows verification of the specification and child deliverables; runtime implementation needs separate evidence and tracking.

Acceptance Criteria

• Verify the current parent specification and its relationship to [AI Ops] Design footer/header/badge templates for unified branding agent #46 and [AI Ops] Schema update for unified branding agent (category, tags, badges) #49.
• Define scope and precedence for frontmatter, tags, path-based defaults and safe fallback.
• Cover issue, pull-request, docs, ai-ops, agents, instructions, prompts, schema, readme, test, utility, awesome-copilot, research, audit, workflow and governance.
• Specify accessible, readable, low-noise header, badge and footer rules, including required variants.
• Record and justify the configuration and schema choice and validation behaviour.
• Identify owners, sequencing and separate implementation/QA work; obtain maintainer approval.
• Check labels and types against current standards.

Dependencies / Blockers

The two design children are closed, but their closure and PR #537 do not demonstrate a working agent. Verify where the merged specification lives and what implementation, tests and handoff remain.

Additional Context

In scope: repository-local Markdown branding, category taxonomy, frontmatter/path mapping, configuration, examples, accessibility and maintainability. Out of scope: unrelated audits, non-Markdown branding and unapproved restructuring. Verify current paths before linking older instruction, agent and schema files as live artefacts.

Definition of Ready (DoR)

• Planning goal, children, owner, milestone, dependencies and approver confirmed.

Definition of Done (DoD)

• Maintainer approves the verified parent specification and division of work.
• Planning children and deliverable locations reconciled.
• Outstanding implementation and validation linked separately; epic reviewed before closure.