@piercebarney/whs-eleventy 2026.9.1

package/standard/CHANGELOG.md

@@ -0,0 +1,625 @@
+# Changelog
+
+Slug-keyed. A change to a shared concept (a `core.md` chapter) lists the slug so
+"when did the deploy philosophy last change, and which docs moved" is answerable
+at a glance. Stack-only changes list the file.
+
+Format: `## <date>` → `### core: <slug>` / `### <stack>` entries.
+
+---
+
+## 2026-09-01 — the shared tooling package (#compliance mechanism, eleventy)
+
+### stacks/eleventy-netlify.md
+
+- **`@piercebarney/whs-eleventy` — the `whs` CLI.** The generic eleventy checks
+  (compliance sweep, doctor, link/CSP, a11y, content-check) move out of every
+  project's `scripts/` into one shared package (`packages/whs-eleventy/`).
+  Projects add it as a `devDependency` and run `whs compliance` / `whs links` /
+  … ; a fix lands once and `npm update` carries it. Only the asset *generators*
+  (`scripts/og*.js`, `scripts/icons.js`, `og-card.js`) stay per-project. The
+  `#the-gate` `package.json` snippet, `#compliance`, `#a11y` (now axe-core via
+  headless Chrome, not `pa11y`), `#audit-page`, the file tree, and the
+  new-project + migration checklists are updated to match.
+- The drift check no longer needs the `~/.claude/standards` path: the package
+  bundles a `core.md` + `CHANGELOG.md` snapshot (overridable with
+  `WHS_STANDARD`), and reports a visible `MANUAL` row — never a silent pass —
+  when the standard can't be resolved. Its CHANGELOG slug parser now reads every
+  slug on a multi-slug `### core: …` line.
+
+### tooling
+
+- **`bin/set-version <YYYY-MM-DD>`** bumps every version string the standard
+  carries — `**Version:**` (`core.md` + 3 stack docs), `index.json` `version`,
+  the `#adopting` block pin, each `templates/*/CLAUDE.md` `standard-version`, and
+  `packages/*/package.json` `version` (the date dotted, `2026-09-01` →
+  `2026.9.1`) — in one shot. `bin/check`'s fifth check fails if they disagree.
+- **`.github/workflows/publish.yml`** publishes `@piercebarney/whs-eleventy` to
+  npm when a `YYYY-MM-DD` version tag is pushed — it lints + tests the package,
+  checks the tag date (dotted) matches `package.json`, and publishes unless that
+  version is already up. Needs the `@piercebarney` npm scope and an `NPM_TOKEN`
+  repo secret. `--provenance` is omitted (needs a public source repo).
+- `standard.yml` gains a `package` job (prettier + eslint + `node:test`); the
+  `templates` job installs the file: package's own tree and points
+  `WHS_STANDARD` at the checkout so drift is checked against the live standard.
+
+---
+
+## 2026-08-31 — the Cowork ↔ Claude Code loop: concept brief + content ops (#content-model)
+
+### core: adopting
+
+- Stack-selection **Q1** no longer offers SvelteKit as a selectable framework.
+  It is one of: Eleventy + Netlify *(default)* · Elixir/Phoenix *(database /
+  server-side state in scope)* · other. `stacks/sveltekit.md` is now a
+  **parked** stub — friction points and open questions written, per-section
+  "how" not — and the flow says to treat SvelteKit as "other" until a real
+  project forces those decisions. `README.md` doc map + flow and `index.json`
+  (`status: parked`, reworded warning) follow; the sveltekit STATUS banner
+  says PARKED. No `**Version:**` change (same day).
+
+### core: content-model
+
+- The "non-developer editing" spec gains an **agent-editing** clause: where an
+  LLM agent edits the content data files directly, it follows a documented
+  per-project content-ops protocol — what it may change (content, not code), a
+  pre-commit content check (the content-relevant slice of the gate), a
+  `content:` commit convention. Header + block-template pin → `2026-08-31`.
+
+### stacks/eleventy-netlify.md
+
+- `#content-model` gains the mechanism: a project-root **`CONTENT.md`** (the
+  content set, the commit convention, "deploys are a human step") and
+  **`scripts/content-check.js`** / `npm run content-check` — `lint → validate →
+  build → links` (no browser, no `test`; a11y backstopped by `bin/deploy`),
+  plus a warning when the working tree has changes outside the content set.
+  `compliance.js`'s `content-model` row reports whether the protocol is
+  present. Header → `2026-08-31`.
+- `#internal-links`: the glossary is labelled **opt-in** — the baseline now has
+  no glossary wiring at all. `src/_data/glossary.js` (empty stub) and the no-op
+  `glossify` filter are removed; `explainer.njk` drops `| glossify`;
+  `check-links.js` wraps the `glossary.js` require in `try/catch` so the
+  `/glossary/#slug` check activates only when the add-on ships the file. The
+  `glossary` add-on gains an `explainer.njk` and its README/config-snippet stop
+  referring to a baseline no-op.
+
+### stacks/phoenix.md · sveltekit.md
+
+- `#content-model` each gets a one-line agent-editing note (`CONTENT.md` + a
+  `content.check` alias) — `TODO`, pointing at the eleventy pattern. Headers →
+  `2026-08-31`.
+
+
+
+### templates/concept-brief.md (new)
+
+- A stack-agnostic fill-in brief that ideation (Cowork / a Claude chat)
+  produces and Claude Code builds from. Sections map to concrete output: **the
+  idea** → home intro / about / meta descriptions; **House style** (a fenced
+  `- key: value` block) → copied into the project's `CLAUDE.md`, answers the
+  `#adopting` five questions; **Brand** (concept-level — "muted teal, calm, a
+  leaf mark") → `src/_data/brand.js`, verified AA on `/audit/`; **Content**
+  (collection name, extra fields, 3–5 seed entries) → the content model +
+  schema + rendered collection; **Pages & layout** → the templates;
+  **Add-on packs** (checklist) → which `add-ons/<name>/` to apply; **Meta** →
+  name / pkg / currency / owner.
+
+### templates/eleventy-netlify/bin/init · new-project.sh
+
+- `bin/init --brief <path>`: reads the brief's House-style block + Meta (no
+  deps — a line parser), writes the House-style answers into `CLAUDE.md`
+  (dropping the decision-menu comments), and takes name / package / URL /
+  currency from Meta + the block; prompts only for what the brief left blank.
+- `new-project.sh <stack> <dest> --brief <path>` resolves a relative brief
+  path before `cd`-ing, forwards it, and errors with a checklist pointer when
+  the stack has no template.
+
+### docs — adopting pointer
+
+- `core.md#adopting` / `README.md` / `TEMPLATE.md` gain a pointer: the filled
+  brief is the recommended input to the new-project flow. No contract or spec
+  change of its own — the version move above is the content-ops clause. An
+  existing project re-checks `#adopting` and finds nothing to do: the brief is
+  new-project tooling.
+
+---
+
+## 2026-08-30 — a copy-and-modify template for Eleventy + Netlify (#adopting)
+
+### templates/eleventy-netlify (new)
+
+- A copy-and-modify starter for the Eleventy + Netlify stack, co-located at
+  `templates/eleventy-netlify/`, versioned / CHANGELOG'd / consistency-checked
+  with the docs. Its structure was lifted from a live compliant project; from
+  here it is maintained **against the standard** (`core.md` +
+  `stacks/eleventy-netlify.md`, verified by `templates/verify.sh`), not synced
+  from any project. `npm run check` and `npm run compliance` pass on commit 1
+  (`28 pass · 0 fail`), so a new project starts at "fill in brand + content".
+  - **Baseline:** the always-true compliant skeleton — the generic
+    tooling/config/scripts verbatim, the GWP files with `__PKG_NAME__` /
+    `__SITE_NAME__` / `https://example.com` / `USD` placeholders, a neutral
+    `guides` content model with 3 sample entries, and one example client-logic
+    module. An obviously-placeholder magenta brand (still AA) so nothing
+    un-branded ships by accident.
+  - **`add-ons/<name>/`** — opt-in packs mirroring the opt-in chapters:
+    `ads` (`#ads`), `ai-proxy` (`#llm-integration` — a worked Netlify Function
+    proxy + a pure tested transform), `feed` (article feeds, via
+    `@11ty/eleventy-plugin-rss@3`'s `feedPlugin`), `glossary`
+    (`#internal-links`), `calculator` (`#client-logic` / `#domain-tests`). Each
+    is a folder + a numbered copy-in README. All five smoke-tested against a
+    fresh init'd project (`ai-proxy`'s model call excepted — no key in CI).
+  - **`bin/init`** (Node, no deps) substitutes the placeholders, installs,
+    commits, and runs the gate, then deletes the template-meta files.
+    `templates/new-project.sh` wraps copy + `git init` + `bin/init`.
+  - **`templates/verify.sh`** runs each template's `check` + `compliance
+    --strict` and fails on `standard-version` drift. **`bin/check`** runs the
+    four doc-consistency checks (CORE-slug · slug-set mirror · no restatement ·
+    sterile). **`.github/workflows/standard.yml`** runs both on every push / PR
+    / weekly — the weekly run is the drift + supply-chain alarm. (The stray
+    nested `templates/eleventy-netlify/.github/workflows/template-verify.yml` —
+    inert, since GitHub only reads root workflows — is removed.)
+  - `scripts/compliance.js` + `test/compliance.test.js` sweep the Part J
+    chapters (`llm-integration` / `agent-artifacts` / `usage-metering`) — they
+    were missing from the seed (it predated 2026-08-29) despite the
+    `2026-08-30` pin. `N/A` for a static site unless `ai: llm-api`. The
+    `stacks/eleventy-netlify.md#compliance` PASS-criteria table gains the row.
+  - `compliance.js` `#ci-cd` no longer depends on the **live** `core.hooksPath`
+    state — that's "`npm install` has run here", not a codebase property, so a
+    fresh clone stays compliant. `doctor` still surfaces it on `/audit/` as a
+    warn. The template's `prepare` script is guarded to no-op unless it's the
+    repo root, so `npm ci` in a template checked out inside another repo (this
+    one) doesn't touch the outer git config. `#ci-cd` gains a one-liner.
+
+### core: adopting
+
+- New **"Starting point"** paragraph after the stack-selection flow: where a
+  `templates/<stack>/` exists, starting from it *is* the new-project path; the
+  impl doc's checklist is the by-hand equivalent and the annotated inventory.
+  Stack-agnostic wording — only `eleventy-netlify` has one today. Header version
+  and the block-template `standard-version` pin → `2026-08-30`.
+
+### stacks/eleventy-netlify.md
+
+- `#adopting`: a **"Fastest path — start from the template"** lead-in above the
+  new-project checklist (`new-project.sh` → `bin/init` → `brand.js` + content →
+  `npm run deploy`); the 11-step checklist kept verbatim as the by-hand path /
+  inventory. `#ads` and `#llm-integration` each gain a one-line pointer to their
+  `add-ons/<name>/` pack. Header version → `2026-08-30`.
+- `#styling` (`pico-classes`) + `#brand-source`: `src/tokens.css.njk` maps
+  `brand.js`'s core palette (primary, background, text, danger) onto the
+  matching `--pico-*` vars, so a `brand.js` colour change reaches the **live
+  CSS** — not just re-pinned hexes Pico already has. The template does this;
+  the earlier pattern of pinning a Pico theme's hexes into `brand.js` left the
+  live CSS unchanged and is a `#brand-source` gap. Pico's build still supplies
+  the derived neutrals.
+
+### stacks/phoenix.md · sveltekit.md
+
+- `#adopting`: a one-line "no starter template for this stack yet — follow the
+  checklist; `stacks/eleventy-netlify.md` has the reference template". Header
+  versions → `2026-08-30`.
+
+### README.md
+
+- Doc-map gains a `templates/` row. A "Starting a new project" paragraph in
+  "How to use it". "Home" notes the templates ship in-repo and a remote unlocks
+  `degit`. Consistency checks gain `templates/verify.sh` as the 4th check.
+  "Proposing changes" gains the template-sync rule (update the template in the
+  same change as a mirrored-section edit, re-pin, run `verify.sh`).
+
+### index.json
+
+- Each framework gains a `template` field (`templates/eleventy-netlify/` or
+  `null`). `version` → `2026-08-30`.
+
+### not a standard-content change
+
+- No CORE contract changed. The `#adopting` edit adds a path, not a rule; the
+  `stacks/eleventy-netlify.md` `#styling` / `#brand-source` / `#compliance`
+  edits clarify existing mechanism; the version bump is for the template pin +
+  the doc-set additions above.
+
+---
+
+## 2026-08-30 — the standard is a git repo
+
+### repo
+
+- Consolidated the two loose copies (the canonical set under
+  `~/.claude/standards/web-house-style/` and a stale pre-`#compliance` copy at
+  `~/Dev/web-house-style/`) into one git-tracked project at
+  `~/Dev/web-house-style/`, default branch `main`. `~/.claude/standards/web-house-style/`
+  is now a symlink to it, so every existing reference resolves unchanged.
+- `README.md` "Provisional home" → "Home", updated for the repo layout and the
+  remaining deferred items (global `CLAUDE.md` pointer, a GitHub remote,
+  existing-project migration).
+- No standard-content change — versions and slugs untouched.
+
+---
+
+## 2026-08-29 — AI & agent capabilities, opt-in (#llm-integration, #agent-artifacts, #usage-metering)
+
+### core: llm-integration · agent-artifacts · usage-metering (new chapters)
+
+- New **Part J — AI & agent capabilities (opt-in)**, three chapters, inserted
+  before the old Part J (Meta), which becomes **Part K**. All three are
+  need-gated the way `#beyond-this-standard` and `#ads` are — opt-in per project,
+  **not** a consequence of the framework. A project that calls no model API is
+  unaffected (all three `N/A`).
+  - **`#llm-integration`** — in scope whenever the project calls a model
+    provider's API at all. Server-side-only key handling per environment
+    (extends `#secrets`), explicit timeout + capped-backoff retry + an app-side
+    per-user request ceiling, per-request token/cost telemetry + spend-anomaly
+    alert (extends `#observability`), a moderation/safety layer sized to the
+    subject's risk (three tiers), a plain visible AI disclosure to end users, and
+    a pre-launch provider-usage-policy fit check with a recorded date. The
+    response transform is a pure tested function (`#domain-tests`).
+  - **`#agent-artifacts`** — in scope only when users generate downloadable files
+    via model-driven code execution. Sandboxed execution (no route to secrets /
+    DB / network), object-storage with an enforced TTL, authorization-checked
+    delivery with defensive `Content-Type` / `Content-Disposition` / `nosniff` /
+    CSP, per-artifact cost as its own `#observability` signal.
+  - **`#usage-metering`** — in scope only when pricing isn't flat. An immutable
+    per-subject event log, server-side pre-spend plan-tier enforcement, a
+    scheduled reconciliation job against the payment processor (idempotent usage
+    reporting, webhook-driven tier state), a user-facing usage view from the same
+    rows, tested partial-failure paths, tested allowance boundaries.
+- Threaded one-liners into `#third-parties` (a model provider is a declared third
+  party; key-bearing → server-side), `#privacy` (sending end-user content to a
+  provider is a privacy-page entry; use the no-train/zero-retention mode),
+  `#secrets` (model-provider key = per-env, spend-capped, scoped, rotatable
+  without redeploy), `#observability` (per-request token/cost + reconciliation
+  drift join the loop), `#beyond-this-standard` (an LLM/agent surface is its own
+  opt-in axis; a single stateless call is a serverless function, streaming /
+  artifacts / metering are past the envelope), `#compliance` (the Part J chapters
+  are `N/A` when `ai: none`), `#out-of-scope` (ML infrastructure — fine-tuning,
+  RAG retrieval layer, evals harness, prompt-versioning — is not covered),
+  `#anti-patterns` (six new entries).
+- `#adopting`: a **5th** stack-selection question ("Does the project call an
+  LLM / agent API?", default No, with the `+artifacts` / `+metering` follow-ups);
+  `ai: none` added to the `CLAUDE.md` block template. The example block's
+  `standard-version` pin and the doc header move to `2026-08-29`.
+- Slug registry gains `llm-integration` · `agent-artifacts` · `usage-metering`
+  (after `observability`).
+
+### stacks/phoenix.md
+
+- Three new mirrored sections (the concrete "how" this change is grounded in):
+  `#llm-integration` — a context module + `Req` with explicit timeout, an Ash
+  `Conversation` / `Message` resource for chat state, LiveView streamed assigns
+  for token streaming, a `LLM.Usage` Ash resource written per call, `Oban` for
+  async summarisation/metering, a `Moderation` pass, the provider origin in the
+  `ThirdParties` manifest; `#agent-artifacts` — an Oban job driving a sandboxed
+  runner (a separate container / microVM, never the app node), R2/S3 storage with
+  a TTL + an Oban cron sweeper, an authorization-checked `ArtifactController`
+  download with defensive headers; `#usage-metering` — a `UsageEvent` immutable
+  Ash resource, a pre-spend `Ash.Policy` / plan check, an `Oban` reconciliation
+  worker against Stripe with idempotent usage records and webhook handlers.
+  Adds AI items to the new-project checklist and the migration list; two
+  Phoenix-specific anti-patterns.
+
+### stacks/eleventy-netlify.md
+
+- Three new mirrored sections, all **out-of-scope-with-a-pointer**: a single
+  stateless model call belongs in a `netlify/functions/*` proxy (the one
+  sanctioned serverless carve-out — key in the Function env, timeout, the origin
+  in `_data/thirdparties.js`, the privacy page updated, a visible AI disclosure,
+  the transform pure-tested); conversation state, streaming, sandboxed code
+  execution, and usage metering are all past `#beyond-this-standard` → use
+  `stacks/phoenix.md`. `ai: none` added to the `CLAUDE.md` block template and a
+  change-checklist line.
+
+### stacks/sveltekit.md
+
+- Three new mirrored sections — `TODO` stubs with hints (a `+server.js` endpoint
+  or a serverless function for the keyed call under `adapter-static`; anything
+  stateful/streamed/metered → `core.md#beyond-this-standard` and the Phoenix
+  reference). `ai:` note added to the change checklist.
+
+---
+
+## 2026-08-28 — codebase-vs-standard conformance (#compliance)
+
+### core: compliance (new chapter)
+
+- New chapter `#compliance` in Part I, between `#the-gate` and `#ci-cd`.
+  Contract: one command reports the codebase's state against **every chapter** —
+  `PASS` / `FAIL` / `MANUAL` / `N/A` — as the drift-and-completeness sweep that
+  `#the-gate` (regressions only) does not do. It is **not** part of the gate: a
+  `FAIL` is a migration gap, not a regression, and gating on it would freeze work
+  mid-migration. Specs: walks every CORE chapter + mirrored impl section; summary
+  line `N pass · M fail · K manual`; runs on demand and at build time
+  (cache-aware) feeding the audit page's Compliance panel; the deploy pre-flight
+  warns on any `PASS → FAIL` since the last deploy; a standard-version drift row
+  compares the pinned `standard-version` to `core.md`'s version header and emits
+  `MANUAL: re-check #<slug>` per CHANGELOG slug changed since. Reuses existing
+  machinery (repo introspection + link-check output scan). The assistant runs it
+  at onboarding, when the pin is behind, before a multi-chapter release, and when
+  asked "are we still in line?".
+- Threaded into `#the-gate` (a bullet: completeness + version drift are
+  `#compliance`'s job, not the gate's), `#audit-page` (a Compliance tab),
+  `#ci-cd` (production-deploy pre-flight warns on `PASS → FAIL`), `#adopting`
+  (the "four questions" fix, a `#compliance` line in the directive, an
+  "Onboarding an existing project" paragraph, a Change-checklist item),
+  `#observability` (a re-run trigger), `#anti-patterns` (compliance in the gate /
+  treating a `FAIL` as a regression, working the backlog without re-running it,
+  a stale `standard-version` pin).
+- Slug registry gains `compliance` (after `the-gate`).
+
+### stacks/eleventy-netlify.md
+
+- New `compliance` mirrored section: `scripts/compliance.js`,
+  `"compliance": "node scripts/compliance.js"` in `package.json` (**not** in
+  `check`), a per-chapter PASS-criteria table, the MANUAL list, the
+  standard-version drift check (`standard-version` in `CLAUDE.md` vs `**Version:**`
+  in `core.md` vs `### core:` entries in `CHANGELOG.md`), `_data/infra.js`
+  running it cache-aware for the audit-page Compliance tab, `bin/deploy`
+  diffing against `.cache/compliance-last.json` and warning on `PASS → FAIL`
+  (non-zero exit only under `--strict`). "Compliance" added to the audit-page
+  tabs; the House-style directive block, the new-project checklist, and the
+  existing-project migration note updated.
+
+### stacks/phoenix.md
+
+- New `compliance` mirrored section: a `mix whs.check` task (**not** in the
+  `check` alias), reusing `mix links.check`'s output scan and the `/audit`
+  repo-config introspection; an Ash-flavored per-chapter table; the
+  standard-version drift row; `/audit` Compliance tab + `bin/deploy` pre-flight
+  wiring.
+
+### stacks/sveltekit.md
+
+- New `compliance` mirrored section — `TODO` stub with a hint
+  (`scripts/compliance.js` or a Vite task over `build/` + repo, the drift row,
+  the prerendered `/audit` Compliance tab).
+
+---
+
+## 2026-08-28 — the `CLAUDE.md` House-style directive
+
+### core: adopting
+
+- The recommended `CLAUDE.md` content changed from a bare data block (with one
+  passive "read the docs" sub-bullet) to a **`## House style` section**: a
+  directive paragraph — *use the standard for all work unless a request
+  explicitly says otherwise; check the governing chapter before implementing;
+  a conflict with the current code is a migration gap to surface, not route
+  around; never silently diverge from a Contract, record deliberate deviations;
+  where the standard is silent, do what's idiomatic; run the gate before
+  reporting done* — followed by the data block. Verify updated to require both
+  parts. Header version → 2026-08-28.
+
+### stacks/eleventy-netlify.md · phoenix.md · sveltekit.md
+
+- Each `adopting` section now shows its filled-in `## House style` section with
+  the gate command substituted (`npm run check` / `mix check`) and any
+  stack-specific `CLAUDE.md` prose (Eleventy: the generated-assets note;
+  Phoenix: the brand-tokens note) folded in. New-project checklists point at it.
+
+---
+
+## 2026-08-28 — display advertising (AdSense)
+
+### core: ads (new chapter)
+
+- New chapter `#ads` in Part G, after `#privacy`. Contract: display ads are
+  opt-in per project (`ads:` key in the `CLAUDE.md` block, `none` default);
+  consent-gated via a provider-certified CMP; every ad origin declared in the
+  manifest; slots carry reserved dimensions (CLS); the loader never runs on a
+  non-production build; `ads.txt` is generated/managed; the CSP relaxation is
+  the widest it ever gets, scoped to the ad directives, documented, and never
+  touches `default-src` or adds `'unsafe-eval'`.
+- Threaded one-liners into `#security-headers` (the ad CSP relaxation),
+  `#privacy` (ads always need a CMP + cookies — never privacy-first),
+  `#third-parties` (an ad provider is a declared third party), `#noindex` (same
+  `isProduction` gate covers ads), `#observability` (ads regress CLS/LCP;
+  reserved slots hold CLS), `#out-of-scope` (ad density / editorial),
+  `#anti-patterns` (ad loader before consent, ads on non-prod, drifted
+  `ads.txt`, unreserved slots, non-certified CMP, `'unsafe-eval'`).
+- `#adopting`: a 4th stack-selection question ("Display advertising?" default
+  No); `ads: none` added to the `CLAUDE.md` block template.
+- Slug registry gains `ads`.
+
+### stacks/eleventy-netlify.md
+
+- New `ads` mirrored section: `_data/ads.js`, `_includes/ad-slot.njk` (wrapper
+  div + `<ins class="adsbygoogle">`, no inline `style`), the `push({})` in
+  `site.js`, `src/ads.txt.njk`, the `style.css` reserved-height rules, the
+  `netlify.toml` CSP fence with a representative AdSense/CMP directive set, the
+  `build.isProduction` gate on the CMP + loader + macro, `check-links.js`
+  non-prod / `ads.txt` checks, and an `/audit/` **Ads** tab. Google's GDPR
+  message named as the low-friction certified CMP.
+- Tree, `noindex`, `security-headers`, `internal-links`, `audit-page`,
+  `adopting`, and `anti-patterns` gained ad cross-refs.
+
+### stacks/phoenix.md
+
+- New `ads` mirrored section: `<App>Web.Ads` module (`enabled?/0` =
+  `config_env() == :prod`), `config.exs` holds the ids, `<.ad_slot>` component,
+  `/ads.txt` controller, the CSP in the `SecurityHeaders` plug, the LiveView
+  nonce vs `'unsafe-inline'` note. `noindex` / `audit-page` / `anti-patterns`
+  cross-refs.
+
+### stacks/sveltekit.md
+
+- New `ads` mirrored section (skeleton + hints): `src/lib/ads.js`, the loaders in
+  `+layout.svelte` gated on `import.meta.env.PROD` + a consent store, an
+  `<AdSlot>` component, `/ads.txt` as a `+server.js` route, the `svelte.config.js`
+  `csp` interaction.
+
+---
+
+## 2026-08-28 — hardening from the first full Eleventy migration
+
+Fixes and gaps surfaced running the first full Eleventy migration end to end.
+
+### core: (client-logic, theme, assets, internal-links, security-headers)
+
+- **`client-logic`** — the page wiring is **CSP-safe**: no inline `<script>`, no
+  `on*=`; it's a loaded file, and for a per-page calculator the browser-only
+  wiring sits in a `typeof document !== "undefined"` block *inside the same pure
+  module* (one file, DOM-free in the test runner). Resolves the standing
+  contradiction with `security-headers`' `script-src 'self'`.
+- **`theme`** — the anti-FOUC script is a separate render-blocking file (or a
+  hashed inline block), never a raw inline `<script>` — same CSP reason.
+- **`assets`** — added: verify a custom font's subset actually covers the
+  site's text (a mis-scoped subset fails silently to the system stack); serve
+  the web manifest as `application/manifest+json`.
+- **`internal-links`** — the build check also fails on any inline `<script>` /
+  `<style>` / `on*=` / `style=` in the output (CSP-regression guard), and on any
+  CSP-granted origin missing from the manifest (the reverse isn't required —
+  a host/form-processor is in the manifest but loads nothing).
+- **`security-headers`** — Verify reworded to the one-directional CSP↔manifest
+  check; note that the CSP only applies once served (check live + click through
+  in a real browser after deploy); don't restate platform-managed HSTS.
+
+### stacks/eleventy-netlify.md
+
+- `client-logic` / `theme` — the calc module now carries the browser wiring
+  block; `data-calc=` on the button; anti-FOUC → `static/theme-init.js`.
+- `og-image` — Satori needs a **static** ttf/otf/woff (not woff2, not a
+  variable font's `fvar`); bundle `@fontsource/<family>` static weights; build
+  the card as a vnode object, drop `satori-html`.
+- `the-gate` — `"test": "node --test test/*.test.js"` (the glob; bare
+  `node --test test/` errors on newer Node). `png-to-ico` + `@fontsource/*` in
+  deps; `node-html-parser` (check-links) in devDeps; note `npm ci` installs
+  both tiers.
+- `ci-cd` — `actions/checkout@v5` / `setup-node@v5` (v4 → deprecated Node 20);
+  shallow checkout is fine for the `git log` `<lastmod>`; `NETLIFY_SITE_ID` is
+  the UUID Netlify now labels "Project ID".
+- `security-headers` — `[[headers]]` for `/site.webmanifest` content-type.
+- `internal-links` — the CSP-safety + CSP-origin scan documented in
+  `check-links.js`; ad/privacy opt-out `<a>` allowlist.
+- `adopting` Pattern A — steps 6/8 reworded to write CSP-shaped modules up front
+  and land `theme-init.js` + the inline-code scan with the headers.
+
+### stacks/sveltekit.md
+
+- `theme` hint — anti-FOUC must be a hashed inline block (SvelteKit `csp`) or a
+  `<script src>`, not raw inline.
+
+---
+
+## 2026-08-28 — solo is the default working mode
+
+### core: ci-cd
+
+- Reframed from a PR-centric flow with solo accommodations to **solo as the
+  documented default**: branch → pre-push hook runs the gate → fast-forward
+  `main` → push; open a pull request only for a concrete reason (CI vetting a
+  branch before `main`, the rendered diff, a paper trail), never as
+  self-approval ceremony; multi-committer projects add the PR/review layer on
+  top and nothing below changes. New specs: the pre-push hook is *the*
+  enforcement point solo; push `main` after each merge (offsite copy + CI
+  actually runs); CI is a clean-room environment-drift check, not a merge gate.
+  Rationale gained a paragraph; Verify now checks the hook is *installed*.
+
+### core: repo-hygiene
+
+- "one logical change per pull request" → "per commit (and per PR, on projects
+  that use them)". Contract line "small reviewable changes" → "small
+  self-contained changes".
+
+### core: adopting
+
+- "PR review checklist" → "Change checklist" — run before a merge to `main` and
+  again before `bin/deploy`; "all in this PR" → "all in the same change".
+
+### stacks/eleventy-netlify.md · phoenix.md · sveltekit.md
+
+- `ci-cd` mirrors: the Eleventy binding states the solo flow up front and
+  `ci.yml` triggers on `push: {}` (any branch) + `pull_request`; "every merged
+  PR" → "everything on `main`"; "PR review checklist" → "Change checklist"
+  across all three; migration `[one PR:]` markers → `[together:]`; the
+  "busy PR flow" build-minutes framing dropped.
+
+## 2026-08-27 — netlify deploy `--no-build`
+
+### stacks/eleventy-netlify.md
+
+- `ci-cd` — corrected the deploy command. The doc claimed `netlify deploy`
+  "without `--build`" uploads the artifact without building; the current Netlify
+  CLI (v17+, verified on v27) runs `netlify.toml`'s `build.command` **by
+  default** on `netlify deploy`. Without `--no-build` it rebuilds `_site/` with
+  no `DEPLOY_TARGET`, i.e. in preview mode, and ships `noindex` + `robots`
+  `Disallow: /` to production. Surfaced by the first real `bin/deploy` on the
+  first Eleventy migration — production served `noindex` for ~35 min.
+  `bin/deploy`, the `deploy.yml`/PR-preview snippets, the "zero build minutes"
+  line, and the anti-pattern entry all now carry `--no-build`.
+
+### stacks/sveltekit.md
+
+- `ci-cd` hint — same `--no-build` fix in the `adapter-static` + Netlify note.
+
+## 2026-08-27 — initial split
+
+The single 1518-line "Eleventy + Netlify static-site house style" document was
+split into a stack-agnostic CORE contract plus per-stack implementation
+bindings.
+
+### core: all
+
+- Created `core.md` — ~34 contract chapters (`Contract / Specs / Rationale /
+  Verify / Implementation`), each with a frozen slug. The 23 sections of the
+  source doc were dispositioned CORE / IMPL / SPLIT; every stack-agnostic
+  principle landed in CORE with its concrete specs preserved verbatim (the CSP
+  string, the OG/Twitter tag table, the a11y checklist, the security-header
+  values, the OG image dimensions).
+- `#privacy` — encodes the "consent-gated allowed" decision: default is
+  no-tracking; third-party analytics (incl. GA/GTM) permitted **only** when
+  privacy-first or gated behind a CMP that loads nothing until opt-in.
+- `#ci-cd` — genericized from the Netlify "a git push never triggers a build"
+  framing to "deploys are gated, sanctioned, no bypass, on your schedule";
+  push-to-deploy is explicitly fine where the gate runs first.
+- `#security-headers` — "framing denied" accepts `X-Frame-Options: DENY` **or**
+  `SAMEORIGIN` + `frame-ancestors 'none'` (surfaced by writing the Phoenix
+  binding, where `put_secure_browser_headers` uses SAMEORIGIN).
+- `#assets` — "a system font stack also satisfies 'no external font origin'"
+  (surfaced by the Phoenix binding).
+- `#content-model` — the validation-gate contract holds for DB-backed content
+  via changeset/resource validation; "no database" is not a CORE rule (it is the
+  static envelope, addressed in `#beyond-this-standard`).
+
+### stacks/eleventy-netlify.md
+
+- The source doc reworked as the Eleventy binding (~90% mechanism reuse). 4
+  impl-only sections (`stack-baseline`, `project-layout`, `eleventy-config`,
+  `templating`) + 31 mirrored sections + Eleventy-specific `adopting` /
+  `out-of-scope` / `anti-patterns`.
+- Two migration paths added, keyed to common starting conditions (Pattern A:
+  self-hosted, content in templates, no CI; Pattern B: CDN assets + a form
+  processor, content already externalized).
+
+### stacks/phoenix.md
+
+- New binding, grounded in a real production Phoenix/Ash codebase (unnamed —
+  the standard is project-agnostic). Every CORE contract could be expressed as a
+  Phoenix "how" — none had to move back to Eleventy-specific.
+- Notable idiomatic contrasts: cached `SitemapController` + `Ash.Notifier`
+  invalidation (not a build-time template); `bin/deploy {env}` `git push` to a
+  release remote (push-to-deploy is fine); the serverless key-hiding proxy
+  dissolves (call from a context module); `internal-links` partly free via
+  verified routes `~p`.
+- The common non-compliance of an existing Phoenix app (no CSP, per-page meta
+  unassigned, no JSON-LD, marketing scripts with no CMP, no a11y tooling, a
+  `.env` in git history, an unrouted health check, a misplaced `force_ssl`
+  `exclude:` key, unauthenticated AshAdmin, no CI workflow) is documented
+  per-section as **common gaps** and consolidated into a migration checklist.
+
+### stacks/sveltekit.md
+
+- New binding as a **stub**: full mirrored-slug skeleton, per-section "how" is
+  `TODO` with a concrete hint. The `where-sveltekit-fights-the-grain` (5
+  friction points + 3 places it helps) and `open-questions-for-later` (6 items)
+  sections are written.
+
+### deleted
+
+- `eleventy-house-style.md` (the source) — superseded by `core.md` +
+  `stacks/eleventy-netlify.md`.
+
+### not done (deferred)
+
+- Move the doc set to a permanent home; wire the global `~/.claude/CLAUDE.md`
+  pointer; backfill the House-style block into and migrate existing Eleventy
+  projects. Each needs its own review.