docs: spell out check → build workflow for enhanced migrations

[Kamirus]

Agents working on enhanced migrations often stop after mops check --fix and treat the migration as complete, even though no wasm is produced until mops build runs.

Before: Enhanced migrations docs said where to put chain files and that check/build auto-inject --enhanced-migration, but did not state the two-step workflow up front.

After: Right after "Create migration files directly in the chain directory", docs and the mops-cli skill now say to run mops check --fix (or mops check <canister>) first, then mops build — and that check alone does not produce output.

Closes #557.

Made with Cursor

[github-actions]

Cursor AI review

👍 APPROVE — looks safe to merge

Category	Assessment	Details
Summary	✅	Docs-only clarification: after creating enhanced migration chain files, run mops check/mops check --fix to validate compilation, then mops build for the wasm artifact. Updates docs/docs/09-mops.toml.md and .agents/skills/mops-cli/SKILL.md in sync.
Code Quality	✅	Minimal, focused additions; no speculative content.
Consistency	✅	Matches existing enhanced-migration docs and skill structure; skill and config reference stay aligned.
Security	✅	No code or auth/surface changes.
Tests	✅	Documentation-only; no behavioral change to test.
Maintainability	✅	Addresses agent confusion (issue #557) without duplicating full command docs elsewhere.

Verdict

Decision: APPROVE
Risk: Very Low
Reason: Two-line documentation and skill update accurately describe the check-then-build workflow for enhanced migrations, with no CLI, backend, or config schema changes. No correctness or production risks identified.

---

Generated for commit 17734f3