docs: fix README consumer on-ramp (host + fonts); fold tracking into WP-0003 T06

- README: correct the Node-tooled install host (placeholder gitea.example.com →
  gitea.coulomb.social/coulomb/whynot-design) and rewrite the Type/font prose to
  match the actual tokens (system font stacks, no webfont; Plex kept as history).
- WHYNOT-WP-0003 T06: add a "Tracking whynot-design from a consuming repo" README
  section (pin → inspect → drift → adopt) and reconcile the install pin once
  T01/T02 publish a tag.
- Record the README fixes as ADHOC-2026-06-27.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

workplans/ADHOC-2026-06-27.md

@@ -0,0 +1,38 @@
+---
+id: ADHOC-2026-06-27
+type: workplan
+title: "Ad hoc fixes — 2026-06-27"
+domain: infotech
+repo: whynot-design
+status: active
+owner: claude
+topic_slug: custodian
+created: "2026-06-27"
+updated: "2026-06-27"
+---
+
+# Ad hoc fixes — 2026-06-27
+
+Low-risk opportunistic fixes completed directly during the WHYNOT-WP-0003 session.
+
+## README consumer-onboarding accuracy
+
+```task
+id: ADHOC-2026-06-27-T01
+status: done
+priority: medium
+```
+
+Two staleness fixes in `README.md` found while reviewing the consumer on-ramp:
+
+- **Quick-start install host** — the Node-tooled install line used the placeholder
+  `gitea.example.com/whynot/...`; corrected to the real remote
+  `gitea.coulomb.social/coulomb/whynot-design`. (The `#v0.2.0` pin is intentional but
+  only resolves once WHYNOT-WP-0003 T01 cuts the tag.)
+- **Font prose** — the Type section and font note still described `IBM Plex` loaded
+  from Google Fonts, contradicting the actual tokens, which switched to system stacks
+  (`ui-sans-serif`/`ui-monospace`/`ui-serif`) in WHYNOT-WP-0002 T06. Rewrote both to
+  state the current reality (no webfont loaded) and keep the Plex rationale as history.
+
+Deeper consumer-tracking docs (pin → inspect → drift loop) are folded into
+WHYNOT-WP-0003 T06, not here.

workplans/WHYNOT-WP-0003-downstream-consumption.md

@@ -194,6 +194,15 @@ example consuming-repo fixture under `examples/` (or `docs/`) that exercises the
 loop against a fixed version, so the workflow is copy-pasteable. Cross-link from
 `README.md` and `MultiFrameworkSupport.md`.
 
+As part of this task, add a **"Tracking whynot-design from a consuming repo"**
+section to `README.md` (next to *Quick start*) — the README currently documents only
+*component usage*, not how a consumer pins a version, inspects it (`ir/INDEX.md` /
+`ir/manifest.json`), runs `drift`, and adopts the new sync-point at its own pace.
+Point it at the full guide above. While there, finish the install-line correctness
+the 2026-06-27 adhoc started: the `pnpm add …#v0.2.0` pin only resolves once T01 has
+cut the tag and T02 has published, so reconcile the README to the real, tagged
+registry coordinates as those land.
+
 ---
 
 ## Phase 3 — Inspectability