Do a freshness pass over docs/ (and the top-level *.md: README, TODO, PROGRESS, BACKLOG) against how the system actually behaves now. Known-stale hot spots to check first: - PROGRESS.md — only partially caught up (entries between 2026-06-16 and 2026-07-06 were not backfilled: interactor import, vector Phases 0-2, df65 retirement, the provider-protocol milestone, session-lifecycle work). - docs/architecture.md — recently grew the provider-protocol section; verify the surrounding seam/provider text still matches (ProviderProtocol + config.chat/embed facade, no api_style branching in consumers). - Anything the "claude" results flagged (session isolation, capability, runner docs) that describes retired mechanisms.

Method: use semantic_search / vec-search to pull the doc chunk for a behavior, compare to the code/current reality, and correct. This operationalizes the accuracy axis already in docs/review-checklist.md.

Acceptance: - A pass over docs/ + top-level *.md with each stale claim either corrected or ticketed. - PROGRESS.md backfilled (or an explicit note of the gap window with pointers). - A short docs/ freshness note recorded (date of last audit).

Relates to docs/review-checklist.md (accuracy axis) and the summary-as-staleness-detector ticket.