mx-pg-controller-migration
Installation
SKILL.md
mx-core PG Cutover · Controller Verification & Downstream Sync
Repos in scope (paths assume worktree root)
| Layer | Path | Concern |
|---|---|---|
| Server | apps/core/src/modules/<mod>/ |
controller / service / repository correctness |
| SDK | packages/api-client/{models,controllers}/ |
type definitions must match server response |
| Dashboard | /Users/innei/git/innei-repo/admin-vue3/apps/admin/src/{models,api,views/manage-<mod>}/ |
consumer code reads new field names |
No server-side back-compat shim. If a field rename is correct on PG, propagate it through SDK and dashboard. The user has explicitly opted out of legacy aliases.
Data completeness IS a bug. A migration that compiles but silently drops related, category, or any joined value is broken. Always cross-check what the old mongoose pipeline emitted against what the new repository emits.
Workflow (run in this order)
1 · Snapshot the migration delta
Identify the PG cutover commit for the module and diff against the last Mongo-era commit. The mx-core history convention: