Run husky precommit, stage and commit all files

Author: ashleyshaw

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

@@ -7,6 +7,17 @@ permissions: ["read", "write", "execute", "shell", "filesystem"]
 
 # Multi-Block Plugin Scaffold Generator
 
+
+## Wizard Integration
+
+This agent uses the interactive wizard implemented in [`scripts/lib/wizard.js`](../../scripts/lib/wizard.js) via the `runWizard` function. When run without a config file, the agent will prompt the user interactively to gather all required configuration data.
+
+**Wizard usage:**
+- The agent imports and calls `runWizard` for interactive mode.
+- The wizard implementation is currently a placeholder and should be extended for full user input.
+
+See also: [`scripts/agents/generate-plugin.agent.js`](../../scripts/agents/generate-plugin.agent.js)
+
 I'm your comprehensive multi-block plugin generator. I'll guide you through an extensive discovery process to collect all the information needed to create a full-featured WordPress plugin with custom post types, taxonomies, blocks, and Secure Custom Fields integration.
 
 ## 🔍 IMPORTANT: Repository Context Detection

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

@@ -107,7 +107,7 @@ The following files MUST contain mustache variables and should NOT be processed:
    - Check CHANGELOG.md (ensure [Unreleased] → [X.Y.Z] transformation)
    - Validate CONTRIBUTING.md mentions current workflow
    - Check for broken internal links
-   - Verify docs/GENERATE-PLUGIN.md is current
+   - Verify docs/GENERATE_PLUGIN.md is current
 
 5. **Plugin Generator Validation**
    - Run generator with sample config from `.github/schemas/examples/plugin-config.example.json`

.github/agents/reporting.agent.md

@@ -3,7 +3,7 @@ name: Reporting Agent
 description: "AI agent for generating, organising, and managing reports in the .github/reports/ directory"
 target: github-copilot
 version: v1.0
-last_updated: 2025-12-15
+last_updated: "2025-12-15"
 author: LightSpeedWP
 maintainer: Ash Shaw
 file_type: agent

.github/agents/task-researcher.agent.md

@@ -10,7 +10,7 @@ file_type: "agent"
 category: "research"
 status: "active"
 visibility: "public"
-tags: ["research", "block-plugins", "wordpress", "block-editor", "planning", "automation", "theme.json"]
+tags: ["research", "block-plugins", "wordpress", "block-editor", "planning", "automation", "theme-json"]
 owners: ["lightspeedwp/maintainers"]
 tools: ["changes", "search/codebase", "edit/editFiles", "extensions", "fetch", "problems", "readFile", "runCommands", "runCommands/terminalLastCommand", "runCommands/terminalSelection", "usages", "search", "search/searchResults", "vscodeAPI", "new", "wordpress_docs", "wp_cli", "php_cs", "stylelint", "eslint", "context7"]
 metadata:

.github/instructions/agent-spec.instructions.md

