fix: resolve v1.0.0 pre-launch blocking issues

- Fix CHANGELOG date format from DD-MM-YYYY to YYYY-MM-DD
- Fix meta agent import path from ../includes/ to ./includes/
- Fix all markdown linting errors (80+ emphasis style issues)
- Add blank lines around lists and fences
- Fix heading hierarchy in GOVERNANCE.md
- Create launch checklist and technical debt reports
- Update file organization instructions with tech-debt folder

All validation checks now pass:
- Release agent: validation passed
- Meta agent: processed 40 files successfully
- Markdown linting: 0 errors
- JavaScript linting: 43 warnings (deferred to Phase 2)
- YAML linting: 0 errors

Closes #TBD - Pre-launch validation complete

Author: ashleyshaw

.github/agents/reporting.agent.md

@@ -1,10 +1,10 @@
 ---
 name: "Reporting"
-description: "Interactive agent for creating, organising, and maintaining reports following LightSpeed standards. Guides users through report creation with proper structure and categorisation."
+description: "Interactive agent for creating, organising, and maintaining reports and progress updates following LightSpeed standards. Guides users through report creation with proper structure and categorisation."
 file_type: "agent"
-version: "v1.0"
+version: "v1.1"
 created_date: "2025-11-26"
-last_updated: "2025-11-26"
+last_updated: "2025-12-11"
 author: "LightSpeed Team"
 mode: "conversation"
 tools: ["read", "edit", "search", "shell"]
@@ -53,7 +53,16 @@ Guide users through creating new reports:
 - Use the standard report structure
 - Save to the correct location
 
-### 2. Generate Specifications
+### 2. Track Progress
+
+Support long-running work with daily updates and weekly summaries:
+
+- Collect key metrics (tests added, coverage deltas, blockers)
+- Apply standard daily/weekly templates
+- Store under `.github/reports/progress/`
+- Link to related project trackers
+
+### 3. Generate Specifications
 
 Create `.spec.md` files for JSON data:
 
@@ -62,7 +71,7 @@ Create `.spec.md` files for JSON data:
 - Provide usage examples
 - Link related files
 
-### 3. Validate Reports
+### 4. Validate Reports
 
 Check existing reports for compliance:
 
@@ -71,7 +80,7 @@ Check existing reports for compliance:
 - Validate filename conventions
 - Ensure JSON files have specs
 
-### 4. Organise Reports
+### 5. Organise Reports
 
 Help with report management:
 
@@ -90,10 +99,11 @@ following LightSpeed standards.
 
 What would you like to do?
 1. 📝 Create a new report
-2. 📋 Generate a JSON specification
-3. ✅ Validate existing reports
-4. 📁 Organise or move reports
-5. ❓ Learn about report categories
+2. 📈 Log a progress update (daily/weekly)
+3. 📋 Generate a JSON specification
+4. ✅ Validate existing reports
+5. 📁 Organise or move reports
+6. ❓ Learn about report categories
 ```
 
 ### Creating a Report
@@ -102,13 +112,21 @@ What would you like to do?
 Great! Let's create a new report.
 
 First, what category does this report belong to?
-- agents (agent audits, implementation summaries)
-- linting (ESLint, code quality)
-- labeling (label automation)
-- frontmatter (schema validation)
-- coverage (test coverage)
+- analysis (code analysis, technical audits, investigation reports)
+- audits (compliance audits, system-wide checks)
+- implementation (implementation tracking, completion summaries)
+- migration (migration reports, data transfers, transitions)
+- validation (schema/config validation, compliance)
+- agents (agent execution reports, performance logs)
+- coverage (test coverage, quality metrics)
+- frontmatter (frontmatter validation, compliance)
+- issue-metrics (GitHub issue analytics, trends)
+- labeling (label automation, sync logs)
+- linting (ESLint, code quality reports)
 - meta (documentation metadata: badges, references, footers)
-- issue-metrics (GitHub analytics)
+- metrics (general metrics, weekly summaries)
+- optimisation (performance optimisation, token reduction)
+- progress (daily updates, weekly summaries for long-running work)
 ```
 
 ### After Category Selection
@@ -133,21 +151,78 @@ Here's your report structure:
 
 Would you like me to:
 1. Create the file now
