@piercebarney/whs-eleventy 2026.10.24 → 2026.10.26

package/package.json

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

package/standard/CHANGELOG.md

@@ -23,6 +23,114 @@ enforced, new *opt-in* chapters/capabilities, tooling-only changes — is
 
 ---
 
+## 2026-10-26 [non-breaking]
+
+### CLAUDE-PROJECT.md
+
+`COWORK.md` renamed to `CLAUDE-PROJECT.md` (`git mv`, history kept) — the
+title, the paste-in quote, and every other self-reference now name the new
+file. In its place, a small `COWORK.md` stub: it tells any Claude Project
+whose instructions still say `COWORK.md` to read and follow
+`CLAUDE-PROJECT.md` instead, asks the reading Project to remind the human
+once per session to change those instructions, and says the stub will be
+deleted. The paste-in instruction now reads: "This Claude Project works
+with the web house style. Follow `~/Dev/web-house-style/CLAUDE-PROJECT.md`
+exactly — it explains how to handle everything from here." Deleting the
+stub is tracked in `BACKLOG.md` as `remove-cowork-stub`, parked until the
+owner confirms every Claude Project's instructions point at
+`CLAUDE-PROJECT.md`.
+
+### templates/commands/whs/new.md
+
+The four `COWORK.md` mentions (the ideation-flow comparison, the
+project-location convention, the success report's hand-off line, and the
+failure-stance line) now name `CLAUDE-PROJECT.md`.
+
+### PROJECT-OVERVIEW.md
+
+Both mentions of the router file the Claude Project hands off through now
+name `CLAUDE-PROJECT.md`.
+
+### CLAUDE.md, .claude/agents/infra.md
+
+Both agents'-territory lists' `COWORK.md` entries now read
+`CLAUDE-PROJECT.md` (+ its temporary `COWORK.md` stub) — the pairing stays
+until the stub is deleted.
+
+### BACKLOG.md
+
+- The `project-workflow-system` entry's Touches list and the
+  `cowork-upstream-channel` entry's body (two mentions) now name
+  `CLAUDE-PROJECT.md`; `cowork-upstream-channel`'s own slug is unchanged.
+- New `parked` entry `remove-cowork-stub` (source: request, owner, filed
+  2026-09-29): delete the `COWORK.md` stub and its two territory-list
+  mentions once the owner confirms every Claude Project's instructions
+  point at `CLAUDE-PROJECT.md`.
+
+## 2026-10-25 [non-breaking]
+
+### core: adopting
+
+"Cowork" retired from live prose as a standalone product name — it was
+folded into Claude generally, and current product surfaces just say
+"Claude" / "a Claude Project." Wording only, no mechanism change: the
+`content-ops: reserved` paragraph now reads "a separate content operation
+(a Claude Project, a non-developer editing the data files directly)", and
+the Design artifacts paragraph's ideation-workspace example now reads "a
+Claude Project, say".
+
+### COWORK.md
+
+Title now "how a Claude Project works with web-house-style"; the paste-in
+instruction, the "one … Project per site" model line, and every other
+"Cowork Project" mention now read "Claude Project". The file **keeps its
+filename** — renaming it would ripple into every file that points at it by
+name — and gains a one-line historical note explaining the name is kept
+only so existing references don't break.
+
+### README.md
+
+Both mentions ("a Cowork / Claude Project" in the content-ops question, "a
+Cowork / Claude chat" in the concept-brief intro) now read "a Claude
+Project" and "a Claude Project or chat".
+
+### templates/commands/whs/new.md
+
+The four prose mentions of "Cowork" (referring to the ideation flow and the
+project-location convention) now read "a Claude Project"; the `COWORK.md`
+path references are unchanged.
+
+### templates/concept-brief.md
+
+"Fill this in during ideation (Cowork / a Claude chat)" now reads "(a Claude
+Project or chat)"; "maintained by the content arm (Cowork)" now reads
+"maintained by the content arm".
+
+### templates/eleventy-netlify / stacks/eleventy-netlify.md
+
+Every "Cowork" mention across the binding replaced with "the content arm" or
+"the editorial Claude Project", matching `core.md#content-model`'s own
+wording and `bin/init`'s existing "editorial project" phrasing:
+`stacks/eleventy-netlify.md`'s `CONTENT.md` ownership line now says the file
+"names the reserving party (the editorial Claude Project)";
+`CONTENT.md`'s "reserved for: Cowork" now reads "reserved for: the
+editorial Claude Project"; `CLAUDE.md`'s two "reserved for Cowork" /
+"Cowork replaces the placeholder" mentions; `.claude/agents/content.md`'s
+two "those are Cowork's" / "blocked on Cowork" mentions; `requests/README.md`,
+`bin/init`, `add-ons/glossary/README.md`, and `add-ons/pages/README.md`'s
+single mentions each. Wording only — no mechanism change.
+
+### templates/sveltekit-netlify
+
+`AGENTS.md`'s "reserved for Cowork" and `CONTENT.md`'s "reserved for:
+Cowork" now read "reserved for the content arm" and "reserved for: the
+editorial Claude Project", matching the Eleventy binding's wording.
+
+The retired term stays untouched in `CHANGELOG.md`'s own dated history
+(append-only log of what was true when written) and in `BACKLOG.md`'s
+`cowork-upstream-channel` entry (a separate, already-tracked feature idea
+about a Cowork/Claude-Code tethering system, not about the term itself).
+
 ## 2026-10-24 [breaking]
 
 ### module: pages

package/standard/core.md

@@ -1,6 +1,6 @@
 # Web project house style — CORE (stack-agnostic)
 
-**Version:** 2026-10-24 · **Status:** active
+**Version:** 2026-10-26 · **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
@@ -1438,7 +1438,7 @@ project), before non-trivial work. Ask six questions with defaults:
    a plain CRUD app that calls no model is unaffected.
 6. **Who edits content after launch?** *Default: the builder* — record
    `content-ops: in-repo`; no reservation file ships, no protocol to follow.
-   A **separate content operation** (a Claude Project / Cowork, a
+   A **separate content operation** (a Claude Project, a
    non-developer editing the data files directly) → record
    `content-ops: reserved`, `#content-model` Ownership — ships `CONTENT.md`
    (the reserved set + escalation protocol) at the project root. The voice
@@ -1468,7 +1468,7 @@ binding, or the nearest stack with the compromise recorded.
 wireframes, mockups, prototype HTML, a supporting written spec — lives in
 `.claude/design/`, committed, each listed by path in `.claude/brief.md`'s
 "Pages & layout" section: a build session can't reach the ideation workspace
-(a Cowork Project, say), so an artifact never exported there doesn't exist
+(a Claude Project, say), so an artifact never exported there doesn't exist
 for the build. Precedence: the standard (core plus the stack binding) beats
 the written spec (the brief's prose plus any file under `.claude/design/`),
 which beats a mockup — a mockup guides arrangement and hierarchy only where
@@ -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-24  # recommended — enables standard-version drift tracking (#compliance)
+- standard-version: 2026-10-26  # recommended — enables standard-version drift tracking (#compliance)
 
 <!-- optional, present only while a filed need is unresolved -->
 ### Waiting on the standard