@cparkerwebm/webmonterey 1.1.0 → 1.3.0

package/CHANGELOG.md

@@ -11,6 +11,110 @@ build. See `/webm:upgrade`.
 
 ---
 
+## 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
+
+- **Every site has a `/webmaster` page.** Injected by the integration, rendered with the site's
+  own chrome, indexable and in the sitemap. It says who designed, built and manages the site and
+  who to contact when something is wrong, carries its own share image (served from the package at
+  `/webmaster/og.png`, so a redesign reaches every site on `npm update`) and its own structured
+  data — a `WebPage` about the agency's `Organization`, using the same `@id` the agency's own site
+  declares. Every word is overridable through `copy.webmaster`. Off switch: `webmaster: false` on
+  the integration.
+
+- **`webm audit`** — the pre-launch checks only a build can answer: images with no `alt`
+  attribute (an explicit `alt=""` is fine), internal links that land on no page or Worker route,
+  and a sitemap that is missing, unadvertised, or lists a page that was not built. External links
+  are probed and reported as warnings. `/webm:launch` runs it and says how to act on each finding.
+
+- **Branch previews are a different build.** On any Workers Builds branch other than the
+  production one (`main`, or `productionBranch` on the integration), every page is noindex with
+  no canonical, there is no sitemap, `robots.txt` disallows everything, Google Tag Manager does
+  not load, and `/webmaster` emits no graph. Detected from the `WORKERS_CI_BRANCH` variable
+  Workers Builds injects; a local build is production. Mail on previews was already redirected by
+  the `workers.dev` hostname. Nothing to do on a site.
+
+- **`/webm:launch` asks two questions out loud** before the flip: is Google Tag Manager
+  configured and published for this site, and has the launch annotation been added in Google
+  Analytics. Neither is knowable from the repo, so the skill waits for the answer.
+
+### Changed
+
+- **The default share image is `public/opengraph.png`** (was `open-graph.png`). `webm new` seeds
+  the WebMonterey artwork there - the same image the `/webmaster` page uses - and a client replaces
+  it with their own; `webm doctor` flags the seed until they do. **On an existing site:** rename
+  `public/open-graph.png` to `public/opengraph.png`, or every page's `og:image` points at a file
+  that is not there.
+
+- **The footer credit is an internal link.** `Powered by WebMonterey` now goes to the site's own
+  `/webmaster` page instead of leaving the site; that page carries the one outbound link, with
+  the UTM parameters (`utm_campaign=webmaster`). The email footer keeps the outbound link — an
+  email cannot usefully point at a page on the site it is about.
+
+  **On an existing site:** the import moves —
+  `@cparkerwebm/webmonterey/webmonterey/credits/Credit.astro` is now
+  `@cparkerwebm/webmonterey/webmonterey/webmaster/Webmaster.astro`, and the module
+  `webmonterey/credits` is `webmonterey/webmaster`. The doctor check is `webmaster-credit`. The
+  site's `structuredData` component is not rendered on `/webmaster`; the page emits its own.
+
+---
+
 ## 1.1.0 — 2026-09-02
 
 ### Changed

package/README.md

@@ -20,6 +20,12 @@ 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.
 
+**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