@piercebarney/whs-eleventy 2026.9.26 → 2026.9.28

package/lib/compliance.js

@@ -186,6 +186,13 @@ const CHECKS = {
     const toml = read("netlify.toml") || "";
     if (!/for = "\/site\.webmanifest"[\s\S]*?application\/manifest\+json/.test(toml))
       return { status: FAIL, note: "site.webmanifest not served as application/manifest+json" };
+    if (!has("_site/site.webmanifest"))
+      return {
+        status: FAIL,
+        note:
+          "netlify.toml declares site.webmanifest's header, but the file " +
+          "doesn't exist in the built output",
+      };
     const fontFiles = walk(path.join(ROOT, "static")).filter((f) => /\.(woff2?|ttf|otf)$/.test(f));
     if (fontFiles.length && !grepSrc(/@font-face/, [".css"]).length)
       return { status: FAIL, note: `${fontFiles.length} font file(s) but no @font-face` };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@piercebarney/whs-eleventy",
-  "version": "2026.9.26",
+  "version": "2026.9.28",
   "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"

package/standard/CHANGELOG.md

@@ -21,6 +21,51 @@ enforced, new *opt-in* chapters/capabilities, tooling-only changes — is
 
 ---
 
+## 2026-09-28 [non-breaking]
+
+### packages/whs-eleventy
+
+`assets` in `lib/compliance.js` reported `PASS` for `site.webmanifest` based
+solely on `netlify.toml` declaring a header rule for it — never checking
+whether the file itself existed in the built output. A project could pass
+having only declared the rule, never having actually generated the file (it's
+produced at build time by `scripts/icons.js`), and the `PASS` message gave no
+sign anything was missing — the same silent-pass class as the
+`styling`/`brand-source`/`domain-tests` fix documented under 2026-09-23. No
+`feedback/` file this time: found and fixed live in this conversation while
+reviewing a real project's `/audit/` page work, not filed by an adopting
+session. Fixed in `8773e26`: now also checks `_site/site.webmanifest` exists,
+the same way `sitemap-robots` and `privacy` already check their own built-output
+files in this file.
+
+---
+
+## 2026-09-27 [non-breaking]
+
+### templates/eleventy-netlify
+
+`.claude/hooks/agent-only.js` gated every main-session `Edit`/`Write`/
+`MultiEdit` regardless of the target file's location — including a
+plan-mode plan file outside the project entirely, which no agent is
+allowed to write (plan mode's own contract requires the main session to
+write it directly). Now scoped to only gate files inside
+`$CLAUDE_PROJECT_DIR`; anything outside it is allowed through
+unconditionally, and an unset `$CLAUDE_PROJECT_DIR` still fails toward the
+original, stricter behavior. Found by a real adopting session using the
+agent-delegation setup for the first time.
+
+### templates/commands
+
+`templates/commands/whs/adopt.md` now tells the adopting session, at the
+point it wires in the Eleventy agent-delegation set, that a fresh Claude
+Code session is required before the newly-added agents
+(`brand`/`content`/`infra`/`layout`/`pack`) become selectable via the
+Agent tool — the subagent roster is fixed at session start, so the
+current session still needs `general-purpose` for anything it delegates
+itself. The command's final report now repeats this if step 5 wired the
+agent set in. Previously the command said nothing, and a real adopting
+session had to rediscover the restart requirement the hard way.
+
 ## 2026-09-26 [non-breaking]
 
 ### stacks/eleventy-netlify.md

package/standard/core.md

@@ -1,6 +1,6 @@
 # Web project house style — CORE (stack-agnostic)
 
-**Version:** 2026-09-26 · **Status:** active
+**Version:** 2026-09-28 · **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
@@ -1467,7 +1467,7 @@ governs it and follow that chapter — the slugs are the index (a `<script>` →
 - production-url: https://example.com
 - content-type: tool           # tool | article  (article => feeds)
 - publishing-rate: ~5 pages/week
-- standard-version: 2026-09-26  # recommended — enables standard-version drift tracking (#compliance)
+- standard-version: 2026-09-28  # recommended — enables standard-version drift tracking (#compliance)
 ```
 
 If the section is absent, the assistant's first action is to run the flow above