docs(book): publish complete source-grounded edition

[BenAlaa]

Outcome

Publishes the complete source-grounded T3 Code architecture book as a 40-chapter public edition. Readers can follow one causal route from ownership and boot through the durable kernel, five harness integrations, work lifecycle, clients, remote access, distribution, and architectural synthesis.

Scope

• Add five front-matter routes and Chapters 1–40 in eight ordered parts.
• Explain the provider adapter contract, Codex, Claude, Cursor, Grok, OpenCode, and both usage-accounting systems.
• Cover tasks, plans, context, memory, permissions, checkpoints, worktrees, terminals, files, previews, VCS, and pull requests.
• Cover shared web, desktop, and mobile semantics plus remote access, reconnect, release, updates, and observability.
• Add interactive labs, Mermaid exploration, fixed chapter navigation, collapsible contents, source cards, keyboard operation, reduced motion, and print fallbacks.
• Add the public README, editorial plan, contribution guide, complete test suite, and GitHub Pages workflow.

Non-goals

• This edition does not replace the upstream product guide or claim behavior beyond the pinned revision.
• Roadmap observations remain classified as shipped, latent, transitional, inferred, or explicit future work.
• No third-party analytics or runtime network dependency is added to the local book.

Evidence

• Canonical source lock: sources/t3code.lock.json at fa219001dc2f14cfd9c7774c2c03c153359144be
• Primary anchors:
  • sources/excerpts.manifest.json
  • sources/references.manifest.json
  • src/generated/excerpts.json
  • scripts/validate-sources.mjs
• Claim class notes: verified behavior, documented intent, inference, and future/proposed claims are explicitly separated throughout the book.
• Discrepancies or uncertainty: known source/documentation disagreements are presented as bounded discrepancies instead of silently reconciled.

Visuals and interaction

The edition includes source-linked figures and reader-controlled labs for command boundaries, receipts, projections, recovery, provider routing, usage, work lifecycle, clients, remote access, releases, and complete traces. Controls are keyboard accessible, respect reduced motion, retain no-JavaScript fallbacks, and provide printable static states. Mermaid diagrams support zoom, two-axis pan, drag, reset, and expanded mode.

Validation

• npm test — 55/55 passing
• npm run build — 46 pages built; 45 indexed
• npm run source:check — 184 excerpts, 525 references, 1,844 production files, and 881 test files verified
• Internal routes, source links, and headings checked
• Claims reviewed at the pinned revision
• Accessibility and static print state checked for changed visuals
• All branch commits and reachable objects scanned for excluded identifiers

Review focus

Focus on causal reading order, the separation between durable acceptance and external completion, the distinction between live context telemetry and transcript usage accounting, and whether every interactive artifact preserves its static evidence trail.