@@ -3,8 +3,8 @@ description: >-
   How to author, format, and review agent specification files for the LightSpeed
   multi-block plugin scaffold
 applyTo: .github/agents/*.agent.md
-version: 1
-lastUpdated: 2025-12-11T00:00:00.000Z
+version: "1.0"
+lastUpdated: "2025-12-11"
 references:
   - ../custom-instructions.md
 ---

.github/instructions/folder-structure.instructions.md

@@ -85,6 +85,14 @@ Use this guide when creating, moving, or auditing files. It covers where to plac
 - Used by `inc/class-block-styles.php` to auto-register block variations
 - **Shipped**: Yes
 
+**`generated-plugins/`** - Sample generator output
+
+- Each subdirectory (e.g., `tour-operator/`) is a generated plugin snapshot used for testing and documentation.
+- Regenerate with `node scripts/generate-plugin.js` if the scaffold changes.
+- Keep these folders in `.gitignore` and do not edit them manually unless updating generated examples.
+
+### Build & Development
+
 ### Build & Development
 
 **`bin/`** - Shell scripts and entry points
@@ -129,6 +137,7 @@ Use this guide when creating, moving, or auditing files. It covers where to plac
 - `instructions/` - AI/Copilot rules
 - `prompts/` - AI prompt templates
 - `workflows/` - GitHub Actions CI/CD
+- `projects/` - Planning outcomes (active/completed/plans folders)
 - **Shipped**: No
 
 ### Runtime Data
@@ -153,7 +162,7 @@ Use this guide when creating, moving, or auditing files. It covers where to plac
 - **Shipped**: No
 - **Safe to delete**: Yes
 
-**`reports/`** - Analysis reports
+**`.github/reports/`** - Analysis reports
 
 - Migration reports
 - Audit results
@@ -231,9 +240,9 @@ Use this guide when creating, moving, or auditing files. It covers where to plac
 
 **Report**:
 
-- **Location**: `reports/`
+- **Location**: `.github/reports/`
 - **Format**: Markdown with date and context
-- **Example**: `reports/STYLELINT-MIGRATION.md`
+- **Example**: `.github/reports/STYLELINT-MIGRATION.md`
 
 ## Naming Conventions
 
@@ -346,7 +355,7 @@ Never ship:
 - `bin/`
 - `logs/`
 - `tmp/`
-- `reports/`
+- `.github/reports/`
 - `node_modules/`
 - `vendor/`
 - All config files

.github/instructions/instructions.instructions.md

@@ -3,8 +3,8 @@ description: >-
   Guidelines for writing Copilot instruction files for the LightSpeed
   multi-block plugin scaffold, focused on block plugin development
 applyTo: '**/.github/instructions/*.instructions.md'
-version: 1
-lastUpdated: 2025-12-11T00:00:00.000Z
+version: "1.0"
+lastUpdated: "2025-12-11"
 references:
   - ../custom-instructions.md
 ---

.github/instructions/reporting.instructions.md

@@ -37,6 +37,8 @@ These instructions define standards for creating, storing, and managing reports
 
 ## Report Types
 
+Common categories include analysis, migration, performance, audit, consolidation, implementation, and research. Research outputs belong in `.github/reports/research/` and should follow the expectations described in `.github/instructions/task-researcher.instructions.md`.
+
 ## Examples
 
 - `.github/reports/analysis/2025-12-11-instruction-audit.md`
@@ -352,7 +354,7 @@ fs.rmSync(tmpDir, { recursive: true, force: true });
 
 ### By Developers
 
-1. **Create report** in `reports/` with proper naming
+1. **Create report** in `.github/reports/` with proper naming
 2. **Determine category** (e.g., `analysis`, `migration`).
 3. **Place in subdirectory**: Move the file to `.github/reports/{category}/`.
 4. **Include frontmatter** with all required fields.
@@ -362,7 +364,7 @@ fs.rmSync(tmpDir, { recursive: true, force: true });
 
 ### By Scripts/Agents
 
-1. **Verify location**: Always use `reports/` directory
+1. **Verify location**: Always use `.github/reports/` directory
 2. **Create subdirectory** if needed (e.g., `tmp/reports/analysis/`)
 3. **Log execution** to `logs/` directory
 4. **Generate report** file with timestamp
@@ -427,7 +429,7 @@ logStream.end();
 
 Agents MUST:
 
-1. **Always use `reports/` location**: Never create reports in root
+1. **Always use `.github/reports/` location**: Never create reports in root
 2. **Determine category**: Identify the report category (e.g., `analysis`).
 3. **Save to subdirectory**: Save the report in `.github/reports/{category}/`.
 4. **Follow naming**: Use proper naming convention.
@@ -439,7 +441,7 @@ Agents MUST:
 ```
 When generating reports:
 
-1. Always save to `reports/` directory, NEVER to repository root
+1. Always save to `.github/reports/` directory, NEVER to repository root
 2. Use naming format: {TYPE}-{SUBJECT}-{TIMESTAMP}.md
 3. Include YAML frontmatter with title, description, category, audience, date
 4. Organize content with Executive Summary, Context, Findings, Recommendations
@@ -502,7 +504,7 @@ Required fields:
    ↓
 3. Choose name: {TYPE}-{SUBJECT}-{TIMESTAMP}.md
    ↓
-4. Create in reports/ directory
+4. Create in `.github/reports/` directory
    ↓
 5. Add frontmatter with metadata
    ↓
@@ -512,7 +514,7 @@ Required fields:
    ↓
 8. Commit to version control
    ↓
-9. Update reports/README.md with entry if major
+9. Update `.github/reports/README.md` with entry if major
 ```
 
 ### Report Lifecycle
@@ -524,17 +526,17 @@ Analysis Phase
   └─ Script/Agent Runs
 
 Report Generation
-  ├─ Create: reports/{TYPE}-{SUBJECT}-{TIMESTAMP}.md
+  ├─ Create: `.github/reports/{TYPE}-{SUBJECT}-{TIMESTAMP}.md`
   ├─ Add Frontmatter: title, description, category, date
   └─ Structure: Summary, Context, Findings, Recommendations
 
 Publication
   ├─ Version Control: git add, git commit
   ├─ Documentation: Reference in docs/ if needed
-  └─ Update: reports/README.md entry
+  └─ Update: `.github/reports/README.md` entry
 
 Archive
-  ├─ Location: reports/ (permanent)
+  ├─ Location: `.github/reports/` (permanent)
   ├─ Retention: Indefinite (historical record)
   └─ Cleanup: tmp/reports/{type}/ can be cleaned
 ```

.github/instructions/scaffold-extensions.instructions.md

@@ -465,7 +465,7 @@ When adding new placeholders:
   - Category (namespace, text, meta)
   - Example value
   - All files where it's used
-- [ ] Update `docs/GENERATE-PLUGIN.md` if it's user-facing
+- [ ] Update `docs/GENERATE_PLUGIN.md` if it's user-facing
 - [ ] Add example to this instruction file showing correct usage
 - [ ] Update `.github/agents/generate-plugin.agent.md` if it affects the generator interface
 

.github/instructions/task-planner.instructions.md

@@ -17,6 +17,8 @@ You are a planning assistant. Follow our LightSpeed planning approach to break m
 
 Use these rules when outlining implementation plans or task lists for this repository. Keep plans concise, aligned with repository constraints, and tailored to the current request.
 
+This guidance is the canonical reference for human planners and AI planners such as Claude, Gemini, and Copilot. Always save new plan files and updates under `.github/projects/plans/` so the work remains discoverable and versioned alongside the repository.
+
 ## General Rules
 
 - Keep plans short and sequential; avoid single-step or sprawling plans.
@@ -36,6 +38,12 @@ Use these rules when outlining implementation plans or task lists for this repos
 - Highlight risks or unknowns with a single clarifying question when necessary.
 - Include validation steps (tests, linters, build commands) that match the files being changed.
 
+## Storage & Publication
+
+- Save all plan documents inside `.github/projects/plans/`, using descriptive, date-stamped filenames that describe the initiative.
+- If you track progress, drop intermediate notes in `.github/projects/active/` and move finished plans to `.github/projects/completed/`.
+- Never drop new plans in `docs/plans/`; the directory has been retired in favour of the `.github/projects` hierarchy.
+
 ## Examples
 
 - 1) Audit affected files; 2) Implement change; 3) Run `npm test`; 4) Summarise.