tegwick
8165f8ab71
- 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>
1.2 KiB
1.2 KiB
id, type, title, domain, repo, status, owner, topic_slug, created, updated
| id | type | title | domain | repo | status | owner | topic_slug | created | updated |
|---|---|---|---|---|---|---|---|---|---|
| ADHOC-2026-06-27 | workplan | Ad hoc fixes — 2026-06-27 | infotech | whynot-design | active | claude | custodian | 2026-06-27 | 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
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 remotegitea.coulomb.social/coulomb/whynot-design. (The#v0.2.0pin is intentional but only resolves once WHYNOT-WP-0003 T01 cuts the tag.) - Font prose — the Type section and font note still described
IBM Plexloaded 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.