Harness 6.1 Native Windows Codex #6561

Part of #6535.

• Already in place: the Job Object plumbing (compatibility.ts ~318; Claude's supervisor.ts ~318-334).
• To build:
  • a Windows conformance leg
  • the windowsSandbox/setupStart probe (codex-appserver/PROBES.md ~25)
  • foreignMcpServerOverrides on win32 (bridge/mcp-isolation.ts ~80)
  • process-tree ownership and cleanup
  • paths and quoting
  • approvals
• Dependency: a Windows CI runner or host. If none is available, Windows stays unresolved; it is not recorded as a pass.
• Acceptance: conformance evidence for the exact pack and layer, plus real product runs (native-plus-MCP, continuation, approval, cancel) for both clients on win32-x64.

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#6568: refactor(harness): share native conformance process observers
• MCPJam/inspector#6569: feat(harness): prepare Codex Windows sandbox conformance
• MCPJam/inspector#6570: fix(harness): isolate Windows Codex MCP servers using effective config
• MCPJam/inspector#6571: ci(harness): add native Windows Codex qualification

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