instar 1.3.1049 → 1.3.1050

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

@@ -2,5 +2,5 @@
   "sha256": "b75c147afd1f5a9843ca4eac372159f3623f24731fe63b2f59e48043ae488af9",
   "articleCount": 82,
   "generatedFrom": "docs/STANDARDS-REGISTRY.md",
-  "packageVersion": "1.3.1049"
+  "packageVersion": "1.3.1050"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "instar",
-  "version": "1.3.1049",
+  "version": "1.3.1050",
   "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/scripts/instar-dev-precommit.js

@@ -252,14 +252,14 @@ if (bootstrapTrigger) {
 
 let tierSignal = { suggestedTier: 2, sizeTier: 2, riskFloor: 1, reasons: [] };
 let totalChangedLoc = 0;
+let addedLines = 0;
+let deletedLines = 0;
 // Hoisted to module scope (docs/specs/self-action-convergence.md → E3 impl
 // note): addedDiffText is computed in the Step-3.5 block but consumed later by
 // assertSelfActionDeclared at BOTH the enforceTier1 and Tier-2 pass-through call
 // sites. It must outlive the block.
 let addedDiffText = '';
 {
-  let addedLines = 0;
-  let deletedLines = 0;
   try {
     const numstat = execSync(
       `git diff --cached --numstat -- ${inScopeFiles.map((f) => JSON.stringify(f)).join(' ')}`,
@@ -441,6 +441,9 @@ const decisionEntryPath = writeDecisionAudit({
   belowFloor,
   files: inScopeFiles.length,
   loc: totalChangedLoc,
+  scopeFiles: inScopeFiles,
+  addedLines,
+  deletedLines,
   causalAutopsy,
   classClosure: (freshestTrace && typeof freshestTrace.classClosure === 'object' && freshestTrace.classClosure) || null,
 });
@@ -1356,7 +1359,7 @@ function blockCommit(files, reason) {
 // fire, the line just evaporated with the worktree). If the commit is later
 // blocked by the gate, the staged line simply rides the retry commit — both
 // lines describe real gate evaluations.
-function writeDecisionAudit({ slug, suggestedTier, declaredTier, riskFloor, riskFloorReasons, belowFloor, files, loc, causalAutopsy = null, classClosure = null }) {
+function writeDecisionAudit({ slug, suggestedTier, declaredTier, riskFloor, riskFloorReasons, belowFloor, files, loc, scopeFiles, addedLines, deletedLines, causalAutopsy = null, classClosure = null }) {
   try {
     fs.mkdirSync(DECISIONS_DIR, { recursive: true });
     const ts = new Date().toISOString();
@@ -1382,6 +1385,12 @@ function writeDecisionAudit({ slug, suggestedTier, declaredTier, riskFloor, risk
       belowFloor,
       files,
       loc,
+      scope: {
+        basis: 'staged-in-scope-additions-plus-deletions',
+        files: scopeFiles,
+        addedLines,
+        deletedLines,
+      },
       // Causal autopsy (directive 2026-06-05): what caused the issue this
       // commit fixes — prior-pr / environment-shift / new-code / latent /
       // unknown, with linked PRs. null = not declared (advisory in slice 1).

package/src/data/builtin-manifest.json

@@ -1,8 +1,8 @@
 {
   "$schema": "./builtin-manifest.schema.json",
   "schemaVersion": 1,
-  "generatedAt": "2026-07-29T10:16:28.309Z",
-  "instarVersion": "1.3.1049",
+  "generatedAt": "2026-07-29T10:34:17.724Z",
+  "instarVersion": "1.3.1050",
   "entryCount": 202,
   "entries": {
     "hook:session-start": {

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

@@ -2,5 +2,5 @@
   "sha256": "b75c147afd1f5a9843ca4eac372159f3623f24731fe63b2f59e48043ae488af9",
   "articleCount": 82,
   "generatedFrom": "docs/STANDARDS-REGISTRY.md",
-  "packageVersion": "1.3.1049"
+  "packageVersion": "1.3.1050"
 }

package/upgrades/1.3.1050.md

@@ -0,0 +1,25 @@
+# Upgrade Guide — vNEXT
+
+<!-- assembled-by: assemble-next-md -->
+<!-- bump: patch -->
+
+## What Changed
+
+Development decision records now retain the exact staged source files and
+added/deleted-line counts behind their compact file and line totals.
+
+## What to Tell Your User
+
+Internal development audit records now explain exactly what their size
+counters measured.
+
+## Summary of New Capabilities
+
+- Self-describing scope evidence for development decisions.
+
+## Evidence
+
+- The focused hook integration test verifies the persisted counting basis,
+  file list, additions, and deletions.
+- Existing compact `files` and `loc` fields remain unchanged for compatible
+  readers.

package/upgrades/decision-audit-scope.eli16.md

@@ -0,0 +1,23 @@
+# Decision records now explain what their counters measured
+
+The development commit gate already records two compact numbers for each
+reviewed source change: how many source files were in scope and how many lines
+changed. Those numbers are useful, but the record did not retain the concrete
+file list or say whether the line count represented additions, deletions, or a
+different basis. A later reader could see “three files, eighteen lines” without
+being able to tell which files produced that result.
+
+The gate now stores an additional `scope` object beside the existing counters.
+It names the counting basis, lists the exact staged source files included, and
+records added and deleted lines separately. The old `files` and `loc` fields
+remain unchanged, so existing readers continue to work.
+
+The new values come from the same staged-diff calculation the gate already
+uses for tier signaling. There is no second calculation that can disagree with
+the original counters. If that existing calculation cannot run, the gate keeps
+its current fail-open behavior and records the same zero counts explicitly.
+
+This changes evidence only. It does not change which files require review,
+which tier is suggested, which trace is selected, or whether a commit passes.
+A focused integration test runs the real hook in a temporary repository and
+asserts the emitted record’s basis, file list, additions, and deletions.

package/upgrades/side-effects/decision-audit-scope.md

@@ -0,0 +1,73 @@
+# Side-Effects Review — development decision audit scope
+
+**Version / slug:** `decision-audit-scope`
+**Date:** 2026-07-29
+**Author:** Instar Agent (instar-codey)
+
+## Summary
+
+The development pre-commit gate now persists the exact in-scope staged file
+list, added-line count, deleted-line count, and named counting basis beside
+each decision record’s existing compact `files` and `loc` counters.
+
+## Decision-point inventory
+
+This changes evidence emitted by an existing gate, not its authority. Tier
+classification, trace selection, refusal conditions, and verdict finalization
+remain unchanged.
+
+## 1. Over-block
+
+No new refusal is introduced. Audit writing remains best-effort and fail-open,
+as before. The additive fields cannot prevent a commit.
+
+## 2. Under-block
+
+The record still reflects only files covered by the gate’s existing `inScope`
+predicate, not every file in the pull request. That boundary is now explicit
+in the `staged-in-scope-additions-plus-deletions` basis and concrete file list,
+rather than hidden behind a compact count. Removing the emitted object made the
+focused assertion fail before the implementation was restored, proving the
+test does not merely restate its own derivation.
+
+## 3. Level-of-abstraction fit
+
+The audit writer is the correct owner because it already receives the tier
+signal and writes the durable decision record. The added values reuse the
+same staged `numstat` calculation rather than asking downstream consumers to
+reconstruct a vanished diff.
+
+## 4. Signal vs authority compliance
+
+Compliant with `docs/signal-vs-authority.md`. The scope fields are evidence
+only. They add no detector, filter, or blocking authority and do not alter the
+gate’s verdict.
+
+## 5. Interactions
+
+Existing consumers retain the unchanged `files` and `loc` fields. New
+consumers can inspect `scope`. The values are captured before any gate exit and
+therefore accompany both passing and blocked decision records through the
+existing verdict-finalization path.
+
+## 6. External surfaces
+
+Internal decision JSON gains one additive object. No runtime API, user-facing
+message, configuration, credential, or operator action changes.
+
+## 7. Multi-machine posture
+
+Repository-replicated evidence. Decision records already ride the commit as
+distinct files, so the new fields follow the same Git replication path and do
+not introduce machine-local state or cross-machine authority.
+
+## 8. Rollback cost
+
+A direct revert removes the additive fields. Records already written with
+`scope` remain readable by older consumers because they ignore unknown keys.
+No migration or state repair is required.
+
+## Conclusion
+
+The change makes existing gate evidence interpretable without changing what
+the gate decides.