@piercebarney/whs-eleventy 2026.11.113 → 2026.11.115

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@piercebarney/whs-eleventy",
-  "version": "2026.11.113",
+  "version": "2026.11.115",
   "description": "The web house style's Eleventy + Netlify tooling — the compliance sweep, the infra doctor, the link/CSP integrity check, and the a11y scan, shared by every project on the stack.",
   "bin": {
     "whs": "cli.js"
@@ -32,7 +32,7 @@
     "node": ">=22"
   },
   "dependencies": {
-    "@piercebarney/whs-core": ">=2026.11.113",
+    "@piercebarney/whs-core": ">=2026.11.115",
     "node-html-parser": "^9.0.2"
   },
   "devDependencies": {

package/standard/CHANGELOG.md

@@ -21,8 +21,92 @@ Everything else — wording fixes, doc corrections that don't change what's
 enforced, new *opt-in* chapters/capabilities, tooling-only changes — is
 **non-breaking**. `bin/check` fails if a heading is missing the tag.
 
+Every breaking change ships with its `/whs:upgrade` migration (`CHARTER.md` P15).
+
 ---
 
+## 2026-11-01-15 [non-breaking]
+
+web-house-style adopts its own charter (`CHARTER.md`) and aligns its docs with
+it: scope tiers, what one-time setup stays with the account holder, a push rule
+for Claude Code sessions, and a lifecycle coverage table.
+
+Non-breaking: wording, a new doc, and opt-in capability; nothing a compliant
+project does today becomes non-compliant.
+
+**What an adopting project does:** nothing required; `/whs:upgrade` picks up the
+new wording. Optionally set `status: parked` in `.claude/project/index.md` to
+have `bin/fleet` skip the project.
+
+`templates/verify.sh` is still red only on the known bandit advisory
+(phoenix-bandit-advisory), unrelated to this release.
+
+**Closes:** whs-charter-v1
+
+### CHARTER.md
+New: the standard's own charter (idea, audience, success criteria S1–S8, principles P1–P18, out of scope X1–X10).
+
+### core: beyond-this-standard
+Scope tiers; apps of any size sit inside the standard (Idea / S7). Drift-guarded — all three stacks rechecked.
+
+### core: adopting
+One-time setup: only buying, signing up, and minting credentials stay with the account holder; the rest is tooling, tracked as `verifiedOn` until a tool exists (X9 / P16). P15 pointer added.
+
+### core: out-of-scope
+Server logic at the static tier is a tier change, not an extension of the static tier.
+
+### stacks/eleventy-netlify.md
+Mirrored wording for the `beyond-this-standard`, `adopting`, and `out-of-scope` changes.
+
+### stacks/sveltekit-netlify.md
+Mirrored wording for the `beyond-this-standard`, `adopting`, and `out-of-scope` changes.
+
+### stacks/phoenix.md
+Mirrored wording for the `beyond-this-standard`, `adopting`, and `out-of-scope` changes.
+
+### PROCESS.md
+The push line points to `CLAUDE-PROJECT.md`; optional `status: parked` documented; P14 pointer.
+
+### CLAUDE-PROJECT.md
+Auto-push rule: a Mac Claude Code session may push a group of commits only where a push can't deploy, never force-pushes, and runs a pre-push sensitive check first. That check isn't built yet, so pushing stays with the owner for now. The VM never pushes (P4 / X3).
+
+### README.md
+Doc-map row for `CHARTER.md`; lifecycle coverage table (S8); P17 pruning pass with its sweep rule; P13 pointer.
+
+### PROJECT-OVERVIEW.md
+Aligned with the charter (X2).
+
+### bin/fleet
+Parked rows are shown, skipped, and counted.
+
+### BACKLOG.md
+Fleet-upgrade-runner design rewritten; new entries: pre-push-sensitive-check, content-check-vm-mode, shared-record-scripts, ops-automation.
+
+## 2026-11-01-14 [non-breaking]
+
+`whs doctor`'s repo tier gains a `native-platform` blocker row: an installed
+package whose `package.json` `os`/`cpu` excludes this machine means
+`node_modules` came from another platform (e.g. the desktop app's Linux shell
+over a Mac install). The row names the packages and points at
+`CLAUDE-PROJECT.md` "Shell environment". It also surfaces in deploy preflight
+and eleventy's audit page via `runRepoChecks`.
+
+Non-breaking: tooling only; a normal install on its own machine passes.
+
+Still unverified: whether `content-check` fails the same way in the desktop
+app's Linux shell.
+
+**What an adopting project does:** `npm update` the whs packages.
+
+**Closes:** doctor-platform-mismatch
+
+### packages/whs-core
+
+`runRepoChecks` gains the `native-platform` blocker check (last in the repo
+tier) and exports a new `foreignNativePackages(root, { platform, arch })`
+helper. The check reads only top-level and `@scope` `package.json` files and
+follows npm's `os`/`cpu` allow/negation semantics.
+
 ## 2026-11-01-13 [non-breaking]
 
 The charter template's Audience section gains an Ownership line: the owner's

package/standard/core.md

@@ -1,6 +1,6 @@
 # Web project house style — CORE (stack-agnostic)
 
-**Version:** 2026-11-01-13 · **Status:** active
+**Version:** 2026-11-01-15 · **Status:** active
 
 This is the stack-agnostic contract every web project follows, regardless of
 framework, host, or CSS system. It says **what** must be true, with concrete
@@ -1397,10 +1397,14 @@ the audit page reflects it after a rebuild.
 
 **Implementation.** See your stack's impl doc, same slug.
 
-## beyond-this-standard — Beyond this standard
+## beyond-this-standard — Scope tiers: beyond the static envelope
 
-**Contract.** This standard covers content sites, tool sites, and their forms.
-When a project needs more, that is a deliberate threshold crossing, not a drift.
+**Contract.** This standard covers websites and web apps of any size
+(`CHARTER.md` Idea, S7), in tiers. `static+forms` is the default: content
+sites, tool sites, and their forms, inside the static envelope. The app tier
+(`+db` / `+auth` / `+ssr`) is also inside the standard, bound by
+`stacks/phoenix.md`. Crossing from the static tier to the app tier is a
+deliberate, recorded step (the `scope:` key), not a drift.
 
 **Specs.**
 - **Signals you are past the static envelope:** a database; user accounts /
@@ -1550,9 +1554,14 @@ scaffold it reports the partial result honestly and points at that stack's
 own `TEMPLATE.md`.
 
 **One-time setup.** Adopting, converting, or upgrading against the standard
-often leaves a project owing **one-time human setup** no script can finish for
-it — hosting/repo config, DNS, minting a secret (`#secrets`). That debt is
-tracked the same way `#compliance` already tracks a `MANUAL` row: a committed
+often leaves a project owing **one-time human setup**. Only buying, signing up
+and granting access stay with the account holder (the owner, or the client for
+a client's site): registering domains, paying, creating hosting or service
+accounts, minting credentials (`#secrets`). Everything after an account
+exists — site/hosting setup, build settings, DNS records, headers, wiring
+secrets in, monitoring — is done by a tool (`CHARTER.md` P16, X9). Where no
+tool exists yet, the step is tracked the same way `#compliance` already tracks
+a `MANUAL` row until tooling replaces it: a committed
 item carrying a dated `verifiedOn` confirmation, not a message printed once
 to a terminal and forgotten. A session-start check flags any item still
 unconfirmed so it can't go silently stale — **not a gate**; per
@@ -1609,7 +1618,7 @@ governs it and follow that chapter — the slugs are the index (a `<script>` →
 - content-type: tool           # tool | article  (article => feeds)
 - add-ons: none                # or: comma list of modules/ packs no field above implies (calculator, glossary, pages) — see modules/README.md
 - publishing-rate: ~5 pages/week
-- standard-version: 2026-11-01-13  # recommended — enables standard-version drift tracking (#compliance)
+- standard-version: 2026-11-01-15  # recommended — enables standard-version drift tracking (#compliance)
 
 <!-- optional, present only while a filed need is unresolved -->
 ### Waiting on the standard
@@ -1659,7 +1668,9 @@ wire in, runs an initial compliance pass. It **produces** the initial
 migration backlog; it does not work it — working the backlog stays
 incremental, by hand or later via `/whs:upgrade` once the project is
 version-pinned and catching up to a newer standard release. `/whs:adopt` and
-`/whs:upgrade` are deliberately different commands with different scopes.
+`/whs:upgrade` are deliberately different commands with different scopes. A
+release that would break a pinned project ships with the `/whs:upgrade` step
+that fixes it (`CHARTER.md` P15).
 
 **Feedback to the standard.** Adopting the house style is what surfaces its
 bugs — a check that misfires, a `core.md` ↔ impl-doc contradiction, a Contract
@@ -1876,9 +1887,9 @@ project actually needs it.
   recorded in `CLAUDE.md`, not specified here.
 - **A design-token pipeline** (Style Dictionary et al.) — `#brand-source` as one
   file is the small-project version; graduate only when tokens outgrow it.
-- **Server-side application logic as a way to run the app** — that is
-  `#beyond-this-standard`; a thin key-hiding proxy is the one carve-out
-  (`#third-parties`).
+- **Server-side application logic in a project recorded at the static tier** —
+  that is a tier change (`#beyond-this-standard`), not an addition; a thin
+  key-hiding proxy is the one static-tier carve-out (`#third-parties`).
 - **ML infrastructure** — model fine-tuning or training pipelines, a
   vector-store / RAG retrieval layer, an evals harness, a prompt-versioning
   system. `#llm-integration` covers *calling* a model API; building the