Release v3.2.3 — vc-update runs adaptive migration on version-equal installs

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

Author: withkynam

.claude/skills/vc-update/SKILL.md

@@ -86,7 +86,10 @@ node -e "console.log(JSON.parse(require('fs').readFileSync('$VC_UPDATE_TMPDIR/vc
 
 Compare the remote manifest `version` against `currentVersion`.
 
-- If they are equal: report **"Already up to date (vX.Y.Z)"** and clean up `$TMPDIR`. **Stop.**
+- If they are equal: **do NOT stop yet.** Version equality means the deterministic file-sync will be a no-op, but the ADAPTIVE legacy-layout migration (Part D) is NOT version-gated and may still have work to do — e.g. an old project was just brought to the current version by `install.sh` (which writes `.vc-version` but cannot run the adaptive migration), leaving legacy-format dirs un-migrated. So on equal versions, run the **legacy-artifact scan** before deciding:
+  - Scan for any of: flat `*_PLAN_*.md` files directly under `process/general-plans/active/` or `process/features/*/active/`; sibling `process/general-plans/{reports,references}/`; sibling `process/features/*/{reports,references}/`; `process/development-protocols/references/` (any non-empty legacy layout dir in scope per Part D).
+  - **If the scan finds ZERO legacy artifacts:** report **"Already up to date (vX.Y.Z) — no legacy artifacts to migrate"**, clean up `$TMPDIR`, and **Stop.**
+  - **If the scan finds ANY legacy artifacts:** report **"Already up to date (vX.Y.Z), but N legacy artifact(s) found — running content migration"** and CONTINUE to the diff/apply path. The file diff will be empty (no add/modify/delete), but Part D safe legacy-layout migration MUST run so the legacy content is moved into task folders. Skip the version-bump messaging; the version stays the same.
 - If remote is newer (or currentVersion is `0.0.0`): continue to diff.
 - If remote is **older** than `currentVersion`: print `⚠ WARNING: downgrade v{remoteVersion} → v{currentVersion} detected. The source kit is older than your installed version. Continuing will overwrite newer harness files with older ones.` then ask for explicit confirmation before continuing. If the user does not confirm, clean up `$VC_UPDATE_TMPDIR` and stop.
 

.claude/skills/vc-update/references/vc-update.md

@@ -206,7 +206,7 @@ Classified as **removals**. Deleted locally after confirmation.
 
 ### Already up to date
 
-If `.vc-version` matches the remote manifest version, report "Already up to date" and exit. No diff computed.
+If `.vc-version` matches the remote manifest version, the deterministic file-sync is a no-op, but the adaptive legacy-layout migration (Part D) is NOT version-gated. Run the legacy-artifact scan first: if zero legacy artifacts exist, report "Already up to date — no legacy artifacts to migrate" and exit (no diff computed); if any legacy artifacts exist (e.g. `install.sh` just bumped `.vc-version` without running migration), report "Already up to date, but N legacy artifact(s) found — running content migration" and continue to the apply path so Part D migrates them (file diff stays empty; version unchanged).
 
 ### Adding a new skill to the kit
 

CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to vibecode-pro-max-kit are documented in this file.
 
+## [3.2.3] - 2026-06-20
+
+### Fixed
+
+- `vc-update` no longer skips the adaptive content migration when the installed version already matches the remote. Previously, version equality (`Step 5: Compare Versions`) stopped the run immediately — but the deterministic `install.sh` writes `.vc-version` to the new version *without* being able to run the adaptive legacy-layout migration (it has no agent). The documented upgrade flow is "run `curl install.sh | bash`, then run `vc-update` to finish migrating old folders" — yet `vc-update` would bail with "Already up to date. No changes applied," stranding legacy `reports/`/`references/` dirs and flat plans un-migrated. Now version equality runs a legacy-artifact scan first: if legacy-format dirs/plans exist, `vc-update` continues to the apply path and Part D migrates them into task folders (file diff stays empty, version unchanged); only when no legacy artifacts remain does it report up-to-date and stop. Fixed in both the skill body and the `references/vc-update.md` deep reference.
+
 ## [3.2.2] - 2026-06-20
 
 ### Fixed

README.md

@@ -88,7 +88,7 @@
   <a href="LICENSE"><img src="https://img.shields.io/github/license/withkynam/vibecode-pro-max-kit" alt="License"></a>
   <a href="https://github.com/withkynam/vibecode-pro-max-kit/graphs/contributors"><img src="https://img.shields.io/github/contributors/withkynam/vibecode-pro-max-kit" alt="Contributors"></a>
   <a href="https://github.com/withkynam/vibecode-pro-max-kit/actions/workflows/validate.yml"><img src="https://img.shields.io/github/actions/workflow/status/withkynam/vibecode-pro-max-kit/validate.yml" alt="CI"></a>
-  <a href="CHANGELOG.md"><img src="https://img.shields.io/badge/version-3.2.2-2EA043" alt="Version"></a>
+  <a href="CHANGELOG.md"><img src="https://img.shields.io/badge/version-3.2.3-2EA043" alt="Version"></a>
   <img src="https://img.shields.io/badge/agents-15-orange" alt="Agents">
   <img src="https://img.shields.io/badge/skills-33-purple" alt="Skills">
   <img src="https://img.shields.io/badge/hooks-10-blue" alt="Hooks">

vc-manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "3.2.2",
+  "version": "3.2.3",
   "include": [
     ".claude/agents/**",
     ".claude/skills/**",