instar 1.3.1158 → 1.3.1159

package/dist/data/standards-guard-index.json

@@ -2,7 +2,7 @@
   "schemaVersion": 1,
   "generatedFrom": "source-tree",
   "registrySha256": "81b53363a440e832672618965540b3e507ae0d93adcc67ec2b93daf7933b3ab4",
-  "packageVersion": "1.3.1158",
+  "packageVersion": "1.3.1159",
   "guards": [
     {
       "ref": "docs/audits/phase-b/f10-triage.md",

package/dist/data/standards-guard-index.meta.json

@@ -1,5 +1,5 @@
 {
-  "sha256": "9cbf312433ed10eafb3f33a245b9ba17546fdd534ce1c2caf3dcaf28157ee33c",
+  "sha256": "64b362d2e7aed4d92d9e9948a954ae1c099930efc5972c89842953e81cfd36ff",
   "registrySha256": "81b53363a440e832672618965540b3e507ae0d93adcc67ec2b93daf7933b3ab4",
-  "packageVersion": "1.3.1158"
+  "packageVersion": "1.3.1159"
 }

package/dist/data/standards-registry.meta.json

@@ -2,5 +2,5 @@
   "sha256": "81b53363a440e832672618965540b3e507ae0d93adcc67ec2b93daf7933b3ab4",
   "articleCount": 88,
   "generatedFrom": "docs/STANDARDS-REGISTRY.md",
-  "packageVersion": "1.3.1158"
+  "packageVersion": "1.3.1159"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "instar",
-  "version": "1.3.1158",
+  "version": "1.3.1159",
   "description": "Coherence infrastructure for self-evolving AI agents — on the Claude Code or Codex subscription you already have.",
   "type": "module",
   "main": "dist/index.js",

package/src/data/builtin-manifest.json

@@ -1,8 +1,8 @@
 {
   "$schema": "./builtin-manifest.schema.json",
   "schemaVersion": 1,
-  "generatedAt": "2026-08-15T04:14:15.394Z",
-  "instarVersion": "1.3.1158",
+  "generatedAt": "2026-08-15T04:46:02.884Z",
+  "instarVersion": "1.3.1159",
   "entryCount": 202,
   "entries": {
     "hook:session-start": {

package/src/data/standards-guard-index.json

@@ -2,7 +2,7 @@
   "schemaVersion": 1,
   "generatedFrom": "source-tree",
   "registrySha256": "81b53363a440e832672618965540b3e507ae0d93adcc67ec2b93daf7933b3ab4",
-  "packageVersion": "1.3.1158",
+  "packageVersion": "1.3.1159",
   "guards": [
     {
       "ref": "docs/audits/phase-b/f10-triage.md",

package/src/data/standards-guard-index.meta.json

@@ -1,5 +1,5 @@
 {
-  "sha256": "9cbf312433ed10eafb3f33a245b9ba17546fdd534ce1c2caf3dcaf28157ee33c",
+  "sha256": "64b362d2e7aed4d92d9e9948a954ae1c099930efc5972c89842953e81cfd36ff",
   "registrySha256": "81b53363a440e832672618965540b3e507ae0d93adcc67ec2b93daf7933b3ab4",
-  "packageVersion": "1.3.1158"
+  "packageVersion": "1.3.1159"
 }

package/src/data/standards-registry.meta.json

@@ -2,5 +2,5 @@
   "sha256": "81b53363a440e832672618965540b3e507ae0d93adcc67ec2b93daf7933b3ab4",
   "articleCount": 88,
   "generatedFrom": "docs/STANDARDS-REGISTRY.md",
-  "packageVersion": "1.3.1158"
+  "packageVersion": "1.3.1159"
 }

package/upgrades/1.3.1159.md

@@ -0,0 +1,40 @@
+# Upgrade Guide — vNEXT
+
+<!-- assembled-by: assemble-next-md -->
+<!-- bump: patch -->
+
+## What Changed
+
+The two vitest globalSetup files that prepare the packed standards-registry asset
+(`tests/setup/build-dist.globalSetup.ts` and
+`tests/setup/ensure-registry-asset.globalSetup.ts`) decided whether to regenerate it
+on PRESENCE alone — `if (outputs.every(exists)) return`. An asset generated from an
+older revision of `docs/STANDARDS-REGISTRY.md` was therefore never regenerated.
+
+Both now consult a shared `registryAssetIsStale()` helper that compares the oldest
+output's mtime against the newest input's (`docs/STANDARDS-REGISTRY.md`,
+`docs/standards-registry-floor.json`, `package.json`) — the same shape the sibling
+`ensureDistBuilt()` twelve lines above already used.
+
+## What to Tell Your User
+
+None — internal change (no user-facing surface).
+
+## Summary of New Capabilities
+
+None — internal change (no user-facing surface).
+
+## Evidence
+
+- Measured 2026-08-15: in a checkout whose asset was generated at 17:59 from a source
+  three hours newer, `standards-registry-asset`, `standards-enforcement-auditor` and
+  `standards-coverage-route` failed with 8 assertions. Regenerating the asset alone
+  made all 77 pass.
+- `tests/unit/registry-asset-freshness.test.ts` — 9/9.
+- Negative controls, both fired: reverting the comparison fails THE DEFECT case
+  (1 failed / 8 passed); reverting one call site to the presence check fails the
+  wiring case, naming the file. Both sources restored byte-exact.
+- The wiring guard matches the MODULE SPECIFIER, not the imported identifier, so an
+  aliased import cannot defeat it — the alias blindness found in an invariant test
+  earlier this week.
+- `tsc --noEmit` exit 0; full lint chain exit 0 across 45 lints.

package/upgrades/side-effects/registry-asset-freshness.md

@@ -0,0 +1,76 @@
+# Side-effects review — registry asset freshness
+
+## The change
+
+Two vitest globalSetup files decided whether to regenerate the packed
+standards-registry asset by asking only whether its outputs EXIST. Both now share a
+`registryAssetIsStale()` helper that compares the oldest output's mtime against the
+newest input's. Test-only; no runtime surface.
+
+## Review answers
+
+1. **Over-block.** This is the dominant risk and it got the most care, because the
+   check runs at the START of every suite and an over-eager rule regenerates on every
+   run. Three conservative cases, each with its own test: equal mtimes are NOT stale;
+   no readable input is NOT stale; an empty output list is NOT stale. Measured cost of
+   a genuine regeneration is one generator invocation (~1s), and it self-limits — a
+   freshly written asset is newer than its inputs, so the next run skips.
+
+2. **Under-block.** mtime is a proxy for content, not content itself. A source edited
+   and reverted leaves a newer mtime and triggers one unnecessary regeneration
+   (harmless). A content-identical touch does the same. Conversely, a filesystem that
+   does not preserve mtimes, or a checkout that sets all mtimes equal, would report
+   fresh when stale. A content hash would be exact — the generator already writes a
+   `sha256` into its metadata — and that is the stronger version of this fix. NOT done
+   here: it means reading and hashing a 450KB document on every suite start, where the
+   mtime compare is four `stat` calls, and the sibling `ensureDistBuilt()` this mirrors
+   uses mtimes too. Stated rather than implied.
+
+3. **Level-of-abstraction fit.** Correct layer: the setup layer is where every test
+   file inherits the guarantee. The file's own history says this explicitly — a
+   per-file `beforeAll` bootstrap was found to be invisible to the next file that
+   needed it.
+
+4. **Signal vs authority.** Not a gate. It decides whether to run a generator; it
+   blocks nothing and rejects no input.
+
+5. **Interactions.** `ensureRegistryAsset()` must still run AFTER `ensureDistBuilt()`
+   (the generator imports from `dist/`). Unchanged — only the early-return predicate
+   moved. The exported `ensureRegistryAsset(root)` keeps its signature, so the
+   production-generator parity ratchet that imports it is unaffected.
+
+6. **External surfaces.** None. Test setup only; nothing ships to an agent or a user.
+
+7. **Multi-machine posture.** Machine-local BY DESIGN — a per-checkout build artifact.
+   There is nothing to replicate: each checkout generates its own copy, and the whole
+   defect was one checkout trusting its own stale copy.
+
+8. **Rollback cost.** Revert the commit. The helper is additive; the two call sites
+   return to a presence check.
+
+## Class closure — what this does NOT close
+
+- **Only these two sites.** A sweep of `tests/setup/` and `scripts/` for
+  regenerate-on-presence guards found exactly these two making a regeneration decision
+  on existence alone; the other `existsSync` hits are ordinary existence guards, not
+  regeneration decisions. The wiring test pins both and fails if either drifts, but it
+  knows only about setups that generate THIS asset.
+- **`src/data/builtin-manifest.json`** is named in the generator's own comment as
+  having a related defect (generated only into `src/data/` while its reader resolves
+  module-relative from `dist/data/`). Different feature, different defect, untouched.
+- **mtime is not content** — see review answer 2.
+
+## Evidence
+
+- `tests/unit/registry-asset-freshness.test.ts` — 9/9 green.
+- Negative controls, BOTH fired and both restored byte-exact: reverting the comparison
+  fails THE DEFECT case (1 failed / 8 passed — the 8 passing are the controls, which is
+  what makes them controls); reverting one call site to the presence check fails the
+  wiring case and names the file.
+- Observed live: running the new test in a fresh checkout regenerated the asset
+  ("88 articles → src/data + dist/data"). Under the presence check it would have
+  skipped, because the outputs existed.
+- The originating measurement: three test files / eight assertions failing against a
+  three-hour-stale asset; regeneration alone made all 77 pass.
+- `tsc --noEmit` exit 0 (run via the real binary — `npx tsc` here is intercepted by a
+  shim that exits 0 without typechecking). Full lint chain exit 0 across 45 lints.