feat(cli): add mops deployed post-deploy hook + init bootstrap

[Kamirus]

What

Implements specs/mops-deployed.md.

After a successful deploy, mops deployed promotes the just-built .most into a committed deployed/<name>.most so mops check-stable compares against the deployed version on the next build. Closes the manual gap that today silently rots the stable-check baseline whenever someone forgets to copy the file.

CLI surface

mops deployed [canisters...]      # post-deploy hook: copy <outputDir>/<name>.most → <dir>/<name>.most
mops deployed init [canisters...] # one-time bootstrap: empty-actor baseline + sets [check-stable].path

• Source: [build].outputDir (default .mops/.build); override with --output.
• Destination: new [deployed].dir config (default deployed); override with --dir.
• Canister selection mirrors mops build / mops check.
• Missing source → error, never regenerates.
• Warns when [check-stable].path doesn't point at <dir>/<name>.most so silent baseline drift is visible.
• init is idempotent and only rewrites mops.toml when something actually changes.

Lifecycle (from the spec)

mops deployed init backend     # once, before first deploy
mops check backend             # every change
mops build backend
icp deploy
  mops deployed backend        # post-deploy hook
git add deployed/ && git commit

Out of scope

• .did handling — interface-change-driven, lives in mops generate candid (separate spec).
• Per-canister directory override, per-environment dirs, deployed-manifest fields — all flagged as open questions in the spec for v2.

Made with Cursor

[github-actions]

Cursor AI review

👍 APPROVE — looks safe to merge

Category	Assessment	Details
Summary	✅	Adds mops deployed (post-deploy .most promotion) and mops deployed init (empty-actor baseline + [check-stable].path wiring), with [deployed].dir config, docs, changelog, skill, and Jest coverage.
Code Quality	✅	Reuses filterCanisters, resolveCanisterConfigs, resolveConfigPath, and writeConfig; no speculative scope beyond the spec.
Consistency	✅	Canister selection, --output/[build].outputDir defaults, and all-canisters-with-no-args behavior mirror mops build / mops check.
Security	✅	Local file copy/write only; no chain access, signing, or registry interaction.
Tests	✅	Broad coverage (init idempotency, path warnings, config overrides, multi-canister filtering, e2e with check-stable); snapshot used for the primary init happy path, targeted assertions elsewhere.
Maintainability	✅	Clear separation of config-relative vs resolved paths; warnings surface baseline drift when [check-stable].path and [deployed].dir diverge.

Verdict

Decision: APPROVE
Risk: Low
Reason: This is an additive, well-documented CLI feature with sensible error handling (missing source fails hard, path mismatches warn) and no breaking changes to existing commands or config. Project sync requirements (types, docs, changelog, skill) are met.

---

Generated for commit cf80a1b