@cparkerwebm/webmonterey 1.2.0 → 1.4.0

package/CHANGELOG.md

@@ -11,6 +11,108 @@ build. See `/webm:upgrade`.
 
 ---
 
+## 1.4.0 — 2026-09-04
+
+### Added
+
+- **A site can lay out the `/webmaster` page itself.** Export `webmasterPage` from
+  `src/components/registry.ts` - an Astro component receiving
+  `{ title, description, intro, body }` - and the page renders it in place of the built-in
+  `<h1>` and stack of paragraphs. `intro` and each `body` entry are HTML, rendered with
+  `set:html` - the agency link is already in `intro`; `title` and `description` are text. The route, the copy, the document title, the meta
+  description, the share image and the agency JSON-LD stay the package's, so the page says the
+  same thing on every site and looks like the site it is on. Until now a site whose legal pages
+  used a richer document layout got a `/webmaster` that looked like a different site, and adding
+  its own `src/pages/webmaster.astro` collided with the injected route. The component carries no
+  copy of its own: the words are still `copy.webmaster` in `webmonterey.json`.
+
+  **`/webm:webmaster` is the skill**, materialized on the next `webm sync` - it carries a
+  complete reference component, the registry line and the checks to run on the built page, so a
+  site session has something to copy rather than a description. `/webm:new-component` sends a
+  session there the moment a site gains its document block, and `/webm:start` and
+  `/webm:launch` both point at it, so on a new site it happens in sequence; on an existing site
+  the upgrade lists it as a new skill.
+  The props are exported as `WebmasterPageProps` from
+  `@cparkerwebm/webmonterey/webmonterey/webmaster`.
+
+  **Nothing changes on a site that does not export it.** The built-in layout, `pageHeader`
+  seam included, renders as before, and examples/minimal asserts the whole `<main>` as a literal
+  so it cannot drift.
+
+### Changed
+
+- **The `/webmaster` copy.** "This custom website was designed, built and managed by
+  WebMonterey, a webmaster service in Monterey, California. WebMonterey handles the hosting,
+  security, strategy and ongoing care of the site…" - _custom_ added, _maintenance_ dropped,
+  _updates_ is now _strategy_ - and the contact paragraph is bold. `copy.webmaster.intro` and
+  `copy.webmaster.body` now take the same inline subset as page prose (`**bold**`, `_italic_`,
+  `[text](/url)`), which is how the bold is expressed. A site overriding `copy.webmaster` in
+  `webmonterey.json` keeps its own words; one that does not gets these. The agency's
+  description in the page's JSON-LD drops _maintenance_ too.
+
+### Fixed
+
+- **"managed byWebMonterey".** The built-in `/webmaster` intro had no space before the agency
+  link - Astro drops the whitespace between an expression and an element on separate lines. It
+  reads "managed by WebMonterey" now.
+
+---
+
+## 1.3.0 — 2026-09-02
+
+### Changed
+
+- **A staging site is a preview build everywhere.** `environment: "staging"` in webmonterey.json
+  now makes every build a preview — every page noindex with no canonical, no sitemap, `robots.txt`
+  `Disallow: /`, no Google Tag Manager — on every hostname and in every build: a feature branch,
+  `main` on Workers Builds, a laptop. Until now only a non-production branch was a preview, so a
+  site that had not launched was crawlable on its `workers.dev` URL the moment `main` deployed.
+  The branch rule stays: a feature branch of a launched site is still a preview. An unset
+  `environment` is production, as everywhere else, so a site predating the field builds as before.
+  The decision is one pure function, `isPreviewBuild`; the build log says which signal made a
+  build a preview, and `virtual:webm/build` carries it as `reason`.
+
+  **A launched site whose webmonterey.json still says `"staging"` disappears from search after
+  this update:** every page goes noindex and the sitemap is gone. `/webm:launch` sets
+  `"environment": "production"` and `launched` together; `webm doctor` already fails a launched
+  site still declared staging, and its message now names this consequence. Flipping `environment`
+  is what makes a site indexable, so it must not happen before the custom domain is live —
+  `/webm:start` and `/webm:launch` both say so.
+
+- **`/webm:start` creates the Worker.** Step 5 is now one deploy from the laptop — `npm run build
+  && npx wrangler deploy`, guarded by `wrangler deployments list` so a re-run skips it — and step 6
+  connects the repo to the Worker that now exists (Settings → Builds), a smaller dashboard step
+  than importing a repository and typing the Worker name in by hand. The skill used to stop and
+  ask for the Worker to be made in the dashboard; on one site it was not, and the result was a
+  repo, a database and nothing serving. That laptop deploy is the only one a site ever gets: once
+  the repo is connected, a laptop deploy is a version no build produced, which the next push
+  reverts. The adapter's auto-provisioned `<slug>-session` KV namespace is expected and stays out
+  of wrangler.jsonc. The scaffolded README's deploy note says the same.
+
+### Added
+
+- **`webm doctor` checks that the Worker exists.** It asks wrangler for the deployments of the
+  Worker named in wrangler.jsonc and warns when there are none — the silent failure above. It skips
+  with a note when wrangler is not installed or not logged in, so CI and a fresh laptop are not
+  failed for being unable to ask.
+
+- **Hard rule 12 in a site's CLAUDE.md: a session in a client repo never edits the package.** Not
+  in `node_modules`, and not in the package's checkout when it sits on the same machine. The
+  deliverable for an upstream problem is a description of the fix — what, where, expected
+  behaviour, how to verify — as a prompt for a session opened in the package repo; the site takes
+  the fix with `npm update`. Enforced as far as Claude Code's rules reach: `.claude/settings.json`
+  denies `Edit(**/node_modules/**)`, and **`webm sync` now merges the package's deny rules into a
+  site's settings on every install** — adding what is missing, leaving the site's own rules alone,
+  and dropping the two `Write(...)` rules 1.2.0 scaffolded, which Claude Code never consults and
+  warns about at startup. The docs have no rule syntax for "any path outside this project", so
+  that half stays prose.
+
+  **On an existing site:** the settings arrive with the next install. `CLAUDE.md` is the site's
+  own file, so copy rule 12 in from
+  `node_modules/@cparkerwebm/webmonterey/template/site/CLAUDE.md`.
+
+---
+
 ## 1.2.0 — 2026-09-02
 
 ### Added

