Docs Consistency

Docs explain implementation; they do not rewrite design. Flow: design intent (What/Why) → implementation survey (How) → docs update (explanation).

Phase 1: Extract Design Intent

Read design docs (docs/internal/) and write tmp/docs-review/{feature}-intent.md capturing What, Why, constraints, and what users need to know.

Phase 2: Survey Implementation

Identify implementation files, public API, defaults, and edge cases. Write tmp/docs-review/{feature}-implementation.md.

Phase 3: Diff Against Current Docs

Compare intent + implementation memos against current docs. Build a diff table: