Harness 2.1 Local Claude Code: approving re-proposes the same command (QA-02, confirmed) [inspector] #6541

Part of #6535.

Do this after 1.3. Once Claude parks, it goes through the same strict claim.

• Cause:
  • Only Codex sets liveApprovalRuntime: true (server/utils/harness/registry.ts ~997). The doc comment (~319-327) assumes Claude can be resumed from disk.
  • At the pause nothing is parked (run-harness-turn.ts ~4443-4457). Local teardown (~4618-4628, local/local-turn.ts ~660-680) kills the bridge whose canUseTool is waiting.
  • On resume, classifyDiskLog chooses a rerun with "Continue.". The model then proposes the command again.
• Change:
  • Set liveApprovalRuntime: true for Claude Code, and make parking work. Verify each of these:
    • bridgeGenerationOf reads Claude's bridge token;
    • the parked bridge stays reachable for reattach;
    • adoptParkedLocalTurn and the lease rebind work with Claude's model gateway;
    • canUseTool doesn't time out before the 30-minute park TTL.
  • Correct the comments in registry.ts and local/resume-state.ts.
• Tests: a local Claude approval across two HTTP requests that goes through the route's real pause and teardown path. Cover:
  • approve
  • deny
  • double submit
  • reload
  • Stop while waiting
  • park TTL expiry
  • process registry is empty after Stop
• Done: the QA-02 reproduction passes.

Delivery rules

• Fresh worktree and branch; each PR at most 400 handwritten changed lines; stack when necessary.
• Verify the actual failing boundary and run repository checks.
• Preserve broker-only model auth, no venue/engine fallback, and separate infrastructure failures.
• Human-only: production deployment, flags/env changes, rebuilds/backfills, signed/published packs and large paid runs.

Status: planned; completion requires the acceptance evidence above.

Pull request stack

• MCPJam/inspector#6567: fix(harness): retain local Claude bridges while approval is pending

The implementation hub records merge order, current verification and remaining release gates. PR publication does not mark the deployed or packaged acceptance matrix complete.