recall_active: guard against harness-mismatch driver attribution

You are being dispatched from flower Brief #21: recall_active: guard against harness-mismatch driver attribution

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

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: flower/recall-active-harness-guard
- worktree: not specified
- kind: fresh

Current brief spec:
## Problem
`recall_active` confidently mis-attributes a live session to the WRONG Solo process.
Observed (flower_feedback mcp_issue #31, source flower-tda-orchestrator, 2026-07-01):
the live **codex** session #3266 (thedarkroom_automation) was returned with
`driver:"solo"` linked to Solo **pid 984** — which is the **claude**
`flower-tda-orchestrator` daemon, a different harness entirely. It was a confident
exact link (`driver:"solo"`), NOT `driver:"ambiguous"` with candidates.
Secondary observation: session #3266 also read `live` ~2h after its last activity
despite completed work (lifecycle staleness — likely a separate issue; note but do
not necessarily fix here).

## Fix
In the recall_active -> Solo correlation path (solo-cli correlation / whatever resolves
`driver` + the linked Solo agent), add a **harness-mismatch guard**: a candidate Solo
agent must not be returned as the confident `driver:"solo"` owner of a session whose
harness differs from the Solo agent's harness (a codex session cannot be owned by a
claude Solo process, and vice-versa). On mismatch, downgrade to `driver:"ambiguous"`
(with candidates) or no link — never a confident wrong link.

## Acceptance
- A codex session is never returned with a confident `driver:"solo"` link to a claude
  Solo process (and vice-versa); mismatches degrade to ambiguous/none.
- Add a regression test covering the harness-mismatch case.
- Keep `php artisan test` green; run pint on changed files.
- Add a `Brief: #<id>` trailer to every commit; report material progress via brief_append.

## Provenance
flower_feedback mcp_issue #31 during the 2026-07-01 thedarkroom_automation daemon-spawn dogfood.

Recent/key trace events:
[1] participant_joined flower-orchestrator: (no body)
[2] note_added flower-orchestrator: Filed from flower_feedback mcp_issue #31 (flower-tda-orchestrator). recall_active confidently linked a live codex session to a claude Solo process.
[3] plan_proposed flower-orchestrator: ## Problem
`recall_active` confidently mis-attributes a live session to the WRONG Solo process.
Observed (flower_feedback mcp_issue #31, source flower-tda-orchestrator, 2026-07-01):
the live **codex** session #3266 (thedarkroom_automation) was returned with
`driver:"solo"` linked to Solo **pid 984** — which is the **claude**
`flower-tda-orchestrator` daemon, a different harness entirely. It was a confident
exact link (`driver:"solo"`), NOT `driver:"ambiguous"` with candidates.
Secondary observation: session #3266 also read `live` ~2h after its last activity
despite completed work (lifecycle staleness — likely a separate issue; note but do
not necessarily fix here).

## Fix
In the recall_active -> Solo correlation path (solo-cli correlation / whatever resolves
`driver` + the linked Solo agent), add a **harness-mismatch guard**: a candidate Solo
agent must not be returned as the confident `driver:"solo"` owner of a session whose
harness differs from the Solo agent's harness (a codex session cannot be owned by a
claude Solo process, and vice-versa). On mismatch, downgrade to `driver:"ambiguous"`
(with candidates) or no link — never a confident wrong link.

## Acceptance
- A codex session is never returned with a confident `driver:"solo"` link to a claude
  Solo process (and vice-versa); mismatches degrade to ambiguous/none.
- Add a regression test covering the harness-mismatch case.
- Keep `php artisan test` green; run pint on changed files.
- Add a `Brief: #<id>` trailer to every commit; report material progress via brief_append.

## Provenance
flower_feedback mcp_issue #31 during the 2026-07-01 thedarkroom_automation daemon-spawn dogfood.
[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.
- Add a git commit trailer `Brief: #21` to every commit for this brief so flower can exact-link commits back to the brief.