Submit Suggested Changes

Persist a plan emitted by the agent.

Each call creates a new plan and supersedes the ACTIVE plan in the same supersede scope, of which there is at most one:

• In case of a routine run, the scope is the routine, so a later fire replaces what an earlier fire left pending (even if the plan is in a different session).
• In case of a manual chat, the scope is that session alone — it can never withdraw a routine's pending plan.

version does not follow the scope: it counts resubmissions within one session. See plan.repository.create_plan.

The plan id we return is server-generated and stable; the agent's own Plan.id is intentionally not used as an idempotency key (the agent isn't trusted to mint stable ids, and a duplicate-content row is harmless).