Queue this work after the dashboard effort in #210 is complete and merged. Do not begin the comprehensive audit as part of that PR.
Audit the full documentation set against an exact current implementation baseline: ADRs, DDD documents, internal architecture/engineering guides, and user-facing documentation. Treat source code, tests, actual command/help output, current integrations, and authoritative upstream contracts as evidence; documentation is not proof of implementation.
Scope:
- Inventory and classify all documentation and its intended audience/authority.
- Reconcile architectural decisions and DDD boundaries with implementation, including Proposed/Accepted/Implemented/Superseded status and dates.
- Find stale, contradictory, overstated, unsupported, or missing claims across guides, API/data contracts, configuration/ownership rules, host capabilities, safety boundaries, and UI behavior.
- Validate commands, examples, defaults, prerequisites, configuration paths, links, source citations, screenshots, and troubleshooting guidance.
- Distinguish configured/cached state from runtime facts, and supported behavior from experimental or planned capabilities.
- Update documentation coherently without silently modifying code to make old claims true; record implementation defects separately.
Acceptance:
- A coverage matrix lists audited documents, implementation evidence, findings, and disposition.
- Findings are prioritized by user impact and authority/safety risk, with concrete source references.
- Corrected documentation agrees across ADR, DDD, internal, and user-facing layers.
- Runnable examples and documentation checks are validated where practical; unavailable verification is explicitly recorded.
- An evidence-backed PR records the exact baseline, validation, and remaining gaps.
Requested as a separate follow-up during #210. The current dashboard PR remains responsible only for documentation directly affected by its own changes.
Queue this work after the dashboard effort in #210 is complete and merged. Do not begin the comprehensive audit as part of that PR.
Audit the full documentation set against an exact current implementation baseline: ADRs, DDD documents, internal architecture/engineering guides, and user-facing documentation. Treat source code, tests, actual command/help output, current integrations, and authoritative upstream contracts as evidence; documentation is not proof of implementation.
Scope:
Acceptance:
Requested as a separate follow-up during #210. The current dashboard PR remains responsible only for documentation directly affected by its own changes.