[#216 PR-2] /decisions Capture seam — enrich DecisionAutoLinkService to link sessions/commits/feedback/parent

Merged flower/221-decisions-capture-seam into master on MAIN — merge commit **576c17e** (worker commit 89d80fa). Full suite green on MAIN (1088 passed, 2 pre-existing skips, 6744 assertions); pint clean. No Horizon reload: DecisionAutoLinkService has zero Jobs/Listeners references — it runs inline from DecisionService (MCP/web), so web + new sessions get new code immediately; standing daemon MCP servers self-heal on next reset. TODO (post-#222): run `flower:backfill-decision-links` on MAIN to enrich existing decisions so /decisions buckets populate on real data. Worker proc 1124 closed.

**PR-2 Capture seam landed (flower-221-worker, dispatch #102).** Branch `flower/221-decisions-capture-seam`, commit **89d80fa** (off master f54c7ac). NOT merged — orchestrator merges from MAIN. **What changed** - `app/Services/Briefs/DecisionAutoLinkService.php` (+116) — `syncDecision()` now, for a Brief-subject decision, also links the originating context off the subject brief, reusing the unchanged idempotent `link(Decision, Model, BriefLinkRelation, auto)` (firstOrCreate). No `DecisionService` dep; writes `decision_links` directly. - **Sessions** → subject brief's participant `session_id`s, as `Execution`. - **Commits** → the brief's own commit links (`brief_links` where `linkable_type=Commit`), as `Result`. - **Feedback** → `brief.feedback_id`, as `Seed`. - **Parent/epic** → `brief.parent_brief_id`, as `Reference` (distinct `linkable_id` from the subject self-link). - Bounded: `MAX_PER_BUCKET=5` sessions/commits, most-recent-first (participants by `last_seen_at` desc; commit links by `ts` desc). Feedback + parent are single-valued. - `app/Console/Commands/BackfillDecisionLinks.php` (new) — `flower:backfill-decision-links {project?} {--all} {--dry-run}`. Replays the additive/idempotent sync over existing decisions (open by default; every non-standalone decision with `--all`; project-scoped by id/slug/name/root_path). `--dry-run` reports `in_scope=N` without writing. Uses `eachById` chunking; summary line `processed/links_created/decisions_enriched`. - Tests: `tests/Feature/Decisions/DecisionAutoLinkServiceTest.php` (+enrichment: each bucket+relation, cap-most-recent-first, enriched idempotency; existing subject/idempotent/standalone stay green) and new `tests/Feature/Console/BackfillDecisionLinksCommandTest.php` (enrich / dry-run / --all / project-scope). **Morph-type ↔ bucket confirmation (design doc Open question):** no morph map in the app, so `linkable_type` is the full class name and `class_basename` yields `Session`/`Commit`/`Feedback`/`Brief` — exactly what PR-1's `components/decisions/trace-summary.blade.php` buckets (Session/Segment→sessions, Commit→commits, Feedback→feedback, parent-Brief-by-id→epic; subject-brief Reference self-link deduped by `id===subject_id`). Buckets populate as designed. **Verification:** full suite green (`~/bin/php artisan test` → 1088 passed, 2 pre-existing skips, 6744 assertions); `pint --test` clean on all four files. syncDecision fires unchanged from `DecisionService` ask/answer paths (lines 72/121), so live decisions enrich on next mutate; the backfill covers already-open ones.

Child of Brief #216. Design doc: `docs/design/216-decisions-feed-redesign.md` §"Sequenced delivery" PR-2. Sequenced AFTER PR-1 (#220) — PR-2 populates the trace-summary + detail link list PR-1 renders. ## Scope (≈ ≤300 lines) Today `DecisionAutoLinkService::syncDecision()` (`app/Services/Briefs/DecisionAutoLinkService.php:30`) links ONLY the subject brief as `reference` — so the "linked context" list is empty or one row. Extend it to derive and `link()` the originating context, reusing the existing idempotent `link(Decision, Model, BriefLinkRelation, auto=true)` (`:46`, `firstOrCreate` on `[linkable_type, linkable_id, relation]`) — no signature change needed: - **Sessions/segments** — from the subject brief's participants (`brief_participants.session_id`). - **Commits** — from the subject brief's events/links (the brief's own commit links). - **Feedback** — from `brief.feedback_id` (the source feedback). - **Parent/epic** — the brief's `parent_brief_id` brief. Pick relations from the existing `BriefLinkRelation` vocab (Seed/PlanSource/Execution/Result/Reference) — keep the subject-brief `Reference` self-link as-is (PR-1's trace-summary dedupes it). Bound the fan-out (cap N per bucket, most-recent-first) so a hot brief doesn't link hundreds of rows. Add a **backfill artisan command** to sync open decisions retroactively so existing calls populate. ## Constraints - `link()` stays idempotent — re-running `syncDecision()` must not duplicate. - Writes `decision_links` directly (no `DecisionService` dep — avoid the container cycle, as the class doc notes). - Confirm the linked morph types match PR-1's trace-summary bucket mapping (Session/Segment/Commit/Feedback/parent-Brief) so buckets populate as designed (design doc Open question "Trace-summary buckets"). ## Acceptance A decision with a real subject brief shows populated trace-summary counts + a multi-row grouped linked-context list; backfill covers open decisions; no duplicate links on re-sync; `php artisan test` green; `pint` clean.