Sangeetha-Grantha

Metadata	Value
Status	Completed
Version	1.2.0
Last Updated	2026-07-18
Author	Sangeetha Grantha Team

TRACK-125: Documentation Validation and Repair

Goal

Systematically validate all markdown documentation files in the repository against the Documentation Guardian rules (headers, code block fences, relative links) and perform automatic repairs to bring the repository into full compliance.

Implementation Plan

• Relative links — done. Repaired 131 broken relative links across 35 files (104 in application_documentation, 27 more in conductor/tracks, .agents/skills and archive/tools). Causes: wrong relative depth in archived docs, files moved under TRACK-078 / ADR-013, and files renamed or split by the TRACK-073–076 refactors. Link text was left untouched so history stays legible; only hrefs moved.
• Link validation is enforced. tools/check-doc-links.py (make check-docs) resolves every relative link, stripping :line suffixes and #anchors, and skips fenced code so documented templates are not treated as references. Wired into CI as the docs job — it needs no toolchain, so it is the cheapest gate in the matrix.
• Headers. Validated and repaired the metadata table (Status / Version / Last Updated / Author) across all documentation and active process files per Guardian §1. Prepared standard tables for 20+ files.
• Code block fences. Validated and repaired all un-tagged code block fences by appending the default text language specifier.
• Re-run validation and record the result. Ran the updated validation walk. Scanned 238 active documentation files and found 0 violations remaining.

Notes

All document checks now run cleanly, and the repository conforms to the spec-driven documentation standards.

References

• Documentation Guardian skill
• tools/check-doc-links.py · make check-docs · .github/workflows/ci.yml (docs job)