Deck — Decisions page + project colors (v3)

# v3 — Decisions page + project color coding

Decisions = human-in-the-loop queue: every agent question (runplan HALT, decisions-inbox, preflight) lands here as a collapsed row — answer inline with one click or free text; click the title to expand full context. Project colors: auto-assigned with maximum hue separation (settings panel bottom), used everywhere — left edge + tag here, same colors on Overview cards, Map chips, Inbox.

Deck
Overview Inbox5 Decisions4 Map
Operations
Plans1▶ 1⛔ Agents8 CI & Runners1 Bots4
Health
Limits & Spend Gates Scoreboard
System
Settings

## Decisions

4 waiting · oldest 42m · answering unblocks the run immediately
jump / answer… `⌘K`
All 4 multideal 2 zync.is 1 platform 1 Snoozed 1
multideal
Pin drizzle-orm at 0.44 or bump to 0.45?
runplan dep-provisioning · wave 3/4 · task drizzle-pin-decision · engine blocked on answer
waiting 42m▲ collapse

##### Full question from agent

Lockfile has drizzle-orm 0.44.2. 0.45.0 released 3 days ago and changes the pgTable generic signature — 14 call sites in packages/db would need the new form. Migration journal re-baseline (M2) is planned but not landed; bumping now means the re-baseline plan must be regenerated against 0.45 types. Pinning keeps the M2 plan valid but defers the breaking bump to after go-live.

##### Data

    affected: packages/db/src/schema/*.ts (14 sites) · migration journal: 131 sql / 77 entries (broken, M2 pending)
    0.45.0 changelog: pgTable generics, $inferSelect rename · security advisories: none on 0.44.2
    CI: both versions typecheck-clean on branch probe-drizzle-045 (run #4788 ✓)

##### Context

plan runplan-dep-provisioningjournal runstate/runplan-dep-provisioning.log.jsonl:412asked by wave-3 implementerimpact if wrong redo M2 plan (~2h agent)

##### Answer

zync.is
Payment gateway: Stripe or PayPlus? (P0.3 — blocks Z3)
plan-preflight · one gets built, the other two adapter stubs get deleted
waiting 2d▼ expand
multideal
e2e checkout spec failed twice — quarantine the spec or block the merge queue?
babysitter · CI #4821 · same assertion both runs, screenshot attached
waiting 18m▼ expand
platform
.warnignore addition requested: esbuild "import.meta" warning from vite 6 dep
gate0 · upstream, not bumpable yet · needs your benign-justification sign-off
waiting 1h▼ expand

#### Settings → Projects → Colors (auto-assigned, editable)

multideal auto · hue 1/12#7aa2f7
zync.is auto · hue 5/12#ff9e64
press.zone auto · hue 9/12#4fd6be
platform auto · hue 3/12#bb9af7
Botmaster auto · hue 7/12#e0af68
security-gate auto · hue 11/12#f7768e
Assignment: 12-hue OKLCH wheel walked in max-distance order (1,5,9,3,7,11,…) so consecutive projects are never neighbors; when all 12 are taken, second rotation reuses hues at shifted lightness/chroma (still ≥ ΔE 20 apart). Override any swatch manually; both themes derive light/dark variants from the same hue token.
Decisions sources: harness decisions-inbox + steer-inbox (dynwf-ux plan) + runplan HALTs + gate sign-offs — one queue, answer posts back to the control API. Reply in terminal: approve or adjust.