docs: design-dev accepted the SVOS retrofit — the /vor-ui brief is declined, and why

The ROADMAP row requiring a /vor-ui brief predates the IA doc. With that doc,
the landed templates and the seven handoff constraints, a /vor-ui pass would
have cost the operator a serial Q&A to re-derive IA already measured. design-dev
made that argument and it is better than the row it overrides.

Also settles: we merge and restart; he works against a copy, never :8090; the
concept round goes to the operator; webfonts by CDN link with display=swap,
because the CDN-free property turned out to be accreted rather than an
invariant (checked CLAUDE.md, the non-goals and the IA doc).

Corrects a memory defect in the same commit: a postbox send note is a
point-in-time snapshot and one was promoted into persistent memory as a durable
fact about a handle's delivery mode. It was wrong within the hour.

ROADMAP.md

@@ -152,11 +152,26 @@ weighed against the v1 path and lost on purpose.
 
 ## Post-v1, already committed
 
-- **SVOS theme retrofit by `design-dev`.** Runs as a parallel track, not a v1
+- **SVOS theme retrofit by `design-dev` — HANDED OFF AND ACCEPTED 2026-09-22**
-  gate: we own the information architecture (it is driven by the measurement
+  (althing thread `01M369321KNBPZ7FYDQGZG7AXP`). Runs as a parallel track, not a
-  above), design-dev owns the visual and interaction system. The handoff is a
+  v1 gate: we own the information architecture (it is driven by the measurement
-  `/vor-ui` brief written against the landed v1 structure — the same shape
+  above), design-dev owns the visual and interaction system.
-  `hamr-dev` and `pewpew-dev` used.
+
+  ⚠ **The `/vor-ui` brief this row used to require was DECLINED, and rightly.**
+  The row predates `docs/design/information-architecture.md`; with that doc, the
+  landed templates and the seven handoff constraints in hand, a `/vor-ui` pass
+  would have cost the operator a serial Q&A to re-derive IA we had already
+  measured — the exact operator-load this project exists to reduce. The handoff
+  message is the brief. If the design system ever wants the IA different,
+  design-dev raises it and we re-measure rather than either side guessing.
+
+  Settled with it: **we merge and restart** (the deployment root stays in one
+  pair of hands); design-dev works on `svos-retheme` in his own clone against a
+  COPY of `~/booth-data`, never touching `:8090`; a concept round goes to the
+  OPERATOR before any fixup. Webfonts arrive by Google Fonts `<link>` with
+  `display=swap` and a system fallback stack — the CDN-free property was
+  accreted, not an invariant, and self-hosting is a v1.1 item because
+  `v1.0.0b1` promises no new features.
 
 ## Gate
 

persistent-memory.d/2026-09-22-v1-staged-as-a-beta-and-a-second-copy-of-the-version.md

@@ -58,6 +58,15 @@ running the real import chain under `/usr/bin/python3` 3.11.2 with no venv.
 
 The SVOS design-system retrofit went to `design-dev` (althing thread
 `01M369321KNBPZ7FYDQGZG7AXP`) — the IA is ours and settled, the visual and
-interaction system is his. ⚠ **`design-dev` is PULL-ONLY and last read
+interaction system is his. **ACCEPTED in-session within five minutes**; he
-2026-09-21T18:44Z**, so the message is queued, not picked up. Do not read
+declined a `/vor-ui` brief on the grounds that the IA doc, the landed templates
-silence as a decision.
+and the seven constraints already are one, and a `/vor-ui` pass would cost the
+operator a serial Q&A to re-derive IA we had already measured. Agreed.
+
+⚠ **A `postbox send` note is a POINT-IN-TIME SNAPSHOT, not a durable fact about
+a handle.** The send response said `design-dev: pull-only; last read
+2026-09-21T18:44Z`, and this file first recorded that as standing truth —
+including a "silence is not a decision" warning built on it. `postbox handles`
+says **`design-dev  push  reachable`**, and his reply landed in-session. Read the
+mode from `postbox handles` when it matters; never promote a send-time note into
+memory.

persistent-memory.md

@@ -38,10 +38,15 @@ _As of 2026-09-22:_
   until now — `scripts/booth` executes it before every one of the documented
   three. Now covered by `test_stdlib_only`. Same detail file carries why
   `importlib.metadata` is the WRONG version source in this repo.
-- 🔶 **SVOS design-system retrofit HANDED OFF to `design-dev`** (althing thread
+- 🔶 **SVOS design-system retrofit ACCEPTED by `design-dev`** (althing thread
   `01M369321KNBPZ7FYDQGZG7AXP`). We own the IA; he owns the visual and
-  interaction system. ⚠ He is **PULL-ONLY, last read 2026-09-21T18:44Z** — the
+  interaction system. He declined a `/vor-ui` brief — the IA doc plus the seven
-  message is QUEUED, not picked up. Silence is not a decision.
+  constraints already are one. He works on `svos-retheme` in his own clone
+  against a COPY of `~/booth-data`; **we merge and restart**, he never touches
+  `:8090`. A concept round goes to the OPERATOR before any fixup.
+- ⚠ **A `postbox send` note is a point-in-time snapshot, NOT a durable fact.**
+  The send said `design-dev: pull-only`; `postbox handles` says `push
+  reachable`, and he replied in-session. Read the mode from `postbox handles`.
 - ⚠ **U7'S CONTRACT CARRIED A MEASUREMENT THAT DID NOT REPRODUCE**, and it was
   the number the scope departure rested on. The stated rule gives 24 and 27
   groups where the table claimed 5 and 1; the table was assembled from two