Plan integration 2: Centralize mutations and checkpoints

[NetDevAutomate]

Parent

• Integrate Study Plans across Now, Web architect, and MCP #7 — Integrate Study Plans across Now, Web architect, and MCP

What to build

Route create, revision, document replacement, milestone changes, lifecycle changes, evaluation, and deletion through PlanApplication so CLI and Web share one policy implementation.

Acceptance criteria

• CLI and Web no longer mutate Study Plans directly through the persistence layer.
• Plan identifier and creation time survive revisions and validated document replacement.
• Milestone changes set an explicit done value and are idempotent under retries.
• Checkpoint results distinguish complete recording from partial Markdown or SQLite writes.
• Deletion retains checkpoint history and returns an immutable result view.
• Transport adapters map shared domain failures without reimplementing lifecycle policy.

Blocked by

• Plan integration 1: Centralize reads and activation #8 — Plan integration 1: Centralize reads and activation

Definition of Done

• All remaining existing CLI and Web lifecycle paths use PlanApplication.
• An architecture test prevents CLI, Web, and MCP adapters from importing mutable store operations.
• Store, evaluation, CLI plan, and Web plan suites pass.
• Partial checkpoint failures have regression coverage.
• Capability specs and docs reflect the centralized lifecycle contract.