📋 Tiny Wire v1.5 follow-ups — priority & build order (start here)

[LinzLos]

The shared, visible plan for the v1.5 green→cobalt follow-ups. Open this first — it's the priority + build order. Numbers are identity; the wave plan is the execution order.

Context

v1.5 reserved green strictly for trust states (--success) and moved brand/action to cobalt (--brand). These three issues are the follow-ups. The framing: #2 and #3 are symptoms; #1 is the cure.

Wave plan

▶ Wave 1 — parallel-safe (disjoint files, run together)

• Reconcile standalone demo (Tiny Wire.html) inline tokens with lib/globals.css #2 — Reconcile demo inline tokens with lib/globals.css · Tiny Wire.html · chore P2
• Re-scope a11y finding F-014 after brand moved to cobalt (green-text → --success) #3 — Re-scope a11y finding F-014 (green-text → --success) · docs/a11y.html · documentation P3

▶ Serialize-alone (shared/global files — run one at a time)

• Gated propagation: design-system change → human review → standalone demo (epic) #1 — Gated propagation pipeline → demo (epic) · lib/globals.css, lib/components.css, Tiny Wire.html, build/ · enhancement epic P1

Dependencies

• #1 ──▶ #2 (soft): Reconcile standalone demo (Tiny Wire.html) inline tokens with lib/globals.css #2 is a tactical fix you can do now; if Gated propagation: design-system change → human review → standalone demo (epic) #1 lands first, Reconcile standalone demo (Tiny Wire.html) inline tokens with lib/globals.css #2 closes as obsolete.
• Re-scope a11y finding F-014 after brand moved to cobalt (green-text → --success) #3 is independent.
• Hand-offs: none (single owner).

Invariant

Within any wave, no two issues share a file → safe to run one agent per issue concurrently, each in its own issue<NN> git worktree.

Suggested order of play

1. Now (before more prototype work): Reconcile standalone demo (Tiny Wire.html) inline tokens with lib/globals.css #2 ‖ Re-scope a11y finding F-014 after brand moved to cobalt (green-text → --success) #3 — parallel, disjoint.
2. Deliberately, not under deadline: Gated propagation: design-system change → human review → standalone demo (epic) #1 — the architecture that makes Reconcile standalone demo (Tiny Wire.html) inline tokens with lib/globals.css #2 never recur.