Search in the UI wishlist: - filter by document type (ie: briefs/feed

You are being dispatched from flower Brief #197: Search in the UI wishlist:

- filter by document type (ie: briefs/feed

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

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: flower/197-search-doctype-filter
- worktree: not specified
- kind: fresh

Current brief spec:
## Goal
Make flower's corpus searchable in the UI the way agents search it via MCP: (1) filter search by document/source type, and (2) full-text search within /briefs.

## Asks (operator, 2026-07-04)
1. **Filter search by document type** (briefs / feedback / scratchpad / session / commit / todo / doc). Motivating use case: "is there an active brief about the slow /projects & /sessions views?" — operator can't tell if it's addressed or in limbo.
2. **Search WITHIN briefs** on /briefs (like /sessions), not just filter.

## Backend already supports both — this is UI wiring
- Source-type filter: recall_search already accepts `sources` (chunkable_type); Meili `chunks` is filterable by `chunkable_type` (SPEC §8). Expose as a UI facet on the global search surface.
- /briefs search: recall_briefs already accepts a `query` (title/slug/spec/summary). /briefs currently exposes only status/project FILTERS — add a search input wired to that query path (mirror the /sessions search UX).

## Scope
- Global search UI: a document-type facet (multi-select of source types) mapping to the `sources`/`chunkable_type` filter; sensible default (all) + clear active-filter state.
- /briefs view: a debounced full-text search box (Livewire property → title/spec/summary query), composable with the existing status/project filters, persisted in the query string like the other /briefs filters.
- bloom design system; reuse existing filter/search patterns (`resources/views/components/ui/*`, the /sessions search).

## Out of scope
- Search RANKING/quality fixes → #194.
- New backend search capability (both already exist).

## Acceptance
- Global search can be restricted to one or more document types; results respect it.
- /briefs has working full-text search (title/spec/summary) composable with status/project filters; state persists across navigation.
- Livewire/feature tests for both; `php artisan test` green + pint. `Brief: #197` trailer.

## Provenance
Operator note (2026-07-04). Related: top-bar typeahead full-content search (todo #330), /briefs UX epic #87, recall search quality #194. Backend refs: RecallService (recall_search `sources`, recall_briefs `query`), Meili `chunks.chunkable_type` (SPEC §8).

Recent/key trace events:
[1] participant_joined operator:mike: (no body)
[2] note_added operator:mike: Search in the UI wishlist:

- filter by document type (ie: briefs/feedback/scratchpad/etc) - use case here is that I'm trying to find if I have a brief out/active right now about how slow the /projects and /sessions views load - I know I've said something a handful of times and just not sure if we've addressed it or it's in limbo somewhere
- ability to search _within_ briefs on the /briefs view, presumably how it works on /sessions - I can filter /briefs but not search them specifically.
[3] status_change operator:mike: (no body)
[4] participant_joined flower-refine: (no body)
[5] spec_snapshot flower-refine: Search in the UI wishlist:

- filter by document type (ie: briefs/feedback/scratchpad/etc) - use case here is that I'm trying to find if I have a brief out/active right now about how slow the /projects and /sessions views load - I know I've said something a handful of times and just not sure if we've addressed it or it's in limbo somewhere
- ability to search _within_ briefs on the /briefs view, presumably how it works on /sessions - I can filter /briefs but not search them specifically.
[6] refinement flower-refine: ## Goal
Make flower's corpus searchable in the UI the way agents search it via MCP: (1) filter search by document/source type, and (2) full-text search within /briefs.

## Asks (operator, 2026-07-04)
1. **Filter search by document type** (briefs / feedback / scratchpad / session / commit / todo / doc). Motivating use case: "is there an active brief about the slow /projects & /sessions views?" — operator can't tell if it's addressed or in limbo.
2. **Search WITHIN briefs** on /briefs (like /sessions), not just filter.

## Backend already supports both — this is UI wiring
- Source-type filter: recall_search already accepts `sources` (chunkable_type); Meili `chunks` is filterable by `chunkable_type` (SPEC §8). Expose as a UI facet on the global search surface.
- /briefs search: recall_briefs already accepts a `query` (title/slug/spec/summary). /briefs currently exposes only status/project FILTERS — add a search input wired to that query path (mirror the /sessions search UX).

## Scope
- Global search UI: a document-type facet (multi-select of source types) mapping to the `sources`/`chunkable_type` filter; sensible default (all) + clear active-filter state.
- /briefs view: a debounced full-text search box (Livewire property → title/spec/summary query), composable with the existing status/project filters, persisted in the query string like the other /briefs filters.
- bloom design system; reuse existing filter/search patterns (`resources/views/components/ui/*`, the /sessions search).

## Out of scope
- Search RANKING/quality fixes → #194.
- New backend search capability (both already exist).

## Acceptance
- Global search can be restricted to one or more document types; results respect it.
- /briefs has working full-text search (title/spec/summary) composable with status/project filters; state persists across navigation.
- Livewire/feature tests for both; `php artisan test` green + pint. `Brief: #197` trailer.

## Provenance
Operator note (2026-07-04). Related: top-bar typeahead full-content search (todo #330), /briefs UX epic #87, recall search quality #194. Backend refs: RecallService (recall_search `sources`, recall_briefs `query`), Meili `chunks.chunkable_type` (SPEC §8).
[7] status_change flower-refine: (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: #197` to every commit for this brief so flower can exact-link commits back to the brief.