@plurnk/plurnk-meta 1.0.7 → 1.0.8

package/DIVERGENCES.md

@@ -11,7 +11,7 @@ Doctrine (owner, 2026-07-13): industry standard unless informed, explicit except
 | 5 | Config | Layered dotenv + example files | `.env.defaults` assembled floor: reader-declares, ONE-LAW key ownership, set-if-unset under operator env | **EXCEPTION (owner design, core SPEC §operator-config-env-defaults)** — standard dotenv layering PLUS a uniqueness law and self-documenting floor; strictly more disciplined than the standard, same operator surface. |
 | 6 | CI | Hosted CI (GitHub Actions) | Committed local git hooks; the 82s drill is the whole gate | **EXCEPTION (owner doctrine, AGENTS §one-gate)** — supply-chain posture: no write-token attack surface, the gate that cannot be forgotten, failures caught before the remote sees them. |
 | 7 | Monorepo dev loop | Build-based (project references, turbo/nx caches) | No-build source resolution via the `plurnk-dev` exports condition | **EXCEPTION** — a direct consequence of committing fully to Node 26 no-compile TS (type-stripping), which the runtime is not walking back with Bun at its heels. Zero-build inner loop; the one sharp edge (types-condition ordering) found + fixed 2026-07-13. No compat hedge — Node 26 to the bone. Owner-ruled 2026-07-15. |
-| 8 | Internal versioning | Independent semver + ranges | Lockstep exact pins inside the monorepo | **EXCEPTION** — exact-pinned, fully-reproducible publish surface with zero pin maintenance (release script); consumers see ordinary semver. The per-release publish volume is not a cost to minimize but the honest WEIGHT of a coherent release — every ship is felt, releases stay deliberate ("pain is the best teacher"). Outside leaves peer `^1` = CONVERGED. Owner-ruled 2026-07-15. |
+| 8 | Internal versioning | Independent semver + ranges | Lockstep exact pins inside the monorepo | **EXCEPTION** — exact-pinned, fully-reproducible publish surface with zero pin maintenance (release script); consumers see ordinary semver. The per-release publish volume is not a cost to minimize but the honest WEIGHT of a coherent release — every ship is felt, releases stay deliberate ("pain is the best teacher"). Outside leaves: `^1` RETIRED (owner-ruled 2026-07-17, #512 — a `^1` peer on a fail-forward surface is dishonest; xai@1.0.0 detonated beside providers@1.0.7 to prove it): stepchildren pin heads EXACT until the stability declaration, swept by the release train's stepchild phase every release. |
 | 9 | Package naming | `@scope/name` | `@plurnk/plurnk-name` | **EXCEPTION (owner ruling 2026-07-11)** — shipped surface frozen; renames rejected as churn without user-facing gain. |
 | 10 | Commit convention | Conventional Commits | Conventional subjects ≤80, subject-only, no trailers, hook-enforced | **CONVERGED-plus** — standard grammar, stricter brevity; context rides references (#N / hash / SPEC tag), owner-ruled 2026-07-12. |
 | 11 | Test tooling | Vitest/Jest common; node:test rising | node:test + node:assert exclusively | **EXCEPTION (owner mandate, global)** — zero-dep native runner; the direction the ecosystem itself is moving. |

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@plurnk/plurnk-meta",
-    "version": "1.0.7",
+    "version": "1.0.8",
     "description": "The plurnk metaproject layer, published: plugin-membership primitives (the ONE trust rule, scope-agnostic symlink-aware enumeration, deployment-root resolution), the family teaching corpus (personality, requirements, scheme docs), and the home for family tooling.",
     "license": "MIT",
     "type": "module",