Update agents files

Author: ashleyshaw

.github/agents/a11y.agent.md

@@ -1,7 +1,8 @@
 ---
 description: "Block Theme Accessibility Expert — WCAG-aligned guidance and actionable checks for WordPress block themes"
+title: "Block Theme Accessibility Expert"
 model: GPT-4.1
-tools: ["changes", "codebase", "edit/editFiles", "extensions", "fetch", "findTestFiles", "githubRepo", "new", "openSimpleBrowser", "problems", "runCommands", "runTasks", "runTests", "search", "searchResults", "terminalLastCommand", "terminalSelection", "testFailure", "usages", "vscodeAPI"]
+tools: ["vscode", "execute/testFailure", "execute/getTerminalOutput", "execute/runTask", "execute/getTaskOutput", "execute/createAndRunTask", "execute/runInTerminal", "execute/runTests", "read/problems", "read/readFile", "read/terminalSelection", "read/terminalLastCommand", "edit/editFiles", "search", "web"]
 ---
 
 # Block Theme Accessibility Expert (WCAG & WordPress)

.github/agents/block-theme-build.agent.md

@@ -1,10 +1,12 @@
 ---
-title: Block Theme Build Agent Spec
-description: Specification for the build, lint, and test automation agent for block themes
-category: Agent
-type: Agent Specification
-audience: Developers, AI Agents
+title: "Block Theme Build Agent Spec"
+description: "Specification for the build, lint, and test automation agent for block themes"
+category: "Agent"
+type: "Agent Specification"
+audience: "Developers, AI Agents"
+model: "GPT-4.1"
 date: 2025-12-01
+tools: ["search", "edit", "fetch"]
 ---
 
 # Block Theme Build Agent Spec
@@ -14,20 +16,23 @@ This document defines the specification for the `block-theme-build.agent.js` aut
 ---
 
 ## Purpose
+
 - Automate the build, lint, test, and validation process for a block theme.
 - Ensure all code changes are validated against WordPress and org standards before merging or deployment.
 - Provide a consistent, reproducible build and test process for local and CI/CD environments.
 
 ---
 
 ## Key References
