@piercebarney/whs-eleventy 2026.10.13 → 2026.10.15

package/package.json

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

@@ -23,6 +23,77 @@ enforced, new *opt-in* chapters/capabilities, tooling-only changes — is
 
 ---
 
+## 2026-10-15 [non-breaking]
+
+Each scaffolded project already self-checks its own standard-version drift
+(`whs status`), but nothing reported the whole local fleet in one pass.
+`bin/fleet` closes that gap — read-only, no per-project tooling invoked, so
+it covers every stack today, not just the one with compliance-sweep tooling.
+
+### bin/fleet
+
+New `bin/fleet [dir]` (dir: arg > `$WHS_FLEET_DIR` > `~/Dev/whs-projects`).
+For each immediate subdirectory, reads its `standard-version: <date>` pin
+(`CLAUDE.md`, else `AGENTS.md`) and reports it against this checkout's
+`core.md` version and the CHANGELOG dates after the pin — one row per
+project (stack, pin, `N behind (M breaking)` or `current` or `not pinned`),
+then a fleet-wide summary. The "N behind" count mirrors `versionsBehind()`
+in `packages/whs-eleventy/lib/status.js`; a suffixed `-N` pin compares by
+its date, same as that function. Exit 0 always (drift is a backlog signal);
+a missing/non-directory fleet dir exits 1. `bin/test-fleet` is its test
+suite, run alongside `bin/check` in CI's `consistency` job
+(`.github/workflows/standard.yml`).
+
+### README.md
+
+New paragraph documenting `bin/fleet`, next to the `bin/set-version` docs
+in the Consistency checks section.
+
+**Closes:** fleet-audit
+
+## 2026-10-14 [non-breaking]
+
+The House-style block gains an optional `add-ons:` line so a project can
+record which `modules/` pack it applied, once a pack exists that no other
+field already implies.
+
+### core: adopting
+
+New optional line in the recommended data block, right after
+`content-type:`: `add-ons: none  # or: comma list of modules/ packs no field
+above implies (calculator, glossary, pages) — see modules/README.md`. A
+missing line reads as `none`. "Follow-ups when relevant" gains a matching
+clause: a `modules/` pack is recorded under `add-ons:` only when no other
+field already implies it — `ads:` still records `ads`, `ai:` still records
+`ai-proxy`, and `content-type: article` still records `feed`.
+
+### README.md
+
+The House-style data block copy mirrors the new `add-ons:` line, same
+shape and placement as `core.md`'s.
+
+### templates/eleventy-netlify
+
+`CLAUDE.md`'s data block gets the same `add-ons:` line, worded to match its
+siblings (`apply add-ons/<name>/`). `.claude/agents/pack.md`: after applying
+`calculator`, `glossary`, or `pages`, the pack agent appends that pack's name
+to the project's `add-ons:` line in the same commit (adding the line if it's
+missing); `ads`, `ai-proxy`, and `feed` stay untouched since their own fields
+already record them.
+
+### stacks/eleventy-netlify.md
+
+The `#adopting` data-block fence mirrors the new `add-ons:` line; no
+restated principle, just the mechanism plus the `modules/README.md` pointer.
+
+### module: README
+
+New "Recording an applied pack" note: a project records an applied pack on
+its `add-ons:` line only when no other field already implies it, so today
+that's `calculator`, `glossary`, and `pages`.
+
+**Closes:** house-style-add-ons-line
+
 ## 2026-10-13 [non-breaking]
 
 Module pool: `modules/README.md` introduces the standard for a reusable,

package/standard/core.md

@@ -1,6 +1,6 @@
 # Web project house style — CORE (stack-agnostic)
 
-**Version:** 2026-10-13 · **Status:** active
+**Version:** 2026-10-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
@@ -1417,7 +1417,10 @@ project), before non-trivial work. Ask six questions with defaults:
    guide ships either way, read by whichever party writes copy.
 
 Follow-ups when relevant: production domain; content type (`tool` vs `article` —
-`article` implies feeds); publishing rate for content sites.
+`article` implies feeds); publishing rate for content sites; any `modules/`
+pack applied that no other field implies (`ads:` → ads, `ai:` → ai-proxy,
+`content-type: article` → feed) is recorded under `add-ons:` — absent means
+none.
 
 **Starting point.** Where a copy-and-modify template exists for the chosen stack
 (`templates/<stack>/` — see the impl doc and `README.md`), starting from it *is*
@@ -1509,8 +1512,9 @@ governs it and follow that chapter — the slugs are the index (a `<script>` →
 - content-ops: in-repo         # or: reserved — a separate content operation owns content, see core.md#content-model
 - production-url: https://example.com
 - 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-10-13  # recommended — enables standard-version drift tracking (#compliance)
+- standard-version: 2026-10-15  # recommended — enables standard-version drift tracking (#compliance)
 
 <!-- optional, present only while a filed need is unresolved -->
 ### Waiting on the standard