Let's add some sort of charts/analytics to the /briefs view to surface

Merged flower/107-briefs-analytics into master on MAIN — merge commit **2aafe63** (7 files, +1012). Clean merge. Full suite green (1126 passed, 2 skips, 6974 assertions); pint clean; npm build done (/briefs analytics views). Integrated cleanly with #219 (dup-search panel wrapped inside the new "New Brief" disclosure, not clobbered) + #90 untouched. New BriefAnalyticsService (bounded non-N+1 aggregates, /briefs query-count constant, audit budget 4→8). Worker proc 1135 closed. Worker suggested an orchestrator eyeball of the real corpus in dark bloom on flower.test (deferred to post-reset).

Built + committed on `flower/107-briefs-analytics` (commit 297f575, worktree wt2). Not merged — orchestrator merges from MAIN. **Scope A — collapse create form:** `/briefs` header is now a flex row with an opposite-aligned **"New Brief"** button (Alpine `captureOpen` on the component root). Clicking reveals the full capture form inside an Alpine disclosure (`#brief-capture`, `x-show` + slide `x-transition`) ABOVE the analytics, auto-focuses the note (`data-capture-note` + `$root.querySelector`), and auto-collapses on `focusout` when the note is empty. **#219's live duplicate-search panel is wrapped inside the same disclosure (revealed with the form, not clobbered), and #90's textarea auto-expand + remembered project select are untouched** — the whole existing `<form wire:submit="captureNote">` (incl. Capture / Capture&dispatch / Capture&Refine + dup-panel's continue/follow-up/merge actions) is moved verbatim into the disclosure. **Scope B — analytics panel** (default content of the reclaimed space, `resources/views/livewire/briefs/partials/analytics.blade.php`, hidden only on an empty scoped corpus): - **"now" ribbon** (4 tiles) — in-flight / **dispatchable-now** (→ sets `dispatchableOnly`) / blocked (dependency-gated) / **awaiting-you** (→ `toggleOpenQuestions`, foot shows pending-approval). Tiles set the inbox's own filters. - **corpus by status** — proportion bar (lifecycle-ordered) + clickable status chips (→ `$set('status', …)`). - **throughput** — created (accent) vs completed (live) per day, dual-line SVG sharing one y-axis, last 30d, with totals + sparse axis labels. - **author mix** — operator vs daemon split meter + top authors (operator = `operator` / `operator:*`, else daemon). - **cycle time** — creation→complete + refining→planned avg & median, plus an "oldest in flight" callout linking to the brief. **Data / cost:** new `App\Services\Briefs\BriefAnalyticsService::forScope(?projectId)` — 4 bounded, non-N+1 aggregates (brief roll-up + status-transition trace + dependency join + open-questions count), each `whereIn`-scoped to the roll-up's ids, so scope follows the page's project filter and the query count is constant regardless of corpus size. Short-circuits to `['total'=>0]` (1 query) on an empty corpus. Charts reuse the dark-bloom `/analytics` SVG + meter idioms and `x-ui.stat`/`sparkline` geometry (legible in dark bloom; verified via a full render-dump — 2×30-pt polylines, real proportional bar segments, cycle/oldest/author text all present). **Metrics chosen** = the spec's v1 set, unchanged. Scoped analytics to the **project** filter only (status/drafts/etc. are list-view filters; counts-by-status would collapse under a status filter). **Tests:** new `tests/Feature/Briefs/AnalyticsPanelTest.php` (5 tests: metric accuracy with frozen time — counts/author-mix/now, throughput totals + cycle avg/median, project scoping, empty-corpus hide, panel-render + disclosure + #219/#90 markers + ordering). Bumped `QueryEfficiencyAuditTest` `/briefs` budget 4→8 (documented +4). Retargeted one existing IndexTest assertion (`test_status_and_drafts_filters_narrow_the_inbox`) to assert on the `rows` list rather than whole-page text, since the corpus "oldest in-flight" callout can legitimately name a status-filtered-out brief. **Full suite green: 1125 passed / 3 pre-existing skips / 0 failures; pint clean** on all changed files. Files: `app/Services/Briefs/BriefAnalyticsService.php` (new), `app/Livewire/Briefs/Index.php`, `resources/views/livewire/briefs/index.blade.php`, `resources/views/livewire/briefs/partials/analytics.blade.php` (new), `tests/Feature/Briefs/AnalyticsPanelTest.php` (new), `tests/Feature/Briefs/IndexTest.php`, `tests/Feature/QueryEfficiencyAuditTest.php`. Note for MAIN verification: no cache (queries are cheap + the panel only re-renders on filter changes; capture box collapsed by default). Suggest an orchestrator eyeball of the real corpus in dark bloom on flower.test.

