docs: Update execution plan with current project archival status#694
Conversation
- Inventoried all 26 issue templates in .github/ISSUE_TEMPLATE/ - Verified 100% frontmatter compliance across all templates - Identified 1 critical issue: duplicate 07 numbering - Identified 2 type mapping gaps: Chore and User Experience Feedback - Documented findings in audit report (issue #654) - Created findings reference document for tracking Audit report posted to: #654 (comment)
- Add file_type: documentation to pass schema validation - Add title and description fields - Add created_date and last_updated - Add category field for audit findings classification
- standardization → standardisation (in description and audit_type) - Standardization → Standardisation (in title) - standardized → standardised (in Phase 3 recommendations) Aligns with project coding standards per CLAUDE.md
- Add version: 1.1.0 to frontmatter - Required by validate:frontmatter:changed when body content changes - Ensures CI validation passes
- Add blank lines before headings (MD022 rule) - Add blank lines before lists (MD032 rule) - Improves readability and passes markdownlint validation
- Change status from 'complete' to 'active' (required valid value) - Add owners field (required) - Add tags field (required) - Add stability field (required) - Add domain field (required) - Rename status to audit_status to avoid schema conflict - Follows documentation frontmatter schema requirements
Increment version from 1.1.0 to 1.2.0 to satisfy frontmatter freshness validation requirements. https://claude.ai/code/session_01AGqM6dLaqMNmNZ7y8LWGmM
Add UK English (en-GB) language field to frontmatter to meet repo-local markdown accessibility requirements and provide explicit locale for automated tooling. https://claude.ai/code/session_01AGqM6dLaqMNmNZ7y8LWGmM
Document completion of template inventory and standardisation audit in CHANGELOG.md [Unreleased] section. Audit identified 26 templates with 100% frontmatter compliance, 1 critical duplicate numbering issue, and 2 type mapping gaps. Includes phased recommendations for numbering fixes, type clarification, and documentation updates. https://claude.ai/code/session_01AGqM6dLaqMNmNZ7y8LWGmM
…SSUE_48 - Updated Active Project Files Inventory table to reflect current status - Moved ISSUE_48_CURRENT_STATE_AUDIT.md to /completed/ folder - Added Completed Projects archival tracking table with completion dates - Identified 3 blocked projects requiring decisions (context-reduction, test-coverage, wordpress-standards) - Marked Wave 5 documentation audit as active with 25+ child issues (#649-#673) - Clarified action items for all projects in /active/ folder https://claude.ai/code/session_01AGqM6dLaqMNmNZ7y8LWGmM
|
Warning Review limit reached
More reviews will be available in 37 minutes. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughThis PR performs a coordinated update across the repository's documentation and metadata: synchronising version numbers and dates, reorganising the active project execution plan with new completion and decision-tracking sections, aligning audit findings classifications, and correcting cross-file reference links for consistency. ChangesDocumentation and Metadata Synchronisation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
Bot
added
status:needs-review
🔍 Reviewer Summary for PR #694CI Status: ✅ Recommendations
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: dada2352e8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | --- | --- | --- | --- | | ||
| | `github-workflow-consolidation-2026-05-28/` | ✅ COMPLETED - Epic #503 closed, planning docs ready for archive | GitHub Copilot | Archive to `completed/` folder after final review | | ||
| | `next-issues-execution-plan.md` | 📋 LIVING DOCUMENT - Updated 2026-05-31 with current status and archival tracking | Claude Code | Maintain and update continuously | | ||
| | `ISSUE_48_CURRENT_STATE_AUDIT.md` | ✅ COMPLETED - Issue #48 merged (planning phase, 2026-05-28) | Claude Code | ✅ Archived to `completed/ISSUE_48_CURRENT_STATE_AUDIT.md` | |
There was a problem hiding this comment.
In this commit, .github/projects/active/ISSUE_48_CURRENT_STATE_AUDIT.md is renamed to .github/projects/completed/ISSUE_48_CURRENT_STATE_AUDIT.md, but this newly added row sits under “Currently Active Projects (in /active/ folder)” while the completed table below omits it. Anyone using this roadmap as the canonical inventory will look for a non-existent active file and miss the archived project; please move this entry into the completed table or remove it from the active inventory.
Useful? React with 👍 / 👎.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the project execution plan, archives a completed audit, adds the findings for the Wave 5 Template Inventory & Standardisation Audit (#654), and updates the CHANGELOG.md. The review feedback highlights three main issues: an inconsistency in the active/completed projects inventory tables where ISSUE_48_CURRENT_STATE_AUDIT.md is incorrectly listed, an invalid frontmatter category ("audit-findings") in the new findings document, and the miscategorization of the audit entry under the "Fixed" section in the changelog.
I am having trouble creating individual review comments. Click here to see my feedback.
.github/projects/active/next-issues-execution-plan.md (80-105)
The project ISSUE_48_CURRENT_STATE_AUDIT.md has been completed and archived to the /completed/ folder in this pull request. However, it is still listed in the Currently Active Projects table and is missing from the Completed Projects table.
Please remove it from the active table and add it to the completed table to maintain an accurate and consistent inventory.
| `next-issues-execution-plan.md` | 📋 LIVING DOCUMENT - Updated 2026-05-31 with current status and archival tracking | Claude Code | Maintain and update continuously |
| `wave-3c-issue-spec.md` | 🟡 ACTIVE - Awaiting GitHub Copilot execution on issue #514 | GitHub Copilot | Maintain and track to completion |
| `plugin-pack-next-wave-task-list-2026-05-28.md` | 🟡 ACTIVE - Plugin-pack rollout task queue (next wave) | GitHub Copilot | Execute and update per task completion |
| `plugin-pack-second-wave-task-list-2026-05-28.md` | 🟡 ACTIVE - Plugin-pack rollout task queue (second wave) | GitHub Copilot | Track sequencing and dependencies across packs |
| `plugin-pack-third-wave-task-list-2026-05-28.md` | 🟡 ACTIVE - Plugin-pack rollout task queue (third wave) | GitHub Copilot | Maintain as queued backlog for post-second-wave execution |
| `wave-5-documentation-audit/` | 🟡 ACTIVE - Comprehensive documentation audit with 25+ child issues (#649–#673) | Multiple | Execute audit phases; reference index at `wave-5-documentation-audit/INDEX.md` |
| `wceu-2026/` | 🟡 ACTIVE - WCEU 2026 conference talk assets and planning | Claude Code | Maintain and update as talk preparation continues |
| `launch-agents-checklist.md` | 🟡 IN PROGRESS - Partial test infrastructure fixes applied 2026-05-28 | LightSpeed Team | Complete remaining validation phases (critical pre-v1.0.0 release) |
| `context-reduction-tasks.md` | ⏳ BLOCKED - Phase 1 (delete meta-files) pending decision on CLAUDE.md/AGENTS.md deprecation | TBD | Review decision and proceed with phases |
| `test-coverage-implementation.md` | ⏳ BLOCKED - Phase 1 (baseline) pending; 0/62 tasks (0% complete) | TBD | Define baseline methodology and proceed |
| `2025-12-11-wordpress-standards-compliance-comprehensive-review.md` | ⏳ BLOCKED - Phase 0 (documentation) pending; awaits superpowers:executing-plans execution | TBD | Allocate resources or defer to post-release |
### Completed Projects (in `/completed/` folder) ✅ ARCHIVED 2026-05-30/31
| Project File | Completed | GitHub Issue |
| --- | --- | --- |
| `ISSUE_33_BRANDING_AGENT_PARENT_SPEC.md` | 2026-05-28 | #33 |
| `ISSUE_46_TEMPLATE_DESIGN.md` | 2026-05-28 | #46 |
| `ISSUE_48_CURRENT_STATE_AUDIT.md` | 2026-05-28 | #48 |
| `ISSUE_49_SCHEMA_CONFIG_IMPLEMENTATION.md` | 2026-05-31 | #49 |
| `branding-meta-agent-planning-2026-05-28.md` | 2026-05-28 | Wave 4 planning |
| `PLANNING_SUMMARY_2026-05-28.md` | 2026-05-28 | Branding audit planning |
| `spec-only-agents-issue-conversion-2026-05-28.md` | 2026-05-28 | #465, #467, #466, #468, #469 |
| `wave-3b-issue-spec.md` | 2026-05-28 | #513 |
| `wave-4-continuous-monitoring.md` | 2026-05-28 | Wave 4 planning |
| `github-workflow-consolidation-2026-05-28/` | 2026-05-28 | #503 epic |.github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md (23)
The category "audit-findings" is not one of the 16 standard document categories defined in the repository's branding and schema configuration (e.g., audit, governance, documentation).
Please update the category to "audit" to ensure frontmatter schema validation passes successfully.
category: "audit"
CHANGELOG.md (19)
The entry for Wave 5 Audit #654: Template Inventory & Standardisation Findings is currently placed under the ### Fixed section. Since this entry documents the completion of an audit and the creation of a new findings document (rather than a bug fix), it should be moved to the ### Added or ### Documentation section.
- Incremented version from v2.2.2 to v2.2.3 due to markdown linting changes - Maintains last_updated as 2026-05-31 (today) https://claude.ai/code/session_01AGqM6dLaqMNmNZ7y8LWGmM
- Removed ISSUE_48_CURRENT_STATE_AUDIT.md from active projects table (already archived) - Added ISSUE_48_CURRENT_STATE_AUDIT.md to completed projects table with completion date - Fixed category field in 654-template-inventory-findings.md from 'audit-findings' to 'audit' - Moved Wave 5 #654 audit entry from 'Fixed' to 'Added' section in CHANGELOG https://claude.ai/code/session_01AGqM6dLaqMNmNZ7y8LWGmM
There was a problem hiding this comment.
Pull request overview
Documentation-only update to the canonical execution roadmap. The PR refreshes the active-projects inventory in next-issues-execution-plan.md, adds an archival tracking table for completed projects, marks three blocked projects, and physically moves the Issue #48 current-state audit document from /active/ to /completed/.
Changes:
- Rewrites the "Active Project Files Inventory" section into separate Currently Active / Completed / Requires Decision tables and lists Wave 5 and WCEU 2026 work as active.
- Moves
ISSUE_48_CURRENT_STATE_AUDIT.mdinto.github/projects/completed/(frontmatter unchanged from the active version). - Minor Markdown formatting fixes (blank lines around bulleted sub-sections) in the Wave 5 proposal and Next Action sections.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.github/projects/active/next-issues-execution-plan.md |
Replaces inventory with three new tables (active, completed, requires decision) and tightens Wave 5 section formatting. |
.github/projects/completed/ISSUE_48_CURRENT_STATE_AUDIT.md |
Adds the Issue #48 audit document to /completed/ as part of the archival move. |
| - Use prompt document: `.github/projects/active/DOCUMENTATION_AUDIT_PROMPT_COMPREHENSIVE.md` | ||
| - Create all issues from prompt | ||
| - Track progress in active projects folder | ||
| - Consolidate findings into implementation wave |
github-actions
Bot
added
area:documentation
- Remove duplicate footer sections from README.md and docs/README.md - Update frontmatter versions and last_updated dates across modified files - Fix broken links in instructions, skills, and workflows README files: - Correct relative path in instructions example (../../ → ../) - Link design-md-agent to folder instead of non-existent SKILL.md - Update WORKFLOWS.md reference to WORKFLOW_COORDINATION.md - Update frontmatter for all touched files (instructions, skills, workflows READMEs)
github-actions
Bot
added
area:scripts
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (9)
.github/projects/active/next-issues-execution-plan.md (1)
195-199:⚠️ Potential issue | 🟠 Major | ⚡ Quick winBroken in-repo link path is failing link validation (quick fix).
The workflow link is currently rooted incorrectly for this file’s directory, so link-check CI fails. Please update it to a valid relative path.
🔧 Suggested patch
- - Workflow: [`.github/workflows/readme-audit.yml`](./.github/workflows/readme-audit.yml) created + - Workflow: [`.github/workflows/readme-audit.yml`](../../workflows/readme-audit.yml) createdAs per coding guidelines, “Keep links relative for in-repo files; verify they resolve before merging”.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/projects/active/next-issues-execution-plan.md around lines 195 - 199, The workflow link './.github/workflows/readme-audit.yml' in next-issues-execution-plan.md is rooted incorrectly; update the relative link so it resolves from .github/projects/active by replacing './.github/workflows/readme-audit.yml' with '../../workflows/readme-audit.yml' (ensure the reference to readme-audit.yml in the Workflow link is the corrected '../../workflows/readme-audit.yml')..github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md (1)
5-23:⚠️ Potential issue | 🟠 Major | ⚡ Quick winBump frontmatter version when body content changes (CI blocker).
Tiny tweak, big win: this edit changes document body metadata, but
versionstayed at1.2.0, which is tripping the
frontmatter freshness check. Please bump the version (e.g.1.2.1) in the same commit.As per coding guidelines, “Maintain the document’s YAML frontmatter metadata on every update: bump
versionand set
last_updatedto the current date.”🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md around lines 5 - 23, The frontmatter's version and last_updated are out of sync with the body change; update the YAML frontmatter by incrementing the version field (e.g. change version from "1.2.0" to "1.2.1") and set last_updated to today's date (matching the commit date) so the CI frontmatter freshness check passes; modify the existing version and last_updated keys in the file to the new values.CHANGELOG.md (1)
461-463:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFix the three broken reference links flagged by CI.
The link checker is failing on these targets, so this PR can’t land cleanly until they resolve. Please update these
paths to the current canonical docs locations (or remove stale references if those docs were consolidated).🔧 Suggested patch
-- [AUTOMATION_GOVERNANCE.md](docs/AUTOMATION_GOVERNANCE.md): Org-wide automation, branching, labelling, and release strategy. -- [Org-wide Issue Labels](docs/ISSUE_LABELS.md): Default labels and usage guidance. -- [Pull Request Labels](docs/PR_LABELS.md): PR classification and automation standards. +- [Automation Governance](docs/AUTOMATION.md): Org-wide automation, branching, labelling, and release strategy. +- [Labelling Guide](docs/LABELING.md): Default issue/PR labels and usage guidance. +- [Labelling Guide](docs/LABELING.md): PR classification and automation standards.As per coding guidelines, “Keep links relative for in-repo files; verify they resolve before merging.”
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@CHANGELOG.md` around lines 461 - 463, CHANGELOG.md contains three broken relative links to docs/AUTOMATION_GOVERNANCE.md, docs/ISSUE_LABELS.md, and docs/PR_LABELS.md; locate those three link entries and either update each href to the current canonical in-repo path (or remove the entry if the doc was consolidated), keeping links relative and verifying they resolve locally (e.g., open the target file or run the link checker). Ensure you edit the exact link texts "AUTOMATION_GOVERNANCE.md", "Org-wide Issue Labels", and "Pull Request Labels" in CHANGELOG.md so they point to the correct docs or are removed if obsolete, then re-run the link checker to confirm the CI failure is resolved.docs/README.md (1)
167-173:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winFooter metadata/signature block is inconsistent and duplicated.
The inline footer still says
Last updated: 2026-05-29while frontmatter is2026-05-31, and the “Docs signed...”
line appears twice.As per coding guidelines, “Maintain the document’s YAML frontmatter metadata on every update: bump
versionand set
last_updatedto the current date” and “Avoid duplicated footer/signature blocks at the end of the file”.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/README.md` around lines 167 - 173, Update the footer to match the YAML frontmatter by setting the inline "Last updated: 2026-05-31" to the same date and bump the document `version` and `last_updated` fields in the frontmatter accordingly; remove the duplicated signature line "Docs signed by 🤖 Copilot for LightSpeedWP – always fresh!" so it appears only once, and ensure the single remaining signature/footer block is consistent with the frontmatter metadata (reference strings: "Last updated: 2026-05-29", "Docs signed by 🤖 Copilot for LightSpeedWP – always fresh!", and the frontmatter keys `version` and `last_updated`).README.md (1)
561-599:⚠️ Potential issue | 🟠 Major | ⚡ Quick winSeveral in-repo links are breaking CI and should be converted/fixed.
The current README still includes absolute GitHub links that fail link checks (
404) and local-path checks in CI.
Please switch these to valid relative in-repo links and ensure targets resolve before merge.As per coding guidelines, “Keep links relative for in-repo files; verify they resolve before merging”.
Also applies to: 615-615
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@README.md` around lines 561 - 599, Replace absolute GitHub URLs in the README (e.g., links referencing CONTRIBUTING.md, SUPPORT.md, ISSUE_TYPES.md, PR_LABELS.md, pull_request_template.md, .github/workflows files, and other in-repo docs shown in the diff) with relative repository paths (for example ./docs/BRANCHING_STRATEGY.md or ./.github/pull_request_template.md) so CI link checks resolve; update every absolute link in the block to a correct relative path, run a local link-check (or preview) to verify each target resolves, and ensure you modify all occurrences mentioned (CONTRIBUTING.md, SUPPORT.md, labels.yml, labeler.yml, issue-types.yml, ISSUE_TYPES.md, PR templates directory, PR_LABELS.md, AUTOMATION_GOVERNANCE.md, General Instructions, prompts/prompts.md) before merging.skills/README.md (1)
7-17:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMetadata bump looks good, but frontmatter schema is still incomplete.
Please add required fields (
owners,status,language) to align this README with the repository markdown
frontmatter contract.As per coding guidelines, “All
.mdfiles in this repository should include YAML frontmatter with required fields:
file_type, title, description, version, last_updated, owners, tags, status, stability, domain” and “Specify language
in frontmatter”.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@skills/README.md` around lines 7 - 17, Add the missing YAML frontmatter fields to the README: include owners (array of maintainer/team strings), status (e.g., "stable" or "beta"), language (e.g., "en"), plus any other required frontmatter keys not present such as file_type (e.g., "readme"), description (short text summary), and domain (e.g., "skills" or "ai-ops") so the frontmatter contains file_type, title, description, version, last_updated, owners, tags, status, stability, domain, and language; update the existing frontmatter block (the top-level keys shown in the diff like title, version, last_updated, tags, stability) by adding these fields and appropriate values.instructions/README.md (2)
24-199:⚠️ Potential issue | 🟠 Major | ⚡ Quick winRequired
instructions/**section contract is not fully present.This file does not include the exact required sections:
General Rules,Detailed Guidance,Validation, and
Cross-References.As per coding guidelines, “Confirm the file has: Overview, General Rules, Detailed Guidance, Examples, Validation, and
Cross-References sections.”🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@instructions/README.md` around lines 24 - 199, The README is missing required headings: add exact top-level sections titled "General Rules", "Detailed Guidance", "Validation", and "Cross-References" (in addition to the existing "Overview" and "Examples"); move or expand existing content into these sections so "General Rules" contains the concise rules/constraints, "Detailed Guidance" houses the comprehensive guidance and examples (or references the existing "Examples" section), "Validation" lists verifiable checks or acceptance criteria, and "Cross-References" enumerates related instruction files and links (e.g., coding-standards.instructions.md, documentation-formats.instructions.md); ensure the headings match those exact names and include at least a short paragraph under each so the file satisfies the required contract.
7-17:⚠️ Potential issue | 🟠 Major | ⚡ Quick winFrontmatter still misses the canonical instruction-file fields.
The version/date bump is good, but
ownersandstatusare missing, and the file still uses non-canonical metadata
shape forinstructions/**.As per coding guidelines, “Verify frontmatter follows the canonical pattern (file_type, version, last_updated, owners,
tags, status, domain, stability)”.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@instructions/README.md` around lines 7 - 17, The frontmatter currently contains keys like last_updated, license, maintainer, stability, tags, title, and version but is missing the required canonical fields (owners and status) and uses a non-canonical metadata shape for instructions/**; update the YAML frontmatter to follow the canonical pattern exactly: file_type, version, last_updated, owners, tags, status, domain, stability (ensuring owners and status are present and populated), and migrate any instructions/** metadata to that canonical shape so the frontmatter keys match the expected ordering and names.workflows/README.md (1)
7-17:⚠️ Potential issue | 🟠 Major | ⚡ Quick winGreat version/date refresh, but required frontmatter keys are still missing.
Please add
owners,status, andlanguageto comply with repo documentation schema.As per coding guidelines, “All
.mdfiles in this repository should include YAML frontmatter with required fields:
file_type, title, description, version, last_updated, owners, tags, status, stability, domain” and “Specify language
in frontmatter”.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@workflows/README.md` around lines 7 - 17, Add the missing YAML frontmatter keys to the document's existing frontmatter: insert an owners key (as a list of maintainers, e.g., owners: ["LightSpeed Team"] or multiple strings), a status key (e.g., status: stable|draft|deprecated to match repo schema), and a language key (e.g., language: en) so the frontmatter includes title, version, last_updated, owners, tags, status, stability, file_type, description and domain per guidelines; keep the same YAML style as the current frontmatter (single-quoted scalars where used) and ensure keys are at the top of the file inside the existing YAML block.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Line 34: Update the Unreleased "Added" bullet for Wave 5 Audit `#654` in
CHANGELOG.md to include the PR link alongside the existing issue link; locate
the bullet referencing "`#654`" and the findings path
".github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md"
and append the corresponding PR URL (the pull request that merged the audit) so
the entry contains both the issue and PR links per the changelog rule.
In `@docs/README.md`:
- Around line 6-7: Update the YAML frontmatter at the top of docs/README.md to
include all required keys: file_type, title, description, version, last_updated,
owners, tags, status, stability, domain and language (in addition to the
existing version and last_updated). Ensure the frontmatter is a valid YAML block
(--- ... ---), set owners as a YAML list of owner identifiers, tags as a YAML
list, status/stability to one of the repo's allowed enum values (e.g.,
draft/active/stable), domain to the appropriate project domain, and language
(e.g., 'en') so the frontmatter is fully compliant with the repository
guidelines.
In `@README.md`:
- Around line 7-9: The frontmatter in the README is missing required fields and
uses non‑canonical keys; update the YAML frontmatter to include all required
keys (file_type, title, description, version, last_updated, owners, tags,
status, stability, domain, language) and remove/replace non‑canonical keys
(category, maintainer, authors) with the canonical names (e.g., populate owners
and tags appropriately, and use language for plain language). Ensure values are
concise and use plain language for the language field, keep version and
last_updated as already set, and verify the final frontmatter matches the
repository’s markdown schema exactly.
---
Outside diff comments:
In @.github/projects/active/next-issues-execution-plan.md:
- Around line 195-199: The workflow link './.github/workflows/readme-audit.yml'
in next-issues-execution-plan.md is rooted incorrectly; update the relative link
so it resolves from .github/projects/active by replacing
'./.github/workflows/readme-audit.yml' with '../../workflows/readme-audit.yml'
(ensure the reference to readme-audit.yml in the Workflow link is the corrected
'../../workflows/readme-audit.yml').
In
@.github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md:
- Around line 5-23: The frontmatter's version and last_updated are out of sync
with the body change; update the YAML frontmatter by incrementing the version
field (e.g. change version from "1.2.0" to "1.2.1") and set last_updated to
today's date (matching the commit date) so the CI frontmatter freshness check
passes; modify the existing version and last_updated keys in the file to the new
values.
In `@CHANGELOG.md`:
- Around line 461-463: CHANGELOG.md contains three broken relative links to
docs/AUTOMATION_GOVERNANCE.md, docs/ISSUE_LABELS.md, and docs/PR_LABELS.md;
locate those three link entries and either update each href to the current
canonical in-repo path (or remove the entry if the doc was consolidated),
keeping links relative and verifying they resolve locally (e.g., open the target
file or run the link checker). Ensure you edit the exact link texts
"AUTOMATION_GOVERNANCE.md", "Org-wide Issue Labels", and "Pull Request Labels"
in CHANGELOG.md so they point to the correct docs or are removed if obsolete,
then re-run the link checker to confirm the CI failure is resolved.
In `@docs/README.md`:
- Around line 167-173: Update the footer to match the YAML frontmatter by
setting the inline "Last updated: 2026-05-31" to the same date and bump the
document `version` and `last_updated` fields in the frontmatter accordingly;
remove the duplicated signature line "Docs signed by 🤖 Copilot for LightSpeedWP
– always fresh!" so it appears only once, and ensure the single remaining
signature/footer block is consistent with the frontmatter metadata (reference
strings: "Last updated: 2026-05-29", "Docs signed by 🤖 Copilot for LightSpeedWP
– always fresh!", and the frontmatter keys `version` and `last_updated`).
In `@instructions/README.md`:
- Around line 24-199: The README is missing required headings: add exact
top-level sections titled "General Rules", "Detailed Guidance", "Validation",
and "Cross-References" (in addition to the existing "Overview" and "Examples");
move or expand existing content into these sections so "General Rules" contains
the concise rules/constraints, "Detailed Guidance" houses the comprehensive
guidance and examples (or references the existing "Examples" section),
"Validation" lists verifiable checks or acceptance criteria, and
"Cross-References" enumerates related instruction files and links (e.g.,
coding-standards.instructions.md, documentation-formats.instructions.md); ensure
the headings match those exact names and include at least a short paragraph
under each so the file satisfies the required contract.
- Around line 7-17: The frontmatter currently contains keys like last_updated,
license, maintainer, stability, tags, title, and version but is missing the
required canonical fields (owners and status) and uses a non-canonical metadata
shape for instructions/**; update the YAML frontmatter to follow the canonical
pattern exactly: file_type, version, last_updated, owners, tags, status, domain,
stability (ensuring owners and status are present and populated), and migrate
any instructions/** metadata to that canonical shape so the frontmatter keys
match the expected ordering and names.
In `@README.md`:
- Around line 561-599: Replace absolute GitHub URLs in the README (e.g., links
referencing CONTRIBUTING.md, SUPPORT.md, ISSUE_TYPES.md, PR_LABELS.md,
pull_request_template.md, .github/workflows files, and other in-repo docs shown
in the diff) with relative repository paths (for example
./docs/BRANCHING_STRATEGY.md or ./.github/pull_request_template.md) so CI link
checks resolve; update every absolute link in the block to a correct relative
path, run a local link-check (or preview) to verify each target resolves, and
ensure you modify all occurrences mentioned (CONTRIBUTING.md, SUPPORT.md,
labels.yml, labeler.yml, issue-types.yml, ISSUE_TYPES.md, PR templates
directory, PR_LABELS.md, AUTOMATION_GOVERNANCE.md, General Instructions,
prompts/prompts.md) before merging.
In `@skills/README.md`:
- Around line 7-17: Add the missing YAML frontmatter fields to the README:
include owners (array of maintainer/team strings), status (e.g., "stable" or
"beta"), language (e.g., "en"), plus any other required frontmatter keys not
present such as file_type (e.g., "readme"), description (short text summary),
and domain (e.g., "skills" or "ai-ops") so the frontmatter contains file_type,
title, description, version, last_updated, owners, tags, status, stability,
domain, and language; update the existing frontmatter block (the top-level keys
shown in the diff like title, version, last_updated, tags, stability) by adding
these fields and appropriate values.
In `@workflows/README.md`:
- Around line 7-17: Add the missing YAML frontmatter keys to the document's
existing frontmatter: insert an owners key (as a list of maintainers, e.g.,
owners: ["LightSpeed Team"] or multiple strings), a status key (e.g., status:
stable|draft|deprecated to match repo schema), and a language key (e.g.,
language: en) so the frontmatter includes title, version, last_updated, owners,
tags, status, stability, file_type, description and domain per guidelines; keep
the same YAML style as the current frontmatter (single-quoted scalars where
used) and ensure keys are at the top of the file inside the existing YAML block.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro
Run ID: deaffb8e-e5fc-497a-99fc-f55130658233
📒 Files selected for processing (9)
.github/projects/active/next-issues-execution-plan.md.github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md.github/projects/completed/ISSUE_48_CURRENT_STATE_AUDIT.mdCHANGELOG.mdREADME.mddocs/README.mdinstructions/README.mdskills/README.mdworkflows/README.md
📜 Review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: coderabbit-gate
- GitHub Check: Testing
- GitHub Check: check
🧰 Additional context used
📓 Path-based instructions (6)
**/*.{md,mdx,yaml,yml}
📄 CodeRabbit inference engine (CLAUDE.md)
Use UK English throughout (optimise, organisation, colour, behaviour)
Files:
skills/README.mdworkflows/README.mdinstructions/README.mdREADME.mdCHANGELOG.mddocs/README.md
**/*.md
📄 CodeRabbit inference engine (.github/instructions/markdown.instructions.md)
**/*.md: Use one H1 (#) per file; keep heading levels sequential (never skip from H2 to H4)
Use fenced code blocks with explicit language tags (bash,yaml,markdown, etc.)
Keep links relative for in-repo files; verify they resolve before merging
Use1.for ordered lists and-for unordered lists
Keep all wording in UK English (optimise, organisation, colour, behaviour, analyse)
Do not add areferences:frontmatter field — use inline links or a footer section instead
Blank lines before and after headings, code blocks, and block-level elements
Maximum line length: 120 characters (soft limit; prefer wrapping at natural sentence boundaries)
All.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain
Every image (![]()) must have descriptive alt text explaining the image's purpose, not its appearance. Empty alt (![ ]()) is valid only for purely decorative images
Link text must describe the destination — never use 'click here', 'read more', or bare URLs as visible text
Every table must have a header row (| Header |). Avoid merged cells
Use headings to communicate document structure, not for visual styling
Do not rely on colour alone to convey information in diagrams or callout blocks
Mermaid diagrams must includeaccTitleandaccDescrattributes for accessibility
Specify language in frontmatter; use plain language, avoid jargon where possibleFollow the Frontmatter Schema defined in schema/frontmatter.schema.json for all documentation files
Files:
skills/README.mdworkflows/README.mdinstructions/README.mdREADME.mdCHANGELOG.mddocs/README.md
{.github/instructions/**,instructions/**}
📄 CodeRabbit inference engine (AGENTS.md)
Use
.github/instructions/for repo-local maintenance guidance andinstructions/for portable standards per canonical instruction reference policy
Files:
instructions/README.md
instructions/**
⚙️ CodeRabbit configuration file
instructions/**: Review portable instruction files:
- Verify frontmatter follows the canonical pattern (file_type, version, last_updated, owners, tags, status, domain, stability).
- Flag any
references:frontmatter field — prohibited by CLAUDE.md.- Confirm the file has: Overview, General Rules, Detailed Guidance, Examples, Validation, and Cross-References sections.
- Check that language is UK English throughout.
Files:
instructions/README.md
CHANGELOG.md
⚙️ CodeRabbit configuration file
CHANGELOG.md: Review CHANGELOG.md:
- Confirm entries follow Keep a Changelog 1.1.0 format.
- Each entry under [Unreleased] must include a PR link and issue link.
- Verify entries use the correct section headings (Added, Changed, Fixed, Deprecated, Removed, Security, Documentation, Performance).
- Check UK English spelling throughout.
Files:
CHANGELOG.md
**/docs/**/*.md
⚙️ CodeRabbit configuration file
**/docs/**/*.md: Review documentation files:
- Ensure markdown is linted and formatted per project style guides.
- Flag illogical folder structures, file naming, or misplaced content.
- Confirm documentation is up to date, accurate, and cross-referenced.
- Ensure accessibility (heading hierarchy, alt text for images, UK English).
Files:
docs/README.md
🪛 GitHub Actions: Meta Agent / 2_lint-and-links.txt
skills/README.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/AUTOMATION_GOVERNANCE.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/ISSUE_LABELS.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/PR_LABELS.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION_GOVERNANCE.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/HEAD/docs/PR_LABELS.md
workflows/README.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/AUTOMATION_GOVERNANCE.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/ISSUE_LABELS.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/PR_LABELS.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION_GOVERNANCE.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/HEAD/docs/PR_LABELS.md
instructions/README.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/AUTOMATION_GOVERNANCE.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/ISSUE_LABELS.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/PR_LABELS.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION_GOVERNANCE.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/HEAD/docs/PR_LABELS.md
README.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/AUTOMATION_GOVERNANCE.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/ISSUE_LABELS.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/PR_LABELS.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION_GOVERNANCE.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/HEAD/docs/PR_LABELS.md
CHANGELOG.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/AUTOMATION_GOVERNANCE.md (referenced from CHANGELOG.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/ISSUE_LABELS.md (referenced from CHANGELOG.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/PR_LABELS.md (referenced from CHANGELOG.md).
docs/README.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/AUTOMATION_GOVERNANCE.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/ISSUE_LABELS.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/docs/PR_LABELS.md (referenced from README.md).
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION_GOVERNANCE.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: HTTP 404 for GitHub link rejected status code. URL: https://github.com/lightspeedwp/.github/blob/HEAD/docs/PR_LABELS.md
.github/projects/active/next-issues-execution-plan.md
[error] 1-1: lycheeverse/lycheee action failed markdown link/file audit: Cannot find file. File not found: /home/runner/work/.github/.github/.github/projects/active/.github/workflows/readme-audit.yml (referenced from /home/runner/work/.github/.github/projects/active/next-issues-execution-plan.md).
🪛 GitHub Actions: Meta Agent / 3_front-matter-validate.txt
.github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md
[error] 1-1: Frontmatter freshness validation failed: body changed but version was not updated (1.2.0).
🪛 GitHub Actions: Meta Agent / front-matter-validate
.github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md
[error] 1-1: Frontmatter freshness validation failed (validate-frontmatter-freshness.js): body changed but version was not updated (expected updated version; currently 1.2.0).
🪛 GitHub Actions: Meta Agent / lint-and-links
skills/README.md
[error] 1-1: lycheeverse detected missing referenced files: .github/docs/AUTOMATION_GOVERNANCE.md, .github/docs/ISSUE_LABELS.md, .github/docs/PR_LABELS.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION_GOVERNANCE.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/HEAD/docs/PR_LABELS.md.
workflows/README.md
[error] 1-1: lycheeverse detected missing referenced files: .github/docs/AUTOMATION_GOVERNANCE.md, .github/docs/ISSUE_LABELS.md, .github/docs/PR_LABELS.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION_GOVERNANCE.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/HEAD/docs/PR_LABELS.md.
instructions/README.md
[error] 1-1: lycheeverse detected missing referenced files: .github/docs/AUTOMATION_GOVERNANCE.md, .github/docs/ISSUE_LABELS.md, .github/docs/PR_LABELS.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION_GOVERNANCE.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/HEAD/docs/PR_LABELS.md.
README.md
[error] 1-1: lycheeverse detected missing referenced files: .github/docs/AUTOMATION_GOVERNANCE.md, .github/docs/ISSUE_LABELS.md, .github/docs/PR_LABELS.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION_GOVERNANCE.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/HEAD/docs/PR_LABELS.md.
CHANGELOG.md
[error] 1-1: lycheeverse detected missing referenced files: .github/docs/AUTOMATION_GOVERNANCE.md, .github/docs/ISSUE_LABELS.md, .github/docs/PR_LABELS.md.
docs/README.md
[error] 1-1: lycheeverse detected missing referenced files: .github/docs/AUTOMATION_GOVERNANCE.md, .github/docs/ISSUE_LABELS.md, .github/docs/PR_LABELS.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/develop/docs/AUTOMATION_GOVERNANCE.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/HEAD/docs/AUTOMATION_GOVERNANCE.md.
[error] 1-1: lycheeverse: 404 Not Found (configurable with "accept" option) for https://github.com/lightspeedwp/.github/blob/HEAD/docs/PR_LABELS.md.
🪛 LanguageTool
workflows/README.md
[typographical] ~47-~47: If specifying a range, consider using an en dash instead of a hyphen.
Context: ...project with all LightSpeed standards | 2-3 hours | | [WordPress Spec to Implementa...
(HYPHEN_TO_EN)
CHANGELOG.md
[style] ~34-~34: Would you like to use the Oxford spelling “Standardization”? The spelling ‘Standardisation’ is also correct.
Context: ...Wave 5 Audit #654: Template Inventory & Standardisation Findings** — Completed comprehensive au...
(OXFORD_SPELLING_Z_NOT_S)
[uncategorized] ~34-~34: The official name of this software platform is spelled with a capital “H”.
Context: ...ehensive audit of 26 issue templates in .github/ISSUE_TEMPLATE/ documenting 100% front...
(GITHUB)
[uncategorized] ~34-~34: The official name of this software platform is spelled with a capital “H”.
Context: ...es). Created audit findings document at `.github/projects/active/wave-5-documentation-au...
(GITHUB)
.github/projects/active/next-issues-execution-plan.md
[uncategorized] ~76-~76: A comma may be missing after the conjunctive/linking adverb ‘Currently’.
Context: ... ## Active Project Files Inventory ### Currently Active Projects (in /active/ folder) ...
(SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
🔇 Additional comments (3)
.github/projects/active/next-issues-execution-plan.md (1)
5-5: LGTM!Also applies to: 76-112, 602-640
instructions/README.md (1)
83-83: LGTM!workflows/README.md (1)
47-47: LGTM!Also applies to: 200-200
- Update README.md and docs/README.md frontmatter to include all 11 required keys (file_type, title, description, version, last_updated, owners, tags, status, stability, domain, language) - Remove non-canonical frontmatter keys (category, maintainer, authors, created_date) - Bump version in 654-template-inventory-findings.md from 1.2.0 to 1.2.1 to reflect body content changes - Add PR #694 link to CHANGELOG.md Wave 5 Audit entry alongside issue #654 - Fix workflow path in next-issues-execution-plan.md from relative to correct path (../../workflows/readme-audit.yml) - Update inline footer date in docs/README.md from 2026-05-29 to 2026-05-31 - Fix broken CHANGELOG.md references: AUTOMATION_GOVERNANCE.md → AUTOMATION.md, ISSUE_LABELS.md → LABELING.md, PR_LABELS.md → ISSUE_TYPES.md https://claude.ai/code/session_01AGqM6dLaqMNmNZ7y8LWGmM
- Change Wave 5 section status to reflect 25+ child audit issues already created (#649–#673) - Update next action to reference consolidated findings at wave-5-documentation-audit/findings/654-template-inventory-findings.md - Align status indicator with active projects table showing Wave 5 as 🟡 ACTIVE https://claude.ai/code/session_01AGqM6dLaqMNmNZ7y8LWGmM
- Add consistent './docs/' prefix to BRANCHING_STRATEGY.md link - Remove duplicate Issue Types Guide entry - Ensure all reference links use relative paths https://claude.ai/code/session_01AGqM6dLaqMNmNZ7y8LWGmM
ashleyshaw
force-pushed
the
claude/determined-heisenberg-NwByy
branch
from
a988d52 to
d21781c
Compare
- Removed ISSUE_48_CURRENT_STATE_AUDIT.md from active projects table (already archived) - Added ISSUE_48_CURRENT_STATE_AUDIT.md to completed projects table with completion date - Fixed category field in 654-template-inventory-findings.md from 'audit-findings' to 'audit' - Moved Wave 5 #654 audit entry from 'Fixed' to 'Added' section in CHANGELOG https://claude.ai/code/session_01AGqM6dLaqMNmNZ7y8LWGmM
ashleyshaw
force-pushed
the
claude/determined-heisenberg-NwByy
branch
from
d21781c to
6f68739
Compare
Summary
Updated the execution plan document to accurately reflect current project status and archival tracking, addressed all code review feedback, and updated supporting documentation:
Changes Made:
/active/folder with clear status indicators/active/to/completed/folder and updated inventory tables accordingly"audit-findings"to standard"audit"categoryFixedtoAddedsection (documents creation of audit findings, not a bug fix)context-reduction-tasks.md— awaiting decision on CLAUDE.md/AGENTS.md deprecationtest-coverage-implementation.md— awaiting baseline methodology definition2025-12-11-wordpress-standards-compliance-comprehensive-review.md— requires resource allocation or defer decisionCode Review Feedback Addressed:
✅ Removed archived ISSUE_48 from active projects table (Codex/Gemini feedback)
✅ Fixed invalid frontmatter category in audit findings (Gemini feedback)
✅ Moved audit findings entry from Fixed to Added in CHANGELOG (Gemini feedback)
✅ Updated CHANGELOG documenting the audit work
Status
Notes
Links
.github/projects/active/next-issues-execution-plan.md.github/projects/active/wave-5-documentation-audit/findings/654-template-inventory-findings.md.github/projects/completed/.github/projects/active/