Fix: Pre-existing CI Failures — Broken Links and Frontmatter Validation

[ashleyshaw]

Summary

This issue documents pre-existing CI failures discovered during Wave 5.2.4 audit work (PR #702). These failures are unrelated to the audit report changes and represent technical debt in README files and project configuration files.

Scope

1. Broken Links in README Files

The following README files contain broken links to documentation:

• instructions/README.md — broken links to instruction files (targets in instructions/)
• skills/README.md — broken links to skill documentation (targets in skills/)
• workflows/README.md — broken links to workflow files (targets in workflows/)

Fix: Verify link targets exist and update broken paths.

2. Frontmatter Validation Errors in .github/projects/ Files

Multiple issue files in .github/projects/ have invalid frontmatter:

• Missing required fields — some files lack status, language, or other schema-required fields
• Invalid date formats — unquoted YAML dates (e.g., created_date: 2026-05-31) parsed as date objects instead of strings; schema expects strings
• Invalid enum values — status field contains values outside allowed enum: ["active", "deprecated", "draft", "experimental"]

Fix:

1. Quote all date fields: created_date: '2026-05-31'
2. Add missing required fields: status, language, domain
3. Use only valid status values from allowed enum
4. Validate all files with: npm run validate:frontmatter

Related Issues

• [Child of #651] Audit: Issue Creation Docs - Consolidate Overlapping Files #662 — Issue creation documentation consolidation (parent)
• docs(#685): Add type-to-project-field mapping and decision tree #700 — Label strategy and type mapping documentation updates (PR)
• audit(#662): Issue creation documentation audit and consolidation strategy #702 — Audit report consolidation (blocked by these failures)

Next Steps

1. Audit all README files for broken link targets
2. Run frontmatter validation against .github/projects/ files
3. Fix all failures per remediation steps above
4. Confirm npm run validate:frontmatter passes cleanly
5. Link this issue in related PRs for context

---

Priority: Normal
Domain: Governance
Type: Chore

[linear-code]

LS-852

[ashleyshaw]

Issue created to document pre-existing CI failures discovered during Wave 5.2.4 audit work.

This issue is linked to related PRs #700 and #702, which contain valid changes but are blocked by pre-existing failures in README files and project configuration files that are unrelated to these PRs.

See issue description for full details on broken links and frontmatter validation errors.

---

Generated by Claude Code