#95 PR-0 — Pure rename: brief_questions → decisions (isolate blast radius)

You are being dispatched from flower Brief #116: #95 PR-0 — Pure rename: brief_questions → decisions (isolate blast radius)

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

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: flower/95-pr0-decisions-rename
- worktree: not specified
- kind: fresh

Current brief spec:
## PR-0 — Pure rename: brief_questions → decisions (child of #95; NO deps — dispatchable now)
Rename the `brief_questions` table → `decisions` (rename migration, **no new columns**). Rename
`BriefQuestion` model → `Decision` (repoint `$table`, move casts verbatim). Repoint `Brief::questions()`
at `Decision` and every `BriefQuestion::class` reference (`SafeEnumValue`, `RecallService` buckets, the
three `brief_*` tools). `BriefQuestionPosted/Answered` events unchanged. **No behavior change, no new
enum, no new UI** — `php artisan test` stays green on the same assertions. Front-loads the one
cross-cutting risky op so the tracer (PR-1) is small and reviewable.
Deps: none. Design ref: #95 §5.5 + §8. `php artisan test` green + `./vendor/bin/pint`. `Brief: #116` trailer.

Recent/key trace events:
[2] note_added flower-refine: Child of #95 (Decision records). PR-0 of the 9-PR plan (§8 of the #95 design doc). Full spec via brief_update_spec.
[3] plan_proposed flower-refine: ## PR-0 — Pure rename: brief_questions → decisions (child of #95; NO deps — dispatchable now)
Rename the `brief_questions` table → `decisions` (rename migration, **no new columns**). Rename
`BriefQuestion` model → `Decision` (repoint `$table`, move casts verbatim). Repoint `Brief::questions()`
at `Decision` and every `BriefQuestion::class` reference (`SafeEnumValue`, `RecallService` buckets, the
three `brief_*` tools). `BriefQuestionPosted/Answered` events unchanged. **No behavior change, no new
enum, no new UI** — `php artisan test` stays green on the same assertions. Front-loads the one
cross-cutting risky op so the tracer (PR-1) is small and reviewable.
Deps: none. Design ref: #95 §5.5 + §8. `php artisan test` green + `./vendor/bin/pint`. `Brief: #116` trailer.
[4] parent_set flower-refine: Grouped under epic #95.
[5] status_change flower-refine: (no body)
[6] participant_joined operator:mike: (no body)
[7] status_change operator:mike: (no body)
[8] dispatched operator:mike: Dispatch request #36 queued for flower.
[9] link_added flower-refine: (no body)
[10] link_added flower-refine: (no body)
[11] participant_joined flower-orchestrator: (no body)
[12] dispatched flower-orchestrator: Dispatch request #36 marked cancelled.
[13] status_change 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
        }
    ]
}

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

You are being dispatched from flower Brief #116: #95 PR-0 — Pure rename: brief_questions → decisions (isolate blast radius)

Recall pointer:
- Use recall_brief with id 116 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:
## PR-0 — Pure rename: brief_questions → decisions (child of #95; NO deps — dispatchable now)
Rename the `brief_questions` table → `decisions` (rename migration, **no new columns**). Rename
`BriefQuestion` model → `Decision` (repoint `$table`, move casts verbatim). Repoint `Brief::questions()`
at `Decision` and every `BriefQuestion::class` reference (`SafeEnumValue`, `RecallService` buckets, the
three `brief_*` tools). `BriefQuestionPosted/Answered` events unchanged. **No behavior change, no new
enum, no new UI** — `php artisan test` stays green on the same assertions. Front-loads the one
cross-cutting risky op so the tracer (PR-1) is small and reviewable.
Deps: none. Design ref: #95 §5.5 + §8. `php artisan test` green + `./vendor/bin/pint`. `Brief: #116` trailer.

Recent/key trace events:
[1] participant_joined flower-refine: (no body)
[2] note_added flower-refine: Child of #95 (Decision records). PR-0 of the 9-PR plan (§8 of the #95 design doc). Full spec via brief_update_spec.
[3] plan_proposed flower-refine: ## PR-0 — Pure rename: brief_questions → decisions (child of #95; NO deps — dispatchable now)
Rename the `brief_questions` table → `decisions` (rename migration, **no new columns**). Rename
`BriefQuestion` model → `Decision` (repoint `$table`, move casts verbatim). Repoint `Brief::questions()`
at `Decision` and every `BriefQuestion::class` reference (`SafeEnumValue`, `RecallService` buckets, the
three `brief_*` tools). `BriefQuestionPosted/Answered` events unchanged. **No behavior change, no new
enum, no new UI** — `php artisan test` stays green on the same assertions. Front-loads the one
cross-cutting risky op so the tracer (PR-1) is small and reviewable.
Deps: none. Design ref: #95 §5.5 + §8. `php artisan test` green + `./vendor/bin/pint`. `Brief: #116` trailer.
[4] parent_set flower-refine: Grouped under epic #95.
[5] 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: #116` to every commit for this brief so flower can exact-link commits back to the brief.