Refresh database diagrams and architecture documentation

Bring the independent identity platform schema diagrams and repository documentation up to date through migration 0011 (password reset), including authentication/session state, users/memberships, projects/roles/access, localized registration and reset delivery, and history/outbox boundaries. Use migrations and current code as authority. Preserve Typst as canonical diagram source and regenerate/visually inspect PDF and PNG exports. Correct stale capability/model/command statements without claiming production readiness. No commit unless requested. Verified outcome: replaced the foundation-only diagram with a six-page Typst schema reference (overview plus five domain detail pages), regenerated the PDF and standalone overview PNG, and visually inspected every final page. All tables are defined once and reused across views. Detail cards show exact columns/types/nullability, PKs, unique constraints/partial indexes, all declared FK mappings, RLS and application-vs-database relationship semantics. Updated architecture, authentication, development, frontend, organization/project/user guides and the README; added binary Git attributes for diagram exports. Validation: read-only catalog comparison against the provenance-verified synthetic development database, with all 11 migration checksums matching repository sources, confirms 24 tables, 146 columns, 24 PKs, 28 FKs, all unique constraints/indexes and RLS flags. Typst 0.15.1 PDF/PNG builds reproduce byte-for-byte; PDF text includes every table and all six pages; 48 repository-relative links/anchors across nine Markdown files pass; git diff --check passes. Application tests were not rerun for documentation-only changes. No database records, runtime code, migrations or services changed; work remains uncommitted. Acceptance: all current application tables and declared foreign keys are represented accurately with clear logical-vs-enforced relationships and secret/audit boundaries; existing documentation links and generation commands work; related architecture/authentication/development guides no longer describe superseded foundation-only behavior; exports compile and every page is visually reviewed.