[Docs] Drift audit /docs/architecture against current codebase state

[ProfessorPolymorphic]

Context

app/docs/architecture/page.tsx (231 LOC) has been spot-fixed three times during Sprint 4 (PR #90 dropped presentations/ + RevealDeck.tsx; PR #91 dropped _archive/; PR #93 dropped data.ts). Worth a holistic re-read for other staleness rather than relying on incremental sweeps.

Areas to verify

• Project structure ASCII diagram: now reflects the post-Sprint-4 tree but should be cross-checked against the actual app/, lib/, components/, db/ directory listings.
• Component listing: confirm every component named still exists and any newly-meaningful components (e.g. Callout, MetricCard, ProjectTable, IssueCard, governance explorer components) are present where useful.
• lib/ listing: should not list data.ts (already removed) but should reflect current modules — portfolio.ts, standards-watch.ts, artifacts.ts, builder-guide-data.ts, intake-config.ts, similarity.ts, work.ts, governance/*, etc.
• Database section: confirm migration count is current (migrations/001 → 005 post-Sprint-2; 005 was the friction-ledger + blockers migration).
• Architecture diagram (top of page): still accurate, but verify the API route list matches app/api/*.
• Data flow narrative: any references to the friction ledger, blockers table, ClickUp boundary, or /internal auth-gated views worth adding (Sprints 2–3a content that postdates the original doc).

Acceptance criteria

• All ASCII trees and component/module listings match current state
• Architecture diagram reflects current API route surface
• Friction ledger / blockers / /internal mentioned at least at the boundary level
• Migration count accurate

[ProfessorPolymorphic]

Closed by #321.

The page described the migration-003 schema — five tables, no lifecycle columns, no friction ledger, no ClickUp projections, no request registry, no agent log. It now covers all 17 tables (verified by diffing CREATE TABLE across db/migrations/* against the page), the ~40 columns added to applications since, and why the enums deliberately carry no CHECK constraints.

The component diagram also showed a browser-calls-API architecture that was never true of most of this site; it now states that pages are server components reading lib/* directly, with route handlers reserved for mutations, the agent, and the sync trigger.