feat(widget): campaign-digest built-in — the home-dashboard digest over the campaign routes (#678)

[aarontrowbridge]

Closes #678

What

The first consumer of the campaign routes (#662): a built-in home-dashboard widget — the Campaign Inspector's digest surface, shipping before the Work Column tab per the approved Armonia design ("home digest widget ships FIRST — zero navigation").

The tile: eyebrow (campaign name) · one-line objective (ellipsized) · up to 3 verdict chips from the newest ledger (unit + leading status token, keyword-toned: DONE/MERGED → success, BLOCK/FAIL → danger) · the needs-you line (§4 blocked's first line — "⚠ needs you — …" or muted "nothing blocked") · click composes Open the campaign <slug> into the chat via amico.prompt.

Discipline: esc() on every interpolation; --amc-* tokens only (no hex, no rgb, no localStorage — the sandboxed frame forbids it); empty state on no campaigns / fetch failure / ok:false; onConfig/onTheme re-renders behind an epoch guard; ACTIVE pick is case-insensitive with newest-overall fallback (documented). Unread-state persistence is explicitly v2 (needs a durable last-seen signal the opaque-origin frame can't own).

Beyond the repo's string-level test decision, behavioral evidence: the emitted module was executed against a fake bridge across 7 scenarios — active pick, fallback, empty states, fetch rejection, click composition, and a hostile <script> objective rendering fully escaped.

Acceptance criteria — evidence (all six pass; director-verified)

• Registered in BUILTIN_SOURCES after jump-back-in, valid tile manifest — registry tests 12/12 + HTTP smoke (/amicode/widgets lists both ids)
• Fetches routes, renders active campaign, empty-state on none — string pins + scratch execution (3 scenarios)
• Fetch failures → empty state — bridge rejection + ok:false scenarios
• Click → amico.prompt('Open the campaign <slug>') — asserted in scratch execution
• esc throughout, --amc-* only — vitest pin + hostile-input render
• Registry/content-hash consistency — idempotence test + /amicode/widgets + widget-code route bodies served

Director gates (independently run)

• Typecheck clean; full suite 1774 passed / 3 failed — byte-identical to the pristine origin/main baseline (the known pasqal/terminal pre-existing set); widget tests 12/12; contract suite 74/74
• Sequencing note: merge feat(service): campaign routes — GET /amicode/campaigns + /amicode/campaign over the session ledgers (#658) #662 first — this slice consumes its documented contract and imports nothing from it; runtime wiring (routes + overlay allowlist) completes at that merge. Until then the tile renders its empty state at runtime.
• One test-contract change, per the BUG: Vault knowledge-graph note click opens blank markdown #447 precedent: the fork pin (v1.18.10-amicode.18) predates this built-in, so the three registry-projecting golden entries drift — normalizeBuiltinWidgetDrift strips it from both sides until the next pin re-record.

Merge

Awaiting human review per campaign discipline. Merge order: #662, then this. CI runs on this PR.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 4e02a42e-a474-40ab-b1c7-577d90527e60

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}