package/README.md

@@ -20,6 +20,22 @@ the reset, the Cloudflare includes, the consent system, the form pipeline, the r
 It ships **zero visible components**. Every block a visitor sees is built per client, in that
 client's repo. Every default has a documented way to opt out of it.
 
+A site hands the package its components through `src/components/registry.ts`: `blocks` for the
+block router, `header`, `footer` and `panels` for the chrome, `pageHeader` in place of the
+router's plain `<h1>`, `structuredData` for the site's JSON-LD, and `webmasterPage` for the body
+of the `/webmaster` page. That last one is the seam for a site whose document pages have a richer
+layout than a heading and a stack of paragraphs: the component receives the merged copy
+(`{ title, description, intro, body }`; `intro` and `body` are HTML, the agency link already in
+`intro`) and lays it out; the route, the words, the `<head>`, the share image and the agency graph
+stay the package's. It carries no copy of its own - the words are overridden through
+`copy.webmaster` in `webmonterey.json`, not in the component.
+
+**The package is edited in this repo, and only here.** A session in a client site that finds a
+package bug does not reach into `node_modules` or into this checkout; its deliverable is a
+description of the fix, run later in a session opened here, and the site takes the result with
+`npm update`. That is rule 12 of the site's `CLAUDE.md`, with an `Edit` deny on `node_modules`
+behind it that `webm sync` keeps in place. The inverse holds: nothing here edits a client site.
+
 ## Creating a client site
 
 ```sh

package/dist/webm.mjs

@@ -196,6 +196,53 @@ var init_mcp = __esm({
   }
 });
 
+// src/cli/settings.ts
+function projectSettings(repo) {
+  return {
+    "//": `Project settings for ${repo}.`,
+    "//mcp": "A server declared in .mcp.json is INERT until approved on each machine. Without this line the rules that say consult the Astro and MDN docs before using an API would depend on whoever cloned the repo happening to hit Approve.",
+    includeCoAuthoredBy: false,
+    enabledMcpjsonServers: [...MCP_NAMES],
+    "//permissions": PERMISSIONS_NOTE,
+    permissions: { deny: [...DENY_RULES] }
+  };
+}
+function withDenyRules(settings) {
+  const permissions = settings.permissions && typeof settings.permissions === "object" ? { ...settings.permissions } : {};
+  const current = Array.isArray(permissions.deny) ? permissions.deny.filter((r) => typeof r === "string") : [];
+  const removed = current.filter((r) => STALE_RULES.includes(r));
+  const kept = current.filter((r) => !STALE_RULES.includes(r));
+  const added = DENY_RULES.filter((r) => !kept.includes(r));
+  if (!added.length && !removed.length) return { settings, added, removed };
+  permissions.deny = [...kept, ...added];
+  return {
+    settings: { ...settings, "//permissions": PERMISSIONS_NOTE, permissions },
+    added,
+    removed
+  };
+}
+var DENY_RULES, STALE_RULES, PERMISSIONS_NOTE;
+var init_settings = __esm({
+  "src/cli/settings.ts"() {
+    "use strict";
+    init_mcp();
+    DENY_RULES = [
+      "Read(**/.dev.vars)",
+      "Read(**/.dev.vars.*)",
+      "Read(**/.env)",
+      "Read(**/.env.*)",
+      "Read(**/*.pem)",
+      "Read(**/*.key)",
+      "Read(**/.npmrc)",
+      "Edit(**/.dev.vars)",
+      "Edit(**/.env)",
+      "Edit(**/node_modules/**)"
+    ];
+    STALE_RULES = ["Write(**/.dev.vars)", "Write(**/.env)"];
+    PERMISSIONS_NOTE = "The deny list is package-managed: `webm sync` adds any rule that is missing on every install and leaves everything else in this file alone. Edit(**/node_modules/**) is rule 12 of CLAUDE.md made mechanical - a session in this repo never edits the package.";
+  }
+});
+
 // src/cli/scaffold.ts
 function shiftDays(date, days) {
   const shifted = /* @__PURE__ */ new Date(`${date}T00:00:00Z`);
@@ -279,7 +326,7 @@ export default defineConfig({
       worker: n.worker,
       slug: n.slug,
       launched: null,
-      "//environment": "What this deployment is FOR. 'staging' redirects EVERY email the site sends to stagingEmail below, so testing a form on a preview cannot reach the client's real contacts. A new site starts here; /webm:launch flips it to 'production'. Anything served from workers.dev is treated as staging regardless, so a branch preview of a live site is covered too.",
+      "//environment": "What this deployment is FOR. 'staging' makes every build a PREVIEW - every page noindex with no canonical, no sitemap, robots.txt disallowing everything, no Google Tag Manager - on every hostname, main included, so a site that has not launched cannot be indexed before it exists; and it redirects EVERY email the site sends to stagingEmail below, so testing a form on a preview cannot reach the client's real contacts. A new site starts here; /webm:launch flips it to 'production' once the custom domain is live, and that flip is what makes the site indexable. A branch other than main is a preview regardless, and anything served from workers.dev redirects its mail regardless, so a branch preview of a live site is covered too.",
       environment: "staging",
       "//stagingEmail": "Where staging email goes instead of its real recipients. REQUIRED while environment is staging - a staging site with nowhere to send refuses to send rather than guessing. webm doctor checks.",
       stagingEmail: options.stagingEmail ?? "",
@@ -372,31 +419,7 @@ export default defineConfig({
     null,
     2
   ) + "\n";
-  files[".claude/settings.json"] = JSON.stringify(
-    {
-      "//": `Project settings for ${n.repo}.`,
-      "//mcp": "A server declared in .mcp.json is INERT until approved on each machine. Without this line the rules that say consult the Astro and MDN docs before using an API would depend on whoever cloned the repo happening to hit Approve.",
-      includeCoAuthoredBy: false,
-      enabledMcpjsonServers: MCP_NAMES,
-      permissions: {
-        deny: [
-          "Read(**/.dev.vars)",
-          "Read(**/.dev.vars.*)",
-          "Read(**/.env)",
-          "Read(**/.env.*)",
-          "Read(**/*.pem)",
-          "Read(**/*.key)",
-          "Read(**/.npmrc)",
-          "Edit(**/.dev.vars)",
-          "Edit(**/.env)",
-          "Write(**/.dev.vars)",
-          "Write(**/.env)"
-        ]
-      }
-    },
-    null,
-    2
-  ) + "\n";
+  files[".claude/settings.json"] = JSON.stringify(projectSettings(n.repo), null, 2) + "\n";
   files[".mcp.json"] = JSON.stringify(mcpConfig(), null, 2) + "\n";
   files["src/actions/index.ts"] = `/*
  * Form handlers.
@@ -550,8 +573,11 @@ suffix - \`${n.slug}-portal\`.
 
 ## Deploying
 
-Push to deploy. A \`wrangler deploy\` from a laptop creates a version no build produced, so
-history stops describing what is live and the next push reverts it.
+The Worker is created ONCE from a laptop - \`npm run build && npx wrangler deploy\` - and the
+repo is then connected to it in the dashboard (Worker \u2192 Settings \u2192 Builds). /webm:start does
+both. From then on, push to deploy: a \`wrangler deploy\` from a laptop after that creates a
+version no build produced, so history stops describing what is live and the next push
+reverts it.
 `;
   return files;
 }
@@ -560,6 +586,7 @@ var init_scaffold = __esm({
     "use strict";
     init_slug();
     init_mcp();
+    init_settings();
   }
 });
 
@@ -578,7 +605,7 @@ import {
   writeFileSync,
   readdirSync
 } from "node:fs";
-import { basename, join as join2 } from "node:path";
+import { basename, dirname as dirname2, join as join2 } from "node:path";
 function syncDir(source, target) {
   if (!existsSync2(source)) return [];
   mkdirSync(target, { recursive: true });
@@ -604,6 +631,30 @@ function addMissing(source, target) {
   }
   return added.sort();
 }
+function ensureSettings(siteRoot) {
+  const path = join2(siteRoot, ".claude", "settings.json");
+  if (!existsSync2(path)) {
+    mkdirSync(dirname2(path), { recursive: true });
+    writeFileSync(path, JSON.stringify(projectSettings(basename(siteRoot)), null, 2) + "\n");
+    return { added: [...DENY_RULES], removed: [], created: true, skipped: null };
+  }
+  let parsed;
+  try {
+    parsed = JSON.parse(readFileSync2(path, "utf8"));
+  } catch {
+    return {
+      added: [],
+      removed: [],
+      created: false,
+      skipped: ".claude/settings.json is not valid JSON, so it was left alone"
+    };
+  }
+  const { settings, added, removed } = withDenyRules(parsed);
+  if (added.length || removed.length) {
+    writeFileSync(path, JSON.stringify(settings, null, 2) + "\n");
+  }
+  return { added, removed, created: false, skipped: null };
+}
 function listSkills(dir) {
   if (!existsSync2(dir)) return [];
   return readdirSync(dir, { withFileTypes: true }).filter((e) => e.isDirectory() && existsSync2(join2(dir, e.name, "SKILL.md"))).map((e) => e.name).sort();
@@ -660,7 +711,8 @@ function sync(siteRoot) {
      * which is how code depending on an unpublished package reached main without a word.
      */
     workflows: syncDir(join2(template, "workflows"), join2(siteRoot, ".github/workflows")),
