Task · SKT-0005.15

Make the documentation site locally buildable or verifiable

Description

A clone contains Markdown and a docs.toml navigation fragment but not the externally generated Zensical configuration or a supported local preview command. Give contributors and agents a repository-local way to validate navigation, links, and rendered pages.

Acceptance Criteria

Definition of Done

Implementation Plan

  1. Implement a public-dependency repository-local documentation validation/preview path that understands docs.toml.

  2. Validate navigation, relative links, and expected special pages, then wire the check into the authoritative CI path.

  3. Document fresh-clone usage and verify it from an isolated checkout.

Implementation Notes

Added a Python 3.11+ standard-library docs validator covering docs.toml navigation, authored-page coverage, relative Markdown/HTML links, and docs/404.md. Added make docs-check, wired it before docs dispatch, and documented the external-hub boundary. Focused tests, deliberate broken fixtures, fresh-clone validation, and diff checks passed; external Zensical rendering remains hub-owned.

Integrated CodeRabbit review found malformed-site handling and Python-version enforcement gaps. Added a clear non-table site error, fixture coverage, a local 3.11+ check, and pinned CI Python 3.11. Wave integration make gate and dry-run inventories passed; no blueprint schema regeneration was required.

Final Summary

Landed in e98411b: public-dependency docs validation for navigation, authored-page reachability, links, and 404, enforced locally and before docs sync. Verified with four fixtures, deliberate failure cases, Python 3.9/3.13 checks, fresh-clone simulation, CodeRabbit, make gate, and inventories.

References

View the source file on GitHub