fimo 0.3.2-experimental.1783328062928 → 0.3.2-experimental.1783355472846

package/assets/skills/fimo/SKILL.md

@@ -14,7 +14,7 @@ You are writing code in a Fimo project — a content + media + forms + analytics
 
 This skill is version-locked to this project's installed `fimo` package — the shapes here match what your code can actually use.
 
-For CLI commands and workflows (creating a project, pushing schemas/forms, deploying, managing labels, etc.), the **`fimo-cli`** skill is the source of truth. Run every CLI command as `npx fimo@latest <command>` (always the latest, no global install). If `fimo-cli` isn't loaded for your AI tool, register it with `npx fimo@latest skills install --mode=copy`.
+For CLI commands and workflows (creating a project, pushing schemas/forms, deploying, managing labels, etc.), the **`fimo-cli`** skill is the source of truth. Run every CLI command as `npx fimo <command>` when the project declares a `fimo` dependency (it pins the version matching the project's backend); otherwise use `npx fimo@latest`. If `fimo-cli` isn't loaded for your AI tool, register it with `npx fimo skills install --mode=copy`.
 
 ## Critical: NEVER hardcode user-facing things
 

package/assets/skills/fimo-migration/SKILL.md

@@ -17,7 +17,10 @@ exports, source repositories, CMS exports, media folders, or any hybrid of those
 It owns intake, source inventory, URL crawl bootstrapping, ledger normalization,
 imports, and QA so any LLM can run the work without silently dropping content.
 
-> Run every `fimo` command as `npx fimo@latest <command>` — always the latest CLI, no global install.
+> Run every `fimo` command as `npx fimo <command>` when the project declares a
+> `fimo` dependency (adopted/wrapped projects pin an exact version tied to their
+> backend — never override it with `@latest`). Only fall back to
+> `npx fimo@latest` when the project has no `fimo` dependency.
 
 ## Non-Negotiables
 

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

@@ -66,7 +66,7 @@ rebuild migrations:
       "wrappedMedia": 3,
       "wrappedRichText": 1
     },
-    "planPath": ".fimo/migration/wrap-plan.json"
+    "planPath": ".fimo/migration/plan.json"
   }
 }
 ```

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

@@ -40,8 +40,11 @@ Run this gate before reporting completion.
 
 When the manifest says `mode: "wrap"`:
 
-- `fimo migrate wrap --check` exits zero, or every remaining item is an
-  explicit ignored/unresolved ledger entry with a reason.
+- `fimo migrate wrap --check` exits zero — it enforces coverage (zero
+  unwrapped items), render parity (rendered text/marks/media/links identical
+  to the pre-wrap baseline), and seeding (every wrapped key exists in the
+  database) — or every remaining item is an explicit ignored/unresolved
+  ledger entry with a reason.
 - Labels are seeded: every `FimoText`/`t()` key exists in `fimo labels list`
   with the original string. Fallback-only content fails the gate.
 - Wrapped media/rich text have their `WrappedMedia`/`WrappedRichText` entries

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

@@ -55,7 +55,7 @@ fimo migrate        # inside an adopted JS codebase this IS the wrap flow
 (`fimo migrate wrap` is the explicit form; `fimo migrate <url>` remains the
 crawl-and-rebuild path for URL-only migrations.)
 
-Writes `.fimo/migration/wrap-plan.json` (every unwrapped item with
+Writes `.fimo/migration/plan.json` (every unwrapped item with
 `kind`/`file`/`line`/`preview`) and `.fimo/migration/wrap/agent-prompt.md`.
 The scan finds hardcoded JSX text, `img`/`Image`/`video` sources, file links
 (pdf/zip/docx/…), and user-visible attribute strings (`placeholder`, `title`,
@@ -90,7 +90,7 @@ outside client components (`'use client'`).
 
 ### W4. Wrap
 
-Work through `wrap-plan.json` item by item:
+Work through `plan.json` item by item:
 
 | Item kind                           | Wrap with                                                                              |
 | ----------------------------------- | -------------------------------------------------------------------------------------- |
@@ -131,14 +131,33 @@ Fallbacks are resilience, not storage. Every wrapped item is seeded into Fimo:
 A wrap migration whose labels/entries were never created in Fimo is
 `draft-only`, exactly like a rebuild migration with un-imported seed JSON.
 
-### W6. Verify
+### W6. Verify — three machine-enforced gates
+
+`fimo migrate wrap --check` is the definition of done. It fails until all
+three gates pass:
+
+1. **Coverage** — zero unwrapped items. Deliberate exceptions are recorded in
+   the ledger and the gate honors them: add to
+   `.fimo/migration/manifest.json` → `wrap.exemptions[]` an entry
+   `{ file, kind, preview, reason, status }` where `(file, kind, preview)`
+   matches the plan item exactly (a content change invalidates the exemption
+   so the item resurfaces).
+2. **Render parity** — the check boots the project's dev server and compares
+   every route's rendered text, inline marks, media srcs, and link hrefs
+   against the pre-wrap baseline that `fimo migrate` captured
+   (`.fimo/migration/parity-baseline.json`). Drift is reported per route and
+   block. Run the check right after wrapping (strict, pre-seed) and again
+   after seeding. If the baseline is missing, capture one from the pre-wrap
+   git state: `git stash && npx fimo migrate snapshot && git stash pop`.
+3. **Seeding** — every wrapped key exists in the Fimo database (labels and
+   WrappedMedia/WrappedRichText entries), verified via the API. Fallbacks are
+   not storage.
+
+Never bypass a failing gate (`--no-parity` / `--skip-seeding` are for the
+owner to decide, not the agent). Additional manual checks:
 
-- `fimo migrate wrap --check` exits zero (or every remaining item is an
-  explicit ignored/unresolved ledger entry with a reason).
 - The site builds and runs **with its own toolchain** (`next build`,
   `npm run dev`, …) — never assume Vite.
-- Rendered output is identical to pre-migration: same text, same formatting
-  marks, same media. Diff rendered pages, not just code.
 - Diff audit: the migration diff contains only wiring, wrappers, label calls,
   config, and dependency changes.
 - Then `fimo deploy` (allowed in wrap mode: it pushes the preview env and

package/dist/cli/bundle.json

@@ -1,8 +1,8 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-07-06T08:54:36.096Z",
-  "cliVersion": "0.3.2-experimental.1783328062928",
+  "bundledAt": "2026-07-06T16:31:25.154Z",
+  "cliVersion": "0.3.2-experimental.1783355472846",
   "external": [
     "oxc-parser",
     "fsevents"