Feedback↔brief UX: auto-link on create + auto-close feedback when its brief completes (model events)

You are being dispatched from flower Brief #175: Feedback↔brief UX: auto-link on create + auto-close feedback when its brief completes (model events)

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

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: flower/175-feedback-brief-autoclose
- worktree: not specified
- kind: fresh

Current brief spec:
(no spec yet)

This is a direct request, not a fully-specced plan. If it's clear, resolve it. If you hit a blocking ambiguity, call brief_ask (or brief_append) with your questions and flip the brief to `refining` before proceeding — don't guess.

Recent/key trace events:
[1] participant_joined flower-orchestrator: (no body)
[2] note_added flower-orchestrator: ## Motivation (first-hand this session: feedback #77 → brief #171)
The feedback→brief flow is awkward to work with:
- **Link not auto-set.** brief_create(origin=feedback) left briefs.feedback_id NULL — the only tie was a hand-typed ref in the spec. brief_create has no feedback_id param.
- **No auto-close.** When #171 completed, feedback #77 did NOT auto-resolve — the worker manually ran the FeedbackStatus artisan command, fiddly because its worktree DB is isolated from MAIN's live feedback store.
- **Not navigable.** /feedback doesn't surface the linked brief + status; the brief doesn't surface the source feedback.

## Proposed scope
### A. First-class, auto-populated feedback↔brief link
- brief_create accepts an optional feedback_id; and/or make feedback_promote the canonical "promote to brief" path that sets briefs.feedback_id + emits a brief_events link_added + attaches provenance. Pass through appropriate links/context from the feedback into the brief.
- Back-reference: feedback → its linked brief(s).

### B. Auto-close feedback when its linked brief completes (Eloquent model event)
- A Brief observer: on status → complete, if a linked feedback exists and isn't already resolved, set feedback → addressed with resolution="Brief #N: <summary>", resolved_by/resolved_at. Idempotent.
- **Recommended defaults (operator-confirmable):**
  1. Cardinality: use existing briefs.feedback_id (many briefs → 1 feedback); auto-address the feedback when a linked brief first reaches complete. No polymorphic needed.
  2. cancelled/abandoned brief → do NOT auto-address the feedback (work didn't ship); leave it open.
  3. Feedback status vocab: 'addressed' (matches what #171's worker used + existing feedback.status).

### C. UX / surfacing
- /feedback: show each item's linked brief(s) (id + status, clickable) + whether it auto-closed.
- Brief detail: show the source feedback (id + link) when feedback_id is set.

## Relationship
Concrete FIRST instance of the model-event-driven automation in #172 (app-wide health/audit-log) — proves the observer pattern before the broader audit log. Motivated by feedback #77 / brief #171.

## Open decisions (confirm or accept the recommended defaults above)
1. Link cardinality (recommend: existing FK, many-briefs→1-feedback).
2. cancelled/abandoned brief behavior (recommend: leave feedback open).
3. status vocab: addressed vs resolved (recommend: addressed).

Status: idea — small refinement to lock the 3 decisions, then dispatchable.
[3] note_added flower-orchestrator: Operator confirmed the 3 recommended defaults (2026-07-04) — decisions LOCKED: (1) cardinality = existing briefs.feedback_id FK (many briefs → 1 feedback); auto-address the feedback when a linked brief FIRST reaches complete; no new polymorphic table. (2) cancelled/abandoned brief → do NOT auto-address the linked feedback (work didn't ship) — leave it open. (3) feedback status vocab = 'addressed'. Proceed with the full proposed scope A (auto-link on create: brief_create optional feedback_id + feedback_promote as canonical promote-to-brief that sets briefs.feedback_id + link_added event/provenance; feedback→brief back-reference) + B (Brief Eloquent observer auto-marks linked feedback 'addressed' on status→complete, idempotent, resolution="Brief #N: <summary>") + C (/feedback surfaces linked brief(s)+status clickable; brief detail surfaces source feedback).
[4] status_change flower-orchestrator: (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: #175` to every commit for this brief so flower can exact-link commits back to the brief.