add(DESIGN.md, handoffs): the federal design system document lands, with Blake's Phase 0/1 handoff

The federated design system finally has a home in this repo. DESIGN.md v0.1.0.1
arrives at the root as the federal token source of truth — one token vocabulary
across sixteen sovereign micro-frontends, three modes, a two-tier token spine,
and an F1–F11 runtime contract at version 2.1.

Its frontmatter is not documentation, it is machine-read configuration: the
member registry that scripts/design-drift.mjs consumes, carrying each member's
prefix, root class, documentation tier, remediation debt, and registration
status. splash is explicitly out_of_federation — a separate marketing design
system, never a token source.

Root placement follows three independent signals: the handoff's own next-prompt
reference to augment-it/DESIGN.md, the local_doc_path of <member>/DESIGN.md
which implies the root document is the federal one, and the maintain-design-md
convention. No collision with splash/DESIGN.md, which the federal document
names as out of federation.

New context-v/handoffs/ folder, first entry:
- Federated-Design-System-Phases-0-and-1-Shipped-Nothing-Seen.md — Blake's
  2026-08-01 handoff, filed verbatim with frontmatter and a filing block added.
  handoffs/ is the canonical context-vigilance folder for end-of-session state
  capture, and a cross-machine, cross-engineer handoff is its textbook case.
  Renamed to Train-Case; source_document preserves the phase-8 → phase-10 →
  phase-14 chain reference Blake maintains on his machine.

The filing block records a gap that matters more than the document does. None
of the work the handoff describes is in this repository — verified against all
22 refs, local and remote. scripts/design-drift.mjs is absent entirely,
packages/theme/theme.css is 213 lines here against the 318 claimed, the
design:drift and design:contrast scripts are not in package.json, and all four
referenced context-v documents are missing. Section 5 calls the documentation
untracked; the code is equally untracked. Phases 0 and 1 exist only on the
Windows machine named in the frontmatter.

So the document the drift script reads is now here, and the drift script is not.
Every figure in the handoff was really measured and none of it is reproducible
here until that work is pushed.

Also included:
- The handoff independently confirms, from static analysis of the build, the
  same broken-turbo finding reached the same day from the codebase graph —
  including the Turbo v1 "pipeline" key. Cross-referenced to the note rather
  than restated.

Files changed:
- DESIGN.md (new, 1633 lines)
- context-v/handoffs/Federated-Design-System-Phases-0-and-1-Shipped-Nothing-Seen.md (new)

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019a8tSPbFdvF1pKtADnWyDg

Author: mpstaton