Briefs: "Pending Approval" sub-nav filter row + live badge/counter (mirror Open Questions)

You are being dispatched from flower Brief #180: Briefs: "Pending Approval" sub-nav filter row + live badge/counter (mirror Open Questions)

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

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: choose an appropriate branch
- worktree: not specified
- kind: fresh

Current brief spec:
## Objective
Add a "Pending Approval" sub-nav filter row under Briefs in the left nav, with a live counter/badge — mirroring the existing "Open Questions" sub-nav + badge — so operator-gated briefs awaiting approval are surfaced at a glance and one click away. Operator-requested (2026-07-04). Sibling to approved brief #178 (same for Decisions); same Open Questions precedent.

## Context / why
Ops routes ideas → operator-gated briefs (`needs_operator_approval=true`), which accumulate on /briefs with no at-a-glance signal (e.g. #167, #179; #178 now approved). The operator has to hunt for them. A nav sub-link + counter (like Open Questions) makes the pending-approval queue visible + one click to filter.

## Precedent to mirror (already in the codebase — copy this pattern)
- **Nav sub-link + badge:** `resources/views/components/layouts/app.blade.php` (~L89-97): the "Open Questions" `nav-sublink` under Briefs → `route('briefs.index', ['questions' => 'open'])`, `aria-current` when active (`$onOpenQuestions = routeIs('briefs.index') && query('questions')==='open'`), and a live badge `<span data-open-questions-badge>` (server-rendered count then live-updated; Brief #109).
- **List filter already exists:** `app/Livewire/Briefs/Index.php` L428 — `$approvalOnly` → `->when($this->approvalOnly, fn($q) => $q->where('needs_operator_approval', true))`. So the LIST filter is done; this brief adds the NAV entry + badge + query-param deep-link.
- **Pending-approval definition:** `Brief.needs_operator_approval === true` (boolean cast, Brief.php:24); a brief is dispatchable only when `Planned && !needs_operator_approval` (Index.php:500). Exclude terminal statuses (cancelled/abandoned/complete) from the count.

## Scope
1. **Nav sub-link:** add a "Pending Approval" `nav-sublink` under Briefs in `app.blade.php` → `route('briefs.index', ['approval' => 'only'])`, with active/`aria-current` styling mirroring Open Questions.
2. **Query-param wiring:** make `?approval=only` drive `$approvalOnly` on `Briefs/Index` on mount (mirror how `questions=open` sets the open-questions filter) so the sub-link deep-links into the filtered list.
3. **Live badge/counter:** add a `data-pending-approval-badge` span with the server-rendered count `Brief::where('needs_operator_approval', true)->whereNotIn('status', [cancelled, abandoned, complete])->count()`, refreshed live via the SAME mechanism as the open-questions badge (Brief #109 — reuse it, don't reinvent).
4. **(Stretch — consistency with #78):** optionally trigger the site-wide ding/bell when a new pending-approval brief appears. Keep off the critical path if the ding plumbing is broader than this slice.

## Constraints / non-goals
- Reuse the Open Questions badge refresh mechanism (Brief #109); match its markup/refresh path — do not invent a new one.
- Don't change approval semantics — only SURFACE the existing `needs_operator_approval` queue.
- Frontend + thin Livewire wiring; follow the bloom design system in `resources/views/components/ui/*`.

## Definition of done
A "Pending Approval" sub-nav row under Briefs with active styling + a live badge showing the count of `needs_operator_approval` (non-terminal) briefs; clicking it deep-links to the filtered /briefs list; badge updates live like Open Questions; verified against current pending-approval briefs (#167/#179/…).

Recent/key trace events:
[1] participant_joined flower-ops: (no body)
[2] note_added flower-ops: ## Objective
Add a "Pending Approval" sub-nav filter row under Briefs in the left nav, with a live counter/badge — mirroring the existing "Open Questions" sub-nav + badge — so operator-gated briefs awaiting approval are surfaced at a glance and one click away. Operator-requested (2026-07-04). Sibling to approved brief #178 (same for Decisions); same Open Questions precedent.

## Context / why
Ops routes ideas → operator-gated briefs (`needs_operator_approval=true`), which accumulate on /briefs with no at-a-glance signal (e.g. #167, #179; #178 now approved). The operator has to hunt for them. A nav sub-link + counter (like Open Questions) makes the pending-approval queue visible + one click to filter.

## Precedent to mirror (already in the codebase — copy this pattern)
- **Nav sub-link + badge:** `resources/views/components/layouts/app.blade.php` (~L89-97): the "Open Questions" `nav-sublink` under Briefs → `route('briefs.index', ['questions' => 'open'])`, `aria-current` when active (`$onOpenQuestions = routeIs('briefs.index') && query('questions')==='open'`), and a live badge `<span data-open-questions-badge>` (server-rendered count then live-updated; Brief #109).
- **List filter already exists:** `app/Livewire/Briefs/Index.php` L428 — `$approvalOnly` → `->when($this->approvalOnly, fn($q) => $q->where('needs_operator_approval', true))`. So the LIST filter is done; this brief adds the NAV entry + badge + query-param deep-link.
- **Pending-approval definition:** `Brief.needs_operator_approval === true` (boolean cast, Brief.php:24); a brief is dispatchable only when `Planned && !needs_operator_approval` (Index.php:500). Exclude terminal statuses (cancelled/abandoned/complete) from the count.

## Scope
1. **Nav sub-link:** add a "Pending Approval" `nav-sublink` under Briefs in `app.blade.php` → `route('briefs.index', ['approval' => 'only'])`, with active/`aria-current` styling mirroring Open Questions.
2. **Query-param wiring:** make `?approval=only` drive `$approvalOnly` on `Briefs/Index` on mount (mirror how `questions=open` sets the open-questions filter) so the sub-link deep-links into the filtered list.
3. **Live badge/counter:** add a `data-pending-approval-badge` span with the server-rendered count `Brief::where('needs_operator_approval', true)->whereNotIn('status', [cancelled, abandoned, complete])->count()`, refreshed live via the SAME mechanism as the open-questions badge (Brief #109 — reuse it, don't reinvent).
4. **(Stretch — consistency with #78):** optionally trigger the site-wide ding/bell when a new pending-approval brief appears. Keep off the critical path if the ding plumbing is broader than this slice.

## Constraints / non-goals
- Reuse the Open Questions badge refresh mechanism (Brief #109); match its markup/refresh path — do not invent a new one.
- Don't change approval semantics — only SURFACE the existing `needs_operator_approval` queue.
- Frontend + thin Livewire wiring; follow the bloom design system in `resources/views/components/ui/*`.

## Definition of done
A "Pending Approval" sub-nav row under Briefs with active styling + a live badge showing the count of `needs_operator_approval` (non-terminal) briefs; clicking it deep-links to the filtered /briefs list; badge updates live like Open Questions; verified against current pending-approval briefs (#167/#179/…).
[3] plan_proposed flower-ops: ## Objective
Add a "Pending Approval" sub-nav filter row under Briefs in the left nav, with a live counter/badge — mirroring the existing "Open Questions" sub-nav + badge — so operator-gated briefs awaiting approval are surfaced at a glance and one click away. Operator-requested (2026-07-04). Sibling to approved brief #178 (same for Decisions); same Open Questions precedent.

## Context / why
Ops routes ideas → operator-gated briefs (`needs_operator_approval=true`), which accumulate on /briefs with no at-a-glance signal (e.g. #167, #179; #178 now approved). The operator has to hunt for them. A nav sub-link + counter (like Open Questions) makes the pending-approval queue visible + one click to filter.

## Precedent to mirror (already in the codebase — copy this pattern)
- **Nav sub-link + badge:** `resources/views/components/layouts/app.blade.php` (~L89-97): the "Open Questions" `nav-sublink` under Briefs → `route('briefs.index', ['questions' => 'open'])`, `aria-current` when active (`$onOpenQuestions = routeIs('briefs.index') && query('questions')==='open'`), and a live badge `<span data-open-questions-badge>` (server-rendered count then live-updated; Brief #109).
- **List filter already exists:** `app/Livewire/Briefs/Index.php` L428 — `$approvalOnly` → `->when($this->approvalOnly, fn($q) => $q->where('needs_operator_approval', true))`. So the LIST filter is done; this brief adds the NAV entry + badge + query-param deep-link.
- **Pending-approval definition:** `Brief.needs_operator_approval === true` (boolean cast, Brief.php:24); a brief is dispatchable only when `Planned && !needs_operator_approval` (Index.php:500). Exclude terminal statuses (cancelled/abandoned/complete) from the count.

## Scope
1. **Nav sub-link:** add a "Pending Approval" `nav-sublink` under Briefs in `app.blade.php` → `route('briefs.index', ['approval' => 'only'])`, with active/`aria-current` styling mirroring Open Questions.
2. **Query-param wiring:** make `?approval=only` drive `$approvalOnly` on `Briefs/Index` on mount (mirror how `questions=open` sets the open-questions filter) so the sub-link deep-links into the filtered list.
3. **Live badge/counter:** add a `data-pending-approval-badge` span with the server-rendered count `Brief::where('needs_operator_approval', true)->whereNotIn('status', [cancelled, abandoned, complete])->count()`, refreshed live via the SAME mechanism as the open-questions badge (Brief #109 — reuse it, don't reinvent).
4. **(Stretch — consistency with #78):** optionally trigger the site-wide ding/bell when a new pending-approval brief appears. Keep off the critical path if the ding plumbing is broader than this slice.

## Constraints / non-goals
- Reuse the Open Questions badge refresh mechanism (Brief #109); match its markup/refresh path — do not invent a new one.
- Don't change approval semantics — only SURFACE the existing `needs_operator_approval` queue.
- Frontend + thin Livewire wiring; follow the bloom design system in `resources/views/components/ui/*`.

## Definition of done
A "Pending Approval" sub-nav row under Briefs with active styling + a live badge showing the count of `needs_operator_approval` (non-terminal) briefs; clicking it deep-links to the filtered /briefs list; badge updates live like Open Questions; verified against current pending-approval briefs (#167/#179/…).
[4] status_change flower-ops: (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: #180` to every commit for this brief so flower can exact-link commits back to the brief.