feat: make Plan mode enforceable and recovery-safe - #100
Conversation
|
Important Review skippedToo many files! This PR contains 201 files, which is 101 over the limit of 100. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. ⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (201)
You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
What changed
Why
Plan mode must be a JCode-owned safety boundary—not a provider hint. A Plan turn must not mutate the workspace, invoke unknown capabilities, silently reuse stale plan text, or leak an unanswered prompt into a later Default turn. The UI must also report support and denial reasons truthfully.
User impact
Validation
bun run test— 12/12 tasks; server 2,262 passed / 9 skipped; web 1,106 passedbun run typecheck— 9/9 tasksbun run build— 7/7 tasksbun run fmt:check— passedbun run lint— exit 0, existing warnings only