@piercebarney/whs-eleventy 2026.10.26 → 2026.10.28

package/lib/compliance.js

@@ -35,6 +35,7 @@ const {
 const coreStatus = require("@piercebarney/whs-core/lib/status.js");
 const { runRepoChecks } = require("./doctor.js");
 const { ROOT, resolveStandard, tryProjectRequire } = require("./_project.js");
+const { BINDING_MARKERS } = require("./status.js");
 
 const CACHE = path.join(ROOT, ".cache", "compliance.json");
 // The standard's text — WHS_STANDARD, the bundled copy (@piercebarney/whs-core's),
@@ -810,11 +811,8 @@ const CHECKS = {
 
 // ---- standard-version drift -----------------------------------------
 // Pure slug/severity parsing is @piercebarney/whs-core's lib/status.js; the
-// eleventy binding marker is supplied here.
-
-const BINDING_MARKERS = [
-  { pattern: /^###\s+stacks\/eleventy-netlify\.md/, label: "(eleventy binding)" },
-];
+// eleventy binding markers live in ./status.js (the single definition both
+// `status` and `compliance` share).
 
 function changelogEntries(changelog, pin) {
   return coreStatus.changelogEntries(changelog, pin, { bindingMarkers: BINDING_MARKERS });

package/lib/status.js

@@ -27,8 +27,22 @@ const path = require("node:path");
 const { runStatus, versionsBehind } = require("@piercebarney/whs-core/lib/status.js");
 const { tryProjectRequire } = require("./_project.js");
 
+// Every CHANGELOG heading form this stack's chapters have carried:
+// `stacks/eleventy-netlify.md` (current), `templates/eleventy-netlify` (its
+// own subpaths too), and the two tooling packages themselves
+// (`packages/whs-eleventy`, `packages/whs-core`) — a date block touching only
+// one of those two produces no `### core:`/stack-binding heading at all, so
+// without a marker here it would silently surface zero rows and
+// `.claude/commands/whs/upgrade.md`'s step 3 (which works from `status`'s
+// rows) would skip it entirely. `\b` after the slug matches whichever comes
+// next in the real heading text — `.md`, `,`, `/`, `:`, or end of line — so
+// one pattern covers combined headings too (e.g.
+// `### templates/eleventy-netlify / stacks/eleventy-netlify.md`).
 const BINDING_MARKERS = [
-  { pattern: /^###\s+stacks\/eleventy-netlify\.md/, label: "(eleventy binding)" },
+  { pattern: /^###\s+.*\bstacks\/eleventy-netlify\b/, label: "(eleventy binding)" },
+  { pattern: /^###\s+.*\btemplates\/eleventy-netlify\b/, label: "(eleventy template)" },
+  { pattern: /^###\s+.*\bpackages\/whs-eleventy\b/, label: "(eleventy tooling)" },
+  { pattern: /^###\s+.*\bpackages\/whs-core\b/, label: "(shared tooling)" },
 ];
 
 // "N requested feature(s) delivered — run /whs:upgrade to adopt" and the
@@ -60,4 +74,4 @@ function main() {
 
 if (require.main === module) main();
 
-module.exports = { versionsBehind };
+module.exports = { versionsBehind, BINDING_MARKERS };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@piercebarney/whs-eleventy",
-  "version": "2026.10.26",
+  "version": "2026.10.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"
@@ -31,7 +31,7 @@
     "node": ">=22"
   },
   "dependencies": {
-    "@piercebarney/whs-core": ">=2026.10.26",
+    "@piercebarney/whs-core": ">=2026.10.28",
     "node-html-parser": "^9.0.2"
   },
   "devDependencies": {

package/standard/CHANGELOG.md

@@ -23,6 +23,44 @@ enforced, new *opt-in* chapters/capabilities, tooling-only changes — is
 
 ---
 
+## 2026-10-28 [non-breaking]
+
+### packages/whs-eleventy
+
+`BINDING_MARKERS` now recognizes `templates/eleventy-netlify`,
+`packages/whs-eleventy`, and `packages/whs-core` headings anywhere in a
+`###` line (not just `stacks/eleventy-netlify.md` at the start of the
+line), so a package-only or template-only CHANGELOG block now produces a
+`whs status` / `whs compliance` row instead of none. `compliance.js` no
+longer keeps its own copy of the marker list — both read the single
+definition exported from `status.js`. Eleventy projects: `npm update`
+`@piercebarney/whs-eleventy` to pick up the fix.
+
+### templates/eleventy-netlify
+
+`.claude/commands/whs/upgrade.md` step 3 gains a paragraph explaining that
+`status`/`compliance` are a helper, not the ground truth of what's in
+scope — listing which headings the markers recognize and noting that
+`### module: <name>` has no marker of its own, so a module's own
+CHANGELOG entries need a manual check against `add-ons/`. Eleventy
+projects: pull the new upgrade.md paragraph on next `/whs:upgrade`.
+
+**Closes:** eleventy-status-package-markers
+
+## 2026-10-27 [non-breaking]
+
+### CLAUDE-PROJECT.md
+
+The `COWORK.md` redirect stub is deleted, now that every Claude Project's
+instructions point at `CLAUDE-PROJECT.md`.
+
+### CLAUDE.md, .claude/agents/infra.md
+
+Both agents'-territory lists drop the "(+ its temporary `COWORK.md` stub)"
+pairing — each now lists just `CLAUDE-PROJECT.md`.
+
+**Closes:** remove-cowork-stub
+
 ## 2026-10-26 [non-breaking]
 
 ### CLAUDE-PROJECT.md

package/standard/core.md

@@ -1,6 +1,6 @@
 # Web project house style — CORE (stack-agnostic)
 
-**Version:** 2026-10-26 · **Status:** active
+**Version:** 2026-10-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
@@ -1554,7 +1554,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-10-26  # recommended — enables standard-version drift tracking (#compliance)
+- standard-version: 2026-10-28  # recommended — enables standard-version drift tracking (#compliance)
 
 <!-- optional, present only while a filed need is unresolved -->
 ### Waiting on the standard