[redwon]

What Changed

• persist Cursor plan markdown behind the ACP planUri
• refresh changed plan markdown before a turn completes
• cover the initial-plan and refinement flow with focused adapter tests

Why

Cursor plan refinements edit the plan file returned by cursor/create_plan. T3 previously returned a non-contract response without a backing file, so the Implement action could paste the initial plan after the user refined it. Returning the documented outcome and projecting the backing file keeps implementation aligned with the latest accepted plan.

Verification

• pnpm exec vp test run apps/server/src/provider/acp/CursorAcpExtension.test.ts apps/server/src/provider/Layers/CursorAdapter.test.ts
• pnpm exec vp run --filter t3 typecheck
• targeted lint for all edited files

Checklist

• This PR is small and focused
• I explained what changed and why
• UI screenshots are not applicable; this is a provider adapter fix
• Interaction video is not applicable

Generated with GPT-5.6 Sol in Cursor.

Made with Cursor

Note

Implement three-step refined plan flow in CursorAdapter for ACP create-plan

• Adds a CursorCreatePlanResponse schema in CursorAcpExtension.ts with a discriminated outcome union (accepted, rejected, cancelled) including an optional planUri.
• The cursor/create_plan handler in CursorAdapter.ts now persists plan markdown to a deterministic file path under stateDir/plans/cursor/{instanceId}/{threadId}.md and returns a planUri file URL to the caller.
• Before each turn.completed event, syncProposedPlanFromFile reads the backing file and emits a turn.proposed.completed event, enabling refined plan markdown written during the turn to be surfaced before the turn closes.
• The mock agent in acp-mock-agent.ts implements the full three-prompt flow when T3_ACP_EMIT_CREATE_PLAN=1: propose initial plan (capture planUri), write refined markdown to the file, then re-propose the refined plan.
• Deduplication in emitProposedPlanCompleted prevents repeated turn.proposed.completed events for identical plan content within a session unless forced.

^{Macroscope summarized d646f5d.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 67b04ce2-f024-478e-a35c-7854d7fd72ce

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit dc3766c. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new plan file persistence and syncing capabilities with file I/O, state tracking, and protocol response changes. Despite the 'fix' label, these are significant runtime behavior changes that warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Closing in favor of #2829 (orchestration V2).

#2829 deletes the V1 orchestration layer this PR builds on — apps/server/src/orchestration/**, provider/Layers/*Adapter.ts and provider/Services/** are removed and replaced by apps/server/src/orchestration-v2/**, with the IPC surface renamed to ORCHESTRATION_V2_WS_METHODS. The files this PR touches either no longer exist or are rewritten, so it can't be rebased — it would need reimplementing against the V2 adapters.

This is not a judgement on the change itself. Several of these are real gaps we still want fixed; the base just moved out from under them.

Once #2829 merges, please rebase onto main, port the change to the V2 equivalent, and reopen (or open a fresh PR). Ping me and I'll prioritise the review.