#95 PR-9 — Standalone decision search (buildDecisionChunks) + link-aware indexing

You are being dispatched from flower Brief #125: #95 PR-9 — Standalone decision search (buildDecisionChunks) + link-aware indexing

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

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: flower/125-decision-search
- worktree: not specified
- kind: fresh

Current brief spec:
## PR-9 — Standalone decision search (buildDecisionChunks) + link-aware indexing (child of #95)
Include **standalone** decisions (no brief subject) in `recall_search` — they're durable signals of
intent/direction/context and should be findable like briefs/commits/sessions. (Brief-attached decisions
are already discoverable via their brief; this closes the standalone gap — #95 §5.8.1, **reversed per
operator Q24**.)

## Scope
1. **Make `Decision` a chunkable type.** A `buildDecisionChunks` seam (mirror `buildCommitChunks` / the
   brief chunk builder in `EmbedChunks`) → one Chunk per **standalone** decision, `decision` source/tag,
   re-embeds on change; indexed into Meilisearch + surfaced in `recall_search`, with the recall hit
   carrying the decision + its relations. (Brief-attached decisions need not be double-indexed — already
   covered via their brief.)
2. **Link-aware chunk text (operator ask).** Weave the decision's context into the chunk so associations
   surface in recall: the resolved **question + answer**, the **subject** (if any), and the
   **`decision_links`** — a linked brief's **title + spec excerpt**, plus linked session / scratchpad /
   commits / files. If a brief is linked on the decision, its title/ref is in the chunk text AND the
   recall hit exposes the link, so "what/why is this about" is answerable from search alone.
3. Keep it bounded like other chunk builders (in-scope decisions only; skip unchanged).

## Acceptance
- A standalone decision (question + answer) is found by `recall_search`; its hit exposes linked context
  (linked brief title/excerpt + other decision_links).
- Brief-attached decisions remain discoverable via their brief (no regression / no double-index).
- `php artisan test` green + pint. `Brief: #125` trailer.

## Provenance
Operator #95 Q24 (confirmed 2026-07-03) + link-weaving ask. Deps: PR-1 (#117, Decision model + service) +
PR-2 (#118, `decision_links` + auto-link). Design ref: #95 §5.8.1 (reversed) + Q24. Speced by
flower-refine.

Recent/key trace events:
[6] dependency_added flower-refine: Now depends on #118 (#95 PR-2 — Events, broadcasts, auto-participant + auto-link (decision_links)).
[7] status_change flower-refine: (no body)
[8] link_added flower-refine: (no body)
[9] link_added flower-refine: (no body)
[10] participant_joined flower-118: (no body)
[11] unblocked flower-118: Unblocked — #118 reached complete.
[12] link_added flower-refine: (no body)
[13] participant_joined flower-orchestrator: (no body)
[14] dependency_added flower-orchestrator: Now depends on #122 (#95 PR-6 — Follow-up chains (decision_answers + parent_answer_id)).
[15] link_added flower-orchestrator: (no body)
[16] unblocked flower-orchestrator: Unblocked — #122 reached complete.
[17] link_added flower-orchestrator: (no body)

Recommended linked context:
{
    "todos": [],
    "scratchpads": [
        {
            "id": 364,
            "solo_scratchpad_id": "1055",
            "name": "flower-refine — reset handoff (2026-07-03)",
            "archived": false,
            "revision": 1
        },
        {
            "id": 375,
            "solo_scratchpad_id": "1067",
            "name": "flower-refine — reset handoff (2026-07-03 #2)",
            "archived": false,
            "revision": 2
        },
        {
            "id": 378,
            "solo_scratchpad_id": "1070",
            "name": "flower-refine — reset handoff (2026-07-04)",
            "archived": false,
            "revision": 2
        },
        {
            "id": 381,
            "solo_scratchpad_id": "1073",
            "name": "flower-orchestrator — reset handoff (2026-07-04)",
            "archived": false,
            "revision": 1
        },
        {
            "id": 386,
            "solo_scratchpad_id": "1078",
            "name": "flower-orchestrator (daemon 25) — reset handoff (2026-07-04 #3)",
            "archived": false,
            "revision": 1
        }
    ]
}

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