[P1.8] Deduplicate blocker creation (adapter + runtime each create one → double blockers/webhooks)

[frankbria]

Severity: high | Category: correctness | Phase: P1.8

Problem

VerificationWrapper/plan Agent already persist a blocker before returning AgentResult(status="blocked"), then runtime.execute_agent creates a second one from result.blocker_question. blockers.create has no dedupe and fires the outbound webhook per call, so every blocked run produces two OPEN blockers + two blocker.created webhooks; a human must answer both.

Evidence

codeframe/core/runtime.py:825, codeframe/core/adapters/verification_wrapper.py:204

Acceptance criteria

• Blocker creation has a single owner; runtime creates one only when the result carries a question with no already-persisted blocker (or dedupe on (task_id, question, OPEN)).
• Test: one escalation produces exactly one OPEN blocker and one webhook.

Dependencies

None

---

_{Filed from the SaaS launch-readiness audit. Atomic: one developer, one session. Work order: strictly P0.1 → P3.12 (no forward dependencies).}

[coderabbitai]

🔗 Related PRs

#18 - feat(049-human-in-loop): Complete human-in-the-loop blocker system (Phases 1-9) [merged]
#365 - feat: integrate fix_tracker escalation and blocker detection into ReactAgent [merged]
#495 - feat(web-ui): blocker lifecycle explanation and recovery guidance (#473) [merged]
#530 - feat: differentiate system/agent/human blocker origins visually (#487) [merged]
#531 - fix: address claude-review feedback on blocker origins (#487) [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!