chore: trailing whitespace cleanup

.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)

.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

.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

.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

.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

.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

.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

.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

.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

.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

.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).

.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!

.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!

.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)

.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

.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

.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).

.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.

.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.
 ```
 

.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

.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)

.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

.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

.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*