fimo 0.7.0-experimental.7 → 0.7.0-experimental.9

package/assets/skills/fimo-migration/references/wrap.md

@@ -351,6 +351,41 @@ owner to decide, not the agent). Additional manual checks:
   that an edited label round-trips (`fimo labels set <key> "new"` → reload →
   rendered). `fimo publish` / `fimo deploy --publish` remain owner-only.
 
+### W7. Unwire the previous CMS — the cutover (when scaffolded)
+
+Injecting Fimo is only **half** a migration. If a CMS was scaffolded (W2/W5),
+the site now READS example content from Fimo but is still **wired to the old
+CMS**: the generated Fimo adapter falls back to it, the SDK/client is still
+imported, and the CMS env is still present. The migration is not done until a
+plain `pnpm dev` runs **purely on Fimo, with zero requests to the old CMS**.
+That cutover is the "wow" — deliver it.
+
+This phase is the agent's: every codebase talks to its CMS differently (bare
+`fetch`, an SDK client, axios, GraphQL, RSC loaders, image hosts), so the
+replacement needs judgment. The machine hands you the worklist; you do the work.
+
+1. **Read the worklist.** `npx fimo migrate cutover` lists every remaining
+   coupling — SDK/client/type deps, source lines that reach the CMS (env /
+   content-type IDs / SDK import), and leftover env keys. The generated agent
+   prompt embeds the same list under **Unwire &lt;CMS&gt;**.
+2. **Replace the data-access layer.** Prefer rewriting the CMS **client module**
+   (the one file that instantiates the SDK / holds the fetch helpers) into a
+   Fimo-backed adapter exposing the **same interface**, so every caller is fixed
+   by a single change. Read from Fimo with `fetchEntries` (`fimo/<framework>/server`).
+3. **Sever the fallthrough.** The generated Fimo adapter falls back to the CMS
+   for unmapped reads — a scaffold crutch. Once the client is Fimo-backed, drop
+   the fallthrough so an unmapped read fails loudly, never silently hits the CMS.
+4. **Remove the coupling.** Delete the CMS SDK/client/type dependencies and the
+   base-URL / token env, and fix any standalone routing the CMS handled (e.g. a
+   `/` → `/[locale]` redirect its middleware provided).
+5. **Verify — the cutover gate.** `npx fimo migrate cutover --check` must report
+   a **clean** cutover (0 couplings). Then `pnpm dev` and confirm the network
+   tab shows **zero** requests to the old CMS. Record the cutover in the manifest.
+
+Detection keys on actual CMS references, not filenames — a CMS client module you
+rewrote to call Fimo reads as clean. Keep-live sites (the user chose NOT to
+scaffold) skip this phase: the CMS stays the source of truth.
+
 ## Manifest
 
 Record wrap mode in the canonical ledger (`references/manifest.md`): set

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-07-23T07:43:57.934Z",
+  "bundledAt": "2026-07-23T12:28:05.670Z",
   "cliVersion": "0.6.0",
   "external": [
     "oxc-parser",