#95 PR-3 — Four answer types + recommended + write-in (first Flux adoption)

You are being dispatched from flower Brief #119: #95 PR-3 — Four answer types + recommended + write-in (first Flux adoption)

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

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: flower/95-pr3-answer-types
- worktree: not specified
- kind: fresh

Current brief spec:
## PR-3 — Four answer types + recommended + write-in; first real Flux adoption (child of #95)
`decision_type`-driven affordances — `confirm` (`flux:button`), `single_choice` (`flux:radio.group`),
`multi_choice` (`flux:checkbox.group`), `text` (`flux:input`/`textarea` in `flux:field`). Per-option
`recommended` bloom decoration + `allow_write_in`. Widen the `decision_ask` schema to object options
`{key,label,recommended,detail}` + `allow_write_in` + `decision_type`. **Resolve the Flux-in-bloom
surface/border bridge here** (extend `--color-*` mappings if PR-1's smoke check flagged it).
Deps: PR-1 (#117) + PR-2 (#118, for live updates). Design ref: #95 §4.4 / §8. `php artisan test` green +
pint. `Brief: #119` trailer.

Recent/key trace events:
[1] participant_joined flower-refine: (no body)
[2] note_added flower-refine: Child of #95. PR-3 of the 9-PR plan (§8 of the #95 design doc). Full spec via brief_update_spec.
[3] plan_proposed flower-refine: ## PR-3 — Four answer types + recommended + write-in; first real Flux adoption (child of #95)
`decision_type`-driven affordances — `confirm` (`flux:button`), `single_choice` (`flux:radio.group`),
`multi_choice` (`flux:checkbox.group`), `text` (`flux:input`/`textarea` in `flux:field`). Per-option
`recommended` bloom decoration + `allow_write_in`. Widen the `decision_ask` schema to object options
`{key,label,recommended,detail}` + `allow_write_in` + `decision_type`. **Resolve the Flux-in-bloom
surface/border bridge here** (extend `--color-*` mappings if PR-1's smoke check flagged it).
Deps: PR-1 (#117) + PR-2 (#118, for live updates). Design ref: #95 §4.4 / §8. `php artisan test` green +
pint. `Brief: #119` trailer.
[4] parent_set flower-refine: Grouped under epic #95.
[5] dependency_added flower-refine: Now depends on #117 (#95 PR-1 — Tracer: decisions spine (standalone confirm: ask→board→answer→pull→ack)).
[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)

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