+
 - [Main Agent Index](./agent.md)
 - [WordPress Theme Build Process](https://developer.wordpress.org/themes/advanced-topics/build-process/)
 - [@wordpress/scripts Reference](https://developer.wordpress.org/block-editor/reference-guides/packages/packages-scripts/)
 
 ---
 
 ## Build Process Overview
+
 1. **Install**: Ensure all required dependencies are installed (`npm ci`).
 2. **Lint**: Run all linters (JS, CSS, PHP) and fail on any errors.
 3. **Build**: Use `@wordpress/scripts` and custom webpack config to build assets.
@@ -37,13 +42,15 @@ This document defines the specification for the `block-theme-build.agent.js` aut
 ---
 
 ## Environment Variables
+
 - `DRY_RUN`: If true, only print steps without executing them.
 - `VERBOSE`: If true, print detailed logs for each step.
 - `GITHUB_TOKEN`: For workflow and label operations (if needed).
 
 ---
 
 ## Maintenance & Best Practices
+
 - Keep this spec in sync with the [WordPress Theme Build Process](https://developer.wordpress.org/themes/advanced-topics/build-process/).
 - Update the agent and this spec as new best practices or requirements emerge.
 - Ensure all contributors are aware of this spec and reference it in PRs and workflow changes.

.github/agents/development-assistant.agent.md

@@ -1,12 +1,7 @@
 ---
 name: Block Theme Development Assistant
 description: AI development assistant for WordPress block theme development
-tools:
-  - semantic_search
-  - read_file
-  - grep_search
-  - file_search
-  - run_in_terminal
+tools: ["search", "edit", "fetch", "semantic_search", "read_file", "grep_search", "file_search", "run_in_terminal", "grep_search", "file_search", "run_in_terminal", file_search, run_in_terminal]
 ---
 
 # Block Theme Development Assistant
@@ -16,66 +11,76 @@ I'm your WordPress block theme development assistant for **{{theme_name}}**. I p
 ## Capabilities
 
 ### 🎨 Pattern Development
+
 - Block pattern creation and customisation
 - Pattern registration and categorisation
 - Responsive pattern markup
 
 ### 📄 Template Development
+
 - Block templates (HTML)
 - Template parts
 - Template hierarchy
 
 ### 🎛️ Theme Configuration
+
 - `theme.json` configuration
 - Style variations
 - Global styles and settings
 
 ### 🔧 Technical Support
+
 - WordPress Block Editor (Gutenberg) integration
 - Build process and asset compilation
 - Testing and debugging
 
 ### 📝 Code Generation
+
 - PHP functions following WordPress standards
 - JavaScript for theme functionality
 - SCSS/CSS for styling
 - Block template HTML
 
 ### 🚀 Best Practices
+
 - Performance optimisation
 - Accessibility compliance
 - Security implementation
 - WordPress coding standards
 
 ## Quick Commands
 
-| Command | Description |
-|---------|-------------|
-| `help patterns` | Block pattern assistance |
-| `help templates` | Template development |
-| `help styles` | Styling and theme.json |
-| `help js` | JavaScript functionality |
-| `help testing` | Testing strategies |
-| `help build` | Build process help |
+| Command          | Description              |
+| ---------------- | ------------------------ |
+| `help patterns`  | Block pattern assistance |
+| `help templates` | Template development     |
+| `help styles`    | Styling and theme.json   |
+| `help js`        | JavaScript functionality |
+| `help testing`   | Testing strategies       |
+| `help build`     | Build process help       |
 
 ## Development Modes
 
 ### Pattern Authoring Mode
+
 Focus on block pattern creation, markup, and registration.
 
 **Activate**: "Switch to pattern authoring mode"
 
 ### Theme.json Editing Mode
+
 Focus on schema, tokens, and validation for theme.json and style variations.
 
 **Activate**: "Switch to theme.json editing mode"
 
 ### PHP/JS/SCSS Expert Mode
+
 Focus on advanced code, refactoring, and best practices.
 
 **Activate**: "Switch to expert mode"
 
 ### Testing & QA Mode
+
 Focus on Playwright, Jest, PHPUnit, and accessibility testing.
 
 **Activate**: "Switch to testing mode"

.github/agents/generate-theme.agent.md

@@ -1,16 +1,7 @@
 ---
 name: "Generate Plugin"
 description: "Interactive agent that collects comprehensive requirements and generates a WordPress multi-block plugin with CPT, taxonomies, and SCF fields"
-tools:
-  - "semantic_search"
-  - "read_file"
-  - "grep_search"
-  - "file_search"
-  - "run_in_terminal"
-  - "create_file"
-  - "update_file"
-  - "delete_file"
-  - "move_file"
+tools: ["vscode", "execute", "edit", "search", "web", "semantic_search", "read_file", "grep_search", "file_search", "run_in_terminal", "create_file", "update_file", "delete_file", "move_file", "grep_search"]
 ---
 
 # Block Theme Generate Theme Agent

.github/agents/release-scaffold.agent.md

@@ -12,6 +12,7 @@ status: "active"
 visibility: "public"
 tags: ["release", "scaffold", "automation", "validation", "wordpress", "block-theme"]
 owners: ["lightspeedwp/maintainers"]
+tools: ["vscode", "execute", "edit", "search", "web", "semantic_search", "read_file", "grep_search", "file_search", "run_in_terminal", "create_file", "update_file", "delete_file", "move_file", "grep_search"]
 metadata:
   guardrails: "Never modify WordPress template files that contain mustache placeholders. Use dry-run validation first. Stop if placeholder integrity is compromised."
 ---
@@ -61,6 +62,7 @@ This agent covers scaffold **pre-release preparation**:
 ## Validation Criteria
 
 **Critical (must pass):**
+
 - Placeholder integrity confirmed
 - `VERSION`, `package.json`, `composer.json` versions aligned (SemVer)
 - Dry-run lint/format/test pass
@@ -69,6 +71,7 @@ This agent covers scaffold **pre-release preparation**:
 - No high/critical npm vulnerabilities
 
 **Important (should pass):**
+
 - `docs/RELEASE_PROCESS_SCAFFOLD.md` and `docs/GENERATE_THEME.md` current
 - Release templates still templated with `{{mustache}}`
 - README/CONTRIBUTING references up to date
@@ -130,12 +133,15 @@ Provide a concise markdown report:
 - Security audit: ✅ / ❌
 
 Blockers:
+
 - ...
 
 Warnings:
+
 - ...
 
 Next Steps:
+
 1. Update meta versions only (VERSION, package.json, composer.json)
 2. Fix blockers
 3. Re-run dry-run validation

.github/agents/release.agent.md

@@ -12,6 +12,7 @@ status: "active"
 visibility: "public"
 tags: ["release", "automation", "validation", "wordpress", "block-theme", "{{theme_slug}}"]
 owners: ["{{author}}"]
+tools: ["vscode", "execute", "edit", "search", "web", "semantic_search", "read_file", "grep_search", "file_search", "run_in_terminal", "create_file", "update_file", "delete_file", "move_file", "grep_search"]
 metadata:
   guardrails: "Verify that no {{mustache}} placeholders remain in the generated theme. Never skip validation steps. Stop if any critical check fails."
 ---
@@ -62,13 +63,15 @@ Ensure every release is:
 ## Validation Criteria
 
 **Critical (must pass)**
+
 - No `{{...}}` placeholders remain in the theme.
 - Versions aligned across meta files and `style.css`.
 - Lint/format/test/build pass.
 - `CHANGELOG.md` updated with release entry and links.
 - No high/critical vulnerabilities outstanding.
 
 **Important (should pass)**
+
 - Documentation current (README, release docs).
 - Dependencies not deprecated/out-of-date.
 - Optional checks (bundle size, Lighthouse) within targets.
@@ -116,12 +119,15 @@ Provide a concise readiness report with blockers, warnings, and explicit next st
 - Security audit: ✅ / ❌
 
 Blockers:
+
 - ...
 
 Warnings:
+
 - ...
 
 Next Steps:
+
 1. ...
 2. ...
 3. ...
@@ -163,11 +169,11 @@ When adding new validation steps:
 
 ## Quick Reference
 
-| Task            | Command/Prompt                |
-| --------------- | ----------------------------- |
-| Full validation | "Run full release validation" |
-| Check version   | "Check version consistency"   |
-| Placeholder scan| `grep -R "{{" .`              |
-| Build           | `npm run build`               |
-| Security audit  | `npm audit --audit-level=high`|
-| Quick status    | "Am I ready to release?"      |
+| Task             | Command/Prompt                 |
+| ---------------- | ------------------------------ |
+| Full validation  | "Run full release validation"  |
+| Check version    | "Check version consistency"    |
+| Placeholder scan | `grep -R "{{" .`               |
+| Build            | `npm run build`                |
+| Security audit   | `npm audit --audit-level=high` |
+| Quick status     | "Am I ready to release?"       |

.github/agents/reporting.agent.md

@@ -12,6 +12,7 @@ status: "active"
 visibility: "public"
 tags: ["reporting", "automation", "block-theme", "ci", "lint", "coverage"]
 owners: ["lightspeedwp/maintainers"]
+tools: ["vscode", "execute", "edit", "search", "web", "semantic_search", "read_file", "grep_search", "file_search", "run_in_terminal", "create_file", "update_file", "delete_file", "move_file", "grep_search"]
 metadata:
   guardrails: "Always write reports inside .github/reports/, include ISO date prefixes, link to logs, and clean tmp artifacts."
 ---
@@ -66,15 +67,15 @@ You are the **Reporting Agent** for the Block Theme Scaffold. You coordinate how
 
 ## Report Directory Map
 
-| Category      | Purpose                                  | Example Path                                                         |
-| ------------- | ---------------------------------------- | -------------------------------------------------------------------- |
-| Coverage      | Test coverage (JS/PHP)                   | `.github/reports/coverage/js/2025-12-07-coverage.json`               |
-| Validation    | Lint/quality checks                      | `.github/reports/validation/2025-12-07-eslint-report.json`           |
-| Analysis      | Build audits, accessibility, security    | `.github/reports/analysis/2025-12-07-lighthouse.json`                |
-| Performance   | Budgets, CWV, bundle size                | `.github/reports/performance/2025-12-07-bundle-size.json`            |
-| Agents        | AI agent outputs and summaries           | `.github/reports/agents/2025-12-07-theme-generator.json`             |
-| Comparison    | Before/after deltas across runs          | `.github/reports/comparison/2025-12-07-bundle-size-diff.json`        |
-| Projects/Active | Multi-day project progress updates     | `.github/reports/projects/active/{slug}/2025-12-07-daily-progress.md` |
+| Category        | Purpose                               | Example Path                                                          |
+| --------------- | ------------------------------------- | --------------------------------------------------------------------- |
+| Coverage        | Test coverage (JS/PHP)                | `.github/reports/coverage/js/2025-12-07-coverage.json`                |
+| Validation      | Lint/quality checks                   | `.github/reports/validation/2025-12-07-eslint-report.json`            |
+| Analysis        | Build audits, accessibility, security | `.github/reports/analysis/2025-12-07-lighthouse.json`                 |
+| Performance     | Budgets, CWV, bundle size             | `.github/reports/performance/2025-12-07-bundle-size.json`             |
+| Agents          | AI agent outputs and summaries        | `.github/reports/agents/2025-12-07-theme-generator.json`              |
+| Comparison      | Before/after deltas across runs       | `.github/reports/comparison/2025-12-07-bundle-size-diff.json`         |
+| Projects/Active | Multi-day project progress updates    | `.github/reports/projects/active/{slug}/2025-12-07-daily-progress.md` |
 
 ## Agent Responsibilities
 
@@ -358,14 +359,15 @@ Depending on agent type:
 Date: 2025-12-07
 Project: {project-name-or-slug}
 Work Completed:
+
 - Task X.Y completed
 - N tests added to file.test.js
 - Coverage: 80% → 84% (+4%)
-Blockers:
+  Blockers:
 - None / {describe blockers}
-Next Steps:
+  Next Steps:
 - Continue with Task X.Y+1
-Links:
+  Links:
 - Project doc: .github/projects/active/{project-slug}.md
 - Logs: logs/projects/{YYYY-MM-DD}-{project-slug}.log
 ```
@@ -376,18 +378,19 @@ Links:
 Week of 2025-12-07
 Project: {project-name-or-slug}
 Summary:
+
 - Phase X completed
 - Coverage: 82% → 86% (Δ+4%)
 - Tests added: 12
-Key Achievements:
+  Key Achievements:
 - [...]
-Challenges:
+  Challenges:
 - [...]
-Blockers:
+  Blockers:
 - None / [...]
-Next Steps:
+  Next Steps:
 - Continue with Task X.Y+1
-Links:
+  Links:
 - Daily logs: .github/reports/projects/active/{project-slug}/
 - Project doc: .github/projects/active/{project-slug}.md
 ```
@@ -778,6 +781,7 @@ async function runLighthouse() {
 - Tests: `tests/agents/reporting.agent.test.js`
 - Workflow: `.github/workflows/agent-reporting.yml`
 - Logs: `logs/` (per-category subfolders)
+
 ## Summary
 
 ✅ Each report type has defined structure and location