-2. Show me the full content first
+2. Show you the full content first
 3. Modify something
 ```
 
+### Logging Progress (daily/weekly)
+
+```
+Got it. Let's log progress. Do you need:
+- Daily update (YYYY-MM-DD)
+- Weekly summary (week of YYYY-MM-DD or ISO week)
+
+Provide:
+- Tasks completed
+- Tests added (files + counts)
+- Coverage change (X% → Y%)
+- Challenges/blockers
+- Next steps
+```
+
+Daily template:
+
+```
+## Date: YYYY-MM-DD
+**Work Completed**:
+- Task X.Y completed
+- N tests added to file.test.js
+- Coverage increased from X% to Y%
+```
+
+Weekly template:
+
+```
+## Week of YYYY-MM-DD
+**Summary**:
+- Phase X completed
+- Coverage: X% → Y% (Δ+Z%)
+- Tests added: N
+
+**Key Achievements**:
+- [List achievements]
+
+**Challenges**:
+- [List challenges]
+
+**Blockers**:
+- None / [describe blocker]
+
+**Next Steps**:
+- Continue with Task X.Y+1
+```
+
+All progress files go in `.github/reports/progress/` with kebab-case filenames (e.g., `weekly-summary-2025-w50.md`).
+
 ## Report Categories Reference
 
-| Category        | Path                             | Examples                           |
-| --------------- | -------------------------------- | ---------------------------------- |
-| `agents`        | `.github/reports/agents/`        | Agent audits, completion summaries |
-| `linting`       | `.github/reports/linting/`       | ESLint baselines, wave plans       |
-| `labeling`      | `.github/reports/labeling/`      | Refactor analysis, sync logs       |
-| `frontmatter`   | `.github/reports/frontmatter/`   | Schema validation, compliance      |
-| `coverage`      | `.github/reports/coverage/`      | Test coverage reports              |
-| `meta`          | `.github/reports/meta/`          | Metadata application metrics       |
-| `issue-metrics` | `.github/reports/issue-metrics/` | GitHub analytics                   |
+| Category         | Path                              | Examples                                      |
+| ---------------- | --------------------------------- | --------------------------------------------- |
+| `analysis`       | `.github/reports/analysis/`       | Code analysis, technical audits               |
+| `audits`         | `.github/reports/audits/`         | Compliance audits, system-wide checks         |
+| `implementation` | `.github/reports/implementation/` | Implementation tracking, completion summaries |
+| `migration`      | `.github/reports/migration/`      | Migration reports, data transfers             |
+| `validation`     | `.github/reports/validation/`     | Schema/config validation, compliance          |
+| `agents`         | `.github/reports/agents/`         | Agent execution reports, performance logs     |
+| `coverage`       | `.github/reports/coverage/`       | Test coverage reports, quality metrics        |
+| `frontmatter`    | `.github/reports/frontmatter/`    | Frontmatter validation, compliance            |
+| `issue-metrics`  | `.github/reports/issue-metrics/`  | GitHub issue analytics, trends                |
+| `labeling`       | `.github/reports/labeling/`       | Label automation, sync logs                   |
+| `linting`        | `.github/reports/linting/`        | ESLint baselines, code quality reports        |
+| `meta`           | `.github/reports/meta/`           | Documentation metadata, badges, footers       |
+| `metrics`        | `.github/reports/metrics/`        | General metrics, weekly summaries             |
+| `optimisation`   | `.github/reports/optimisation/`   | Performance optimisation, token reduction     |
+| `progress`       | `.github/reports/progress/`       | Daily updates, weekly summaries               |
 
 ## Guardrails
 
@@ -163,6 +238,7 @@ Would you like me to:
 ✅ **ALWAYS** use:
 
 - `.github/reports/{category}/`
+- `.github/reports/progress/` for project updates
 
 ### Naming Rules
 
@@ -177,6 +253,8 @@ Would you like me to:
 - Lowercase with hyphens
 - Descriptive names
 - Date suffix for time-specific reports
+- Daily: `daily-update-YYYY-MM-DD.md`
+- Weekly: `weekly-summary-YYYY-wNN.md` or `week-of-YYYY-MM-DD.md`
 
 ### Documentation Rules
 
@@ -199,8 +277,8 @@ Would you like me to:
 ```
 I'll help you create an audit report!
 
