@piercebarney/whs-eleventy 2026.11.113 → 2026.11.114

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@piercebarney/whs-eleventy",
3
- "version": "2026.11.113",
3
+ "version": "2026.11.114",
4
4
  "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.",
5
5
  "bin": {
6
6
  "whs": "cli.js"
@@ -32,7 +32,7 @@
32
32
  "node": ">=22"
33
33
  },
34
34
  "dependencies": {
35
- "@piercebarney/whs-core": ">=2026.11.113",
35
+ "@piercebarney/whs-core": ">=2026.11.114",
36
36
  "node-html-parser": "^9.0.2"
37
37
  },
38
38
  "devDependencies": {
@@ -23,6 +23,31 @@ enforced, new *opt-in* chapters/capabilities, tooling-only changes — is
23
23
 
24
24
  ---
25
25
 
26
+ ## 2026-11-01-14 [non-breaking]
27
+
28
+ `whs doctor`'s repo tier gains a `native-platform` blocker row: an installed
29
+ package whose `package.json` `os`/`cpu` excludes this machine means
30
+ `node_modules` came from another platform (e.g. the desktop app's Linux shell
31
+ over a Mac install). The row names the packages and points at
32
+ `CLAUDE-PROJECT.md` "Shell environment". It also surfaces in deploy preflight
33
+ and eleventy's audit page via `runRepoChecks`.
34
+
35
+ Non-breaking: tooling only; a normal install on its own machine passes.
36
+
37
+ Still unverified: whether `content-check` fails the same way in the desktop
38
+ app's Linux shell.
39
+
40
+ **What an adopting project does:** `npm update` the whs packages.
41
+
42
+ **Closes:** doctor-platform-mismatch
43
+
44
+ ### packages/whs-core
45
+
46
+ `runRepoChecks` gains the `native-platform` blocker check (last in the repo
47
+ tier) and exports a new `foreignNativePackages(root, { platform, arch })`
48
+ helper. The check reads only top-level and `@scope` `package.json` files and
49
+ follows npm's `os`/`cpu` allow/negation semantics.
50
+
26
51
  ## 2026-11-01-13 [non-breaking]
27
52
 
28
53
  The charter template's Audience section gains an Ownership line: the owner's
package/standard/core.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Web project house style — CORE (stack-agnostic)
2
2
 
3
- **Version:** 2026-11-01-13 · **Status:** active
3
+ **Version:** 2026-11-01-14 · **Status:** active
4
4
 
5
5
  This is the stack-agnostic contract every web project follows, regardless of
6
6
  framework, host, or CSS system. It says **what** must be true, with concrete
@@ -1609,7 +1609,7 @@ governs it and follow that chapter — the slugs are the index (a `<script>` →
1609
1609
  - content-type: tool # tool | article (article => feeds)
1610
1610
  - add-ons: none # or: comma list of modules/ packs no field above implies (calculator, glossary, pages) — see modules/README.md
1611
1611
  - publishing-rate: ~5 pages/week
1612
- - standard-version: 2026-11-01-13 # recommended — enables standard-version drift tracking (#compliance)
1612
+ - standard-version: 2026-11-01-14 # recommended — enables standard-version drift tracking (#compliance)
1613
1613
 
1614
1614
  <!-- optional, present only while a filed need is unresolved -->
1615
1615
  ### Waiting on the standard