fix(server): Codex plans offer Implement again

[juliusmarminge]

A Codex plan-mode turn that proposes a plan never offers Implement, and the sidebar never shows "Plan Ready". The composer only has the plain send arrow, and the plan cannot be implemented from the UI.

Seen live on Codex 0.156.1 / gpt-6-luna in Plan mode. After the turn settled, orchestration_v2_projection_plans held the proposed plan with "status":"completed":

Why

The Codex adapter published the finished plan item with status: "completed". Everything downstream treats only active as an open proposal:

• web hasActionableProposedPlan (the Implement button) and the sidebar's "Plan Ready" pill,
• the shell's hasActionableProposedPlan,
• message.dispatch, which rejects sourcePlanRef for a plan that is not active.

completed is the state Implement moves a plan into once it consumes it. Claude (status: "active") and Cursor (completed ? "active" : "draft") already publish finished proposals as active. The streaming deltas in the Codex adapter were already active, so the plan flipped to completed only when the item finished.

Fix

The Codex adapter publishes a finished proposed plan as active. Implement still marks it completed when it runs.

This is separate from #13775, which fixes the server-side sourcePlanRef lookup for every provider. Codex plans also need this change before the Implement button appears, and before #13775's path can accept them.

Verification

• The proposed_plan Codex replay fixture (recorded on 0.156.1) now asserts that the final proposed plan is active. It fails on the base (expected 'completed' to equal 'active') and passes with the fix.
• vp test run src/orchestration-v2/testkit/OrchestratorReplayFixtures.integration.test.ts -t "proposed_plan|plan_questions": 5 passed.
• vp test run src/orchestration-v2/Adapters/CodexAdapterV2.test.ts -t "plan|Plan": 2 passed.
• vp exec tsc --noEmit -p . in apps/server: clean. vp lint/vp fmt on the touched files show only the two no-unused-vars warnings that already exist in CodexAdapterV2.ts.
• Not run: the full server suite, and an end-to-end Implement click, because that path also needs fix(server): Implement starts a run from a proposed plan again #13775.

Model: Claude Opus 5.5 (Claude Code)

🤖 Generated with Claude Code

---

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ No successful main baseline artifact is available yet. This run establishes the initial measurement.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	—	4.9 KiB	—	6.8 KiB	✅
Codex	Thread snapshot wire	—	3.7 KiB	—	4.9 KiB	✅
Codex	Live turn WebSocket wire	—	1.2 KiB	—	2.0 KiB	✅
Codex	Live turn WebSocket decoded	—	20.4 KiB	—	29.3 KiB	✅
Codex	Live turn messages	—	2	—	8	✅
Claude	Total thread wire	—	4.9 KiB	—	6.8 KiB	✅
Claude	Thread snapshot wire	—	3.7 KiB	—	4.9 KiB	✅
Claude	Live turn WebSocket wire	—	1.2 KiB	—	2.0 KiB	✅
Claude	Live turn WebSocket decoded	—	20.8 KiB	—	29.3 KiB	✅
Claude	Live turn messages	—	2	—	8	✅

Baseline: unavailable · PR result: 112bbbf · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 106.1 KiB
• Claude decoded thread snapshot: 106.4 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Approvability

Verdict: Approved at 112bbbf

Macroscope's review found this PR approvable — This narrowly scoped Codex lifecycle fix keeps a finished proposed plan actionable until Implement consumes it, while execution nodes and turn items still complete normally. The accompanying fixture assertion covers the behavior, with no schema, infrastructure, default, or static-analysis changes.

^{You can add or adjust custom eligibility rules. Learn more.}