docs-synclisted

# Docs Sync - Documentation Surface Consistency Detects when key documentation surfaces have diverged from each other or from the actual codebase state. Catches contradictions, stale claims, merge conflict markers, and version mismatches across the documentation surface. **All commands run to completion autonomously.** **Config:** `.codex/skills/project.toml` - doc surfaces in `[docs-sync]` --- ## Commands | Command | Usage | Purpose | |---------|-------|---------| | `check` | `$docs-sync` or `$docs-sync check` | Full consistency scan | | `surface` | `$docs-sync surface README.md` | Check a single doc against code | | `fix` | `$docs-sync fix` | Auto-fix trivial inconsistencies | Default to `check` if no command given. --- ## Setup: Read Config Before any command: 1. Read `.codex/skills/project.toml` 2. Extract `[docs-sync]` section if present ### Config schema ```toml [docs-sync] # Documentation surfaces to monitor. Grouped by priority tier. [docs-sync.tier1] # High-traffic docs - checked thoroughly files = ["AGENTS.md", "README.md", "STATUS.md", "CONTRIBUTING.md"] [docs-sync.tier2] # Planning and architecture docs - checked for key claims files = ["docs/architecture/*.md", "docs/planning/*.md"] # Claims to cross-reference across all surfaces. # Each claim type maps to a source of truth in code. [docs-sync.claims] version = { source = "package.json:version", pattern = "version.*?(\\d+\\.\\d+\\.\\d+)" } schema-version = { source = "src/config.h", pattern = "SCH