moveros 4.0.8 → 4.1.0

package/src/workflows/update.md

@@ -49,26 +49,23 @@ Note: File-level backups (Engine files, Areas folder, agent configs) are handled
 
 ---
 
-## 1. VERSION DETECTION
+## 1. VERSION DETECTION & MIGRATION SCAN
 
-Check current installed version:
+**Always run the migration scan. Never skip based on version labels alone.**
 
-1. Read `{VAULT_ROOT}/.mover-version` if it exists → stored version number
-2. If no `.mover-version`, scan Global Rules for `**Version:** V{X.Y}` → infer version
-3. If neither found: assume V3.0 (pre-versioning)
+The installer updates Global Rules before this workflow runs, so inferring version from the rules file will always show the latest version. The only reliable source of truth is what the Engine files actually contain.
 
-Read the CURRENT system version from the loaded Global Rules (the version you're running as).
+1. Read `{VAULT_ROOT}/.mover-version` if it exists → this is the last version the `/update` workflow completed. If it doesn't exist, this is the first time `/update` has run.
+2. Run the Engine Migration Scan (Step 3) immediately — check every Engine file for missing sections.
+3. Count the migrations needed.
 
-Output:
+**If 0 migrations needed AND `.mover-version` exists and matches current version:** "You're already on the latest version. No update needed." → Exit.
+
+**If migrations are needed (any count):** Continue to Step 1.5. Output:
 ```
-Installed: V{old}
-Available: V{new}
+Migration scan: [X] updates needed across [Y] Engine files.
 ```
 
-If versions match: run the Engine Migration Scan (Step 3) first. If 0 migrations needed: "You're already on the latest version. No update needed." → Exit. If migrations are pending: treat as update needed, continue to Step 1.5.
-
-If versions differ: continue to Step 1.5 directly.
-
 **STOP. Confirm with user before proceeding.**
 
 ---