-    migrations: addMissing(join2(template, "migrations"), join2(siteRoot, "migrations"))
+    migrations: addMissing(join2(template, "migrations"), join2(siteRoot, "migrations")),
+    settings: ensureSettings(siteRoot)
   };
 }
 function ensureGitignored(siteRoot) {
@@ -691,6 +743,19 @@ function run(argv2) {
   for (const m of result.migrations) {
     console.log(`  + migrations/${m}  (apply it: npx wrangler d1 migrations apply <DB> --remote)`);
   }
+  if (result.settings.created) {
+    console.log(`  + .claude/settings.json`);
+  } else if (result.settings.skipped) {
+    console.log(`  ${result.settings.skipped}`);
+  } else if (result.settings.added.length || result.settings.removed.length) {
+    const parts = [
+      result.settings.added.length && `+${result.settings.added.length} deny`,
+      result.settings.removed.length && `-${result.settings.removed.length} stale`
+    ].filter(Boolean);
+    console.log(
+      `  .claude/settings.json: ${parts.join(", ")} (package-managed rules; yours are kept)`
+    );
+  }
   if (ensureGitignored(siteRoot)) {
     console.log(`  gitignored .claude/skills/${NAMESPACE}/`);
   }
@@ -707,13 +772,14 @@ var init_sync = __esm({
   "src/cli/sync.ts"() {
     "use strict";
     init_package_root();
+    init_settings();
     NAMESPACE = "webm";
   }
 });
 
 // src/cli/seed.ts
 import { cpSync as cpSync2, existsSync as existsSync3, mkdirSync as mkdirSync2, readdirSync as readdirSync2, writeFileSync as writeFileSync2 } from "node:fs";
-import { dirname as dirname2, join as join3, relative } from "node:path";
+import { dirname as dirname3, join as join3, relative } from "node:path";
 function walk(dir) {
   if (!existsSync3(dir)) return [];
   return readdirSync2(dir, { withFileTypes: true }).flatMap((e) => {
@@ -732,7 +798,7 @@ function seed(packageRoot, siteRoot) {
       const rel = relative(source, file);
       const dest = join3(siteRoot, to === "." ? rel : join3(to, rel));
       if (existsSync3(dest)) continue;
-      mkdirSync2(dirname2(dest), { recursive: true });
+      mkdirSync2(dirname3(dest), { recursive: true });
       cpSync2(file, dest);
       written.push(relative(siteRoot, dest));
     }
@@ -800,7 +866,7 @@ __export(new_exports, {
 });
 import { execFileSync } from "node:child_process";
 import { existsSync as existsSync4, mkdirSync as mkdirSync3, readdirSync as readdirSync3, writeFileSync as writeFileSync3 } from "node:fs";
-import { dirname as dirname3, join as join4, resolve } from "node:path";
+import { dirname as dirname4, join as join4, resolve } from "node:path";
 function parseArgs(argv2) {
   const positional = argv2.filter((a) => !a.startsWith("--"));
   const flag = (name) => {
@@ -863,7 +929,7 @@ function run2(argv2) {
   });
   for (const [path, contents] of Object.entries(files)) {
     const full = join4(root, path);
-    mkdirSync3(dirname3(full), { recursive: true });
+    mkdirSync3(dirname4(full), { recursive: true });
     writeFileSync3(full, contents);
   }
   const seeded = seed(PACKAGE_ROOT, root);
@@ -1982,7 +2048,7 @@ var init_checks = __esm({
       {
         id: "environment",
         title: "The declared environment matches where the site actually is",
-        silentAs: "a launched site whose client email is still being diverted to the agency's inbox",
+        silentAs: "a launched site whose client email is still being diverted to the agency's inbox, and whose every page is noindex",
         run(ctx) {
           const declared = ctx.site.environment;
           if (declared !== void 0 && declared !== "production" && declared !== "staging") {
@@ -1992,12 +2058,37 @@ var init_checks = __esm({
           }
           if (declared === "staging" && isConfigured(ctx.site.launched)) {
             return fail(
-              `this site launched on ${ctx.site.launched} but is still declared staging, so every email it sends is being redirected away from its real recipients. Set "environment": "production" in webmonterey.json.`
+              `this site launched on ${ctx.site.launched} but is still declared staging, so every email it sends is being redirected away from its real recipients - and since 1.3.0 every build of a staging site is a preview: noindex on every page, no canonical, no sitemap, robots.txt disallowing everything. The live site is dropping out of search. Set "environment": "production" in webmonterey.json.`
             );
           }
           if (declared !== "staging" && !isConfigured(ctx.site.launched)) {
             return warn(
-              `this site has no launch date but is treated as production, so testing a form will email the client's real contacts. Set "environment": "staging" in webmonterey.json until /webm:launch.`
+              `this site has no launch date but is treated as production, so testing a form will email the client's real contacts and every page is indexable on its workers.dev hostname. Set "environment": "staging" in webmonterey.json until /webm:launch.`
+            );
+          }
+          return pass;
+        }
+      },
+      {
+        /*
+         * THE WORKER EXISTS. /webm:start used to end with a repo, a D1 database and an instruction
+         * to create the Worker in the dashboard by hand - and on one site nobody did. Nothing local
+         * notices: the build is green, every other check here is green, and the site is a
+         * workers.dev hostname that answers nothing. The Worker is the one resource whose absence
+         * has no symptom on disk, so this asks Cloudflare through wrangler - the one thing a laptop
+         * can ask - and steps aside with a note when it cannot.
+         */
+        id: "worker-exists",
+        title: "The Worker exists",
+        silentAs: "a site with a repo, a database and nothing serving",
+        run(ctx) {
+          if (ctx.worker.skipped) return { status: "pass", detail: `skipped: ${ctx.worker.skipped}` };
+          if (!ctx.worker.name) {
+            return warn("wrangler.jsonc names no Worker, so there is nothing to look for");
+          }
+          if (!ctx.worker.deployments) {
+            return warn(
+              `no deployment of a Worker named "${ctx.worker.name}" on this account. Create it once from the laptop - npm run build && npx wrangler deploy - then connect the repo to it in the dashboard (Worker \u2192 Settings \u2192 Builds). /webm:start, steps 5 and 6.`
             );
           }
           return pass;
@@ -2079,8 +2170,10 @@ __export(doctor_exports, {
   buildContext: () => buildContext,
   run: () => run5
 });
+import { execFileSync as execFileSync2 } from "node:child_process";
 import { existsSync as existsSync8, readFileSync as readFileSync7, readdirSync as readdirSync6 } from "node:fs";
-import { join as join7, relative as relative3 } from "node:path";
+import { createRequire } from "node:module";
+import { dirname as dirname5, join as join7, relative as relative3, resolve as resolve2 } from "node:path";
 function parseJsonc(source) {
   const stripped = source.replace(/\\"|"(?:\\"|[^"])*"|(\/\/.*|\/\*[\s\S]*?\*\/)/g, (m, comment) => comment ? "" : m).replace(/,(\s*[}\]])/g, "$1");
   return JSON.parse(stripped);
@@ -2140,13 +2233,63 @@ function readMcp(siteRoot) {
     enabled: read(".claude/settings.json", (p) => p.enabledMcpjsonServers ?? null)
   };
 }
+function workerState(siteRoot, name) {
+  const worker = { name: name ?? null, deployments: null, skipped: null };
+  if (!worker.name) return worker;
+  let bin;
+  try {
+    const require2 = createRequire(join7(resolve2(siteRoot), "package.json"));
+    bin = join7(dirname5(require2.resolve("wrangler/package.json")), "bin/wrangler.js");
+  } catch {
+    return {
+      ...worker,
+      skipped: "wrangler is not installed here, so the Worker was not looked for"
+    };
+  }
+  try {
+    const out = execFileSync2(
+      process.execPath,
+      [bin, "deployments", "list", "--name", worker.name, "--json"],
+      {
+        cwd: siteRoot,
+        encoding: "utf8",
+        stdio: ["ignore", "pipe", "pipe"],
+        timeout: 3e4,
+        env: { ...process.env, WRANGLER_SEND_METRICS: "false", NO_COLOR: "1" }
+      }
+    );
+    const start = out.indexOf("[");
+    const parsed = start >= 0 ? JSON.parse(out.slice(start)) : [];
+    return { ...worker, deployments: Array.isArray(parsed) ? parsed.length : 0 };
+  } catch (error) {
+    const e = error;
+    const text = `${e.stdout ?? ""}
+${e.stderr ?? ""}
+${e.message ?? ""}`;
+    if (/code: 10007\]|does not exist on your account/i.test(text)) {
+      return { ...worker, deployments: 0 };
+    }
+    if (/CLOUDFLARE_API_TOKEN|not (logged in|authenticated)|Authentication error|code: (10000|6111|9109)\]/i.test(
+      text
+    )) {
+      return {
+        ...worker,
+        skipped: "wrangler is not logged in (npx wrangler login), so whether the Worker exists was not checked"
+      };
+    }
+    const line = text.split("\n").map((l) => l.replace(/\x1b\[[0-9;]*m/g, "").trim()).find((l) => l && !l.startsWith("\u{1FAB5}"));
+    return { ...worker, skipped: `wrangler could not answer: ${line ?? "no output"}` };
+  }
+}
 function buildContext(siteRoot) {
   const { site } = loadSiteFiles(siteRoot);
   const wranglerPath = ["wrangler.jsonc", "wrangler.json"].map((f) => join7(siteRoot, f)).find(existsSync8);
   const syncPath = join7(siteRoot, ".claude/skills/webm/.webm-sync.json");
+  const wrangler = wranglerPath ? parseJsonc(readFileSync7(wranglerPath, "utf8")) : null;
   return {
     site,
-    wrangler: wranglerPath ? parseJsonc(readFileSync7(wranglerPath, "utf8")) : null,
+    wrangler,
+    worker: workerState(siteRoot, wrangler?.name),
     pages: readTree(siteRoot, "src/pages", [".astro", ".ts"]),
     components: readTree(siteRoot, "src/components", [".astro", ".ts"]),
     today: (/* @__PURE__ */ new Date()).toISOString().slice(0, 10),
@@ -2227,7 +2370,7 @@ __export(audit_exports, {
   run: () => run6
 });
 import { existsSync as existsSync9, readdirSync as readdirSync7, readFileSync as readFileSync8, statSync as statSync3 } from "node:fs";
-import { join as join8, relative as relative4, resolve as resolve2 } from "node:path";
+import { join as join8, relative as relative4, resolve as resolve3 } from "node:path";
 function attr(tag, name) {
   const m = new RegExp(`\\s${name}\\s*=\\s*(?:"([^"]*)"|'([^']*)'|([^\\s>]+))`, "i").exec(tag);
   if (!m) return null;
@@ -2376,7 +2519,7 @@ async function probe(urls) {
   return bad.sort((a, b) => a.url.localeCompare(b.url));
 }
 async function run6(argv2) {
-  const dist = resolve2(argv2.find((a) => !a.startsWith("-")) ?? "dist/client");
+  const dist = resolve3(argv2.find((a) => !a.startsWith("-")) ?? "dist/client");
   const noExternal = argv2.includes("--no-external");
   if (!existsSync9(join8(dist, "index.html"))) {
     console.error(`webm audit: no build at ${dist}. Run \`npm run build\` first.`);
@@ -2473,11 +2616,11 @@ var upgrade_exports = {};
 __export(upgrade_exports, {
   run: () => run7
 });
-import { execFileSync as execFileSync2 } from "node:child_process";
+import { execFileSync as execFileSync3 } from "node:child_process";
 import { existsSync as existsSync10, readFileSync as readFileSync9 } from "node:fs";
 import { join as join9 } from "node:path";
 function git(siteRoot, args) {
-  return execFileSync2("git", args, { cwd: siteRoot, encoding: "utf8" }).trim();
+  return execFileSync3("git", args, { cwd: siteRoot, encoding: "utf8" }).trim();
 }
 function installedVersion(siteRoot) {
   const path = join9(siteRoot, "node_modules", PACKAGE, "package.json");
@@ -2507,7 +2650,7 @@ function run7(argv2) {
     git(siteRoot, ["checkout", "-b", branch]);
     console.log(`Branched to ${branch}. Never upgrade on main.`);
   }
-  execFileSync2("npm", ["install", `${PACKAGE}@${target}`], { cwd: siteRoot, stdio: "inherit" });
+  execFileSync3("npm", ["install", `${PACKAGE}@${target}`], { cwd: siteRoot, stdio: "inherit" });
   const to = installedVersion(siteRoot);
   if (!to) {
     console.error("webm upgrade: install did not produce a version. Check the npm output above.");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cparkerwebm/webmonterey",
-  "version": "1.2.0",
+  "version": "1.4.0",
   "type": "module",
   "description": "The WebMonterey Astro framework: plumbing, design system, and Claude Code skills for client sites on Cloudflare Workers",
   "license": "MIT",

package/skills/launch/SKILL.md

@@ -99,6 +99,11 @@ to say, and this is where it gets decided - once, with the client's real details
 4. **Validate** the built home page and one inner page with Google's Rich Results Test before
    moving on.
 
+5. **Look at `/webmaster`.** The package injects it on every site, with its own share image and
+   JSON-LD. If this site's document pages - privacy, terms - use a richer layout than an `<h1>`
+   and a stack of paragraphs, run `/webm:webmaster`: it exports a layout component from the
+   registry so the page looks like the site it is on, with the package's copy intact.
+
 ## 3. Turnstile
 
 If the site has a form: create the widget in the Cloudflare dashboard (**Turnstile → Add
@@ -211,13 +216,21 @@ In one change:
 "launched": "YYYY-MM-DD"
 ```
 
+**This flip is also what makes the site indexable, so it happens here and not before.** While
+`environment` says `staging`, every build is a preview - every page noindex with no canonical,
+no sitemap, robots.txt disallowing everything, no Google Tag Manager - on every hostname, `main`
+included. Flip it before the custom domain is live and the `workers.dev` copy is what gets
+indexed.
+
 Until `environment` flips, every message the site sends is redirected to `stagingEmail` - correct
 right up to the moment the domain is attached and wrong immediately after: the form keeps saying
 thank you, the client's inbox stays empty, and the first anyone hears of it is a customer asking
-why nobody called back. `webm doctor` fails a launched site still declared staging, which is why
-both fields change together.
+why nobody called back. And a launched site left on `staging` is invisible to search: every page
+noindex, no sitemap, `Disallow: /`. `webm doctor` fails a launched site still declared staging,
+which is why both fields change together.
 
-Anything served from `workers.dev` is still treated as staging whatever this says, so branch
-previews of the live site keep redirecting. That is deliberate.
+Anything served from `workers.dev` is still treated as staging for MAIL whatever this says, and
+any branch other than `main` still builds as a preview, so branch previews of the live site keep
+redirecting and stay out of the index. That is deliberate.
 
 Commit, push, and confirm the deploy. Then run `npx webm doctor` one last time: zero failures.

package/skills/new-component/SKILL.md

@@ -83,3 +83,9 @@ npm run preview   # NOT dev - preview is a real build on real workerd
 
 `dev` cannot detect CSS bundling, cascade order, or the asset router. Every trap worth catching is
 invisible in `dev` and visible in `preview`. See `/webm:traps`.
+
+## If this is the site's document block
+
+A long-form block - the one the privacy and terms pages use - is also the layout the package's
+`/webmaster` page should have. The moment that block exists, run `/webm:webmaster`: it exports a
+layout component built on this block, so `/webmaster` stops looking like a different site.