chore(automation/agents,lint): reorganize automation docs/config into .github/automation; add branding agent; tighten package-json linting

- Move and expand automation, branching, labels, issue-types, PR labeling and discussion docs/config into .github/automation/
- Remove legacy root-level labeler/labels/issue-types/project-pr-labeler files (now consolidated under .github/automation/)
- Add branding agent: .github/agents/branding.agent.js and spec .github/agents/branding.agent.md; register in agents index
- Update .github/workflows/lint.yml to run npm-package-json-lint step with granular env toggles; add NPMPKGJSONLINT_REQUIRE_FIELDS env
- Update docs and npmpackagejsonlint.config.cjs to reflect granular NPMPKGJSONLINT flags and remove template-scaffold ignores
- Minor tweaks to LINTING.md (timestamps, guidance) and agent index formatting

Author: ashleyshaw

.github/agents/agent.md

@@ -15,6 +15,7 @@ This document serves as the master index for all agent specifications, templates
 
 > **Label Reference:**  
 > Agents, agent specs, and agent-related issues should use or reference the label:  
+>
 > - `ai-ops:agents` (for agent definitions and specs)  
 > - `ai-ops:chat-modes` (for chatmode-related agents)  
 > - `ai-ops:prompts` (for prompt agents or reusable prompt logic)  
@@ -40,9 +41,11 @@ All agent specs, templates, and stubs should be placed in the `.github/agents/`
 | [template.agent.js](./template.agent.js)                       | JS template for new agent implementations    |
 | [template.agent.py](./template.agent.py)                       | Python template for new agent implementations|
 | [template.agent.sh](./template.agent.sh)                       | Shell script template for agent integrations |
+| [branding.agent.js](./branding.agent.js)                      | Unified branding agent: header, footer, badges|
+| [branding.agent.md](./branding.agent.md)                      | Spec for unified branding agent               |
 | *(Add additional agent files below as needed)*                 |                                              |
 
-> _To add new agents, create a file in `.github/agents/` and update this table. Use descriptive filenames and provide a brief purpose/notes column for each._
+> *To add new agents, create a file in `.github/agents/` and update this table. Use descriptive filenames and provide a brief purpose/notes column for each._
 
 ---
 

.github/agents/branding.agent.js

@@ -0,0 +1,41 @@
+// branding.agent.js - Unified agent for automating header, footer, and badge insertion in Markdown files.
+// See .github/agents/branding.agent.md for spec.
+
+const { insertHeaderFooter } = require('../../scripts/includes/header-footer');
+const { updateBadgesInReadme } = require('../../scripts/includes/badges');
+const path = require('path');
+const Ajv = require('ajv');
+
+// Unified config and schema
+const brandingConfig = require('../../schemas/header-footer-agent/agent-config.schema.json');
+
+function validateConfig(config, schema) {
+    const ajv = new Ajv();
+    const validate = ajv.compile(schema);
+    if (!validate(config)) {
+        throw new Error(
+            `Branding config validation failed: ${JSON.stringify(validate.errors, null, 2)}`
+        );
+    }
+}
+
+async function main() {
+    // Validate branding config
+    validateConfig(brandingConfig, brandingConfig, 'Branding');
+
+    // Example usage: update all README.md files
+    await insertHeaderFooter(
+        'README.md',
+        { headers: brandingConfig.headers, footers: brandingConfig.footers },
+        { backup: true }
+    );
+    await updateBadgesInReadme(
+        path.join(process.cwd(), 'README.md'),
+        '.github/workflows',
+        { backup: true }
+    );
+    console.log('Headers, footers, and badges updated.');
+}
+
+if (require.main === module)
+    main().catch((err) => (console.error(err), process.exit(1)));

.github/agents/branding.agent.md

@@ -0,0 +1,59 @@
+---
+file_type: "agent"
+title: "Branding Agent"
+description: "Unified agent for automating insertion and management of headers, footers, and badges in Markdown documentation files."
+version: "v1.0"
+last_updated: "2025-10-26"
+owners: ["LightSpeedWP Engineering"]
+tags: ["branding", "header", "footer", "badges", "automation", "documentation"]
+category: "automation"
+status: "active"
+references:
+  - "../../schemas/header-footer-agent/agent-config.schema.json"
+  - "../../scripts/includes/header-footer.js"
+  - "../../scripts/includes/badges.js"
+  - "./branding.agent.js"
+  - "./branding.instructions.md"
+  - "./branding.prompt.md"
+  - "../../README.md"
+  - "../../BADGES.md"
+---
+
+## Branding Agent Specification
+
+## Purpose
+
+Automate the insertion, update, and management of headers, footers, and badges in Markdown documentation files, using a unified schema-driven config.
+
+## Triggers
+
+- On README or doc update
+- On CI or workflow_dispatch
+- On branding config change
+
+## Inputs/Outputs
+
+- **Input:** File path, branding config, schema
+- **Output:** Updated doc with selected/random header, footer, and badges
+
+## Actions
+
+- Read unified branding config (headers, footers, badges) in JSON/YAML
+- Validate config against [agent-config.schema.json](../../schemas/header-footer-agent/agent-config.schema.json)
+- Select appropriate category/variant (random or by file type/tag)
+- Insert/update header, footer, and badge blocks in the doc
+
+## Guardrails
+
+- Never overwrite main content
+- Validate config before applying
+- Always backup before changes
+- Only update designated blocks (header, footer, badges)
+
+## References
+
+- [agent-config.schema.json](../../schemas/header-footer-agent/agent-config.schema.json)
+- [header-footer.js](../../scripts/includes/header-footer.js)
+- [badges.js](../../scripts/includes/badges.js)
+- [README.md](../../README.md)
+- [BADGES.md](../../BADGES.md)