/briefs/{id} detail view — collapse dispatch form by default, move auto-dispatch toggle to card header, disable it until wired

You are being dispatched from flower Brief #96: /briefs/{id} detail view — collapse dispatch form by default, move auto-dispatch toggle to card header, disable it until wired

Recall pointer:
- Use recall_brief with id 96 for the full folder if you need provenance.

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: flower/96-briefs-detail-collapse
- worktree: not specified
- kind: fresh

Current brief spec:
(no spec yet)

This is a direct request, not a fully-specced plan. If it's clear, resolve it. If you hit a blocking ambiguity, call brief_ask (or brief_append) with your questions and flip the brief to `refining` before proceeding — don't guess.

Recent/key trace events:
[1] participant_joined flower-orchestrator: (no body)
[2] note_added flower-orchestrator: Child of #87. Brief DETAIL view (`resources/views/livewire/briefs/show.blade.php` + `app/Livewire/Briefs/Show.php`). Distinct from #90 (/briefs index/create) and #81 (markdown editor on this view).

Operator ask (2026-07-03): the dispatch form eats a lot of vertical space but manual dispatch is rare. Reclaim it.

## Items
1. **Move the auto-dispatch toggle into the card header, right-aligned** (out of the body form). It's a persistent per-brief setting, so header placement fits.
2. **Disable the auto-dispatch toggle until the feature is actually wired.** VERIFIED non-functional: `auto_dispatch_on_planned` (migration `2026_06_30_110000`) is written by `Show.php:328` and cast on `Brief`, but there is **NO consumer** — grep of app/Jobs, app/Console, app/Services is empty; the UI even admits it: `show.blade.php:195` "Saved as intent — no agent acts on it yet." So: render the toggle **disabled** with a short "(coming soon / not yet active)" affordance, and **remove** the verbose "When this brief reaches planned … Saved as intent — no agent acts on it yet." helper text.
3. **Collapse the rest of the dispatch form by default;** reveal it only when the operator clicks an expand control (e.g. "Dispatch ▸" / "Show dispatch options"). Saves screen space for the common case where no manual dispatch happens.

## Follow-up (separate brief, NOT this one)
- Actually WIRE auto-dispatch-on-planned so the toggle does something: when a brief with the flag reaches `planned`, enqueue it into the project orchestrator's coordination queue (the #84 substrate) for the orchestrator to pick up on drain. Now feasible given the coordination queue + orchestrator drain loop exist. Flagging as a real follow-up; once built, re-enable the toggle (undo item 2's disable). Orchestrator to spec if operator wants it.

## Constraints
- bloom + FluxUI; Livewire 4; `php artisan test` green; `./vendor/bin/pint`; verify in the real app. Commit trailer `Brief: #<this-id>`.
[3] parent_set flower-orchestrator: Grouped under epic #87.
[4] status_change flower-orchestrator: (no body)
[5] note_added flower-orchestrator: CORRECTION to item 2 (per operator, 2026-07-03): do NOT disable the auto-dispatch toggle. The operator's plan is to WIRE it via the orchestrator drain loop (new sibling brief), so the toggle becomes live. So on this brief (#96), item 2 changes to: **keep the toggle enabled**, MOVE it to the card header (right-aligned) per item 1, and **replace** the stale "Saved as intent — no agent acts on it yet" disclaimer with a short accurate hint (e.g. "Auto-dispatches when it reaches planned"). The actual wiring (making it do something) is tracked separately; this brief stays purely the DETAIL-VIEW UI work (header placement + collapse the dispatch form + toggle relocation). Sequence #96 after the wiring brief lands, or coordinate so the hint text matches reality.
[6] dependency_added flower-orchestrator: Now depends on #98 (Wire auto-dispatch-on-planned via the orchestrator drain loop (the missing consumer)).
[7] participant_joined flower-98-worker: (no body)
[8] unblocked flower-98-worker: Unblocked — #98 reached complete.
[9] link_added flower-orchestrator: (no body)

Recommended linked context:
{
    "todos": [],
    "scratchpads": [
        {
            "id": 346,
            "solo_scratchpad_id": "1026",
            "name": "Orchestrator HANDOFF — flower build (live state)",
            "archived": false,
            "revision": 73
        }
    ]
}

Execution notes:
- Treat the brief as the source of truth.
- Keep work scoped to this dispatch request.
- Use brief_append / brief_update_status when reporting material progress; as your final dispatched-worker step, call brief_dispatch_complete with dispatch_request_id (or brief_id) and actor_ref.
- Codex workers should verify mutating Flower tools with tool_search query `brief_append brief_dispatch_complete flower_feedback` (limit 20) when tool availability is in doubt; report raw SEE/LOAD vs NOT visible instead of silently using local fallbacks.
- Add a git commit trailer `Brief: #96` to every commit for this brief so flower can exact-link commits back to the brief.