Feedback #72: Use attention emojis on daemon messages that need an operator response so they're easy to scan

Merged to master by flower-orchestrator (daemon 29). Merge commit 22125ce (worker commit 9ca5c1e, branch flower/158-attention-emojis). App\Support\AttentionSignal (3-glyph vocab: ❓ awaiting answer, 🛑 blocking, ✋ needs you) + accessible <x-ui.attention> component (role=img + aria-label), wired into FeedService (per-entry token gated on needs_you), the shared x-decisions.card (covers /decisions + rooms + brief open-questions), and inbox open notes. Blade-only (no asset rebuild). tests/Feature/Decisions/IndexTest.php was auto-merged cleanly with #178's earlier edits (non-overlapping) — combined suite green: 988 tests / 986 passed / 2 skipped / 0 failed. JUDGMENT CALL flagged by worker: go/no-go confirm decisions fold into ❓ rather than a distinct 🟢 glyph (a green/A reads as "resolved" on a still-open call); offered a 4th glyph if the operator prefers.

Shipped attention-emoji treatment for operator-directed items. Branch flower/158-attention-emojis @ 9ca5c1e (off master), suite 973/974 green (1 pre-existing skip), pint clean. Design — single source of truth `App\Support\AttentionSignal`: a deliberately tiny 3-glyph vocabulary — ❓ "Awaiting your answer" (open question/decision) · 🛑 "Blocking — needs you" (blocking call, MIA daemon, stuck brief) · ✋ "Needs you" (compaction request/needed, open feedback, open inbox note). Holds all the needs-response gating: forFeed(classification,severity,kind), forDecision(isOpen,isBlocking), forNote(status). Rendered everywhere via a new `<x-ui.attention>` component (role="img" + aria-label/title so it's spoken, not emoji-only; renders nothing for routine/FYI so the highlight stays meaningful). Surfaces wired (the "needs operator response / open" flags that gate each): - Operator feed — FeedService.entry() precomputes an `attention` token per entry, gated on the feed's own `needs_you` classification (so emoji + "Needs you" lane never disagree). Rendered in the rooms/show "Needs you" lane + main stream, and the rooms/index lobby "needs you" pill. - Shared `x-decisions.card` — one change covers /decisions board, rooms answer-now lane, AND brief "Open questions" (all render open Decisions through this card). 🛑 when is_blocking, ❓ otherwise; only open calls flagged. - Inbox — open OperatorNotes (NoteStatus::Open) get ✋; terminal/acked notes stay un-glyphed. Judgment call worth your eye: go/no-go confirm decisions fold into ❓ rather than a distinct 🟢/🅰️ — a green/A glyph reads as "resolved/go" on a still-OPEN call, the exact confusion the highlight is meant to avoid. Happy to add a 4th go/no-go glyph if you'd rather. Tests: AttentionSignalTest (mapping + gating, incl. which feed kinds flag as needs-response), FeedServiceTest extended to assert per-entry `attention` tokens end-to-end, Decisions/IndexTest asserts ❓/🛑 render on open calls and are absent once resolved. Files: +app/Support/AttentionSignal.php, +resources/views/components/ui/attention.blade.php, +tests/Unit/Support/AttentionSignalTest.php; M FeedService.php, decisions/card.blade.php, inbox/index.blade.php, rooms/index.blade.php, rooms/show.blade.php, FeedServiceTest.php, Decisions/IndexTest.php. Not merged — idle for orchestrator review.

Feedback #72 Authority: OPERATOR APPROVAL REQUIRED Funnel: A - operator approved brief Gate: this brief must not be dispatchable until the operator approves it. Kind: idea Source: flower-orchestrator (daemon 17), on operator request Summary: Use attention emojis on daemon messages that need an operator response so they're easy to scan Detail: When a daemon posts something that actually needs the operator's response/decision — a question, a go/no-go, a blocker awaiting the operator — prefix/tag it with a consistent set of attention emojis (e.g. ❓ question needing an answer, 🅰️/🟢 go/no-go decision, 🛑 blocker, ✋ needs-you) so the operator can visually scan a long scrollback and instantly spot the items that need them vs routine activity/FYI. Should apply across daemon reports/notes, inbox notes, brief questions, and the operator-feed "needs_you" items. Keep routine/FYI messages un-emoji'd (or a low-key marker) so the highlight stays meaningful. Operator request 2026-07-03.