[P0.5] `VerificationWrapper` runs gates/quick-fixes against the main repo, not the worktree the agent modified

[frankbria]

Severity: high | Category: correctness | Phase: P0.5

Problem

Runtime passes the worktree path to wrapper.run(...), but the wrapper verifies with run_gates(self._workspace, ...) and quick-fixes self._workspace.repo_path — both the original repo. Under worktree isolation gates test an unmodified tree (trivially pass → false COMPLETED) while corrections target the wrong checkout.

Evidence

codeframe/core/adapters/verification_wrapper.py:92

Acceptance criteria

• Gates and quick-fixes execute against the workspace_path argument passed to run().
• Test: with isolation=worktree, a failing gate in the worktree causes a correction round (not a false pass).

Dependencies

blocked by #714 ([P0.3])

---

_{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

#386 - [Phase 2.5-F] Harden verification gates and add batch-level QA [merged]
#434 - feat(core): verification gate wrapper with quick fixes and escalation [merged]
#441 - feat(core): worktree-per-task isolation for parallel batch execution [merged]
#537 - feat(core): WorktreeRegistry, orphan cleanup, and get_base_branch (#533) [merged]
#705 - fix(security): workspace path allowlist + session ownership (#655) [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!

[frankbria]

Resolved by #714. The problem is explicitly scoped 'Under worktree isolation' and the AC test requires isolation=worktree — but #714 hard-rejects worktree isolation, so a worktree run (and the false-pass it caused) can no longer occur. Verifying gates against the worktree is only meaningful once worktree is re-enabled, so this work is folded into #787. Closing as resolved-by-#714.