Feedback #116: Hide cancelled briefs the same as complete briefs per the toggle on /briefs

You are being dispatched from flower Brief #237: Feedback #116: Hide cancelled briefs the same as complete briefs per the toggle on /briefs

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

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: flower/237-hide-cancelled-briefs
- worktree: not specified
- kind: fresh

Current brief spec:
# Hide cancelled + abandoned briefs via the /briefs "hide completed" toggle

## Problem / operator intent (feedback #116, 2026-07-04)
The `/briefs` list has a "hide completed" toggle. Extend it so it ALSO hides **cancelled** and **abandoned** briefs — i.e., the toggle hides all terminal/closed states, not just `complete`.

## Scope
- In the `/briefs` Livewire index component + its query, extend the existing "hide completed" filter so that when active it excludes briefs with status `complete`, `cancelled`, AND `abandoned` (today it only excludes `complete`).
- Keep the toggle's default + persistence behavior as-is; just broaden which statuses it hides. Confirm the awaiting-count / any status tallies stay correct.
- **Minor UX call (recommended):** relabel the toggle to reflect the broader scope (e.g. "Hide closed" / "Hide done & closed") since it no longer hides only "completed." Flag if you'd rather keep the "Hide completed" label.

## Acceptance
- With the toggle ON, `/briefs` hides `complete` + `cancelled` + `abandoned` briefs; with it OFF they show. Other statuses unaffected.
- `php artisan test` green + `./vendor/bin/pint`. `Brief: #237` trailer. Worktree-pinned; never edit MAIN.

## Provenance / gating
Feedback #116 (operator:ui, 2026-07-04) → promoted to this brief. **`needs_operator_approval=true` (Funnel A)** — stays non-dispatchable until the operator approves it, even at `planned`.

**Disposition:** `planned` — small, mechanical UI; no design-loop. Awaiting operator approval before dispatch.

Recent/key trace events:
[1] participant_joined operator:mike: (no body)
[2] note_added operator:mike: Feedback #116
Authority: OPERATOR APPROVAL REQUIRED
Funnel: A - operator approved brief
Gate: this brief must not be dispatchable until the operator approves it.
Kind: idea
Source: operator:ui

Summary:
Hide cancelled briefs the same as complete briefs per the toggle on /briefs

Detail:
We have the 'hide completed' toggle on /briefs - let's extend that to hide cancelled and abandoned as well
[3] link_added operator:mike: (no body)
[4] status_change operator:mike: (no body)
[5] participant_joined flower-refine: (no body)
[6] plan_proposed flower-refine: # Hide cancelled + abandoned briefs via the /briefs "hide completed" toggle

## Problem / operator intent (feedback #116, 2026-07-04)
The `/briefs` list has a "hide completed" toggle. Extend it so it ALSO hides **cancelled** and **abandoned** briefs — i.e., the toggle hides all terminal/closed states, not just `complete`.

## Scope
- In the `/briefs` Livewire index component + its query, extend the existing "hide completed" filter so that when active it excludes briefs with status `complete`, `cancelled`, AND `abandoned` (today it only excludes `complete`).
- Keep the toggle's default + persistence behavior as-is; just broaden which statuses it hides. Confirm the awaiting-count / any status tallies stay correct.
- **Minor UX call (recommended):** relabel the toggle to reflect the broader scope (e.g. "Hide closed" / "Hide done & closed") since it no longer hides only "completed." Flag if you'd rather keep the "Hide completed" label.

## Acceptance
- With the toggle ON, `/briefs` hides `complete` + `cancelled` + `abandoned` briefs; with it OFF they show. Other statuses unaffected.
- `php artisan test` green + `./vendor/bin/pint`. `Brief: #237` trailer. Worktree-pinned; never edit MAIN.

## Provenance / gating
Feedback #116 (operator:ui, 2026-07-04) → promoted to this brief. **`needs_operator_approval=true` (Funnel A)** — stays non-dispatchable until the operator approves it, even at `planned`.

**Disposition:** `planned` — small, mechanical UI; no design-loop. Awaiting operator approval before dispatch.
[7] note_added flower-refine: Refinement complete — spec is ready to dispatch. Left at `refining` because the Funnel-A `needs_operator_approval` gate blocks a daemon from advancing it to `planned` (attempted; rejected: "Brief #237 needs operator approval before it can move to planned" — correct, working as designed). **Operator: approve #237 (via /briefs or /feedback #116) to release it to `planned`/dispatch.** No further refinement needed unless you want the label change (see spec's minor UX note).
[8] note_added operator:mike: Operator approved this feedback-born brief for dispatch.
[9] status_change operator:mike: (no body)

Recommended linked context:
{
    "todos": [],
    "scratchpads": []
}

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: #237` to every commit for this brief so flower can exact-link commits back to the brief.