## Ask Replace the always-visible create-brief form on `/briefs` with a compact **"New Brief"** button, and use the reclaimed space for a **charts/analytics panel** about the brief corpus. Operator pre-approved "spec and go" (may skip the refine→planned→dispatch wait); operator is open on exact metrics. ## Scope ### A. Collapse the create form behind a "New Brief" button - On `/briefs`, remove the always-open create form. Add a **"New Brief"** button aligned opposite the page title/header. Clicking it **slides/reveals the create form ABOVE the analytics** (toggle; collapse when done / blurred-empty). Preserve the create form's existing behavior + the #90 improvements (textarea auto-expand, remembered project select) — **coordinate with child #90 (same /briefs form).** ### B. Analytics panel (default content of the reclaimed space) A compact analytics strip/cards summarizing the brief corpus. Proposed v1 metrics (operator open to changes): - **Counts by status** (idea/refining/planned/dispatched/in_progress/blocked/complete/cancelled) — small horizontal stacked bar or status chips with counts. - **Author mix** — operator-created vs daemon-created briefs (ratio + count); optionally by actor_ref. - **Throughput** — briefs created over time (last ~30d sparkline) + completed over time. - **Cycle time** — avg (and median) creation→complete, and refining→planned; call out oldest in-flight/aging briefs. - **Now** — # planned & dispatchable, # blocked, # awaiting operator (open questions). - Scope the panel to the current /briefs filter (project etc.) where it makes sense. ## Design/build notes - Follow the **`dataviz` skill** guidance for the charts + the dark bloom palette; charts must be legible in the bloom dark theme; "fun/interesting AND actionable," not busy. - Livewire 4 + bloom `x-ui.*`; Flux (now being added) for the button/disclosure where it fits. - Data from `briefs` / `brief_events` (status, created_by actor, timestamps, status_change events for cycle-time). Keep queries aggregate + cheap (cache if needed). ## Acceptance - `/briefs` shows the analytics panel by default; "New Brief" reveals the create form above it; create flow unchanged (+ #90 improvements) once revealed. - Charts render legibly in dark bloom; metrics accurate against the DB. - `php artisan test` green + pint. `Brief: #107` trailer. ## Provenance Operator note (#107, 2026-07-03) with explicit "spec and go" pre-approval + metric latitude. Speced by flower-refine (2026-07-03). Coordinate the form-collapse with #87 child #90 (/briefs form UX).

Let's add some sort of charts/analytics to the /briefs view to surface things like number/ratio of briefs created by the operator vs daemons, overall numbers/counts of briefs in each state, things like average time from creation to completion, I don't know - either fun/interesting or actionable and informative. We can have these new elements replace _this form_ to create new briefs - which should just have a button opposite-aligned from the page title/header "New Brief" or something that when clicked will slide/show this form above the analytics stuff. I'm super open to what you think we should add in this place - we can discuss if you have questions or want me to make some decisions - otherwise go ahead and just have at it (in that case you have my permission/approval to spec and go and not have to wait for the refine -> planned -> dispatch cycle)

Let's add some sort of charts/analytics to the /briefs view to surface things like number/ratio of briefs created by the operator vs daemons, overall numbers/counts of briefs in each state, things like average time from creation to completion, I don't know - either fun/interesting or actionable and informative. We can have these new elements replace _this form_ to create new briefs - which should just have a button opposite-aligned from the page title/header "New Brief" or something that when clicked will slide/show this form above the analytics stuff. I'm super open to what you think we should add in this place - we can discuss if you have questions or want me to make some decisions - otherwise go ahead and just have at it (in that case you have my permission/approval to spec and go and not have to wait for the refine -> planned -> dispatch cycle)