instar 1.3.868 → 1.3.869

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "instar",
-  "version": "1.3.868",
+  "version": "1.3.869",
   "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-07-18T07:34:42.051Z",
-  "instarVersion": "1.3.868",
+  "generatedAt": "2026-07-18T08:42:34.064Z",
+  "instarVersion": "1.3.869",
   "entryCount": 202,
   "entries": {
     "hook:session-start": {

package/upgrades/1.3.869.md

@@ -0,0 +1,36 @@
+# Upgrade Guide — vNEXT
+
+<!-- assembled-by: assemble-next-md -->
+<!-- bump: patch -->
+
+## What Changed
+
+- Added `docs/apprenticeship/PROGRAM-CONCEPTS.md` — the canonical statement of the
+  apprenticeship program's four operator-ratified concepts (mutual substrate
+  improvement; role asymmetry, not capability asymmetry; fractal role-teaching;
+  required fundamental-gap analysis on defects) plus two bounded evaluation cautions
+  (tripwires-not-targets hidden testing; multi-cycle promotion evidence). Origin:
+  operator directives, topic 29723, 2026-07-16/17 (CMT-872).
+- `docs/specs/FRAMEWORK-ONBOARDING-MENTOR-SPEC.md`: the §13.1 issue schema gains three
+  REQUIRED fields — `rootGapInfrastructure`, `rootGapSentinel`
+  (failing | missing | neither-unpromoted), `rootGapStandard` — and a new §13.9
+  defining the write-time requirement: a defect record without root-gap analysis is
+  refused, like a record without a bucket.
+
+## What to Tell Your User
+
+None — internal change (no user-facing surface).
+
+## Summary of New Capabilities
+
+None — internal change (no user-facing surface).
+
+## Evidence
+
+- Docs-only diff: `docs/apprenticeship/PROGRAM-CONCEPTS.md` (new),
+  `docs/specs/FRAMEWORK-ONBOARDING-MENTOR-SPEC.md` (schema + §13.9),
+  ELI16 at `docs/specs/cmt872-apprenticeship-concepts.eli16.md`,
+  side-effects review at `upgrades/side-effects/cmt872-apprenticeship-concepts.md`.
+- The three-question analysis is already applied live in apprenticeship drive 5's
+  defect matrix (defects #9, #10, #11) — this lands the canonical documentation and
+  schema definition for it.

package/upgrades/side-effects/cmt872-apprenticeship-concepts.md

@@ -0,0 +1,49 @@
+# Side-Effects Review — cmt872-apprenticeship-concepts
+
+**Change:** documentation-only. (a) New `docs/apprenticeship/PROGRAM-CONCEPTS.md`
+(four operator-ratified apprenticeship concepts + evaluation cautions, CMT-872).
+(b) `docs/specs/FRAMEWORK-ONBOARDING-MENTOR-SPEC.md`: three REQUIRED `rootGap*`
+fields added to the §13.1 issue schema + new §13.9 explaining the requirement.
+No runtime code, no tests, no templates, no hooks.
+
+## Phase 1 principle check
+
+Does this change involve a decision point (gates information flow, blocks actions,
+filters messages, constrains agent behavior)? **No.** It is prose: a concepts page and
+a spec schema amendment. The write-time validation §13.9 describes will be a future
+build of the (staged, off-by-default) mentor loop; this commit changes no executable
+path. Signal-vs-authority is not implicated — documentation carries no authority.
+
+## The eight questions
+
+1. **Over-block** — No issue identified. Nothing executable changes; nothing can
+   reject any input.
+2. **Under-block** — No issue identified (nothing enforces yet). Named residual: until
+   the mentor-loop build implements §13.9 validation, the rootGap requirement binds
+   drive practice by convention (already live in drive 5's matrix) rather than by code.
+   That build is governed by the mentor spec's own staged rollout.
+3. **Level-of-abstraction fit** — Correct layer. Concepts page lives in
+   `docs/apprenticeship/` beside RETRO-HARVEST-PROCEDURE.md; the schema change lives in
+   the spec that owns the issue ledger. The drive-workspace matrix template mirrors the
+   same three questions, so judgment structure exists at both layers (program docs +
+   ledger schema).
+4. **Signal vs authority** — Compliant; no authority exists in this change. When built,
+   rootGap validation is a write-time completeness check on a ledger record (like the
+   existing bucket allowlist), not a behavioral gate.
+5. **Interactions** — The mentor spec is converged+approved (2026-05-27). This amends
+   its schema section additively; no existing field is renamed or removed, so no
+   consumer (none built yet for these fields) breaks. §13.8 (Concurrency) numbering is
+   untouched; the new section is §13.9. The concepts page references the spec and vice
+   versa — both references verified present in this diff.
+6. **External surfaces** — None. No user-visible runtime surface, no other-agent
+   surface. The docs ship in the npm package as before.
+7. **Multi-machine posture** — Machine-local BY DESIGN in the trivial sense: these are
+   git-tracked repo docs, identical on every machine via the release; no runtime state,
+   no replication path needed, nothing strands on topic transfer, no URLs generated.
+8. **Rollback cost** — Trivial: revert the docs commit. No data migration, no agent
+   state, no hot-fix pressure.
+
+## Conclusion
+
+Documentation-only, no runtime surface. Tier 1 declared: small, low-risk, records
+operator decisions already made 2026-07-17.