@reddoorla/maintenance 0.94.0 → 0.95.0

package/README.md

@@ -151,6 +151,37 @@ Pre-flights that the site is on pnpm (refuses with a clear remediation if `packa
 
 The full 7-step Svelte 4 → 5 migration: bump framework versions, migrate `svelte.config.js`, run the official `svelte-migrate` codemod, run `@tailwindcss/upgrade`, apply gotcha codemods over `src/**/*.svelte`, verify with `pnpm install` + `pnpm run check`, and write a `MIGRATION_SVELTE_5.md` summary. Each step is its own commit; the file leaves a record of what ran and what may need manual review.
 
+### `match-harness` _(standalone — not part of `init`)_
+
+Installs the matching harness used to rebuild a site against a live reference (a Webflow or Blux original), in one commit on its own branch.
+
+```bash
+reddoor-maint match-harness --ref https://client.webflow.io
+reddoor-maint match-harness acme --ref https://acme.webflow.io --cand http://localhost:4173
+reddoor-maint match-harness --fleet airtable --ref https://client.webflow.io --matrix 1440,834,390
+```
+
+`--ref` is **required**. The harness gates against a live reference; with no reference it can only ever report an absence of errors, so the recipe refuses instead of installing something that goes green on nothing. `--cand` defaults to `http://localhost:5173` and `--matrix` to `1440,834,390`.
+
+What lands, and who owns it:
+
+| Installed                                                                                                           | Owner                                             |
+| ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
+| `matching/harness.json`                                                                                             | **site** — the page table, hosts, matrix, marks   |
+| `matching/harness.mjs`                                                                                              | recipe — the only reader of `harness.json`        |
+| `matching/gate.sh`, `census.sh`                                                                                     | recipe — the geometry and style gates             |
+| `matching/next.mjs`, `strikes.mjs`, `build-spec.mjs`, `census-count.mjs`                                            | recipe — round protocol                           |
+| `matching/floors.mjs`, `census-deviations.mjs`, `LEDGER.md`, `spec-sections/_header.md`, `spec-sections/_chrome.md` | **site** — the records                            |
+| `src/routes/dev/match/[uid]/+page.server.ts`, `+page.svelte`                                                        | recipe — the dev-guarded candidate twin           |
+| `src/lib/site-pages.js` / `site-pages.test.ts`                                                                      | **site** scaffold / recipe test                   |
+| `.gitignore`, `.prettierignore`, `CLAUDE.md`                                                                        | marked blocks appended, once, on their own marker |
+
+**Edit `matching/harness.json`, never `matching/harness.mjs`.** `harness.json` is the data — the page table, the reference and candidate origins, the breakpoint matrix, the threshold, and the `refMark` / `candMark` / `selfHosts` the reference preflight uses. `harness.mjs` is the read layer every gate goes through, and the recipe owns its bytes: it is byte-compared on the next run, safe-replaced when it still matches a shipped version, and FLAGGED and left alone when it does not. A hand edit there is never silently reverted — and never silently kept as though it were ours either.
+
+Site-owned files are install-if-absent and are never rewritten. Re-running is a `noop`: the three appended blocks are idempotent on their markers, and every installed file that still matches its template is skipped.
+
+Two things a fresh install deliberately will **not** do until the operator acts. `harness.json` ships `refMark: ""`, so `gate.sh` refuses before spending a run — a 200 is not evidence that a host is the reference, and a production host repointed at our own build answers 200 too. And no page has a `matching/SPEC.md` section yet, so the Phase 1 preflight refuses geometry rounds. Both are fail-closed on purpose.
+
 ---
 
 ## Audits

package/dist/announce-PGT4SZZB.js

@@ -31,8 +31,8 @@ import {
   renderReportHtml,
   resolveCopy
 } from "./chunk-KJGKZLCT.js";
-import "./chunk-5UINJNAJ.js";
 import "./chunk-BGTYPVLT.js";
+import "./chunk-5UINJNAJ.js";
 import {
   listWebsites,
   siteSlug,

package/dist/{blux-NXQLMS4W.js → blux-4KNXUP2K.js}

@@ -4767,4 +4767,4 @@ ${lines.join("\n")}`,
 export {
   runBluxCommand
 };
-//# sourceMappingURL=blux-NXQLMS4W.js.map
+//# sourceMappingURL=blux-4KNXUP2K.js.map

package/dist/{bump-deps-6OR7LL4E.js → bump-deps-C5G2EFBB.js}

@@ -5,19 +5,19 @@ import {
   appendSkipNotice,
   fleetWorkdir,
   prepareFleetSites
-} from "./chunk-TCF6S7AD.js";
+} from "./chunk-LM2NHRCJ.js";
 import {
   resolveSites
 } from "./chunk-Z2K4JPQ3.js";
 import {
   bumpDeps
-} from "./chunk-PPIZHDJL.js";
-import "./chunk-ZTPPCHDB.js";
+} from "./chunk-CJ2RMTT7.js";
+import "./chunk-ZQV7UQNE.js";
 import "./chunk-Z3JXLULD.js";
 import "./chunk-LBYOLBW7.js";
 import "./chunk-RARREDQE.js";
 import "./chunk-XXTZBPUY.js";
-import "./chunk-XTK5VIQB.js";
+import "./chunk-AVEQUR44.js";
 
 // src/cli/commands/bump-deps.ts
 import { resolve } from "path";
@@ -57,4 +57,4 @@ async function runBumpDepsCommand(site, opts) {
 export {
   runBumpDepsCommand
 };
-//# sourceMappingURL=bump-deps-6OR7LL4E.js.map
+//# sourceMappingURL=bump-deps-C5G2EFBB.js.map

package/dist/{chunk-LS6QPANO.js → chunk-2LYOAB2E.js}

@@ -3,7 +3,7 @@ import {
 } from "./chunk-J7SZQUCW.js";
 import {
   withRecipe
-} from "./chunk-ZTPPCHDB.js";
+} from "./chunk-ZQV7UQNE.js";
 
 // src/recipes/svelte-codemods.ts
 import { writeFile } from "fs/promises";
@@ -32,4 +32,4 @@ async function svelteCodemods(site) {
 export {
   svelteCodemods
 };
-//# sourceMappingURL=chunk-LS6QPANO.js.map
+//# sourceMappingURL=chunk-2LYOAB2E.js.map