[AI Ops] Refactor agents into unified branding.agent.js (header, footer, badge logic)

[ashleyshaw]

AI Ops Summary

The current AI agent-related branding code (header, footer, badge logic) is duplicated and inconsistent across several files. This refactor will unify this logic into a single branding.agent.js module, improving maintainability and reducing technical debt.

Problem / Opportunity

At present, updates to AI branding elements require editing multiple files, increasing the risk of errors and inconsistencies. A centralised module will streamline updates, promote code reuse, and make future changes easier.

Approach / Solution

• Extract existing header, footer, and badge logic from their current locations
• Consolidate them into a single branding.agent.js file as reusable functions or components
• Replace direct logic use in other modules with imports from this unified agent
• Maintain all inline documentation and adhere to WordPress Coding Standards
• Minimise file size; avoid shipping unused code

Acceptance Criteria

• AI workflow/agent described
• Problem/opportunity scoped
• Success metric defined
• Documentation updated
• PR uses correct branch prefix (ai/)
• Approved by at least one maintainer

Additional Context

Refer to organisation standards for code, security, and documentation: https://github.com/lightspeedwp/.github/blob/develop/.github/custom-instructions.md and https://github.com/lightspeedwp/.github/blob/develop/AGENTS.md

References

• Contribution Guidelines
• Branching Strategy
• Automation Governance
• PR Labels
• Saved Replies
• Project Meta
• Labeler Config
• Labels
• Issue Types

---

Definition of Ready (DoR)

• AI ops goal described
• Area/action mapped
• Acceptance criteria listed
• Estimate added

Definition of Done (DoD)

• All acceptance criteria met
• Solution/automation verified
• Documentation updated
• PR uses correct branch prefix (ai/)