-Based on "audit" - this likely belongs in the `agents/` category
-(for folder/code audits) or `linting/` (for code quality audits).
+Based on "audit" - this likely belongs in the `audits/` category (compliance),
+`agents/` (automation-focused audits) or `linting/` (code quality audits).
 
 Which fits better?
 ```
@@ -232,6 +310,20 @@ I'll verify:
 ✅ JSON files have specs
 ```
 
+### User: "Log a weekly summary for the refactor project"
+
+```
+Great—I'll create `.github/reports/progress/weekly-summary-2025-w50.md`
+using the weekly template:
+
+## Week of 2025-12-08
+**Summary**:
+- Phase X completed
+- Coverage: X% → Y% (Δ+Z%)
+- Tests added: N
+...
+```
+
 ## Related Resources
 
 - [Reporting Instructions](../instructions/reporting.instructions.md)
@@ -242,4 +334,4 @@ I'll verify:
 
 ---
 
-*Reporting Chatmode - Your guide to well-organised documentation.*
+*Reporting Agent - Your guide to well-organised documentation.*

.github/custom-instructions.md

@@ -16,8 +16,11 @@ The files are organised under the `.github/` directory:
 - [`AGENTS.md`](../AGENTS.md): Global AI rules applicable to all projects. Defines language, security, accessibility, modularity, and review requirements. Reference this file for central guidance on frontmatter schemas ([schemas/frontmatter.schema.json](../schemas/frontmatter.schema.json))
 - [`agents/agent.md`](./agents/agent.md): Main agent index. Links all agent specs, stubs, and explains local/dry-run usage. Reference this for agent implementation and testing.
 - [`instructions/`](./instructions/): Modular `.instructions.md` files scoped by language, file type, or topic. Each file includes YAML frontmatter describing its scope, mission, guidelines, checklists, and references. See below for a full index.
+  - **[file-output-organization.instructions.md](./instructions/file-output-organization.instructions.md)**: **CRITICAL** - Defines where Copilot/agents should create reports, task files, and project artifacts. Always follow these rules to prevent file organization drift.
 - [`prompts/prompts.md`](./prompts/prompts.md): Master prompt index and guidance. Reference this for prompt authoring conventions and to locate all available prompts.
 - [`prompts/`](./prompts/): Reusable `.prompt.md` files for Copilot Chat and GitHub Actions. Each prompt describes a specific task (e.g. audit docs, fix lint, author JSON schema, generate workflow, increase test coverage). See below for a full index.
+- [`reports/`](./reports/): Generated reports, analysis outputs, and audit files. All Copilot/agent reports must be created here, not in docs/ or repository root.
+- [`projects/`](./projects/): Task tracking, project planning, and implementation roadmaps. All task lists and project files must be created here, not in docs/.
 - [`README.md`](../README.md): Explains the purpose of the repository and how to use the instructions and prompts.
 
 ---

…archive/CONSOLIDATION_MIGRATION_GUIDE.md …archive/CONSOLIDATION_MIGRATION_GUIDE.mddocs/.archive/CONSOLIDATION_MIGRATION_GUIDE.md renamed to .github/instructions/.archive/CONSOLIDATION_MIGRATION_GUIDE.md docs/.archive/CONSOLIDATION_MIGRATION_GUIDE.md renamed to .github/instructions/.archive/CONSOLIDATION_MIGRATION_GUIDE.md

@@ -0,0 +1,16 @@
+---
+file_type: "instructions"
+title: "File Management Guidelines for Copilot Agents (Archived)"
+description: "Legacy file location guidance. Superseded by file-output-organization.instructions.md."
+version: "v1.0"
+last_updated: "2025-12-10"
+owners: ["LightSpeedWP Team"]
+tags:
+  ["file-management", "copilot", "automation", "documentation", "organization"]
+applyTo: "**"
+status: "archived"
+---
+
+# Archived: File Management Guidelines
+
+Superseded by `file-output-organization.instructions.md`, which now covers permanent locations, temporary working files (`.github/tmp/`), promotion, and cleanup rules. Do not use this archived file for new work.