Operator → orchestrator inbox: project-scoped, MCP-interactive, reassignable async notes

## A3 DONE (design, proc 973) — inbox UI, branch `flower/inbox-ui` @ 79b0436, ready for merge Built the UI half on top of 981's merged A2 backend (`OperatorNote` + `OperatorInboxService` + note_* MCP tools). **Shipped:** - **New `/inbox` page** (`App\Livewire\Inbox\Index`): a **"note the orchestrator"** composer (body + target-project select; blank = unassigned), a **status filter ribbon** (open/acknowledged/handled/dismissed + live counts), a **project scope** filter, and the notes list. - **Per-note controls:** color-coded **status pill**, body, `created_by`/`handled_by`/when footer, a **status select** (advance lifecycle), a **reassign select** (→ another project), and a **conditional unassign button** (only when assigned). - **Reads** the `OperatorNote` model; **every mutation** (create/status/reassign/unassign) goes through **`OperatorInboxService`** so the UI shares the MCP write path's audit trail. Scoped view = the project's own notes **+ unassigned** (mirrors `OperatorInboxService::inbox`). - **Global affordances:** an **"Inbox"** nav item (manage group) + a header **"Note"** button (→ `#compose`). - Composer target-project **defaults to the current inbox scope** (`?project=…`). **Notes for merge:** - Reassign select uses the `$wire`-call-then-blank-`$el.value` pattern (returns to "reassign →" placeholder). Action ids are Blade literals so `int` hints are safe under `declare(strict_types=1)`; select-sourced values (status/projectRef) stay strings. - No new migration (A2's `operator_notes` already in the shared DB). CSS rebuilt locally (gitignored; MAIN rebuilds on deploy). **Verification:** 8 new tests (submit assigned/unassigned/blank, status advance + `handled_by` stamp on terminal, reassign→unassign, project-scope+unassigned visibility, status filter, composer default). Full suite **302 green, pint clean**. Verified live on flower-design.test: create → reassign(→flower) → handled (handled_by stamped) → unassign, with pills, counts, and select-reset all correct. Test note cleaned up (inbox left at 0). Standing by for **A5 (daemon roster UI)** — A4 backend is merged per the operator.

## Spec: Operator → orchestrator inbox **Goal:** a lightweight, NON-interrupting async channel. The operator drops a note → it queues → the target project's orchestrator picks it up on its next loop cycle. Keeps "handle later" (inbox) separate from "interrupt now" (a direct message). Not feedback (bugs), not a brief (work items) — its own input type. ### Project-scoped / scopable (Mike) - Each note targets a **project** so it reaches the right project's orchestrator. - A note can be **reassigned to another project** or have its **project assignment removed** (unassigned) — for passing to another project, or when it was sent to the wrong one. Unassigned notes are visible to any orchestrator / the operator until claimed/assigned. ### MCP-interactive (Mike) - Agents interact via MCP: read the inbox, **set status** (e.g. open → acknowledged → handled / dismissed), **reassign** to another project, **unassign** (remove project). Plus operator-create from the UI. - Suggested tools: `recall_inbox(project?)` (read), `inbox_note(id)` (read); `note_create(project?, body)`, `note_update_status(id, status)`, `note_reassign(id, project)`, `note_unassign(id)` (write, actor_ref → audit). ### Data model - `operator_notes`: id, `project_id?` (nullable = unassigned), `body`, `status` (open|acknowledged|handled|dismissed), `created_by`, `handled_by?`, `meta`, timestamps. (Mirror the feedback table's shape/conventions.) ### UI (bloom) - A persistent "note the orchestrator" composer (global affordance) + a per-project inbox view; reassign/unassign controls; status pills. ### Mechanics - The orchestrator, now a looping daemon, drains its project's open inbox notes each cycle and acts (or escalates). This is one of the orchestrator's standing loop responsibilities (alongside the dispatch queue + roster check).