diff --git a/.github/FOOTER_REMEDIATION_GUIDE.md b/.github/FOOTER_REMEDIATION_GUIDE.md index 637571a55..4163ca09a 100644 --- a/.github/FOOTER_REMEDIATION_GUIDE.md +++ b/.github/FOOTER_REMEDIATION_GUIDE.md @@ -58,10 +58,10 @@ Currently, footers are: ### Key Principles -✅ **One footer per document** — Validation enforces this -✅ **Predefined templates** — Choose from validated, category-specific footers -✅ **Schema validation** — Prevent duplicates and invalid footers -✅ **Automation-ready** — Footer insertion can be automated via agent +✅ **One footer per document** — Validation enforces this +✅ **Predefined templates** — Choose from validated, category-specific footers +✅ **Schema validation** — Prevent duplicates and invalid footers +✅ **Automation-ready** — Footer insertion can be automated via agent --- @@ -101,7 +101,7 @@ The configuration defines **15 document categories** with appropriate footers: [🔗 Website](https://lightspeedwp.agency) · [📧 Contact](https://lightspeedwp.agency/contact) · [👥 Contributors](https://github.com/lightspeedwp/.github/graphs/contributors) ``` -**Use for**: README files, general documentation +**Use for**: README files, general documentation **Lines**: 3 lines (title + blank + content) ### `ai-ops-standard` @@ -114,7 +114,7 @@ The configuration defines **15 document categories** with appropriate footers: [📋 AI Governance](https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION_GOVERNANCE.md) · [🧠 Agents](https://github.com/lightspeedwp/.github/blob/develop/AGENTS.md) · [📞 Contact](https://lightspeedwp.agency/contact) ``` -**Use for**: AI ops, agent specs, automation docs +**Use for**: AI ops, agent specs, automation docs **Lines**: 3 lines ### `standards-footer` @@ -127,7 +127,7 @@ The configuration defines **15 document categories** with appropriate footers: [📋 Coding Standards](https://github.com/lightspeedwp/.github/blob/develop/instructions/coding-standards.instructions.md) · [🔗 Related Files](https://github.com/lightspeedwp/.github/tree/develop/instructions) ``` -**Use for**: Instructions, coding standards, guidelines +**Use for**: Instructions, coding standards, guidelines **Lines**: 3 lines ### All Other Templates @@ -457,6 +457,6 @@ Action: Replace and note in commit --- -**Created**: 2026-05-28 -**Status**: Active guidance for footer remediation +**Created**: 2026-05-28 +**Status**: Active guidance for footer remediation **Related issues**: #33 (branding meta agent), #46 (templates), #49 (schema) diff --git a/.github/PULL_REQUEST_TEMPLATE/pr_bug.md b/.github/PULL_REQUEST_TEMPLATE/pr_bug.md index 3fd851ed2..54fc62b4c 100644 --- a/.github/PULL_REQUEST_TEMPLATE/pr_bug.md +++ b/.github/PULL_REQUEST_TEMPLATE/pr_bug.md @@ -9,7 +9,7 @@ category: "github-templates" # Bugfix Pull Request -> This repository enforces changelog, release, and label automation for all PRs and issues. +> This repository enforces changelog, release, and label automation for all PRs and issues. > See the organisation-wide [Automation Governance & Release Strategy](https://github.com/lightspeedwp/.github/blob/main/docs/AUTOMATION_GOVERNANCE.md) for required rules. ## Linked issues diff --git a/.github/PULL_REQUEST_TEMPLATE/pr_chore.md b/.github/PULL_REQUEST_TEMPLATE/pr_chore.md index 58a47958d..e7ebb6058 100644 --- a/.github/PULL_REQUEST_TEMPLATE/pr_chore.md +++ b/.github/PULL_REQUEST_TEMPLATE/pr_chore.md @@ -9,7 +9,7 @@ category: "github-templates" # Chore Pull Request -> This repository enforces changelog, release, and label automation for all PRs and issues. +> This repository enforces changelog, release, and label automation for all PRs and issues. > See the organisation-wide [Automation Governance & Release Strategy](https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md) for required rules. ## Linked issues diff --git a/.github/PULL_REQUEST_TEMPLATE/pr_ci.md b/.github/PULL_REQUEST_TEMPLATE/pr_ci.md index e03b1ca06..a8f416aea 100644 --- a/.github/PULL_REQUEST_TEMPLATE/pr_ci.md +++ b/.github/PULL_REQUEST_TEMPLATE/pr_ci.md @@ -9,10 +9,10 @@ category: "github-templates" # Build/CI Pull Request -This PR updates the build or CI configuration for Pipelines, linting, packaging, or release automation. +This PR updates the build or CI configuration for Pipelines, linting, packaging, or release automation. Please review the summary, baseline/target, and changelog below. -> This PR Template enforces pipelines, linting, changelog, release, and label automation for all PRs and issues. +> This PR Template enforces pipelines, linting, changelog, release, and label automation for all PRs and issues. > See the organisation-wide [Automation Governance & Release Strategy](https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md) for required rules. ## Linked issues diff --git a/.github/PULL_REQUEST_TEMPLATE/pr_dep_update.md b/.github/PULL_REQUEST_TEMPLATE/pr_dep_update.md index 5f12d1c59..a3fa21f2e 100644 --- a/.github/PULL_REQUEST_TEMPLATE/pr_dep_update.md +++ b/.github/PULL_REQUEST_TEMPLATE/pr_dep_update.md @@ -9,10 +9,10 @@ category: "github-templates" # Dependencies / Maintenance Pull Request -This PR updates dependencies or performs routine maintenance (lint, formatting, hygiene). +This PR updates dependencies or performs routine maintenance (lint, formatting, hygiene). Please review the summary, impact, and changelog below. -> This repository enforces changelog, release, and label automation for all PRs and issues. +> This repository enforces changelog, release, and label automation for all PRs and issues. > See the organisation-wide [Automation Governance & Release Strategy](https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md) for required rules. ## Linked issues diff --git a/.github/PULL_REQUEST_TEMPLATE/pr_docs.md b/.github/PULL_REQUEST_TEMPLATE/pr_docs.md index 619e8f44b..790c202a3 100644 --- a/.github/PULL_REQUEST_TEMPLATE/pr_docs.md +++ b/.github/PULL_REQUEST_TEMPLATE/pr_docs.md @@ -9,7 +9,7 @@ category: "github-templates" # Documentation Pull Request -> This repository enforces changelog, release, and label automation for all PRs and issues. +> This repository enforces changelog, release, and label automation for all PRs and issues. > See the organisation-wide [Automation Governance & Release Strategy](https://github.com/lightspeedwp/.github/blob/main/docs/AUTOMATION_GOVERNANCE.md) for required rules. ## Linked issues diff --git a/.github/PULL_REQUEST_TEMPLATE/pr_feature.md b/.github/PULL_REQUEST_TEMPLATE/pr_feature.md index d7c65adf5..ec6432fbc 100644 --- a/.github/PULL_REQUEST_TEMPLATE/pr_feature.md +++ b/.github/PULL_REQUEST_TEMPLATE/pr_feature.md @@ -9,7 +9,7 @@ category: "github-templates" # Feature Pull Request -> This repository enforces changelog, release, and label automation for all PRs and issues. +> This repository enforces changelog, release, and label automation for all PRs and issues. > See the organisation-wide [Automation Governance & Release Strategy](https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md) for contributor rules. ## Linked issues diff --git a/.github/PULL_REQUEST_TEMPLATE/pr_hotfix.md b/.github/PULL_REQUEST_TEMPLATE/pr_hotfix.md index 8a686e018..c7690d58e 100644 --- a/.github/PULL_REQUEST_TEMPLATE/pr_hotfix.md +++ b/.github/PULL_REQUEST_TEMPLATE/pr_hotfix.md @@ -9,7 +9,7 @@ category: "github-templates" # Hotfix Pull Request -> This repository enforces changelog, release, and label automation for all PRs and issues. +> This repository enforces changelog, release, and label automation for all PRs and issues. > See the organisation-wide [Project Operations Spec](../../docs/GITHUB_PROJECT_OPERATIONS_SPEC.md) for contributor rules. ## Linked issues diff --git a/.github/PULL_REQUEST_TEMPLATE/pr_refactor.md b/.github/PULL_REQUEST_TEMPLATE/pr_refactor.md index 7ceec3501..ca88d9859 100644 --- a/.github/PULL_REQUEST_TEMPLATE/pr_refactor.md +++ b/.github/PULL_REQUEST_TEMPLATE/pr_refactor.md @@ -9,7 +9,7 @@ category: "github-templates" # Refactor Pull Request -> This repository enforces changelog, release, and label automation for all PRs and issues. +> This repository enforces changelog, release, and label automation for all PRs and issues. > See the organisation-wide [Automation Governance & Release Strategy](https://github.com/lightspeedwp/.github/blob/main/docs/AUTOMATION_GOVERNANCE.md) for required rules. ## Linked issues diff --git a/.github/PULL_REQUEST_TEMPLATE/pr_release.md b/.github/PULL_REQUEST_TEMPLATE/pr_release.md index 142893155..1d8d542fd 100644 --- a/.github/PULL_REQUEST_TEMPLATE/pr_release.md +++ b/.github/PULL_REQUEST_TEMPLATE/pr_release.md @@ -9,7 +9,7 @@ category: "github-templates" # Release Pull Request -> This repository enforces changelog, release, and label automation for all PRs and issues. +> This repository enforces changelog, release, and label automation for all PRs and issues. > See the organisation-wide [Automation Governance & Release Strategy](https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md) for contributor rules. ## Linked issues & merged PRs diff --git a/.github/SAVED_REPLIES/community/contribution-thanks.md b/.github/SAVED_REPLIES/community/contribution-thanks.md index ad7931014..a6a7c8f8f 100644 --- a/.github/SAVED_REPLIES/community/contribution-thanks.md +++ b/.github/SAVED_REPLIES/community/contribution-thanks.md @@ -14,7 +14,7 @@ category: "Community" ```markdown Hi @username, -Thank you for your contribution to LightSpeedWP! +Thank you for your contribution to LightSpeedWP! Your time and effort make our project better for everyone. If you’d like to get more involved, check out our [good first issues](../../good-first-issues) or join our [community discussions](../../discussions). diff --git a/.github/SAVED_REPLIES/issues/duplicate.md b/.github/SAVED_REPLIES/issues/duplicate.md index 0cc27c17f..b98b45ef6 100644 --- a/.github/SAVED_REPLIES/issues/duplicate.md +++ b/.github/SAVED_REPLIES/issues/duplicate.md @@ -16,7 +16,7 @@ labels: ```markdown Hi @username, -This issue appears to be a duplicate of #X. +This issue appears to be a duplicate of #X. To keep things organized, we’re closing this as a duplicate. Please follow updates on #X and add any further information there. Thank you! diff --git a/.github/SAVED_REPLIES/issues/inactive-issue.md b/.github/SAVED_REPLIES/issues/inactive-issue.md index 77d49f6a4..827934213 100644 --- a/.github/SAVED_REPLIES/issues/inactive-issue.md +++ b/.github/SAVED_REPLIES/issues/inactive-issue.md @@ -16,7 +16,7 @@ labels: ```markdown Hi @username, -This issue has been closed due to inactivity. +This issue has been closed due to inactivity. If you’re still experiencing this problem, please reply with the requested information or open a new issue. Thank you for your contribution! diff --git a/.github/SAVED_REPLIES/issues/needs-reproduction.md b/.github/SAVED_REPLIES/issues/needs-reproduction.md index 645965e4d..cacc0bc5a 100644 --- a/.github/SAVED_REPLIES/issues/needs-reproduction.md +++ b/.github/SAVED_REPLIES/issues/needs-reproduction.md @@ -16,7 +16,7 @@ labels: ```markdown Hi @username, -To help us investigate, could you please provide a minimal, complete, and reproducible example? +To help us investigate, could you please provide a minimal, complete, and reproducible example? If possible, include: - Exact steps (with URLs/screens) diff --git a/.github/SAVED_REPLIES/technical/code-style.md b/.github/SAVED_REPLIES/technical/code-style.md index 93c75a075..2933e7dae 100644 --- a/.github/SAVED_REPLIES/technical/code-style.md +++ b/.github/SAVED_REPLIES/technical/code-style.md @@ -16,7 +16,7 @@ labels: ```markdown Hi @username, -Thank you for your contribution! +Thank you for your contribution! Please update your code to match our [coding standards](../../instructions/coding-standards.instructions.md): - Consistent indentation and spacing diff --git a/.github/SAVED_REPLIES/technical/performance.md b/.github/SAVED_REPLIES/technical/performance.md index fa071f4ee..941b3edf0 100644 --- a/.github/SAVED_REPLIES/technical/performance.md +++ b/.github/SAVED_REPLIES/technical/performance.md @@ -16,7 +16,7 @@ labels: ```markdown Hi @username, -Thank you for your submission! +Thank you for your submission! Please ensure you have benchmarked any new code for performance and resource usage. - Benchmark critical paths before/after changes diff --git a/.github/SAVED_REPLIES/technical/security.md b/.github/SAVED_REPLIES/technical/security.md index aee03fa88..0c97a5250 100644 --- a/.github/SAVED_REPLIES/technical/security.md +++ b/.github/SAVED_REPLIES/technical/security.md @@ -16,7 +16,7 @@ labels: ```markdown Hi @username, -Thank you for your security report or concern. +Thank you for your security report or concern. For the protection of all users, **please do not disclose security vulnerabilities publicly**. Email us at [security@lightspeedwp.com](mailto:security@lightspeedwp.com) or use our [security disclosure form](https://github.com/lightspeedwp/.github/security/policy). diff --git a/.github/SAVED_REPLIES/workflow/draft-pr.md b/.github/SAVED_REPLIES/workflow/draft-pr.md index c6c13b044..ef39f90b1 100644 --- a/.github/SAVED_REPLIES/workflow/draft-pr.md +++ b/.github/SAVED_REPLIES/workflow/draft-pr.md @@ -16,7 +16,7 @@ labels: ```markdown Hi @username, -Thank you for opening a draft PR! +Thank you for opening a draft PR! Drafts are great for early feedback. Please keep your description and checklist updated as you work. When ready for full review, mark the PR as “Ready for review” and ensure all CI checks pass. diff --git a/.github/instructions/.archive/saved-replies.instructions.md b/.github/instructions/.archive/saved-replies.instructions.md index 7de653091..f0c0bd2eb 100644 --- a/.github/instructions/.archive/saved-replies.instructions.md +++ b/.github/instructions/.archive/saved-replies.instructions.md @@ -12,7 +12,7 @@ file_type: "instructions" # Saved Replies Usage Instructions -Saved replies are reusable, pre-written responses for common GitHub interactions. +Saved replies are reusable, pre-written responses for common GitHub interactions. LightSpeedWP maintains a comprehensive library of saved replies for issues, pull requests, triage, and review, kept in the `.github/SAVED_REPLIES/` directory. --- @@ -76,7 +76,7 @@ LightSpeedWP maintains a comprehensive library of saved replies for issues, pull ```markdown Hi @username, -This PR is missing one or more required labels for automation and release. +This PR is missing one or more required labels for automation and release. See our [PR Label Reference](../../PR_LABELS.md) for label meanings. ``` diff --git a/.github/metrics/out/frontmatter-metrics.md b/.github/metrics/out/frontmatter-metrics.md index c5a3d6cba..51a8e9eec 100644 --- a/.github/metrics/out/frontmatter-metrics.md +++ b/.github/metrics/out/frontmatter-metrics.md @@ -1,8 +1,8 @@ # Weekly Frontmatter Metrics -**Coverage:** 94% (141/150) -**Unknown keys:** 0 -**Broken references:** 2 +**Coverage:** 94% (141/150) +**Unknown keys:** 0 +**Broken references:** 2 **Version skews:** 1 ## Broken references diff --git a/.github/projects/PLANNING_TEMPLATE.md b/.github/projects/PLANNING_TEMPLATE.md index fa6e11e76..a7bd918ec 100644 --- a/.github/projects/PLANNING_TEMPLATE.md +++ b/.github/projects/PLANNING_TEMPLATE.md @@ -13,9 +13,9 @@ tags: ["planning", "template", "process"] # Project Planning: [Project Name] -**Created:** YYYY-MM-DD -**Status:** Planning / In Progress / Completed -**Owner:** @username +**Created:** YYYY-MM-DD +**Status:** Planning / In Progress / Completed +**Owner:** @username **Repository:** lightspeedwp/.github --- @@ -226,6 +226,6 @@ Once this planning document is approved, you're ready to: --- -**Template Version:** 1.0 -**Last Updated:** 2026-05-31 +**Template Version:** 1.0 +**Last Updated:** 2026-05-31 **See also:** [CONTRIBUTING.md](../../../CONTRIBUTING.md), [Issue Triage Guide](../../../docs/issue-triage-guide.md) diff --git a/.github/projects/active/AUDIT_PROMPT_README.md b/.github/projects/active/AUDIT_PROMPT_README.md index f9b08c342..c4afeed29 100644 --- a/.github/projects/active/AUDIT_PROMPT_README.md +++ b/.github/projects/active/AUDIT_PROMPT_README.md @@ -96,11 +96,11 @@ Each parent has 4-5 child issues that: Once all audits are complete, you'll have: -✅ Clear understanding of why issue automation doesn't work -✅ Mapping of templates → automation triggers → labeling rules -✅ Consolidated documentation plan (reduce 40+ files to core essentials) -✅ Audit of 44 README files with accessibility fixes -✅ File organization plan aligned with CLAUDE.md +✅ Clear understanding of why issue automation doesn't work +✅ Mapping of templates → automation triggers → labeling rules +✅ Consolidated documentation plan (reduce 40+ files to core essentials) +✅ Audit of 44 README files with accessibility fixes +✅ File organization plan aligned with CLAUDE.md This clarity will guide the next implementation wave to fix the system. @@ -141,6 +141,6 @@ If while creating issues you realize something needs adjustment: --- -**Status:** ✅ Ready to use -**Last Updated:** 2026-05-31 +**Status:** ✅ Ready to use +**Last Updated:** 2026-05-31 **Maintained by:** LightSpeed Team diff --git a/.github/projects/active/DOCUMENTATION_AUDIT_PROMPT_COMPREHENSIVE.md b/.github/projects/active/DOCUMENTATION_AUDIT_PROMPT_COMPREHENSIVE.md index dc66b16eb..3865c24c6 100644 --- a/.github/projects/active/DOCUMENTATION_AUDIT_PROMPT_COMPREHENSIVE.md +++ b/.github/projects/active/DOCUMENTATION_AUDIT_PROMPT_COMPREHENSIVE.md @@ -70,7 +70,7 @@ Create the following **parent issues** in GitHub. Each parent issue will have mu ```markdown ## Overview -Comprehensive audit of issue templates, their relationship to the automated labeling system, +Comprehensive audit of issue templates, their relationship to the automated labeling system, and how AI agents should create issues to trigger proper automation. ## Current Problems @@ -122,7 +122,7 @@ See child issues for detailed audits of: ```markdown ## Overview -Comprehensive audit of canonical configuration files that define labels, issue types, +Comprehensive audit of canonical configuration files that define labels, issue types, issue fields, and how they relate to each other. ## Current Problems @@ -178,7 +178,7 @@ See child issues for detailed audits of: ```markdown ## Overview -Audit of 40+ documentation files across `docs/` to identify duplication, +Audit of 40+ documentation files across `docs/` to identify duplication, overlap, and opportunities for consolidation. ## Current Problems @@ -231,7 +231,7 @@ See child issues for detailed audits of: ```markdown ## Overview -Comprehensive audit of 44 README.md files across the repository to verify +Comprehensive audit of 44 README.md files across the repository to verify Mermaid diagram syntax, accessibility compliance, and content freshness. ## Current Problems @@ -287,7 +287,7 @@ All README.md files across the repository (see audit report for inventory) ```markdown ## Overview -Audit current file organization against the planned structure defined in CLAUDE.md +Audit current file organization against the planned structure defined in CLAUDE.md and identify misalignments requiring refactoring. ## Current Problems diff --git a/.github/projects/active/ISSUE_35_INSTRUCTION_AUDIT_SUMMARY.md b/.github/projects/active/ISSUE_35_INSTRUCTION_AUDIT_SUMMARY.md index 65ab2f19d..54619a322 100644 --- a/.github/projects/active/ISSUE_35_INSTRUCTION_AUDIT_SUMMARY.md +++ b/.github/projects/active/ISSUE_35_INSTRUCTION_AUDIT_SUMMARY.md @@ -11,7 +11,7 @@ file_type: documentation This document summarizes the audit of instruction files across the LightSpeed `.github` repository (issue #35). The audit identified 36 instruction files, classified them by scope, and documented overlapping guidance and cross-linking opportunities. -**Status:** In Progress +**Status:** In Progress **Branch:** `ai/audit-instruction-files-35` --- @@ -20,7 +20,7 @@ This document summarizes the audit of instruction files across the LightSpeed `. ### File Inventory -**Total instruction files:** 36 +**Total instruction files:** 36 **Location:** `instructions/` (repository root level) ### Scope Classification @@ -79,10 +79,10 @@ These files are specific to this `.github` control-plane repository: ## Completed Work -✅ **Expanded a11y.instructions.md** with comprehensive WCAG 2.2 AA guidance -✅ **Updated CLAUDE.md** with clarity on organization-wide vs repo-local files -✅ **Classified all 36 files** by scope and reusability -✅ **Created index/README** for instructions/ folder +✅ **Expanded a11y.instructions.md** with comprehensive WCAG 2.2 AA guidance +✅ **Updated CLAUDE.md** with clarity on organization-wide vs repo-local files +✅ **Classified all 36 files** by scope and reusability +✅ **Created index/README** for instructions/ folder ✅ **Expanded stub files:** copilot-operations.instructions.md, file-organisation.instructions.md --- @@ -175,5 +175,5 @@ The following changes were made to `CLAUDE.md`: --- -*Audit completed: 2026-05-29* +*Audit completed: 2026-05-29* *Branch: ai/audit-instruction-files-35* diff --git a/.github/projects/active/template-enforcement-governance/ACTIONS.md b/.github/projects/active/template-enforcement-governance/ACTIONS.md index d6f7e8b65..558d863ff 100644 --- a/.github/projects/active/template-enforcement-governance/ACTIONS.md +++ b/.github/projects/active/template-enforcement-governance/ACTIONS.md @@ -11,9 +11,9 @@ maintainer: "LightSpeed Team" # Template Enforcement & Governance — Action Plan -**Project Status:** Backlog Published -**Total Issues:** 13 (all created and ready for assignment) -**Timeline:** 2–3 weeks +**Project Status:** Backlog Published +**Total Issues:** 13 (all created and ready for assignment) +**Timeline:** 2–3 weeks **Effort:** ~11.5 hours --- @@ -22,7 +22,7 @@ maintainer: "LightSpeed Team" ### Step 1: Assign Phase 1 Issues (Critical Path) -**Deadline:** Tomorrow +**Deadline:** Tomorrow **Owner:** Project Lead | Issue | Title | Assigned To | Status | @@ -37,8 +37,8 @@ maintainer: "LightSpeed Team" ### Step 2: Manually Add Issue Types to GitHub Org Settings -**Deadline:** Tomorrow -**Owner:** Organization Admin +**Deadline:** Tomorrow +**Owner:** Organization Admin **Issue:** #709 **Steps:** @@ -55,8 +55,8 @@ maintainer: "LightSpeed Team" ### Step 3: Create Phase 1 Config Files -**Deadline:** End of Week 1 -**Owner:** TBD (2 developers, ~1.5h each) +**Deadline:** End of Week 1 +**Owner:** TBD (2 developers, ~1.5h each) **Issues:** #710, #711 **Deliverables:** diff --git a/.github/projects/active/template-enforcement-governance/ISSUES.md b/.github/projects/active/template-enforcement-governance/ISSUES.md index 5f105f187..cb0b428ab 100644 --- a/.github/projects/active/template-enforcement-governance/ISSUES.md +++ b/.github/projects/active/template-enforcement-governance/ISSUES.md @@ -19,8 +19,8 @@ This project coordinates the implementation of organization-wide template enforc ## Status: In Planning -**Total Issues:** 13 -**Priority:** High +**Total Issues:** 13 +**Priority:** High **Timeline:** 2-3 weeks --- @@ -31,12 +31,12 @@ This project coordinates the implementation of organization-wide template enforc #### 1️⃣ [FOUNDATION] Add 2 missing issue types to GitHub organization settings -**Issue Type:** Task -**Priority:** Critical -**Depends on:** None +**Issue Type:** Task +**Priority:** Critical +**Depends on:** None **Effort:** 30min -**Summary:** +**Summary:** Add "Help" and "User Experience Feedback" issue types to the organization's GitHub settings. **Details:** @@ -60,12 +60,12 @@ Add "Help" and "User Experience Feedback" issue types to the organization's GitH #### 2️⃣ [FOUNDATION] Create PULL_REQUEST_TEMPLATE/config.yml with routing rules -**Issue Type:** Task -**Priority:** High -**Depends on:** #1 +**Issue Type:** Task +**Priority:** High +**Depends on:** #1 **Effort:** 1h -**Summary:** +**Summary:** Create configuration file documenting PR template routing rules (which template to use for each branch type). **Details:** @@ -107,12 +107,12 @@ research/ → pr_research.md (if exists) or pr_feature.md #### 3️⃣ [FOUNDATION] Update ISSUE_TEMPLATE/config.yml with enhanced metadata -**Issue Type:** Task -**Priority:** High -**Depends on:** #1 +**Issue Type:** Task +**Priority:** High +**Depends on:** #1 **Effort:** 30min -**Summary:** +**Summary:** Enhance ISSUE_TEMPLATE/config.yml to include metadata about template routing and automation. **Details:** @@ -135,12 +135,12 @@ Enhance ISSUE_TEMPLATE/config.yml to include metadata about template routing and #### 4️⃣ [DOCS] Create PR template router at /pull_request_template.md -**Issue Type:** Task -**Priority:** High -**Depends on:** #2 +**Issue Type:** Task +**Priority:** High +**Depends on:** #2 **Effort:** 1h -**Summary:** +**Summary:** Replace generic `pull_request_template.md` with smart routing guide that directs users to correct template based on branch type. **Details:** @@ -170,12 +170,12 @@ Replace generic `pull_request_template.md` with smart routing guide that directs #### 5️⃣ [DOCS] Create instructions/pr-templates.instructions.md -**Issue Type:** Task -**Priority:** High -**Depends on:** #2, #4 +**Issue Type:** Task +**Priority:** High +**Depends on:** #2, #4 **Effort:** 1.5h -**Summary:** +**Summary:** Create portable, detailed instruction file for PR template usage across all repositories. **Details:** @@ -210,12 +210,12 @@ Create portable, detailed instruction file for PR template usage across all repo #### 6️⃣ [DOCS] Create instructions/issue-templates.instructions.md -**Issue Type:** Task -**Priority:** High -**Depends on:** #1 +**Issue Type:** Task +**Priority:** High +**Depends on:** #1 **Effort:** 1.5h -**Summary:** +**Summary:** Create portable instruction file for issue template usage across all repositories. **Details:** @@ -249,12 +249,12 @@ Create portable instruction file for issue template usage across all repositorie #### 7️⃣ [DOCS] Update AGENT.md with canonical template rules -**Issue Type:** Task -**Priority:** High -**Depends on:** #2, #4, #5, #6 +**Issue Type:** Task +**Priority:** High +**Depends on:** #2, #4, #5, #6 **Effort:** 2h -**Summary:** +**Summary:** Add comprehensive "Template & Issue Type Governance" section to AGENT.md as single source of truth. **Details:** @@ -287,12 +287,12 @@ Add comprehensive "Template & Issue Type Governance" section to AGENT.md as sing #### 8️⃣ [DOCS] Update CLAUDE.md with template routing guide -**Issue Type:** Task -**Priority:** High -**Depends on:** #7 +**Issue Type:** Task +**Priority:** High +**Depends on:** #7 **Effort:** 1h -**Summary:** +**Summary:** Add "PR & Issue Template Selection" section to CLAUDE.md with quick reference for Claude agents. **Details:** @@ -324,12 +324,12 @@ Add "PR & Issue Template Selection" section to CLAUDE.md with quick reference fo #### 9️⃣ [WORKFLOW] Create PR template validation workflow -**Issue Type:** Task -**Priority:** High -**Depends on:** #2, #4 +**Issue Type:** Task +**Priority:** High +**Depends on:** #2, #4 **Effort:** 2h -**Summary:** +**Summary:** Create GitHub Actions workflow that validates PR template compliance. **Details:** @@ -370,12 +370,12 @@ Create GitHub Actions workflow that validates PR template compliance. #### 🔟 [AGENT] Create PR template enforcement agent -**Issue Type:** Task -**Priority:** Medium -**Depends on:** #9 +**Issue Type:** Task +**Priority:** Medium +**Depends on:** #9 **Effort:** 2h -**Summary:** +**Summary:** Create `.github/agents/pr-template-enforcement.md` agent specification for intelligent template validation. **Details:** @@ -419,12 +419,12 @@ Create `.github/agents/pr-template-enforcement.md` agent specification for intel #### 1️⃣1️⃣ [INTEGRATION] Integrate template validation into GitHub branch protection -**Issue Type:** Task -**Priority:** Medium -**Depends on:** #9 +**Issue Type:** Task +**Priority:** Medium +**Depends on:** #9 **Effort:** 1h -**Summary:** +**Summary:** Configure GitHub branch protection to require PR template validation status check. **Details:** @@ -445,12 +445,12 @@ Configure GitHub branch protection to require PR template validation status chec #### 1️⃣2️⃣ [TESTING] Create test fixtures for PR template validation -**Issue Type:** Task -**Priority:** Medium -**Depends on:** #9, #10 +**Issue Type:** Task +**Priority:** Medium +**Depends on:** #9, #10 **Effort:** 1h -**Summary:** +**Summary:** Create test fixtures and examples for PR template validation workflow and agent. **Details:** @@ -480,12 +480,12 @@ Create test fixtures and examples for PR template validation workflow and agent. #### 1️⃣3️⃣ [DOCS] Update BRANCHING_STRATEGY.md with template mappings -**Issue Type:** Task -**Priority:** Medium -**Depends on:** #2, #7 +**Issue Type:** Task +**Priority:** Medium +**Depends on:** #2, #7 **Effort:** 1h -**Summary:** +**Summary:** Update BRANCHING_STRATEGY.md with PR template mapping table and governance notes. **Details:** diff --git a/.github/projects/active/wave-5-documentation-audit/INDEX.md b/.github/projects/active/wave-5-documentation-audit/INDEX.md index e496485bf..fafa12b0f 100644 --- a/.github/projects/active/wave-5-documentation-audit/INDEX.md +++ b/.github/projects/active/wave-5-documentation-audit/INDEX.md @@ -187,6 +187,6 @@ Before creating issues in GitHub, verify: --- -**Last Updated:** 2026-05-31 -**Created By:** Claude Code +**Last Updated:** 2026-05-31 +**Created By:** Claude Code **For:** LightSpeed Team diff --git a/.github/projects/active/wave-5-documentation-audit/children/01-2-audit-report-issue-creation.md b/.github/projects/active/wave-5-documentation-audit/children/01-2-audit-report-issue-creation.md index 618ac6a42..9091fb993 100644 --- a/.github/projects/active/wave-5-documentation-audit/children/01-2-audit-report-issue-creation.md +++ b/.github/projects/active/wave-5-documentation-audit/children/01-2-audit-report-issue-creation.md @@ -15,10 +15,10 @@ domain: "governance" # Issue Creation Documentation Audit Report -**Parent Issue:** #651 (Documentation Consolidation) -**Child Issue:** #662 (Issue Creation Docs Consolidation) -**Audited:** 2026-05-31 -**Auditor:** Claude Code +**Parent Issue:** #651 (Documentation Consolidation) +**Child Issue:** #662 (Issue Creation Docs Consolidation) +**Audited:** 2026-05-31 +**Auditor:** Claude Code --- @@ -52,10 +52,10 @@ Audited 6 documentation files related to issue creation. Found: ### 1. **`docs/ISSUE_CREATION_GUIDE.md`** -**Type:** Practical how-to guide -**Length:** ~165 lines -**Audience:** All contributors -**Quality:** Well-structured, clear formatting +**Type:** Practical how-to guide +**Length:** ~165 lines +**Audience:** All contributors +**Quality:** Well-structured, clear formatting **Scope Covered:** @@ -99,10 +99,10 @@ Instead of creating a new file, update all broken references to `ISSUE_LABELS.md ### 3. **`docs/ISSUE_TYPES.md`** -**Type:** Reference guide -**Length:** ~179 lines -**Audience:** Contributors, maintainers, automation engineers -**Quality:** Comprehensive, well-maintained (last updated 2026-05-29) +**Type:** Reference guide +**Length:** ~179 lines +**Audience:** Contributors, maintainers, automation engineers +**Quality:** Comprehensive, well-maintained (last updated 2026-05-29) **Scope Covered:** @@ -125,10 +125,10 @@ Instead of creating a new file, update all broken references to `ISSUE_LABELS.md ### 4. **`.github/ISSUE_TEMPLATE/README.md`** -**Type:** Directory overview -**Length:** ~116 lines -**Audience:** Contributors using templates -**Quality:** Clear, includes workflow diagram, good use of badges +**Type:** Directory overview +**Length:** ~116 lines +**Audience:** Contributors using templates +**Quality:** Clear, includes workflow diagram, good use of badges **Scope Covered:** @@ -151,10 +151,10 @@ Instead of creating a new file, update all broken references to `ISSUE_LABELS.md ### 5. **`instructions/issues.instructions.md`** -**Type:** Official instructions (for AI agents/maintainers) -**Length:** ~247 lines -**Audience:** AI agents, maintainers, automation engineers -**Quality:** Authoritative but with duplication issues +**Type:** Official instructions (for AI agents/maintainers) +**Length:** ~247 lines +**Audience:** AI agents, maintainers, automation engineers +**Quality:** Authoritative but with duplication issues **Critical Issues Found:** @@ -191,9 +191,9 @@ Instead of creating a new file, update all broken references to `ISSUE_LABELS.md ### 6. **`docs/index.md`** -**Type:** Placeholder -**Length:** ~10 lines -**Status:** Empty/incomplete +**Type:** Placeholder +**Length:** ~10 lines +**Status:** Empty/incomplete **Issues:** No actual index; just a redirect note --- @@ -374,6 +374,6 @@ Instead of creating a new file, update all broken references to `ISSUE_LABELS.md --- -**Audit Completed:** 2026-05-31 -**Auditor:** Claude Code +**Audit Completed:** 2026-05-31 +**Auditor:** Claude Code **Status:** Ready for implementation diff --git a/.github/projects/active/wave-5-documentation-audit/children/03-2-pr-creation-docs.md b/.github/projects/active/wave-5-documentation-audit/children/03-2-pr-creation-docs.md index 5fcf2dac6..4b5ecc52e 100644 --- a/.github/projects/active/wave-5-documentation-audit/children/03-2-pr-creation-docs.md +++ b/.github/projects/active/wave-5-documentation-audit/children/03-2-pr-creation-docs.md @@ -15,10 +15,10 @@ domain: "governance" # PR Creation Documentation Audit Report -**Parent Issue:** #651 (Documentation Consolidation) -**Child Issue:** #663 (PR Creation Docs Consolidation) -**Audited:** 2026-05-31 -**Auditor:** Claude Code +**Parent Issue:** #651 (Documentation Consolidation) +**Child Issue:** #663 (PR Creation Docs Consolidation) +**Audited:** 2026-05-31 +**Auditor:** Claude Code --- @@ -52,10 +52,10 @@ Audited 5 documentation files related to PR creation. Found: ### 1. **`docs/PR_CREATION_PROCESS.md`** -**Type:** Practical how-to guide -**Length:** ~171 lines -**Audience:** All contributors -**Quality:** Well-structured, clear formatting +**Type:** Practical how-to guide +**Length:** ~171 lines +**Audience:** All contributors +**Quality:** Well-structured, clear formatting **Scope Covered:** @@ -106,10 +106,10 @@ Instead of creating a new `PR_LABELS.md`, investigate whether PR labels should b ### 3. **`.github/PULL_REQUEST_TEMPLATE/README.md`** -**Type:** Directory overview -**Length:** ~91 lines (with duplicate footer) -**Audience:** Contributors using templates -**Quality:** Clear structure with badges; footer duplication issue +**Type:** Directory overview +**Length:** ~91 lines (with duplicate footer) +**Audience:** Contributors using templates +**Quality:** Clear structure with badges; footer duplication issue **Scope Covered:** @@ -132,10 +132,10 @@ Instead of creating a new `PR_LABELS.md`, investigate whether PR labels should b ### 4. **`instructions/pull-requests.instructions.md`** -**Type:** Official instructions (for AI agents/maintainers) -**Length:** ~240 lines -**Audience:** AI agents, maintainers, automation engineers -**Quality:** Authoritative, comprehensive, no duplication +**Type:** Official instructions (for AI agents/maintainers) +**Length:** ~240 lines +**Audience:** AI agents, maintainers, automation engineers +**Quality:** Authoritative, comprehensive, no duplication **Critical Strengths:** @@ -169,10 +169,10 @@ Instead of creating a new `PR_LABELS.md`, investigate whether PR labels should b ### 5. **`docs/BRANCHING_STRATEGY.md`** -**Type:** Comprehensive strategy document -**Length:** ~320 lines -**Audience:** All contributors, especially those managing branches and automation -**Quality:** Highly detailed, well-maintained, extensive coverage +**Type:** Comprehensive strategy document +**Length:** ~320 lines +**Audience:** All contributors, especially those managing branches and automation +**Quality:** Highly detailed, well-maintained, extensive coverage **Scope Covered:** @@ -390,6 +390,6 @@ Instead of creating a new `PR_LABELS.md`, investigate whether PR labels should b --- -**Audit Completed:** 2026-05-31 -**Auditor:** Claude Code +**Audit Completed:** 2026-05-31 +**Auditor:** Claude Code **Status:** Ready for implementation diff --git a/.github/projects/active/wave-5-documentation-audit/children/03-3-labeling-docs.md b/.github/projects/active/wave-5-documentation-audit/children/03-3-labeling-docs.md index 2b36ae76e..df89492f2 100644 --- a/.github/projects/active/wave-5-documentation-audit/children/03-3-labeling-docs.md +++ b/.github/projects/active/wave-5-documentation-audit/children/03-3-labeling-docs.md @@ -15,10 +15,10 @@ domain: "governance" # Labeling Documentation Audit Report -**Parent Issue:** #651 (Documentation Consolidation) -**Child Issue:** #664 (Labeling Docs Consolidation) -**Audited:** 2026-05-31 -**Auditor:** Claude Code +**Parent Issue:** #651 (Documentation Consolidation) +**Child Issue:** #664 (Labeling Docs Consolidation) +**Audited:** 2026-05-31 +**Auditor:** Claude Code --- @@ -60,10 +60,10 @@ Audited 4 labeling-related documentation files. Found: ### 1. **`docs/LABELING.md`** -**Type:** Comprehensive reference guide -**Length:** ~363 lines -**Audience:** All contributors, especially those triaging or applying labels -**Quality:** Well-structured, authoritative, up-to-date (2026-05-31) +**Type:** Comprehensive reference guide +**Length:** ~363 lines +**Audience:** All contributors, especially those triaging or applying labels +**Quality:** Well-structured, authoritative, up-to-date (2026-05-31) **Scope Covered:** @@ -95,10 +95,10 @@ Audited 4 labeling-related documentation files. Found: ### 2. **`docs/AUTOMATION.md`** -**Type:** Automation governance & workflow strategy -**Length:** ~254 lines -**Audience:** Platform/governance team, workflow maintainers -**Quality:** Clear, authoritative, well-maintained +**Type:** Automation governance & workflow strategy +**Length:** ~254 lines +**Audience:** Platform/governance team, workflow maintainers +**Quality:** Clear, authoritative, well-maintained **Scope Covered:** @@ -131,10 +131,10 @@ Audited 4 labeling-related documentation files. Found: ### 3. **`instructions/labeling.instructions.md`** -**Type:** Portable instructions (for agents & maintainers) -**Length:** ~87 lines -**Audience:** AI agents, maintainers, automation engineers -**Quality:** Condensed but clear; last updated 2026-05-29 +**Type:** Portable instructions (for agents & maintainers) +**Length:** ~87 lines +**Audience:** AI agents, maintainers, automation engineers +**Quality:** Condensed but clear; last updated 2026-05-29 **Scope Covered:** @@ -162,10 +162,10 @@ Audited 4 labeling-related documentation files. Found: ### 4. **`agents/labeling.agent.md`** -**Type:** Technical agent specification -**Length:** ~238 lines -**Audience:** Developers, automation engineers, maintainers -**Quality:** Detailed, well-documented, technical +**Type:** Technical agent specification +**Length:** ~238 lines +**Audience:** Developers, automation engineers, maintainers +**Quality:** Detailed, well-documented, technical **Scope Covered:** @@ -418,6 +418,6 @@ docs/ --- -**Audit Completed:** 2026-05-31 -**Auditor:** Claude Code +**Audit Completed:** 2026-05-31 +**Auditor:** Claude Code **Status:** Ready for implementation diff --git a/.github/projects/active/wave-5-documentation-audit/children/03-4-file-organization-alignment.md b/.github/projects/active/wave-5-documentation-audit/children/03-4-file-organization-alignment.md index 943ec5173..ad57ec118 100644 --- a/.github/projects/active/wave-5-documentation-audit/children/03-4-file-organization-alignment.md +++ b/.github/projects/active/wave-5-documentation-audit/children/03-4-file-organization-alignment.md @@ -15,10 +15,10 @@ domain: "governance" # File Organization Alignment Audit Report -**Parent Issue:** #651 (Documentation Consolidation) -**Child Issue:** #665 (File Organization Alignment) -**Audited:** 2026-05-31 -**Auditor:** Claude Code +**Parent Issue:** #651 (Documentation Consolidation) +**Child Issue:** #665 (File Organization Alignment) +**Audited:** 2026-05-31 +**Auditor:** Claude Code --- @@ -248,9 +248,9 @@ All required portable asset folders exist and are correctly placed at top level: ### Issue 1: Duplicate Instruction File (`.github/instructions/`) -**File:** `.github/instructions/file-organisation.instructions.md` -**Current state:** Duplicate of `instructions/file-organisation.instructions.md` -**Problem:** Two sources of truth violate CLAUDE.md principle of single source of truth +**File:** `.github/instructions/file-organisation.instructions.md` +**Current state:** Duplicate of `instructions/file-organisation.instructions.md` +**Problem:** Two sources of truth violate CLAUDE.md principle of single source of truth **Solution:** Remove `.github/instructions/` copy; use top-level version. If repo-local override needed, document difference. **Priority:** Medium @@ -259,7 +259,7 @@ All required portable asset folders exist and are correctly placed at top level: ### Issue 2: Archived Instructions Not Documented -**Files:** `.github/instructions/.archive/` (18 deprecated files) +**Files:** `.github/instructions/.archive/` (18 deprecated files) **Problem:** - Not listed in `instructions/DEPRECATED.md` @@ -274,9 +274,9 @@ All required portable asset folders exist and are correctly placed at top level: ### Issue 3: Undocumented `ai/` Folder -**Current state:** CLAUDE.md references `ai/Claude.md`, `ai/Gemini.md`, `ai/RUNNERS.md` but doesn't document folder purpose -**Problem:** New contributors may not know what `ai/` folder is for -**Solution:** Add to CLAUDE.md's "Portable AI Operations Assets" section or document separately +**Current state:** CLAUDE.md references `ai/Claude.md`, `ai/Gemini.md`, `ai/RUNNERS.md` but doesn't document folder purpose +**Problem:** New contributors may not know what `ai/` folder is for +**Solution:** Add to CLAUDE.md's "Portable AI Operations Assets" section or document separately **Purpose:** Likely "Canonical AI agent references and rules" **Priority:** Low (already referenced, just needs documentation) @@ -285,14 +285,14 @@ All required portable asset folders exist and are correctly placed at top level: ### Issue 4: Root-Level Documentation Files -**Files:** BRANDING_AGENT_USAGE.md, BRANDING_CONFIG_SPEC.md, DEVELOPMENT.md, GOVERNANCE.md, SUPPORT.md, MIGRATION_GUIDE.md +**Files:** BRANDING_AGENT_USAGE.md, BRANDING_CONFIG_SPEC.md, DEVELOPMENT.md, GOVERNANCE.md, SUPPORT.md, MIGRATION_GUIDE.md **Problem:** - Makes root directory cluttered - Some duplicate existing `docs/` files (e.g., MIGRATION_GUIDE.md vs. docs/MIGRATION.md) - Not aligned with "permanent human documentation → docs/" guideline -**Solution:** Consolidate with `docs/` directory (move or merge) +**Solution:** Consolidate with `docs/` directory (move or merge) **Decision required:** Which files to keep at root for visibility vs. move to docs/ **Priority:** Low (organizational improvement, not compliance issue) @@ -387,7 +387,7 @@ All required portable asset folders exist and are correctly placed at top level: --- -**Audit Completed:** 2026-05-31 -**Auditor:** Claude Code -**Status:** Ready for implementation +**Audit Completed:** 2026-05-31 +**Auditor:** Claude Code +**Status:** Ready for implementation **Compliance Level:** 97% (largely correct with minor improvements) diff --git a/.github/projects/active/wave-5-documentation-audit/execution/wave-5-3-phase-2-execution-plan.md b/.github/projects/active/wave-5-documentation-audit/execution/wave-5-3-phase-2-execution-plan.md index 4556513df..49b41e145 100644 --- a/.github/projects/active/wave-5-documentation-audit/execution/wave-5-3-phase-2-execution-plan.md +++ b/.github/projects/active/wave-5-documentation-audit/execution/wave-5-3-phase-2-execution-plan.md @@ -15,10 +15,10 @@ domain: "governance" # Wave 5.3 Phase 2 Execution Plan -**Parent Issue:** #651 (Documentation Consolidation) -**Audit Phase Completed:** 2026-05-31 -**Execution Phase Started:** 2026-05-31 -**Executor:** Claude Code +**Parent Issue:** #651 (Documentation Consolidation) +**Audit Phase Completed:** 2026-05-31 +**Execution Phase Started:** 2026-05-31 +**Executor:** Claude Code --- @@ -231,6 +231,6 @@ These are larger reorganization efforts recommended for Phase 2 but deferred to --- -**Status:** Ready to execute -**Estimated Duration:** 3-4 hours total +**Status:** Ready to execute +**Estimated Duration:** 3-4 hours total **Next Phase:** Wave 5.4 (README discovery and updates) diff --git a/.github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md b/.github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md index f3a75f225..4295a73ce 100644 --- a/.github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md +++ b/.github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md @@ -105,6 +105,6 @@ Address the duplicate `07` prefix: --- -**Audit Date:** 2026-05-31 -**Audit Status:** ✅ Complete +**Audit Date:** 2026-05-31 +**Audit Status:** ✅ Complete **Full Details:** [GitHub Issue #654](https://github.com/lightspeedwp/.github/issues/654#issuecomment-4587414901) diff --git a/.github/projects/active/wceu-2026/PARENT_ISSUE.md b/.github/projects/active/wceu-2026/PARENT_ISSUE.md index d22290aee..f917f0bb1 100644 --- a/.github/projects/active/wceu-2026/PARENT_ISSUE.md +++ b/.github/projects/active/wceu-2026/PARENT_ISSUE.md @@ -7,13 +7,13 @@ file_type: documentation # WCEU 2026 Talk Preparation — Parent Issue -**Title**: WCEU 2026 Talk Preparation — Finalize 25-Minute Presentation -**Type**: Epic/Parent Issue -**Priority**: Critical -**Status**: Active -**Due Date**: May 31, 2026 (48 hours) -**Talk Date**: June 5–6, 2026 -**Assignee**: Ash Shaw +**Title**: WCEU 2026 Talk Preparation — Finalize 25-Minute Presentation +**Type**: Epic/Parent Issue +**Priority**: Critical +**Status**: Active +**Due Date**: May 31, 2026 (48 hours) +**Talk Date**: June 5–6, 2026 +**Assignee**: Ash Shaw **Labels**: `wceu-2026`, `talk-preparation`, `critical-path` --- @@ -205,11 +205,11 @@ Jun 5–6: WCEU presentation By **May 31, 2026 EOD**: -✅ **Deliverable**: Google Slides deck with 24 slides (dark mode, speaker notes) -✅ **Quality**: All slides follow WCAG AA/AAA contrast, use consistent design -✅ **Completeness**: All speaker notes, timing, talking points included -✅ **Readiness**: Deck ready for rehearsal (June 1–4) -✅ **Documentation**: Planning, roadmap, glossary, and issues all complete +✅ **Deliverable**: Google Slides deck with 24 slides (dark mode, speaker notes) +✅ **Quality**: All slides follow WCAG AA/AAA contrast, use consistent design +✅ **Completeness**: All speaker notes, timing, talking points included +✅ **Readiness**: Deck ready for rehearsal (June 1–4) +✅ **Documentation**: Planning, roadmap, glossary, and issues all complete --- @@ -287,7 +287,7 @@ By **May 31, 2026 EOD**: --- -**Created**: 2026-05-29 -**Updated**: 2026-05-29 -**Sprint**: WCEU 2026 Critical Path +**Created**: 2026-05-29 +**Updated**: 2026-05-29 +**Sprint**: WCEU 2026 Critical Path **Epic**: WordCamp Europe 2026 Talk diff --git a/.github/projects/active/wceu-2026/WCEU-01-notebooklm-sources-index.md b/.github/projects/active/wceu-2026/WCEU-01-notebooklm-sources-index.md index b79437544..add9fbf6f 100644 --- a/.github/projects/active/wceu-2026/WCEU-01-notebooklm-sources-index.md +++ b/.github/projects/active/wceu-2026/WCEU-01-notebooklm-sources-index.md @@ -7,11 +7,11 @@ file_type: documentation # [WCEU-01] Create NotebookLM sources index -**Title**: Create NotebookLM sources index (`notebooklm/sources-index.md`) -**Priority**: Critical (NOW — next 6 hours) -**Status**: TODO -**Due**: May 29, 2026 (today, ASAP) -**Assignee**: Claude +**Title**: Create NotebookLM sources index (`notebooklm/sources-index.md`) +**Priority**: Critical (NOW — next 6 hours) +**Status**: TODO +**Due**: May 29, 2026 (today, ASAP) +**Assignee**: Claude **Parent**: WCEU 2026 Talk Preparation --- @@ -146,6 +146,6 @@ Once complete, this file will be used in [WCEU-03]: --- -**Status**: TODO -**Effort**: 2 hours +**Status**: TODO +**Effort**: 2 hours **Created**: 2026-05-29 diff --git a/.github/projects/active/wceu-2026/WCEU-02-commit-profile-photo.md b/.github/projects/active/wceu-2026/WCEU-02-commit-profile-photo.md index 2cf91c2ba..9e4361b0e 100644 --- a/.github/projects/active/wceu-2026/WCEU-02-commit-profile-photo.md +++ b/.github/projects/active/wceu-2026/WCEU-02-commit-profile-photo.md @@ -7,11 +7,11 @@ file_type: documentation # [WCEU-02] Commit profile photo to assets -**Title**: Commit profile photo to `wceu-2026/assets/ash-shaw-profile.jpg` -**Priority**: Critical (NOW — next 6 hours) -**Status**: TODO -**Due**: May 29, 2026 (today, ASAP) -**Assignee**: Claude +**Title**: Commit profile photo to `wceu-2026/assets/ash-shaw-profile.jpg` +**Priority**: Critical (NOW — next 6 hours) +**Status**: TODO +**Due**: May 29, 2026 (today, ASAP) +**Assignee**: Claude **Parent**: WCEU 2026 Talk Preparation --- @@ -81,6 +81,6 @@ Related: WCEU 2026 Talk Preparation (#parent-issue) --- -**Status**: TODO -**Effort**: 15 minutes +**Status**: TODO +**Effort**: 15 minutes **Created**: 2026-05-29 diff --git a/.github/projects/archived/portable-ai-plugin-restructure/portable-ai-plugin-restructure-baseline-command-output-2026-05-15.txt b/.github/projects/archived/portable-ai-plugin-restructure/portable-ai-plugin-restructure-baseline-command-output-2026-05-15.txt index 49119356d..9c5360d51 100644 --- a/.github/projects/archived/portable-ai-plugin-restructure/portable-ai-plugin-restructure-baseline-command-output-2026-05-15.txt +++ b/.github/projects/archived/portable-ai-plugin-restructure/portable-ai-plugin-restructure-baseline-command-output-2026-05-15.txt @@ -398,8 +398,8 @@ PASS scripts/agents/includes/__tests__/badgeUtils.test.js ✓ generateWorkflowBadges returns badge markdown (4 ms) ✓ updateReadmeBadges inserts badge block (3 ms) -Warning: Using local schema due to fetch error: -Warning: Using local schema due to fetch error: +Warning: Using local schema due to fetch error: +Warning: Using local schema due to fetch error: Error: Missing required top-level field: reviews PASS scripts/validation/__tests__/validate-coderabbit-yml.test.js Coderabbit YML Validation @@ -581,9 +581,9 @@ PASS scripts/agents/__tests__/adr.agent.test.js ✓ should be defined (4 ms) ----------|---------|----------|---------|---------|------------------- -File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s +File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s ----------|---------|----------|---------|---------|------------------- -All files | 0 | 0 | 0 | 0 | +All files | 0 | 0 | 0 | 0 | ----------|---------|----------|---------|---------|------------------- Test Suites: 41 passed, 41 total Tests: 181 passed, 181 total diff --git a/.github/projects/completed/ISSUE_33_BRANDING_AGENT_PARENT_SPEC.md b/.github/projects/completed/ISSUE_33_BRANDING_AGENT_PARENT_SPEC.md index 8179fdd5c..6d8a019aa 100644 --- a/.github/projects/completed/ISSUE_33_BRANDING_AGENT_PARENT_SPEC.md +++ b/.github/projects/completed/ISSUE_33_BRANDING_AGENT_PARENT_SPEC.md @@ -11,11 +11,11 @@ tags: ["branding", "governance", "automation", "specification"] # Unified Branding Agent — Parent Specification -**Issue**: #33 -**Related Issues**: #46 (template design), #49 (schema/config), #48 (agent implementation) -**Status**: Specification Phase -**Effort**: 12–16 hours (planning complete) -**Timeline**: Week 1–2 implementation +**Issue**: #33 +**Related Issues**: #46 (template design), #49 (schema/config), #48 (agent implementation) +**Status**: Specification Phase +**Effort**: 12–16 hours (planning complete) +**Timeline**: Week 1–2 implementation --- @@ -70,209 +70,209 @@ The branding agent supports **16 document categories**, each with distinct purpo #### Category: `issue-template` -**Purpose**: GitHub issue template files -**Audience**: Repository contributors opening issues -**File Patterns**: `.github/ISSUE_TEMPLATE/*.md` -**Frontmatter Required**: `title`, `description`, `file_type: "issue-template"` -**Header Behavior**: Optional (most templates omit headers) -**Footer Behavior**: Minimal or omitted; if present, link to contributing guide -**Badge Conventions**: `[issue-template]` label only -**Fallback Rules**: No footer if frontmatter missing; use default category badge +**Purpose**: GitHub issue template files +**Audience**: Repository contributors opening issues +**File Patterns**: `.github/ISSUE_TEMPLATE/*.md` +**Frontmatter Required**: `title`, `description`, `file_type: "issue-template"` +**Header Behavior**: Optional (most templates omit headers) +**Footer Behavior**: Minimal or omitted; if present, link to contributing guide +**Badge Conventions**: `[issue-template]` label only +**Fallback Rules**: No footer if frontmatter missing; use default category badge --- #### Category: `pull-request-template` -**Purpose**: GitHub pull request template files -**Audience**: Repository contributors opening pull requests -**File Patterns**: `.github/PULL_REQUEST_TEMPLATE/*.md` -**Frontmatter Required**: `title`, `description`, `file_type: "pr-template"` -**Header Behavior**: Optional -**Footer Behavior**: Link to CI/CD status, review guide, or merge criteria -**Badge Conventions**: `[pull-request]` label; automation status badges if applicable -**Fallback Rules**: Use default footer if frontmatter missing +**Purpose**: GitHub pull request template files +**Audience**: Repository contributors opening pull requests +**File Patterns**: `.github/PULL_REQUEST_TEMPLATE/*.md` +**Frontmatter Required**: `title`, `description`, `file_type: "pr-template"` +**Header Behavior**: Optional +**Footer Behavior**: Link to CI/CD status, review guide, or merge criteria +**Badge Conventions**: `[pull-request]` label; automation status badges if applicable +**Fallback Rules**: Use default footer if frontmatter missing --- #### Category: `docs` -**Purpose**: Repository documentation and guides -**Audience**: End users, maintainers, integrators -**File Patterns**: `docs/**/*.md` -**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `owners: [...]` -**Header Behavior**: Required; includes category badge, version, status -**Footer Behavior**: Attribution footer with maintainer info, last-updated date, link to GitHub edit -**Badge Conventions**: `[docs]`, `[status]`, `[version]`, `[owners]` -**Fallback Rules**: Use README-style defaults if category not specified; infer from filename +**Purpose**: Repository documentation and guides +**Audience**: End users, maintainers, integrators +**File Patterns**: `docs/**/*.md` +**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `owners: [...]` +**Header Behavior**: Required; includes category badge, version, status +**Footer Behavior**: Attribution footer with maintainer info, last-updated date, link to GitHub edit +**Badge Conventions**: `[docs]`, `[status]`, `[version]`, `[owners]` +**Fallback Rules**: Use README-style defaults if category not specified; infer from filename --- #### Category: `ai-ops` -**Purpose**: AI operations, automation, and governance documentation -**Audience**: Maintainers, automation engineers, governance stakeholders -**File Patterns**: `docs/**/*governance*.md`, `docs/**/*automation*.md` -**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "ai-ops"` -**Header Behavior**: Required; includes AI Ops badge, governance level, decision status -**Footer Behavior**: Links to related governance docs, approval chain, review status -**Badge Conventions**: `[AI Ops]`, `[governance]`, `[automation]`, `[decision]` -**Fallback Rules**: Infer from path if `category` not in frontmatter +**Purpose**: AI operations, automation, and governance documentation +**Audience**: Maintainers, automation engineers, governance stakeholders +**File Patterns**: `docs/**/*governance*.md`, `docs/**/*automation*.md` +**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "ai-ops"` +**Header Behavior**: Required; includes AI Ops badge, governance level, decision status +**Footer Behavior**: Links to related governance docs, approval chain, review status +**Badge Conventions**: `[AI Ops]`, `[governance]`, `[automation]`, `[decision]` +**Fallback Rules**: Infer from path if `category` not in frontmatter --- #### Category: `agents` -**Purpose**: Agent specifications, behavior definitions, and documentation -**Audience**: Developers integrating agents, framework maintainers -**File Patterns**: `agents/**/*.md`, `agents/**/*.agent.md` -**Frontmatter Required**: `title`, `description`, `file_type: "agent"`, `owners: [...]` -**Header Behavior**: Required; includes agent name, capabilities badge, status -**Footer Behavior**: Signature footer with agent identity, version, last-updated, links to implementation -**Badge Conventions**: `[agent]`, `[capabilities]`, `[status]`, `[version]` -**Fallback Rules**: Default to agent category if not specified +**Purpose**: Agent specifications, behavior definitions, and documentation +**Audience**: Developers integrating agents, framework maintainers +**File Patterns**: `agents/**/*.md`, `agents/**/*.agent.md` +**Frontmatter Required**: `title`, `description`, `file_type: "agent"`, `owners: [...]` +**Header Behavior**: Required; includes agent name, capabilities badge, status +**Footer Behavior**: Signature footer with agent identity, version, last-updated, links to implementation +**Badge Conventions**: `[agent]`, `[capabilities]`, `[status]`, `[version]` +**Fallback Rules**: Default to agent category if not specified --- #### Category: `instructions` -**Purpose**: Coding standards, guidelines, and best practices -**Audience**: Developers, code reviewers, automation systems -**File Patterns**: `instructions/**/*.md`, `*.instructions.md` -**Frontmatter Required**: `title`, `description`, `file_type: "instructions"`, `owners: [...]` -**Header Behavior**: Required; includes compliance level, applicability scope -**Footer Behavior**: Links to enforcement mechanisms, related guidelines, approval status -**Badge Conventions**: `[instructions]`, `[compliance-level]`, `[scope]` -**Fallback Rules**: Use default instructions footer if not specified +**Purpose**: Coding standards, guidelines, and best practices +**Audience**: Developers, code reviewers, automation systems +**File Patterns**: `instructions/**/*.md`, `*.instructions.md` +**Frontmatter Required**: `title`, `description`, `file_type: "instructions"`, `owners: [...]` +**Header Behavior**: Required; includes compliance level, applicability scope +**Footer Behavior**: Links to enforcement mechanisms, related guidelines, approval status +**Badge Conventions**: `[instructions]`, `[compliance-level]`, `[scope]` +**Fallback Rules**: Use default instructions footer if not specified --- #### Category: `prompts` -**Purpose**: Prompt templates for AI tools, ChatMode, and automation -**Audience**: Prompt engineers, AI tool integrators, LLM users -**File Patterns**: `prompts/**/*.md`, `*.prompt.md`, `wceu-2026/**/*.md` -**Frontmatter Required**: `title`, `description`, `file_type: "prompt"`, `owners: [...]` -**Header Behavior**: Optional; may include version and tool compatibility -**Footer Behavior**: Tool compatibility footer, version info, last-updated, prompt engineering notes -**Badge Conventions**: `[prompt]`, `[tools]`, `[version]`, `[ai-model]` -**Fallback Rules**: Generic prompt footer if not specified +**Purpose**: Prompt templates for AI tools, ChatMode, and automation +**Audience**: Prompt engineers, AI tool integrators, LLM users +**File Patterns**: `prompts/**/*.md`, `*.prompt.md`, `wceu-2026/**/*.md` +**Frontmatter Required**: `title`, `description`, `file_type: "prompt"`, `owners: [...]` +**Header Behavior**: Optional; may include version and tool compatibility +**Footer Behavior**: Tool compatibility footer, version info, last-updated, prompt engineering notes +**Badge Conventions**: `[prompt]`, `[tools]`, `[version]`, `[ai-model]` +**Fallback Rules**: Generic prompt footer if not specified --- #### Category: `schema` -**Purpose**: Data schema definitions, validation rules, and format specifications -**Audience**: Developers consuming schema, API users, automation engineers -**File Patterns**: `schema/**/*.md`, `schemas/**/*.md`, `*.schema.md` -**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "schema"` -**Header Behavior**: Required; includes schema version, validation tool, status -**Footer Behavior**: Links to schema implementation, validation results, related schemas -**Badge Conventions**: `[schema]`, `[version]`, `[validation]`, `[status]` -**Fallback Rules**: Default to docs category if not specified +**Purpose**: Data schema definitions, validation rules, and format specifications +**Audience**: Developers consuming schema, API users, automation engineers +**File Patterns**: `schema/**/*.md`, `schemas/**/*.md`, `*.schema.md` +**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "schema"` +**Header Behavior**: Required; includes schema version, validation tool, status +**Footer Behavior**: Links to schema implementation, validation results, related schemas +**Badge Conventions**: `[schema]`, `[version]`, `[validation]`, `[status]` +**Fallback Rules**: Default to docs category if not specified --- #### Category: `readme` -**Purpose**: Repository, project, or module overview documents -**Audience**: New contributors, integrators, project stakeholders -**File Patterns**: `README.md`, `*/README.md`, `plugins/*/README.md` -**Frontmatter Required**: Optional; if present, include `title`, `description`, `file_type: "documentation"` -**Header Behavior**: Usually omitted (file name is self-documenting) -**Footer Behavior**: Standard footer with repository info, contribution guide link, license -**Badge Conventions**: `[repository]`, `[license]`, `[contributors]` -**Fallback Rules**: Use standard repository footer if no frontmatter +**Purpose**: Repository, project, or module overview documents +**Audience**: New contributors, integrators, project stakeholders +**File Patterns**: `README.md`, `*/README.md`, `plugins/*/README.md` +**Frontmatter Required**: Optional; if present, include `title`, `description`, `file_type: "documentation"` +**Header Behavior**: Usually omitted (file name is self-documenting) +**Footer Behavior**: Standard footer with repository info, contribution guide link, license +**Badge Conventions**: `[repository]`, `[license]`, `[contributors]` +**Fallback Rules**: Use standard repository footer if no frontmatter --- #### Category: `test` -**Purpose**: Test documentation, testing guidelines, and test specifications -**Audience**: QA engineers, developers, CI/CD automation -**File Patterns**: `test/**/*.md`, `*test*.md`, `**/*-test.md` -**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "test"` -**Header Behavior**: Optional; may include test coverage status -**Footer Behavior**: Links to test results, CI/CD status, related test docs -**Badge Conventions**: `[test]`, `[coverage]`, `[status]` -**Fallback Rules**: Generic documentation footer +**Purpose**: Test documentation, testing guidelines, and test specifications +**Audience**: QA engineers, developers, CI/CD automation +**File Patterns**: `test/**/*.md`, `*test*.md`, `**/*-test.md` +**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "test"` +**Header Behavior**: Optional; may include test coverage status +**Footer Behavior**: Links to test results, CI/CD status, related test docs +**Badge Conventions**: `[test]`, `[coverage]`, `[status]` +**Fallback Rules**: Generic documentation footer --- #### Category: `utility` -**Purpose**: Utility scripts, helper tools, and automation utilities -**Audience**: Developers, DevOps, automation engineers -**File Patterns**: `scripts/**/*.md`, `utils/**/*.md`, `*.utility.md` -**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "utility"` -**Header Behavior**: Optional; may include usage/requirements -**Footer Behavior**: Links to source code, usage examples, maintenance info -**Badge Conventions**: `[utility]`, `[language]`, `[status]` -**Fallback Rules**: Generic utility footer +**Purpose**: Utility scripts, helper tools, and automation utilities +**Audience**: Developers, DevOps, automation engineers +**File Patterns**: `scripts/**/*.md`, `utils/**/*.md`, `*.utility.md` +**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "utility"` +**Header Behavior**: Optional; may include usage/requirements +**Footer Behavior**: Links to source code, usage examples, maintenance info +**Badge Conventions**: `[utility]`, `[language]`, `[status]` +**Fallback Rules**: Generic utility footer --- #### Category: `awesome-copilot` -**Purpose**: Awesome Copilot resources, extensions, and integrations -**Audience**: Copilot users, extension developers, integration teams -**File Patterns**: `awesome-copilot/**/*.md`, `**/*awesome*.md` -**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "awesome-copilot"` -**Header Behavior**: Required; includes resource type, compatibility badges -**Footer Behavior**: Links to Copilot docs, integration guides, related resources -**Badge Conventions**: `[awesome-copilot]`, `[copilot-version]`, `[type]` -**Fallback Rules**: Generic awesome-copilot footer +**Purpose**: Awesome Copilot resources, extensions, and integrations +**Audience**: Copilot users, extension developers, integration teams +**File Patterns**: `awesome-copilot/**/*.md`, `**/*awesome*.md` +**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "awesome-copilot"` +**Header Behavior**: Required; includes resource type, compatibility badges +**Footer Behavior**: Links to Copilot docs, integration guides, related resources +**Badge Conventions**: `[awesome-copilot]`, `[copilot-version]`, `[type]` +**Fallback Rules**: Generic awesome-copilot footer --- #### Category: `research` -**Purpose**: Research documents, findings, and investigation results -**Audience**: Decision makers, researchers, stakeholders -**File Patterns**: `research/**/*.md`, `*research*.md`, `*.research.md` -**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `owners: [...]` -**Header Behavior**: Required; includes research scope, methodology, date -**Footer Behavior**: Attribution, sources, related research, update status -**Badge Conventions**: `[research]`, `[status]`, `[date]` -**Fallback Rules**: Default research footer +**Purpose**: Research documents, findings, and investigation results +**Audience**: Decision makers, researchers, stakeholders +**File Patterns**: `research/**/*.md`, `*research*.md`, `*.research.md` +**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `owners: [...]` +**Header Behavior**: Required; includes research scope, methodology, date +**Footer Behavior**: Attribution, sources, related research, update status +**Badge Conventions**: `[research]`, `[status]`, `[date]` +**Fallback Rules**: Default research footer --- #### Category: `audit` -**Purpose**: Audit reports, compliance documentation, and assessment results -**Audience**: Compliance officers, auditors, decision makers -**File Patterns**: `audit/**/*.md`, `*audit*.md`, `*.audit.md` -**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `owners: [...]` -**Header Behavior**: Required; includes audit type, scope, date, findings summary -**Footer Behavior**: Audit authority, remediation status, next review date -**Badge Conventions**: `[audit]`, `[compliance]`, `[status]`, `[date]` -**Fallback Rules**: Default audit footer +**Purpose**: Audit reports, compliance documentation, and assessment results +**Audience**: Compliance officers, auditors, decision makers +**File Patterns**: `audit/**/*.md`, `*audit*.md`, `*.audit.md` +**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `owners: [...]` +**Header Behavior**: Required; includes audit type, scope, date, findings summary +**Footer Behavior**: Audit authority, remediation status, next review date +**Badge Conventions**: `[audit]`, `[compliance]`, `[status]`, `[date]` +**Fallback Rules**: Default audit footer --- #### Category: `workflow` -**Purpose**: Workflow definitions, CI/CD documentation, and automation rules -**Audience**: DevOps engineers, CI/CD maintainers, automation engineers -**File Patterns**: `.github/workflows/**/*.md`, `docs/**/*workflow*.md` -**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "workflow"` -**Header Behavior**: Required; includes trigger events, execution context -**Footer Behavior**: Links to workflow implementation, status page, related workflows -**Badge Conventions**: `[workflow]`, `[trigger]`, `[status]` -**Fallback Rules**: Default workflow footer +**Purpose**: Workflow definitions, CI/CD documentation, and automation rules +**Audience**: DevOps engineers, CI/CD maintainers, automation engineers +**File Patterns**: `.github/workflows/**/*.md`, `docs/**/*workflow*.md` +**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "workflow"` +**Header Behavior**: Required; includes trigger events, execution context +**Footer Behavior**: Links to workflow implementation, status page, related workflows +**Badge Conventions**: `[workflow]`, `[trigger]`, `[status]` +**Fallback Rules**: Default workflow footer --- #### Category: `governance` -**Purpose**: Governance policies, decision records, and organizational rules -**Audience**: Maintainers, decision makers, governance stakeholders -**File Patterns**: `docs/**/*governance*.md`, `governance/**/*.md` -**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "governance"`, `owners: [...]` -**Header Behavior**: Required; includes policy scope, decision status, approval chain -**Footer Behavior**: Policy authority, review cycle, effective date, next review date -**Badge Conventions**: `[governance]`, `[decision]`, `[approval]`, `[effective]` -**Fallback Rules**: Default governance footer +**Purpose**: Governance policies, decision records, and organizational rules +**Audience**: Maintainers, decision makers, governance stakeholders +**File Patterns**: `docs/**/*governance*.md`, `governance/**/*.md` +**Frontmatter Required**: `title`, `description`, `file_type: "documentation"`, `category: "governance"`, `owners: [...]` +**Header Behavior**: Required; includes policy scope, decision status, approval chain +**Footer Behavior**: Policy authority, review cycle, effective date, next review date +**Badge Conventions**: `[governance]`, `[decision]`, `[approval]`, `[effective]` +**Fallback Rules**: Default governance footer --- @@ -310,11 +310,11 @@ Headers provide context and metadata at the top of documents. The branding agent # Document Title -**Category**: [`category-badge`] -**Status**: Active | Draft | Deprecated -**Version**: vX.Y.Z -**Owners**: [@owner1, @owner2] -**Last Updated**: YYYY-MM-DD +**Category**: [`category-badge`] +**Status**: Active | Draft | Deprecated +**Version**: vX.Y.Z +**Owners**: [@owner1, @owner2] +**Last Updated**: YYYY-MM-DD --- @@ -346,8 +346,8 @@ Footers provide attribution, maintenance status, and relevant links. ``` --- -**Documentation maintained by the LightSpeed team.** -[Edit this doc](https://github.com/lightspeedwp/.github/edit/develop/docs/FILENAME.md) | +**Documentation maintained by the LightSpeed team.** +[Edit this doc](https://github.com/lightspeedwp/.github/edit/develop/docs/FILENAME.md) | [Report issue](https://github.com/lightspeedwp/.github/issues/new) ``` @@ -355,8 +355,8 @@ Footers provide attribution, maintenance status, and relevant links. ``` --- -**Status**: Active | **Version**: v2.1.0 -**Last Updated**: 2026-05-28 by @maintainer +**Status**: Active | **Version**: v2.1.0 +**Last Updated**: 2026-05-28 by @maintainer [Edit](https://github.com/lightspeedwp/.github/edit/develop/docs/FILENAME.md) ``` @@ -364,7 +364,7 @@ Footers provide attribution, maintenance status, and relevant links. ``` --- -📚 **Related**: [AUTOMATION_GOVERNANCE.md](./AUTOMATION_GOVERNANCE.md) | [PLUGIN_PACK_ROADMAP.md](./PLUGIN_PACK_ROADMAP.md) +📚 **Related**: [AUTOMATION_GOVERNANCE.md](./AUTOMATION_GOVERNANCE.md) | [PLUGIN_PACK_ROADMAP.md](./PLUGIN_PACK_ROADMAP.md) Maintained with ❤️ by the LightSpeed automation team. ``` @@ -372,8 +372,8 @@ Maintained with ❤️ by the LightSpeed automation team. ``` --- -✅ **Reviewed & Approved** | Last approved: 2026-05-01 -[Suggest changes](https://github.com/lightspeedwp/.github/pulls/new) | +✅ **Reviewed & Approved** | Last approved: 2026-05-01 +[Suggest changes](https://github.com/lightspeedwp/.github/pulls/new) | [View history](https://github.com/lightspeedwp/.github/commits/develop/docs/FILENAME.md) ``` @@ -381,7 +381,7 @@ Maintained with ❤️ by the LightSpeed automation team. ``` --- -Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit! +Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit! [Learn more](https://lightspeedwp.agency) ``` @@ -393,8 +393,8 @@ Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit! ``` --- -🤖 **Agent**: Unified Labeling Agent -**Version**: v1.2.3 | **Status**: Active +🤖 **Agent**: Unified Labeling Agent +**Version**: v1.2.3 | **Status**: Active [Implementation](./agent.js) | [Edit spec](https://github.com/lightspeedwp/.github/edit/develop/agents/AGENT_NAME.agent.md) ``` @@ -402,8 +402,8 @@ Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit! ``` --- -**Capabilities**: Labeling, Issue Triage, PR Analysis -**Maintained by**: @automation-team +**Capabilities**: Labeling, Issue Triage, PR Analysis +**Maintained by**: @automation-team [View capabilities](./capabilities.md) | [Report issue](https://github.com/lightspeedwp/.github/issues/new?labels=agent) ``` @@ -411,7 +411,7 @@ Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit! ``` --- -🤖 **Copilot for LightSpeedWP** — Always fresh, always compliant! +🤖 **Copilot for LightSpeedWP** — Always fresh, always compliant! **Integration Guide**: [Setup](./INTEGRATION.md) | **Docs**: [Agent Spec](./AGENT_SPEC.md) ``` @@ -419,8 +419,8 @@ Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit! ``` --- -**Last Updated**: 2026-05-28 | **Maintained by**: @automation-team -[Current Issues](https://github.com/lightspeedwp/.github/issues?q=label:agent) | +**Last Updated**: 2026-05-28 | **Maintained by**: @automation-team +[Current Issues](https://github.com/lightspeedwp/.github/issues?q=label:agent) | [Changelog](https://github.com/lightspeedwp/.github/blob/develop/CHANGELOG.md) ``` @@ -428,7 +428,7 @@ Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit! ``` --- -**🤖 Agent Spec** | Part of LightSpeed automation infrastructure +**🤖 Agent Spec** | Part of LightSpeed automation infrastructure [Learn more about agents](https://github.com/lightspeedwp/.github/blob/develop/AGENTS.md) ``` @@ -440,7 +440,7 @@ Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit! ``` --- -**Compliance Level**: Required | **Scope**: All repositories +**Compliance Level**: Required | **Scope**: All repositories [Enforcement](./ENFORCEMENT.md) | [Exceptions](./EXCEPTIONS.md) | [Report violation](https://github.com/lightspeedwp/.github/issues/new?labels=compliance) ``` @@ -448,7 +448,7 @@ Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit! ``` --- -✅ **Approved** by @architecture-team on 2026-05-01 +✅ **Approved** by @architecture-team on 2026-05-01 [View approvals](./APPROVALS.md) | [Suggest update](https://github.com/lightspeedwp/.github/pulls/new) ``` @@ -456,7 +456,7 @@ Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit! ``` --- -📋 **Part of Coding Standards** — [Main Guidelines](./CODING_STANDARDS.md) +📋 **Part of Coding Standards** — [Main Guidelines](./CODING_STANDARDS.md) Related: [PHP Standards](./PHP_STANDARDS.md) | [JS Standards](./JS_STANDARDS.md) ``` @@ -464,8 +464,8 @@ Related: [PHP Standards](./PHP_STANDARDS.md) | [JS Standards](./JS_STANDARDS.md) ``` --- -**Enforcement**: Automated by GitHub Actions -**Status**: Active | **Last Review**: 2026-05-15 +**Enforcement**: Automated by GitHub Actions +**Status**: Active | **Last Review**: 2026-05-15 [Automation Details](./ENFORCEMENT.md) ``` @@ -473,7 +473,7 @@ Related: [PHP Standards](./PHP_STANDARDS.md) | [JS Standards](./JS_STANDARDS.md) ``` --- -🎯 **Required Coding Standards** +🎯 **Required Coding Standards** [Contribute](https://github.com/lightspeedwp/.github/blob/develop/CONTRIBUTING.md) ``` @@ -485,7 +485,7 @@ Related: [PHP Standards](./PHP_STANDARDS.md) | [JS Standards](./JS_STANDARDS.md) ``` --- -**Schema Version**: v2.0 | **Validation Tool**: JSON Schema v7 +**Schema Version**: v2.0 | **Validation Tool**: JSON Schema v7 [JSON File](./../schemas/SCHEMA_NAME.schema.json) | [Edit spec](https://github.com/lightspeedwp/.github/edit/develop/schema/SCHEMA_NAME.schema.md) ``` @@ -493,7 +493,7 @@ Related: [PHP Standards](./PHP_STANDARDS.md) | [JS Standards](./JS_STANDARDS.md) ``` --- -✅ **Validation**: All tests passing | **Coverage**: 100% +✅ **Validation**: All tests passing | **Coverage**: 100% [Test results](./TEST_RESULTS.md) | [Validate](./VALIDATE.md) ``` @@ -501,7 +501,7 @@ Related: [PHP Standards](./PHP_STANDARDS.md) | [JS Standards](./JS_STANDARDS.md) ``` --- -📐 **Schema validated by LightSpeedWP** — Always compliant! +📐 **Schema validated by LightSpeedWP** — Always compliant! **Version**: 2.1.0 | [Changelog](./CHANGELOG.md) | [Breaking Changes](./BREAKING_CHANGES.md) ``` @@ -509,7 +509,7 @@ Related: [PHP Standards](./PHP_STANDARDS.md) | [JS Standards](./JS_STANDARDS.md) ``` --- -JSON Schema v7 | **Version**: v2.0 +JSON Schema v7 | **Version**: v2.0 [Learn more](https://json-schema.org) ``` @@ -517,7 +517,7 @@ JSON Schema v7 | **Version**: v2.0 ``` --- -**Part of**: [Unified Frontmatter Schema](./frontmatter.schema.md) +**Part of**: [Unified Frontmatter Schema](./frontmatter.schema.md) **Related**: [Footer Config](./footer-config.schema.md) | [Label Schema](./labels.schema.md) ``` @@ -529,8 +529,8 @@ JSON Schema v7 | **Version**: v2.0 ``` --- -**Tools**: Figma, Canva, PowerPoint, reveal.js -**Version**: v1.0 | **Last Updated**: 2026-05-28 +**Tools**: Figma, Canva, PowerPoint, reveal.js +**Version**: v1.0 | **Last Updated**: 2026-05-28 [Generate slides](https://figma.com/...) | [Edit prompt](https://github.com/lightspeedwp/.github/edit/develop/wceu-2026/SLIDES_GENERATION_PROMPT.md) ``` @@ -538,8 +538,8 @@ JSON Schema v7 | **Version**: v2.0 ``` --- -💬 **Prompt Engineering Notes**: Best with GPT-4, Claude Opus -**Format**: Markdown | **Length**: ~2,000 tokens +💬 **Prompt Engineering Notes**: Best with GPT-4, Claude Opus +**Format**: Markdown | **Length**: ~2,000 tokens [Template](./TEMPLATE.md) | [Examples](./EXAMPLES.md) ``` @@ -547,7 +547,7 @@ JSON Schema v7 | **Version**: v2.0 ``` --- -✨ **Prompt magic by 🦄 LightSpeedWP Automation Unicorns.** +✨ **Prompt magic by 🦄 LightSpeedWP Automation Unicorns.** [Adobe Firefly](./ADOBE_VERSION.md) | [Midjourney](./MIDJOURNEY_VERSION.md) | [DALL-E](./DALLE_VERSION.md) ``` @@ -555,8 +555,8 @@ JSON Schema v7 | **Version**: v2.0 ``` --- -**Status**: Production | **Version**: v1.2.3 -**Maintained by**: @prompt-engineering-team +**Status**: Production | **Version**: v1.2.3 +**Maintained by**: @prompt-engineering-team [Issues](https://github.com/lightspeedwp/.github/issues?labels=prompt) | [Suggestions](https://github.com/lightspeedwp/.github/discussions) ``` @@ -575,8 +575,8 @@ JSON Schema v7 | **Version**: v2.0 ``` --- -**Policy Authority**: @architecture-team | **Effective**: 2026-05-01 -**Next Review**: 2026-08-01 | **Status**: Active +**Policy Authority**: @architecture-team | **Effective**: 2026-05-01 +**Next Review**: 2026-08-01 | **Status**: Active [Decision Record](./DECISION_RECORD.md) | [Report exception](https://github.com/lightspeedwp/.github/issues/new?labels=governance) ``` @@ -584,9 +584,9 @@ JSON Schema v7 | **Version**: v2.0 ``` --- -✅ **Approved by**: -- @architecture-team (2026-05-01) -- @security-team (2026-05-02) +✅ **Approved by**: +- @architecture-team (2026-05-01) +- @security-team (2026-05-02) [Approval Details](./APPROVALS.md) ``` @@ -595,8 +595,8 @@ JSON Schema v7 | **Version**: v2.0 ``` --- -📋 **Governance Decision** — [Full Record](./ADR_0042.md) -**Scope**: All repositories | **Owner**: @governance-lead +📋 **Governance Decision** — [Full Record](./ADR_0042.md) +**Scope**: All repositories | **Owner**: @governance-lead [Effective Date](./TIMELINE.md) | [Transition Plan](./TRANSITION.md) ``` @@ -604,7 +604,7 @@ JSON Schema v7 | **Version**: v2.0 ``` --- -🎯 **Policy Effective**: 2026-05-01 +🎯 **Policy Effective**: 2026-05-01 [Decisions](./DECISIONS.md) | [History](https://github.com/lightspeedwp/.github/commits/develop/docs/GOVERNANCE.md) ``` @@ -612,8 +612,8 @@ JSON Schema v7 | **Version**: v2.0 ``` --- -**Compliance Checklist**: [Requirements](./CHECKLIST.md) -**Status**: All org repos ✅ | **Non-compliance**: 0 +**Compliance Checklist**: [Requirements](./CHECKLIST.md) +**Status**: All org repos ✅ | **Non-compliance**: 0 [Audit Results](./AUDIT.md) | [Next Review](./REVIEW_SCHEDULE.md) ``` @@ -648,10 +648,10 @@ Badges provide quick visual identification and status indicators. **[badge-type]**: value # Examples: -**[status]**: Active -**[version]**: v2.1.0 -**[category]**: [agents] -**[compliance]**: Required +**[status]**: Active +**[version]**: v2.1.0 +**[category]**: [agents] +**[compliance]**: Required **[tools]**: Figma, Canva ``` @@ -747,7 +747,7 @@ templates: default: "default" template: | --- - **Documentation maintained by the LightSpeed team.** + **Documentation maintained by the LightSpeed team.** [Edit this doc](${edit_link}) | [Report issue](${issue_link}) variables: - edit_link (auto-generated from file path) @@ -756,8 +756,8 @@ templates: docs-with-version: template: | --- - **Status**: ${status} | **Version**: ${version} - **Last Updated**: ${last_updated} by ${updated_by} + **Status**: ${status} | **Version**: ${version} + **Last Updated**: ${last_updated} by ${updated_by} [Edit](${edit_link}) variables: - status (from frontmatter) @@ -951,8 +951,8 @@ Footers should feel like metadata, not content. Example of high-noise: ```markdown --- -📚 **Welcome to our comprehensive documentation library!** We're constantly -updating this to serve you better. If you have questions, suggestions, or would +📚 **Welcome to our comprehensive documentation library!** We're constantly +updating this to serve you better. If you have questions, suggestions, or would like to contribute, please don't hesitate to reach out! [Contact us](...) ``` @@ -960,7 +960,7 @@ Example of appropriate-noise: ```markdown --- -**Documentation maintained by the LightSpeed team.** +**Documentation maintained by the LightSpeed team.** [Edit](url) | [Report issue](url) ``` @@ -970,7 +970,7 @@ Example of appropriate-noise: ### Issue #46 — Template Design -**Scope**: Define implementation-ready footer, header, and badge templates +**Scope**: Define implementation-ready footer, header, and badge templates **Deliverables**: - 5 footer variants per key category (6 categories minimum) @@ -979,12 +979,12 @@ Example of appropriate-noise: - Frontmatter-to-template mapping rules - Fallback template behavior -**Dependencies**: Issue #33 (this spec) +**Dependencies**: Issue #33 (this spec) **Unblocks**: Issue #48 (agent implementation) ### Issue #49 — Schema/Config Model -**Scope**: Define JSON Schema validation and YAML config structure +**Scope**: Define JSON Schema validation and YAML config structure **Deliverables**: - `schemas/branding-config.schema.json` (JSON Schema v7) @@ -994,12 +994,12 @@ Example of appropriate-noise: - Validation rules and error messages - Maintainer guidance for extending config -**Dependencies**: Issues #33 (this spec), #46 (template designs) +**Dependencies**: Issues #33 (this spec), #46 (template designs) **Unblocks**: Issue #48 (agent implementation) ### Issue #48 — Agent Implementation & Documentation -**Scope**: Implement branding agent using config from #49 and templates from #46 +**Scope**: Implement branding agent using config from #49 and templates from #46 **Deliverables**: - `.github/agents/branding.agent.md` — Agent specification @@ -1008,7 +1008,7 @@ Example of appropriate-noise: - Remediation script for existing files - CI integration for ongoing validation -**Dependencies**: Issues #33 (spec), #46 (templates), #49 (config) +**Dependencies**: Issues #33 (spec), #46 (templates), #49 (config) **Blocks**: Remediation and validation phase --- @@ -1097,7 +1097,7 @@ Example of appropriate-noise: --- -**Created**: 2026-05-28 -**By**: Claude -**For**: LightSpeed Team +**Created**: 2026-05-28 +**By**: Claude +**For**: LightSpeed Team **Related Work**: Issues #33, #46, #48, #49 diff --git a/.github/projects/completed/ISSUE_46_TEMPLATE_DESIGN.md b/.github/projects/completed/ISSUE_46_TEMPLATE_DESIGN.md index facef30e0..ef24e987a 100644 --- a/.github/projects/completed/ISSUE_46_TEMPLATE_DESIGN.md +++ b/.github/projects/completed/ISSUE_46_TEMPLATE_DESIGN.md @@ -11,11 +11,11 @@ tags: ["branding", "templates", "headers", "footers", "badges", "design"] # Branding Agent Template Design (Issue #46) -**Parent Issue**: #33 (Parent Specification) -**Related Issues**: #49 (Schema/Config), #48 (Agent Implementation) -**Status**: Template Design Phase -**Effort**: 8–10 hours (design and documentation) -**Timeline**: Week 2 implementation +**Parent Issue**: #33 (Parent Specification) +**Related Issues**: #49 (Schema/Config), #48 (Agent Implementation) +**Status**: Template Design Phase +**Effort**: 8–10 hours (design and documentation) +**Timeline**: Week 2 implementation --- @@ -191,15 +191,15 @@ Headers appear at the top of the frontmatter and provide document metadata to re ### 3.7–3.16 Other Categories -**Guides**: Similar to Docs, with "Quick Start" section -**README**: Structured with "Contents", "Quick Links", project overview -**Standards**: Include "Standard Version" and "Adoption Timeline" -**Tools**: Include "Installation" and "Quick Start" sections -**Workflows**: Include "Trigger Events" and "Outputs" sections -**Checklists**: Include "Scope" and "Success Criteria" sections -**Examples**: Include "Language/Framework" and "Complexity Level" -**Proposals**: Include "Decision" and "Impact" sections -**Archives**: Include "Archive Date" and "Replacement Link" (if applicable) +**Guides**: Similar to Docs, with "Quick Start" section +**README**: Structured with "Contents", "Quick Links", project overview +**Standards**: Include "Standard Version" and "Adoption Timeline" +**Tools**: Include "Installation" and "Quick Start" sections +**Workflows**: Include "Trigger Events" and "Outputs" sections +**Checklists**: Include "Scope" and "Success Criteria" sections +**Examples**: Include "Language/Framework" and "Complexity Level" +**Proposals**: Include "Decision" and "Impact" sections +**Archives**: Include "Archive Date" and "Replacement Link" (if applicable) **Metadata**: Minimal header (often just title and description) --- @@ -222,8 +222,8 @@ Footers appear at the end of documents. Each category has 5 variants: --- -**Last Updated**: [Date from frontmatter] -**Owner**: [From frontmatter] +**Last Updated**: [Date from frontmatter] +**Owner**: [From frontmatter] **Status**: [From frontmatter] ``` @@ -288,7 +288,7 @@ Footers appear at the end of documents. Each category has 5 variants: ```markdown --- -**Last Updated**: [Date] +**Last Updated**: [Date] [Related link] ``` @@ -313,7 +313,7 @@ Footers appear at the end of documents. Each category has 5 variants: --- -**Owner**: [From frontmatter] +**Owner**: [From frontmatter] **Status**: [From frontmatter] ``` @@ -373,7 +373,7 @@ See [Related Agents](link) for similar specs. ```markdown --- -**Owner**: [From frontmatter] +**Owner**: [From frontmatter] [Parent spec or related link] ``` @@ -457,7 +457,7 @@ Last Updated: [Date] ```markdown --- -**Owner**: [From frontmatter] +**Owner**: [From frontmatter] See also: [Related instruction](link) ``` @@ -482,7 +482,7 @@ See [Examples](link) for more. --- -**Version**: [Version] +**Version**: [Version] **Owner**: [From frontmatter] ``` @@ -526,7 +526,7 @@ See [Examples](link) for more. ```markdown --- -**Version**: [Version] +**Version**: [Version] [Related schema](link) ``` @@ -619,7 +619,7 @@ Related: [Related prompt](link) ```markdown --- -**Owner**: [From frontmatter] +**Owner**: [From frontmatter] Model: [Model name] ``` @@ -680,7 +680,7 @@ Related policies: [Links] ```markdown --- -**Effective Date**: [Date] +**Effective Date**: [Date] **Owner**: [From frontmatter] ``` @@ -803,8 +803,8 @@ This guide explains how to authenticate and make your first API call. It takes a --- -**Last Updated**: 2026-05-28 -**Owner**: API Team +**Last Updated**: 2026-05-28 +**Owner**: API Team **Status**: Active ``` @@ -849,7 +849,7 @@ owners: ["AI Ops"] --- -**Owner**: AI Ops +**Owner**: AI Ops **Status**: Active ``` @@ -889,7 +889,7 @@ templates: agents: | ## Agent Specification ... - + footers: docs: variant_1: | @@ -900,7 +900,7 @@ templates: --- ## Version & Status ... - + badges: status: active: "![Status: Active](https://...)" diff --git a/.github/projects/completed/ISSUE_48_CURRENT_STATE_AUDIT.md b/.github/projects/completed/ISSUE_48_CURRENT_STATE_AUDIT.md index 5d6fffe06..04d381146 100644 --- a/.github/projects/completed/ISSUE_48_CURRENT_STATE_AUDIT.md +++ b/.github/projects/completed/ISSUE_48_CURRENT_STATE_AUDIT.md @@ -21,11 +21,11 @@ domain: governance # Branding Agent Current-State Audit (Issue #48) -**Parent Issue**: #33 (Parent Specification) -**Related Issues**: #46 (Template Design), #49 (Schema/Config) -**Status**: Current-State Audit Phase -**Effort**: 12–14 hours (audit, analysis, remediation planning, documentation) -**Timeline**: Week 2–3 implementation +**Parent Issue**: #33 (Parent Specification) +**Related Issues**: #46 (Template Design), #49 (Schema/Config) +**Status**: Current-State Audit Phase +**Effort**: 12–14 hours (audit, analysis, remediation planning, documentation) +**Timeline**: Week 2–3 implementation --- diff --git a/.github/projects/completed/ISSUE_49_SCHEMA_CONFIG_IMPLEMENTATION.md b/.github/projects/completed/ISSUE_49_SCHEMA_CONFIG_IMPLEMENTATION.md index 6d08df94a..b1975125a 100644 --- a/.github/projects/completed/ISSUE_49_SCHEMA_CONFIG_IMPLEMENTATION.md +++ b/.github/projects/completed/ISSUE_49_SCHEMA_CONFIG_IMPLEMENTATION.md @@ -22,11 +22,11 @@ domain: governance # Branding Agent Schema and Config Implementation (Issue #49) -**Parent Issue**: #33 (Parent Specification) -**Related Issues**: #46 (Template Design), #48 (Current-state audit) -**Status**: Schema/Config Design Phase -**Effort**: 10–12 hours (schema design, validation, documentation) -**Timeline**: Week 2 implementation +**Parent Issue**: #33 (Parent Specification) +**Related Issues**: #46 (Template Design), #48 (Current-state audit) +**Status**: Schema/Config Design Phase +**Effort**: 10–12 hours (schema design, validation, documentation) +**Timeline**: Week 2 implementation --- @@ -49,8 +49,8 @@ The recommended approach is **YAML authoring with JSON Schema validation**, whic ### 2.1 Recommended Approach: YAML + JSON Schema -**Format**: YAML (human-friendly authoring) -**Validation**: JSON Schema v7 +**Format**: YAML (human-friendly authoring) +**Validation**: JSON Schema v7 **Storage**: `config/branding.config.yaml` (main config) and `schema/branding.schema.json` (validation schema) **Rationale**: @@ -321,33 +321,33 @@ badge_rules: allowed: ["status", "version", "category", "audience"] recommended: ["status"] max_count: 4 - + agents: allowed: ["status", "version", "category", "stability"] recommended: ["status", "stability"] max_count: 4 - + schemas: allowed: ["status", "version", "category", "stability"] recommended: ["version", "stability"] max_count: 4 - + prompts: allowed: ["status", "version", "category", "stability", "audience"] recommended: ["status", "stability"] max_count: 4 - + governance: allowed: ["status", "category"] recommended: ["status"] max_count: 2 - + # Simpler rules for other categories utility: allowed: ["status", "category"] recommended: ["status"] max_count: 2 - + workflow: allowed: ["status", "category"] recommended: ["status"] @@ -370,21 +370,21 @@ template_references: default: "docs-variant-1" variants: ["docs-variant-1", "docs-variant-2", "docs-variant-3", "docs-variant-4", "docs-variant-5"] selection_rule: "use-default" - + agents: header: "agents-spec" footer: default: "agents-variant-1" variants: ["agents-variant-1", "agents-variant-2", "agents-variant-3", "agents-variant-4", "agents-variant-5"] selection_rule: "use-default" - + schemas: header: "schema-definition" footer: default: "schema-variant-1" variants: ["schema-variant-1", "schema-variant-2", "schema-variant-3", "schema-variant-4", "schema-variant-5"] selection_rule: "use-default" - + # Simpler templates for other categories readme: header: "readme-standard" @@ -392,7 +392,7 @@ template_references: default: "readme-simple" variants: ["readme-simple"] selection_rule: "use-default" - + utility: header: "utility-standard" footer: @@ -595,25 +595,25 @@ badges: allowed_values: ["active", "deprecated", "draft", "under-review", "on-hold"] default: "active" source: "frontmatter.status" - + version: label: "Version" type: "semver" source: "frontmatter.version" optional: true - + category: label: "Category" type: "enum" source: "inferred_category" - + stability: label: "Stability" type: "enum" allowed_values: ["stable", "beta", "experimental", "deprecated"] default: "stable" source: "frontmatter.stability" - + audience: label: "Audience" type: "enum" @@ -629,53 +629,53 @@ frontmatter_fields: type: "string" required: true description: "Document title" - + category: type: "string" required: true enum: ["documentation", "agents", "instructions", "schemas", "prompts", "governance", "issue-template", "pr-template", "workflow", "research", "audit", "awesome-list", "readme", "test", "utility", "ai-ops"] description: "Document category" - + last_updated: type: "date" format: "YYYY-MM-DD" required: true description: "Last update date" - + owners: type: "array[string]" required: true minItems: 1 description: "GitHub username or email, at least one" - + # Optional fields tags: type: "array[string]" required: false description: "Tag-driven metadata" - + status: type: "string" enum: ["active", "deprecated", "draft", "under-review", "on-hold"] default: "active" description: "Document lifecycle stage" - + stability: type: "string" enum: ["stable", "beta", "experimental", "deprecated"] default: "stable" description: "API/content stability level" - + domain: type: "string" description: "Semantic domain grouping" - + audience: type: "string" enum: ["internal", "public", "community"] default: "internal" description: "Intended audience" - + version: type: "string" format: "semver" @@ -696,10 +696,10 @@ validation: accessibility: # All badges must include alt text require_badge_alt_text: true - + # Contrast ratio requirements (WCAG AA) min_contrast_ratio: 4.5 - + # Link guidance require_descriptive_links: true avoid_bare_urls: true diff --git a/.github/projects/completed/PLANNING_SUMMARY_2026-05-28.md b/.github/projects/completed/PLANNING_SUMMARY_2026-05-28.md index e21497d6d..70c17fe89 100644 --- a/.github/projects/completed/PLANNING_SUMMARY_2026-05-28.md +++ b/.github/projects/completed/PLANNING_SUMMARY_2026-05-28.md @@ -381,7 +381,7 @@ A **comprehensive, 20-slide generation prompt** covering: --- -**Created**: 2026-05-28 -**By**: Claude -**For**: LightSpeed Team +**Created**: 2026-05-28 +**By**: Claude +**For**: LightSpeed Team **Related work**: Issues #33, #46, #48, #49, #529 diff --git a/.github/projects/completed/branding-meta-agent-planning-2026-05-28.md b/.github/projects/completed/branding-meta-agent-planning-2026-05-28.md index f8fd9527d..3f7c5a15f 100644 --- a/.github/projects/completed/branding-meta-agent-planning-2026-05-28.md +++ b/.github/projects/completed/branding-meta-agent-planning-2026-05-28.md @@ -260,7 +260,7 @@ Build one **unified branding meta agent** that: | #49 | Schema/config model: category fields, validation, examples | 3-4h | #33, #46 (input) | Claude | | #48 | Documentation & agent spec | 2-3h | #33, #46, #49 (input) | Claude | -**Total Effort**: ~12-16 hours +**Total Effort**: ~12-16 hours **Parallelism**: #46 and #49 can start after #33 scope is confirmed --- diff --git a/.github/projects/completed/wave-4-continuous-monitoring.md b/.github/projects/completed/wave-4-continuous-monitoring.md index 6702f269d..37b081c47 100644 --- a/.github/projects/completed/wave-4-continuous-monitoring.md +++ b/.github/projects/completed/wave-4-continuous-monitoring.md @@ -12,10 +12,10 @@ maintainer: "LightSpeed Team" # Wave 4: Continuous README & Mermaid Monitoring -**Phase**: Post-Wave 3C Implementation -**Owner**: TBD (Codex or Claude, to be assigned) -**Estimated Start**: Post-Wave 3C completion -**Effort Estimate**: 2-3 weeks +**Phase**: Post-Wave 3C Implementation +**Owner**: TBD (Codex or Claude, to be assigned) +**Estimated Start**: Post-Wave 3C completion +**Effort Estimate**: 2-3 weeks **Status**: Specification Draft (Ready for Review) --- diff --git a/.github/prompts/normalize-docs-labels.prompt.md b/.github/prompts/normalize-docs-labels.prompt.md index 43523da4b..3ce9ac225 100644 --- a/.github/prompts/normalize-docs-labels.prompt.md +++ b/.github/prompts/normalize-docs-labels.prompt.md @@ -9,7 +9,7 @@ tools: ["codebase", "search", "editFiles"] ## 0. Goal -You are working on the `lightspeedwp/.github` repository, branch **`recover/readmes`**. +You are working on the `lightspeedwp/.github` repository, branch **`recover/readmes`**. Your job is to: 1. **Align configuration** (`labels.yml`, `labeler.yml`, `issue-types.yml`) with the agreed label & issue-type strategy. diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 95c3591d3..48ca00ecd 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -9,7 +9,7 @@ labels: ["status:needs-review"] # General Pull Request -> This repository enforces changelog, release, and label automation for all PRs and issues. +> This repository enforces changelog, release, and label automation for all PRs and issues. > See the organisation-wide [Automation Governance & Release Strategy](https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md) for contributor rules. ## Linked issues diff --git a/.github/reports/audits/issue-creation-docs-audit-report.md b/.github/reports/audits/issue-creation-docs-audit-report.md index d77080a78..dd6f091a1 100644 --- a/.github/reports/audits/issue-creation-docs-audit-report.md +++ b/.github/reports/audits/issue-creation-docs-audit-report.md @@ -25,9 +25,9 @@ stability: stable # Issue Creation Documentation Audit Report -**Audit Date:** 2026-05-31 -**Audit Scope:** 6 overlapping documentation files related to issue creation -**Status:** Complete +**Audit Date:** 2026-05-31 +**Audit Scope:** 6 overlapping documentation files related to issue creation +**Status:** Complete **Issue:** [#662 - Audit Issue Creation Docs](https://github.com/lightspeedwp/.github/issues/662) --- @@ -541,7 +541,7 @@ These files support issue creation but are distinct documentation artifacts. --- -**Report Complete** +**Report Complete** **Next Step:** Review consolidation recommendations with team; proceed with Phase 1 & Phase 2 as approved. *Maintained with ❤️ by LightSpeed — Audit performed 2026-05-31* diff --git a/.github/reports/audits/issue-types-alignment-audit-2026-06-01.md b/.github/reports/audits/issue-types-alignment-audit-2026-06-01.md index b55be13d9..d0660ef95 100644 --- a/.github/reports/audits/issue-types-alignment-audit-2026-06-01.md +++ b/.github/reports/audits/issue-types-alignment-audit-2026-06-01.md @@ -199,6 +199,6 @@ Create template files for the 3 types without templates: --- -**Generated:** 2026-06-01 -**Audit Scope:** `.github/issue-types.yml` (29 types), `.github/ISSUE_TEMPLATE/` (26 templates), `.github/labels.yml` (29+ labels) +**Generated:** 2026-06-01 +**Audit Scope:** `.github/issue-types.yml` (29 types), `.github/ISSUE_TEMPLATE/` (26 templates), `.github/labels.yml` (29+ labels) **Status:** Complete with phase-by-phase remediation plan diff --git a/.github/reports/audits/label-color-consistency-audit-2026-06-01.md b/.github/reports/audits/label-color-consistency-audit-2026-06-01.md index 486e8acee..6b3ab8694 100644 --- a/.github/reports/audits/label-color-consistency-audit-2026-06-01.md +++ b/.github/reports/audits/label-color-consistency-audit-2026-06-01.md @@ -20,10 +20,10 @@ tags: # Label Color Consistency Audit -**Date**: 2026-06-01 -**Auditor**: Claude Code (Wave 5 Documentation Audit) -**Scope**: 151 canonical labels in `.github/labels.yml` (plus 2 new type labels added) -**Reference Document**: `docs/LABEL_COLOR_STRATEGY.md` (v1.0.0) +**Date**: 2026-06-01 +**Auditor**: Claude Code (Wave 5 Documentation Audit) +**Scope**: 151 canonical labels in `.github/labels.yml` (plus 2 new type labels added) +**Reference Document**: `docs/LABEL_COLOR_STRATEGY.md` (v1.0.0) **Status**: Complete --- @@ -467,18 +467,18 @@ See accompanying file: `label-color-audit-spreadsheet-2026-06-01.csv` ## Document Metadata -**File**: `.github/reports/audits/label-color-consistency-audit-2026-06-01.md` +**File**: `.github/reports/audits/label-color-consistency-audit-2026-06-01.md` **Related Files**: - `.github/labels.yml` (canonical label configuration) - `docs/LABEL_COLOR_STRATEGY.md` (color family strategy) - `.github/projects/active/wave-5-documentation-audit/children/02-1-labels-color-consistency.md` (issue specification) -**Status**: ✅ Audit Complete +**Status**: ✅ Audit Complete **Next Action**: Create label update PR based on Phase 1 recommendations --- -**Audit Completed**: 2026-06-01 -**Auditor**: Claude Code +**Audit Completed**: 2026-06-01 +**Auditor**: Claude Code **Approval Pending**: LightSpeed Team diff --git a/.github/reports/audits/workflow-standards-audit-2026-05-31.md b/.github/reports/audits/workflow-standards-audit-2026-05-31.md index 6c5204fd2..f69802f71 100644 --- a/.github/reports/audits/workflow-standards-audit-2026-05-31.md +++ b/.github/reports/audits/workflow-standards-audit-2026-05-31.md @@ -7,8 +7,8 @@ created_date: "2026-05-31" # Workflow Standards Audit & Improvement Plan -**Date:** 31 May 2026 -**Audit Scope:** Linting, metadata, branding, CI/CD workflows, and automation +**Date:** 31 May 2026 +**Audit Scope:** Linting, metadata, branding, CI/CD workflows, and automation **Status:** Active (Implementation in Progress) ## Executive Summary @@ -57,8 +57,8 @@ This audit identifies 6 priority improvements and a roadmap for streamlined, sta ### 1. **Changelog Auto-Sync on Develop Merge** (CRITICAL) -**Current State:** Changelog validated on PR; not updated on merge -**Gap:** No mechanism to append merged PR changelog entries to main CHANGELOG.md +**Current State:** Changelog validated on PR; not updated on merge +**Gap:** No mechanism to append merged PR changelog entries to main CHANGELOG.md **Solution:** New `changelog-auto-update.yml` workflow **Implementation:** @@ -75,8 +75,8 @@ This audit identifies 6 priority improvements and a roadmap for streamlined, sta ### 2. **Automated Project Archival** (HIGH) -**Current State:** Projects in active folder; archival is manual -**Gap:** No workflow to detect completion and move to archived +**Current State:** Projects in active folder; archival is manual +**Gap:** No workflow to detect completion and move to archived **Solution:** New `project-archival.yml` workflow + project schema validation **Implementation:** @@ -93,8 +93,8 @@ This audit identifies 6 priority improvements and a roadmap for streamlined, sta ### 3. **Planner Agent Implementation** (HIGH) -**Current State:** Disabled (`if: false`); script not implemented -**Gap:** Issues not automatically added to project on creation +**Current State:** Disabled (`if: false`); script not implemented +**Gap:** Issues not automatically added to project on creation **Solution:** Implement `scripts/agents/planner.agent.js` **Implementation:** @@ -110,8 +110,8 @@ This audit identifies 6 priority improvements and a roadmap for streamlined, sta ### 4. **Issue Planning Documentation** (MEDIUM) -**Current State:** Issues created ad-hoc; planning not centralised -**Gap:** No standardised location for planning docs before issues +**Current State:** Issues created ad-hoc; planning not centralised +**Gap:** No standardised location for planning docs before issues **Solution:** Pre-issue planning template + checklist in issue-opener guide **Implementation:** @@ -127,8 +127,8 @@ This audit identifies 6 priority improvements and a roadmap for streamlined, sta ### 5. **Workflow Consolidation & Clarity** (MEDIUM) -**Current State:** Linting split across `linting.yml`, `meta.yml`, `testing.yml` -**Gap:** Unclear triggers; potential for redundant/competing runs +**Current State:** Linting split across `linting.yml`, `meta.yml`, `testing.yml` +**Gap:** Unclear triggers; potential for redundant/competing runs **Solution:** Unified pre-merge check workflow + documentation **Implementation:** @@ -144,8 +144,8 @@ This audit identifies 6 priority improvements and a roadmap for streamlined, sta ### 6. **Scheduled Metrics & Reporting** (LOW) -**Current State:** Metrics collected ad-hoc; no scheduled summary -**Gap:** Metrics available but not surfaced to team +**Current State:** Metrics collected ad-hoc; no scheduled summary +**Gap:** Metrics available but not surfaced to team **Solution:** Add scheduled reporting workflow **Implementation:** diff --git a/.github/reports/mermaid-audit/audit-log.md b/.github/reports/mermaid-audit/audit-log.md index 3783e1e02..eccca25dd 100644 --- a/.github/reports/mermaid-audit/audit-log.md +++ b/.github/reports/mermaid-audit/audit-log.md @@ -20,10 +20,10 @@ stability: stable # Wave 3A: Detailed Audit Log -**Audit Execution Date:** 2026-05-28 -**Total Files Scanned:** 30 README files -**Files with Diagrams:** 4 -**Total Diagrams Identified:** 17 +**Audit Execution Date:** 2026-05-28 +**Total Files Scanned:** 30 README files +**Files with Diagrams:** 4 +**Total Diagrams Identified:** 17 --- @@ -42,10 +42,10 @@ stability: stable ### 1. README.md (Root) -**Location:** `./README.md` -**Diagrams Found:** 7 -**Last Modified:** 2026-05-28 -**Status:** 🔴 Requires Accessibility Additions +**Location:** `./README.md` +**Diagrams Found:** 7 +**Last Modified:** 2026-05-28 +**Status:** 🔴 Requires Accessibility Additions #### Diagram Breakdown @@ -79,10 +79,10 @@ stability: stable ### 2. profile/README.md -**Location:** `./profile/README.md` -**Diagrams Found:** 4 -**Last Modified:** 2026-05-28 -**Status:** 🔴 Requires Accessibility Additions +**Location:** `./profile/README.md` +**Diagrams Found:** 4 +**Last Modified:** 2026-05-28 +**Status:** 🔴 Requires Accessibility Additions #### Diagram Breakdown @@ -113,10 +113,10 @@ stability: stable ### 3. scripts/README.md -**Location:** `./scripts/README.md` -**Diagrams Found:** 3 -**Last Modified:** 2026-05-28 -**Status:** 🔴 Requires Accessibility Additions +**Location:** `./scripts/README.md` +**Diagrams Found:** 3 +**Last Modified:** 2026-05-28 +**Status:** 🔴 Requires Accessibility Additions #### Diagram Breakdown @@ -146,10 +146,10 @@ stability: stable ### 4. tests/README.md -**Location:** `./tests/README.md` -**Diagrams Found:** 3 -**Last Modified:** 2026-05-28 -**Status:** 🔴 Requires Accessibility Additions +**Location:** `./tests/README.md` +**Diagrams Found:** 3 +**Last Modified:** 2026-05-28 +**Status:** 🔴 Requires Accessibility Additions #### Diagram Breakdown @@ -293,9 +293,9 @@ The following 26 README files were scanned and contain no Mermaid diagrams (no a ## Sign-Off -**Audit Status:** ✅ COMPLETE -**Quality Assurance:** PASSED -**Ready for Wave 3B:** YES -**Handoff Date:** 2026-05-28 +**Audit Status:** ✅ COMPLETE +**Quality Assurance:** PASSED +**Ready for Wave 3B:** YES +**Handoff Date:** 2026-05-28 This audit log is complete and ready for the Wave 3B repair team. All findings are documented with specific file locations, diagram counts, and estimated repair efforts. diff --git a/.github/reports/mermaid-audit/audit-report-2026-05-28.md b/.github/reports/mermaid-audit/audit-report-2026-05-28.md index 4427b4f2b..c0eba776b 100644 --- a/.github/reports/mermaid-audit/audit-report-2026-05-28.md +++ b/.github/reports/mermaid-audit/audit-report-2026-05-28.md @@ -23,10 +23,10 @@ stability: stable # Wave 3A: README & Mermaid Diagram Audit Report -**Audit Date:** 2026-05-28 -**Scope:** All README.md files across the repository -**Owner:** Codex -**Related Issue:** #512 +**Audit Date:** 2026-05-28 +**Scope:** All README.md files across the repository +**Owner:** Codex +**Related Issue:** #512 --- @@ -102,9 +102,9 @@ This comprehensive audit scanned **30 README.md files** across the LightSpeed `. ### 3. Syntax Validation Summary -✓ All 17 Mermaid diagrams have valid syntax -✓ No render failures or parse errors detected -✓ No deprecated syntax patterns identified +✓ All 17 Mermaid diagrams have valid syntax +✓ No render failures or parse errors detected +✓ No deprecated syntax patterns identified ### 4. Content Freshness Assessment @@ -149,7 +149,7 @@ The following files require repairs in Wave 3B: ### Total Repair Effort -**Estimated Total:** 1.5-2.5 hours +**Estimated Total:** 1.5-2.5 hours - Accessibility attribute additions: ~2 minutes per diagram - Testing and validation: ~30 minutes @@ -202,12 +202,12 @@ All Mermaid diagrams should comply with: ## Sign-Off -**Audit Status:** ✅ COMPLETE -**Quality:** 100% of README files scanned, 100% of diagrams catalogued -**Ready for Wave 3B:** Yes -**Blockers for next phase:** None +**Audit Status:** ✅ COMPLETE +**Quality:** 100% of README files scanned, 100% of diagrams catalogued +**Ready for Wave 3B:** Yes +**Blockers for next phase:** None --- -**Generated:** 2026-05-28 +**Generated:** 2026-05-28 **Next Phase:** Wave 3B (Repair & Update) — Ready to proceed diff --git a/.github/reports/mermaid-diagram-audit.md b/.github/reports/mermaid-diagram-audit.md index 43e328151..42b380620 100644 --- a/.github/reports/mermaid-diagram-audit.md +++ b/.github/reports/mermaid-diagram-audit.md @@ -22,8 +22,8 @@ stability: stable # Mermaid Diagram Syntax Audit — Issue #668 -**Generated**: 2026-05-31 -**Status**: ✅ Complete — All diagrams pass validation +**Generated**: 2026-05-31 +**Status**: ✅ Complete — All diagrams pass validation **Scope**: 24 Mermaid diagrams across 8 README files --- @@ -139,7 +139,7 @@ All 24 diagrams met all validation criteria. - **Issue #669**: Mermaid Accessibility Compliance - Verify all diagrams have `accTitle` and `accDescr` attributes - Generate accessibility audit report - + - **Issue #670**: Fix & Refresh 44 README Files - Apply fixes from #668 and #669 - Update stale content @@ -177,6 +177,6 @@ All 24 diagrams met all validation criteria. --- -**Audit Conducted By**: Claude Code -**Date**: 2026-05-31 +**Audit Conducted By**: Claude Code +**Date**: 2026-05-31 **Related Issues**: #667, #668, #669, #670 diff --git a/.github/reports/wave-4c-remediation-plan.md b/.github/reports/wave-4c-remediation-plan.md index 06db599ec..69a8a8515 100644 --- a/.github/reports/wave-4c-remediation-plan.md +++ b/.github/reports/wave-4c-remediation-plan.md @@ -320,6 +320,6 @@ Phases: --- -*Report generated: 2026-05-29* -*Wave 4C: Current-State Audit* +*Report generated: 2026-05-29* +*Wave 4C: Current-State Audit* *Related: Issue #553, #554, #555, #556* diff --git a/.github/reports/wave-5-4-readme-discovery-audit.md b/.github/reports/wave-5-4-readme-discovery-audit.md index 7265e0192..e362bbd67 100644 --- a/.github/reports/wave-5-4-readme-discovery-audit.md +++ b/.github/reports/wave-5-4-readme-discovery-audit.md @@ -297,6 +297,6 @@ The discovery phase is **complete**. All 57 README files have been inventoried, --- -**Audit Conducted By**: Claude Code -**Date**: 2026-05-31 +**Audit Conducted By**: Claude Code +**Date**: 2026-05-31 **Related**: [#667 — Discover All 44 README Files](https://github.com/lightspeedwp/.github/issues/667) diff --git a/.github/reports/wave-5-completion-summary.md b/.github/reports/wave-5-completion-summary.md index 33b92a6a4..e34e2b238 100644 --- a/.github/reports/wave-5-completion-summary.md +++ b/.github/reports/wave-5-completion-summary.md @@ -26,7 +26,7 @@ Comprehensive Wave 5 audit of all 57 README.md files and 24 Mermaid diagrams acr - Total README files identified: **57** - Mermaid diagrams found: **24** (across 8 files) - Files requiring no updates: **49** - + ### Key Findings | Category | Count | With Diagrams | Without Diagrams | diff --git a/BRANDING_AGENT_USAGE.md b/BRANDING_AGENT_USAGE.md index 96535b9f9..55ae6a621 100644 --- a/BRANDING_AGENT_USAGE.md +++ b/BRANDING_AGENT_USAGE.md @@ -11,8 +11,8 @@ owners: ["LightSpeedWP Automation Team"] # Unified Branding Agent — Usage Guide -**Document Version**: 1.0.0 -**Last Updated**: 2026-05-29 +**Document Version**: 1.0.0 +**Last Updated**: 2026-05-29 **Related Issues**: #555 (Wave 4E Implementation) --- @@ -209,7 +209,7 @@ last_updated: "2026-05-29" # API Documentation -**Category**: [docs] · **Status**: Active · **Version**: 2.0.0 +**Category**: [docs] · **Status**: Active · **Version**: 2.0.0 **Owners**: @ashshaw, team@lightspeedwp.agency · **Last Updated**: 2026-05-29 --- @@ -372,7 +372,7 @@ last_updated: "2026-05-29" # Getting Started -**Category**: [docs] · **Status**: Active · **Version**: 1.0.0 +**Category**: [docs] · **Status**: Active · **Version**: 1.0.0 **Owners**: @ashshaw · **Last Updated**: 2026-05-29 --- @@ -655,21 +655,21 @@ jobs: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - + - name: Setup Node.js uses: actions/setup-node@v3 with: node-version: 18 - + - name: Install dependencies run: npm ci - + - name: Apply branding to changed files run: | git diff --name-only HEAD~1 | grep '\.md$' | while read file; do node scripts/agents/branding-unified.agent.js "$file" --apply done - + - name: Commit changes if: success() run: | diff --git a/BRANDING_CONFIG_SPEC.md b/BRANDING_CONFIG_SPEC.md index 678e77ddb..bc6a9bb09 100644 --- a/BRANDING_CONFIG_SPEC.md +++ b/BRANDING_CONFIG_SPEC.md @@ -11,8 +11,8 @@ owners: ["LightSpeedWP Automation Team"] # Branding Configuration Specification -**Document Version**: 1.0.0 -**Last Updated**: 2026-05-29 +**Document Version**: 1.0.0 +**Last Updated**: 2026-05-29 **Related Issues**: #33 (Parent Spec), #554 (Schema Implementation), #555 (Agent Implementation), #556 (Remediation) --- @@ -228,11 +228,11 @@ When headers are required or included: # Document Title -**Category**: [`category-badge`] -**Status**: Active | Draft | Deprecated -**Version**: vX.Y.Z -**Owners**: @owner1, @owner2 -**Last Updated**: YYYY-MM-DD +**Category**: [`category-badge`] +**Status**: Active | Draft | Deprecated +**Version**: vX.Y.Z +**Owners**: @owner1, @owner2 +**Last Updated**: YYYY-MM-DD --- @@ -523,8 +523,8 @@ governance-footer: --- -**Last Reviewed**: 2026-05-29 -**Next Review**: 2026-06-29 +**Last Reviewed**: 2026-05-29 +**Next Review**: 2026-06-29 **Maintained by**: LightSpeedWP Automation Team --- diff --git a/agents/testing.agent.md b/agents/testing.agent.md index a8eb0e123..dc937bb0d 100644 --- a/agents/testing.agent.md +++ b/agents/testing.agent.md @@ -186,7 +186,7 @@ The Testing Agent is responsible for: ```text Agent: Run all tests in this project and generate a coverage report. -Output: +Output: - Jest: 125 tests pass, 2 fail (coverage: 82%) - Playwright: 8 tests pass, 0 fail - Overall: 96% of tests passing, coverage above threshold diff --git a/ai/AUDIT-SUMMARY.md b/ai/AUDIT-SUMMARY.md index 94a5ef33f..5a716c92b 100644 --- a/ai/AUDIT-SUMMARY.md +++ b/ai/AUDIT-SUMMARY.md @@ -16,7 +16,7 @@ tags: ["audit", "agents", "planning", "improvement"] Complete audit of planner and reviewer agents identified **11 improvement issues** across three priority phases: - **Phase 1 (Critical)**: 4 issues - Fix module system, error handling, tests -- **Phase 2 (Medium)**: 5 issues - Core features, enhancements +- **Phase 2 (Medium)**: 5 issues - Core features, enhancements - **Phase 3 (Low)**: 2 issues - Polish, documentation **Total Effort Estimate**: 20-25 hours diff --git a/ai/README.md b/ai/README.md index 8395d2587..6d1ad2cdf 100644 --- a/ai/README.md +++ b/ai/README.md @@ -67,6 +67,6 @@ The canonical AI references in this folder are used by: --- -**Directory Status:** Active -**Last Updated:** 2026-05-31 +**Directory Status:** Active +**Last Updated:** 2026-05-31 **Curator:** LightSpeedWP Platform Team diff --git a/ai/improvement-plan-planner-reviewer.md b/ai/improvement-plan-planner-reviewer.md index 5dc36e49d..f20f13924 100644 --- a/ai/improvement-plan-planner-reviewer.md +++ b/ai/improvement-plan-planner-reviewer.md @@ -337,7 +337,7 @@ function hasChangelogEntry(filenames) { const changelogNames = [ 'changelog.md', 'changelog.txt', 'history.md', 'news.md', 'releases.md' ]; - return filenames.some(f => + return filenames.some(f => changelogNames.includes(f.toLowerCase().split('/').pop()) ); } @@ -379,25 +379,25 @@ const files = [ ```javascript function detectBlockers(files, stats, state, requireChangelog) { const blockers = []; - + // CI blocker if (state !== "success") blockers.push("CI checks not green"); - + // Changelog blocker if (requireChangelog && hasCodeChange(files) && !hasChangelogEntry(files)) { blockers.push("CHANGELOG.md missing"); } - + // Security blocker if (hasSecurityFileChange(files)) { blockers.push("⚠️ Security-sensitive files modified (review carefully)"); } - + // Large deletion blocker if (stats.deletions > 500) { blockers.push("⚠️ Large deletion detected (>500 lines)"); } - + return blockers; } ``` @@ -437,7 +437,7 @@ npm test -- --testNamePattern="blocker detection" 2. [ ] Search for existing comment: ```javascript - const existingComment = prComments.find(c => + const existingComment = prComments.find(c => c.body.includes('') ); ``` diff --git a/cookbook/spec-driven-workflow-example.md b/cookbook/spec-driven-workflow-example.md index aa49255f9..af54b9d3e 100644 --- a/cookbook/spec-driven-workflow-example.md +++ b/cookbook/spec-driven-workflow-example.md @@ -23,7 +23,7 @@ This example demonstrates the complete spec-driven workflow for implementing a f ### Step 1: Write the Specification -**Feature**: Post Comment Count Display +**Feature**: Post Comment Count Display **User Story**: As a reader, I want to see the number of comments on a post directly on the post card so I can identify popular discussions without clicking through. **Acceptance Criteria**: diff --git a/docs/AUDIT_PR_DOCS_663.md b/docs/AUDIT_PR_DOCS_663.md index d3c0ed42e..31b2c0734 100644 --- a/docs/AUDIT_PR_DOCS_663.md +++ b/docs/AUDIT_PR_DOCS_663.md @@ -10,9 +10,9 @@ completed_date: "2026-06-01" # PR Documentation Audit Report (Issue #663) -**Wave:** 5.3 Phase 3 -**Issue:** #663 - PR Documentation Audit & Consolidation -**Scope:** 5 PR-related files + 1 discovered canonical source +**Wave:** 5.3 Phase 3 +**Issue:** #663 - PR Documentation Audit & Consolidation +**Scope:** 5 PR-related files + 1 discovered canonical source **Status:** Complete audit with consolidation recommendations --- diff --git a/docs/AUTOMATION.md b/docs/AUTOMATION.md index dfddd7023..59870e705 100644 --- a/docs/AUTOMATION.md +++ b/docs/AUTOMATION.md @@ -85,8 +85,8 @@ If your project allows hotfixes directly to `main`, ensure validation workflows ### Canonical Label Definitions -**Ownership:** Platform/Governance Team -**Location:** `.github/labels.yml` +**Ownership:** Platform/Governance Team +**Location:** `.github/labels.yml` **Full Documentation:** [Labelling Guide](./LABELING.md) — comprehensive reference for label families, usage, and automation For complete label definitions, categories, naming conventions, and per-issue/PR labelling requirements, see [LABELING.md](./LABELING.md). diff --git a/docs/BRANCHING_STRATEGY.md b/docs/BRANCHING_STRATEGY.md index 1395fb9b5..5fb70eead 100644 --- a/docs/BRANCHING_STRATEGY.md +++ b/docs/BRANCHING_STRATEGY.md @@ -54,8 +54,8 @@ Enable squash merge only; disable merge commits and rebase merges. ## 3. Branch Naming -**Format:** -`{type}/{scope}-{short-title}` +**Format:** +`{type}/{scope}-{short-title}` Use lower-case, kebab-case, and keep it short. ### 3.1 Required Core Prefixes @@ -220,8 +220,8 @@ Extend your project sync workflow so branch prefixes set the Project **Type** fi - `proto/`, `api/`, `schema/`, `telemetry/`, `ds/` → Feature/Task - `release/` → Release PR -**Principle:** -Labels remain **routing signals** (status, priority, area/component). +**Principle:** +Labels remain **routing signals** (status, priority, area/component). Issue Types and Project fields carry the semantic meaning. --- diff --git a/docs/ISSUE_FIELDS.md b/docs/ISSUE_FIELDS.md index cb279d572..768b7ae14 100644 --- a/docs/ISSUE_FIELDS.md +++ b/docs/ISSUE_FIELDS.md @@ -24,9 +24,9 @@ stability: stable # Issue Fields Specification -**Version**: v1.0.0 -**Created**: 2026-05-31 -**Owner**: LightSpeed Team +**Version**: v1.0.0 +**Created**: 2026-05-31 +**Owner**: LightSpeed Team **Reference Config**: `.github/issue-fields.yml` --- @@ -405,9 +405,9 @@ Why both exist: --- -**Document Status**: ✅ Active -**Last Updated**: 2026-05-31 -**Next Review**: 2027-05-31 (annual) +**Document Status**: ✅ Active +**Last Updated**: 2026-05-31 +**Next Review**: 2027-05-31 (annual) **Owner**: LightSpeed Team --- diff --git a/docs/LABEL_COLOR_STRATEGY.md b/docs/LABEL_COLOR_STRATEGY.md index 4a0de9d0d..60fdc1bf6 100644 --- a/docs/LABEL_COLOR_STRATEGY.md +++ b/docs/LABEL_COLOR_STRATEGY.md @@ -23,9 +23,9 @@ stability: stable # Label Color Strategy Specification -**Version**: v1.0.0 -**Created**: 2026-05-31 -**Owner**: LightSpeed Team +**Version**: v1.0.0 +**Created**: 2026-05-31 +**Owner**: LightSpeed Team **Status**: Active --- @@ -463,7 +463,7 @@ This specification should be reviewed annually or when: --- -**Document Status**: ✅ Active -**Last Updated**: 2026-05-31 -**Next Review**: 2027-05-31 (annual) +**Document Status**: ✅ Active +**Last Updated**: 2026-05-31 +**Next Review**: 2027-05-31 (annual) **Owner**: LightSpeed Team diff --git a/docs/LABEL_INVENTORY.md b/docs/LABEL_INVENTORY.md index 179a90789..98457ba64 100644 --- a/docs/LABEL_INVENTORY.md +++ b/docs/LABEL_INVENTORY.md @@ -24,9 +24,9 @@ stability: stable # Label Inventory — Complete Reference -**Version**: v1.1.0 -**Created**: 2026-05-31 -**Last Updated**: 2026-06-01 +**Version**: v1.1.0 +**Created**: 2026-05-31 +**Last Updated**: 2026-06-01 **Total Labels**: 150+ This document provides a complete inventory of all canonical labels organized by semantic family. Use this as a reference when: diff --git a/docs/LABEL_STRATEGY.md b/docs/LABEL_STRATEGY.md index 931a06475..11550e6a0 100644 --- a/docs/LABEL_STRATEGY.md +++ b/docs/LABEL_STRATEGY.md @@ -24,9 +24,9 @@ stability: stable # Label Strategy & Governance -**Version**: v1.0.0 -**Created**: 2026-05-31 -**Owner**: LightSpeed Team +**Version**: v1.0.0 +**Created**: 2026-05-31 +**Owner**: LightSpeed Team **Reference Config**: `.github/labels.yml`, `.github/labeler.yml` --- diff --git a/docs/README.md b/docs/README.md index 224c90709..6cc8771f2 100644 --- a/docs/README.md +++ b/docs/README.md @@ -169,7 +169,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md) for documentation contribution guideli --- -*Last updated: 2026-05-31* +*Last updated: 2026-05-31* *Maintained by: LightSpeed Team* *Docs signed by 🤖 Copilot for LightSpeedWP – always fresh!* diff --git a/docs/index.md b/docs/index.md index 69f56e731..2e1403673 100644 --- a/docs/index.md +++ b/docs/index.md @@ -287,8 +287,8 @@ For recent governance changes and file relocations, see [GOVERNANCE_REVISION_LOG --- -**Last updated:** 2026-06-01 -**Maintained by:** LightSpeed Team +**Last updated:** 2026-06-01 +**Maintained by:** LightSpeed Team **Status:** Active & Current *This documentation index is kept current as part of Wave 5.3 Phase 3 governance audit (Issue #666).* diff --git a/instructions/a11y.instructions.md b/instructions/a11y.instructions.md index bd0b769fe..aa9bbf811 100644 --- a/instructions/a11y.instructions.md +++ b/instructions/a11y.instructions.md @@ -23,9 +23,9 @@ applyTo: # Accessibility (A11y) Instructions -**Scope**: Organization-wide standard for all code, content, and documentation. -**Baseline**: WCAG 2.2 Level AA (minimum requirement). -**Owner**: LightSpeed Accessibility Team +**Scope**: Organization-wide standard for all code, content, and documentation. +**Baseline**: WCAG 2.2 Level AA (minimum requirement). +**Owner**: LightSpeed Accessibility Team **Status**: Active --- diff --git a/instructions/issues.instructions.md b/instructions/issues.instructions.md index 282a2661d..7d881e179 100644 --- a/instructions/issues.instructions.md +++ b/instructions/issues.instructions.md @@ -43,8 +43,8 @@ Applies to all issue templates and issue creation workflows. Covers frontmatter, - Verify labels meet one-hot rules and align with `labels.yml`/`labeler.yml`. - Confirm templates live under `.github/ISSUE_TEMPLATE/*.md`. -This document defines how to create, label, and manage Issues in LightSpeedWP repositories. -It covers templates, issue types, labels, frontmatter, and workflows, referencing all canonical guides, configs, and automation logic. +This document defines how to create, label, and manage Issues in LightSpeedWP repositories. +It covers templates, issue types, labels, frontmatter, and workflows, referencing all canonical guides, configs, and automation logic. **All contributors, maintainers, and bots must follow these instructions for consistency, automation, and project health.** --- @@ -52,7 +52,7 @@ It covers templates, issue types, labels, frontmatter, and workflows, referencin ## 1. Use Markdown Issue Templates with YAML Frontmatter - All issue templates are Markdown (`.md`) files with a YAML frontmatter block. -- Templates are located in: +- Templates are located in: `.github/ISSUE_TEMPLATE/*.md` - **Do NOT use YAML Issue Forms**. All automation, labeling, and triage depend on Markdown-based templates. - See: [Issue Creation Guide](../docs/ISSUE_CREATION_GUIDE.md) diff --git a/instructions/pull-requests.instructions.md b/instructions/pull-requests.instructions.md index 8983d3472..363f3e683 100644 --- a/instructions/pull-requests.instructions.md +++ b/instructions/pull-requests.instructions.md @@ -89,7 +89,7 @@ See [frontmatter instructions](./documentation-formats.instructions.md) and [fro ## 3. Branch Naming Requirements -- **Follow the canonical branch naming pattern:** +- **Follow the canonical branch naming pattern:** `{type}/{scope}-{short-title}` - Examples: `feat/block-editor-colors`, `fix/theme-json-colors`, `docs/readme-update` - **Allowed prefixes** map directly to PR type and automation: @@ -114,7 +114,7 @@ See [BRANCHING_STRATEGY.md](../docs/BRANCHING_STRATEGY.md) for full details and - **Changelog section:** [Required for release automation.] - **Checklist:** Complete all items, including explicit accessibility and security checks. -4. **Write a clear title** +4. **Write a clear title** Format: `[Type] Area/Component: Brief summary (Closes #issue)` Example: `[Feature] Block Patterns: Add new testimonial pattern (Closes #201)` diff --git a/instructions/self-explanatory-code-commenting.instructions.md b/instructions/self-explanatory-code-commenting.instructions.md index 2156e82d2..c6d0e9cfa 100644 --- a/instructions/self-explanatory-code-commenting.instructions.md +++ b/instructions/self-explanatory-code-commenting.instructions.md @@ -139,7 +139,7 @@ function processUserRegistration($email, $password) { $this->validateEmailFormat($email); $this->checkEmailUniqueness($email); $this->enforcePasswordStrength($password); - + return $this->createUser($email, $password); } ``` diff --git a/scripts/README.md b/scripts/README.md index a98b91a32..3c6d2c38e 100644 --- a/scripts/README.md +++ b/scripts/README.md @@ -86,18 +86,18 @@ accDescr: "Sequential flow showing developer executing scripts, loading utilitie ## Directory Structure -- **awesome-copilot/** — Utilities for prompt/collection management and validation. +- **awesome-copilot/** — Utilities for prompt/collection management and validation. *See:* `awesome-copilot/README.md` -- **includes/** — Shared Bash helpers and test utilities. +- **includes/** — Shared Bash helpers and test utilities. *See:* `includes/README.md` -- **json-validation/** — Node.js/YAML validation scripts and tests. +- **json-validation/** — Node.js/YAML validation scripts and tests. *See:* `json-validation/README.md` - **logs/** — Log output for script runs. -- **maintenance/** — Scripts for repo maintenance, documentation, and label automation. +- **maintenance/** — Scripts for repo maintenance, documentation, and label automation. *See:* `maintenance/README.md` -- **projects/** — GitHub Projects management and automation scripts. +- **projects/** — GitHub Projects management and automation scripts. *See:* `projects/README.md` -- **utility/** — General-purpose shell and Node.js utilities for label management, logging, and validation. +- **utility/** — General-purpose shell and Node.js utilities for label management, logging, and validation. *See:* `utility/README.md` ## Core Components @@ -322,14 +322,14 @@ markdownlint scripts/**/*.md # README / docs lint ## Change Log / History -Version: 2.5 (increment when public script interfaces or includes contracts change). +Version: 2.5 (increment when public script interfaces or includes contracts change). Refer to `../CHANGELOG.md` for release context and automation evolution. ## FAQ / Troubleshooting -**Collection validation failed?** Ensure `collection.schema.json` is up to date and YAML frontmatter paths are correct. -**Scripts sourcing wrong path?** Use `$(dirname "$0")` patterns and avoid relative assumptions. -**Permission denied running script?** Add executable bit: `chmod +x