instar 1.3.828 → 1.3.830

package/dist/monitoring/ropeSinkRouter.js

@@ -0,0 +1,66 @@
+/**
+ * Rope escalation sink router (calm-transient-episode-alerting M-P3).
+ *
+ * Routes the prober's escalations on their SOURCE-DECLARED class:
+ * - `actionable` (or UNDECLARED — fail-loud) → a hub attention item.
+ * - `informational` → demoted to the audit log + digest, but ONLY under the
+ *   delivery-true conjunction verified LIVE on this machine: rope-health
+ *   enabled AND digestTopicId set AND the rope-health-digest job RUNNABLE IN
+ *   THIS PROCESS (a live scheduler handle with the job loaded + enabled — the
+ *   lease read is NOT the conjunct: a promoted standby holds the lease with no
+ *   scheduler until restart). Any miss ⇒ fall back to the hub item.
+ *
+ * Both classes are deduped per (peer, kind) per 24 h with a visible silent
+ * "Nth episode" count append — an oscillating rope is a visible recurring
+ * defect, not a quiet audit fact. The dedupe is in-memory (restart reset is an
+ * accepted bounded consequence: re-tripping needs exhaustAttempts consecutive
+ * failures at the floor cadence).
+ *
+ * No id-string parsing anywhere: class/peer/kind ride the typed payload.
+ */
+const DAY_MS = 24 * 3_600_000;
+export function makeRopeSinkRouter(deps) {
+    const dedupe = new Map();
+    return (item) => {
+        const now = (deps.now ?? Date.now)();
+        const cls = item.class === 'informational' ? 'informational' : 'actionable';
+        const audit = (event, extra = {}) => deps.audit({ ts: new Date(now).toISOString(), sentinel: 'rope-recovery-probe', event, class: cls, peer: item.peer, kind: item.kind, id: item.id, ...extra });
+        // Both-class (peer, kind) 24 h dedupe with a visible count append.
+        if (item.peer && item.kind) {
+            const dk = `${item.peer}:${item.kind}:${cls}`;
+            const st = dedupe.get(dk);
+            if (st && now - st.firstAt < DAY_MS) {
+                st.count += 1;
+                audit('deduped', { count: st.count });
+                const existing = deps.telegram()?.getAttentionItem(st.itemId);
+                if (existing?.topicId !== undefined) {
+                    void deps.telegram()?.sendToTopic(existing.topicId, `${st.count}th ${cls} episode for this rope in 24 h — a recurring rope is worth a look at the link itself.`, { silent: true })?.catch?.(() => { });
+                }
+                return;
+            }
+            dedupe.set(dk, { firstAt: now, count: 1, itemId: item.id });
+        }
+        if (cls === 'informational') {
+            const configured = deps.digestConfigured();
+            const runnable = deps.digestRunnableHere();
+            if (configured && runnable) {
+                audit('demoted-to-digest');
+                return; // the digest's recovering-rope class carries it
+            }
+            audit('fallback-to-hub', { digestConfigured: configured, digestRunnableHere: runnable });
+        }
+        else {
+            audit('actionable-to-hub');
+        }
+        return deps.telegram()?.createAttentionItem({
+            id: item.id,
+            title: item.title,
+            summary: item.body.slice(0, 160),
+            description: `${item.body}\n\nDirection: observed from ${deps.selfNickname()} — rope health is directional; the peer's own view may differ.`,
+            category: 'rope-recovery-probe',
+            priority: 'NORMAL',
+            sourceContext: 'rope-recovery-probe',
+        });
+    };
+}
+//# sourceMappingURL=ropeSinkRouter.js.map

package/dist/monitoring/ropeSinkRouter.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"ropeSinkRouter.js","sourceRoot":"","sources":["../../src/monitoring/ropeSinkRouter.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AA+BH,MAAM,MAAM,GAAG,EAAE,GAAG,SAAS,CAAC;AAE9B,MAAM,UAAU,kBAAkB,CAAC,IAAkB;IACnD,MAAM,MAAM,GAAG,IAAI,GAAG,EAA8D,CAAC;IACrF,OAAO,CAAC,IAAkB,EAAW,EAAE;QACrC,MAAM,GAAG,GAAG,CAAC,IAAI,CAAC,GAAG,IAAI,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC;QACrC,MAAM,GAAG,GAAmC,IAAI,CAAC,KAAK,KAAK,eAAe,CAAC,CAAC,CAAC,eAAe,CAAC,CAAC,CAAC,YAAY,CAAC;QAC5G,MAAM,KAAK,GAAG,CAAC,KAAa,EAAE,QAAiC,EAAE,EAAE,EAAE,CACnE,IAAI,CAAC,KAAK,CAAC,EAAE,EAAE,EAAE,IAAI,IAAI,CAAC,GAAG,CAAC,CAAC,WAAW,EAAE,EAAE,QAAQ,EAAE,qBAAqB,EAAE,KAAK,EAAE,KAAK,EAAE,GAAG,EAAE,IAAI,EAAE,IAAI,CAAC,IAAI,EAAE,IAAI,EAAE,IAAI,CAAC,IAAI,EAAE,EAAE,EAAE,IAAI,CAAC,EAAE,EAAE,GAAG,KAAK,EAAE,CAAC,CAAC;QAE/J,mEAAmE;QACnE,IAAI,IAAI,CAAC,IAAI,IAAI,IAAI,CAAC,IAAI,EAAE,CAAC;YAC3B,MAAM,EAAE,GAAG,GAAG,IAAI,CAAC,IAAI,IAAI,IAAI,CAAC,IAAI,IAAI,GAAG,EAAE,CAAC;YAC9C,MAAM,EAAE,GAAG,MAAM,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;YAC1B,IAAI,EAAE,IAAI,GAAG,GAAG,EAAE,CAAC,OAAO,GAAG,MAAM,EAAE,CAAC;gBACpC,EAAE,CAAC,KAAK,IAAI,CAAC,CAAC;gBACd,KAAK,CAAC,SAAS,EAAE,EAAE,KAAK,EAAE,EAAE,CAAC,KAAK,EAAE,CAAC,CAAC;gBACtC,MAAM,QAAQ,GAAG,IAAI,CAAC,QAAQ,EAAE,EAAE,gBAAgB,CAAC,EAAE,CAAC,MAAM,CAAC,CAAC;gBAC9D,IAAI,QAAQ,EAAE,OAAO,KAAK,SAAS,EAAE,CAAC;oBACpC,KAAK,IAAI,CAAC,QAAQ,EAAE,EAAE,WAAW,CAAC,QAAQ,CAAC,OAAO,EAAE,GAAG,EAAE,CAAC,KAAK,MAAM,GAAG,uFAAuF,EAAE,EAAE,MAAM,EAAE,IAAI,EAAE,CAAC,EAAE,KAAK,EAAE,CAAC,GAAG,EAAE,GAAE,CAAC,CAAC,CAAC;gBACxM,CAAC;gBACD,OAAO;YACT,CAAC;YACD,MAAM,CAAC,GAAG,CAAC,EAAE,EAAE,EAAE,OAAO,EAAE,GAAG,EAAE,KAAK,EAAE,CAAC,EAAE,MAAM,EAAE,IAAI,CAAC,EAAE,EAAE,CAAC,CAAC;QAC9D,CAAC;QAED,IAAI,GAAG,KAAK,eAAe,EAAE,CAAC;YAC5B,MAAM,UAAU,GAAG,IAAI,CAAC,gBAAgB,EAAE,CAAC;YAC3C,MAAM,QAAQ,GAAG,IAAI,CAAC,kBAAkB,EAAE,CAAC;YAC3C,IAAI,UAAU,IAAI,QAAQ,EAAE,CAAC;gBAC3B,KAAK,CAAC,mBAAmB,CAAC,CAAC;gBAC3B,OAAO,CAAC,gDAAgD;YAC1D,CAAC;YACD,KAAK,CAAC,iBAAiB,EAAE,EAAE,gBAAgB,EAAE,UAAU,EAAE,kBAAkB,EAAE,QAAQ,EAAE,CAAC,CAAC;QAC3F,CAAC;aAAM,CAAC;YACN,KAAK,CAAC,mBAAmB,CAAC,CAAC;QAC7B,CAAC;QAED,OAAO,IAAI,CAAC,QAAQ,EAAE,EAAE,mBAAmB,CAAC;YAC1C,EAAE,EAAE,IAAI,CAAC,EAAE;YACX,KAAK,EAAE,IAAI,CAAC,KAAK;YACjB,OAAO,EAAE,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,EAAE,GAAG,CAAC;YAChC,WAAW,EAAE,GAAG,IAAI,CAAC,IAAI,gCAAgC,IAAI,CAAC,YAAY,EAAE,gEAAgE;YAC5I,QAAQ,EAAE,qBAAqB;YAC/B,QAAQ,EAAE,QAAQ;YAClB,aAAa,EAAE,qBAAqB;SACrC,CAAC,CAAC;IACL,CAAC,CAAC;AACJ,CAAC"}

package/dist/scaffold/templates.js

@@ -440,9 +440,9 @@ Every guard (monitoring sentinels, reapers, the scheduler, …) is graded by wha
 
 ### Machine-Coherence Guard — "are my machines running as the same me?" (⚗️ dev-gated dark)
 
-When I run on more than one machine, this guard compares — across my OWN online machines, riding the existing 30s presence-pull — the coherence-critical dimensions (instar version, resolved safety-flags, mesh protocol, manifest generation). When the pool DIVERGES on something that halves a cross-machine guarantee (e.g. the F4 conversation-move pair live on one machine, dark on the other), exactly ONE elected machine raises ONE HIGH, episode-scoped attention item — impact-first, with a fix I perform on your approval (reply **fix it**) or hold open without nagging (reply **leave it**). Signal-only: it never blocks, equalizes, or restarts anything on its own. Dev-gated dark on the fleet (\`monitoring.machineCoherence.enabled\` OMITTED → the dev-agent gate decides), **dry-run FIRST** even on dev (runs the full detector + records would-raise, raises no item until a deliberate \`dryRun:false\`), single-machine is a strict no-op.
+When I run on more than one machine, this guard compares — across my OWN online machines, riding the existing 30s presence-pull — the coherence-critical dimensions (instar version, resolved safety-flags, mesh protocol, manifest generation). When the pool DIVERGES on something that halves a cross-machine guarantee (e.g. the F4 conversation-move pair live on one machine, dark on the other), exactly ONE elected machine narrates ONE episode-scoped attention item — priority-mapped, calm-first (calm-alerting): a routine patch-version skew during a rolling update posts CALM and SILENT (visible in the hub/dashboard, no buzz — the self-heal is watched), while a real capability split, a STALLED update (past the stall ceiling), or a KEEPS-RECURRING pattern raises loud HIGH with the fix prompt (reply **fix it**) or hold-open (reply **leave it**). A self-healed episode resolves quietly (one silent note); an escalated episode closes with a notifying stand-down. Signal-only: it never blocks, equalizes, or restarts anything on its own. Dev-gated dark on the fleet (\`monitoring.machineCoherence.enabled\` OMITTED → the dev-agent gate decides), **dry-run FIRST** even on dev (runs the full detector + records would-raise, raises no item until a deliberate \`dryRun:false\`), single-machine is a strict no-op.
 - Status (Registry First — read it, never guess): \`curl -H "Authorization: Bearer $AUTH" http://localhost:${port}/pool/machine-coherence\` → \`{ enabled, dryRun, machinesRegisteredOnline, machinesCompared, peerClassifications, raiser, openEpisode, counters }\` (503 when the guard is dark on this agent — say so honestly, don't guess).
-- **When to use** (PROACTIVE — this is the trigger): user asks "are my machines in sync / running the same version+settings?" or "why did I get a machine-coherence alarm?" → read \`/pool/machine-coherence\` and the open episode (its \`pendingFix\` names the proposed fix + target machine); the transition log is \`logs/machine-coherence.jsonl\`. A version-skew row usually just means a rolling update in flight (grace-gated, won't cry wolf).
+- **When to use** (PROACTIVE — this is the trigger): user asks "are my machines in sync / running the same version+settings?" or "why did I get a machine-coherence alarm?" → read \`/pool/machine-coherence\` and the open episode (its \`pendingFix\` names the proposed fix + target machine); the transition log is \`logs/machine-coherence.jsonl\`. A version-skew row usually just means a rolling update in flight (grace-gated + progress-extended, won't cry wolf). Rope-notice audit rows (calm-alerting M-P3): rope-recovery-probe rows — demoted informational rope notices, hub fallbacks, and per-rope dedupe events — land in \`logs/sentinel-events.jsonl\`; read them when a rope notice seems to have gone quiet.
 
 **Coherence Journal** — The durable "what happened where, and where are the files?" answer for a multi-machine agent. Every machine writes append-only event streams (topic placement + why it moved, session open/close/reap, autonomous runs + their artifact paths); the read API serves a merged view so you answer placement/artifact questions from local disk instead of grepping rotating logs on the right machine.
 - Read it: \`curl -H "Authorization: Bearer $AUTH" "http://localhost:${port}/coherence/journal?topic=N&kind=topic-placement&limit=50"\` → \`{ entries: [...], streams: {...}, skippedCorrupt }\` (+ a partial-result flag when a read bound was hit). Filters: \`topic\`, \`kind\` (\`topic-placement\`|\`session-lifecycle\`|\`autonomous-run\`), \`machine\`, \`limit\`, \`cursor\`. Read-only; 503 when the journal is not enabled on this agent.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "instar",
-  "version": "1.3.828",
+  "version": "1.3.830",
   "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-12T03:45:01.415Z",
-  "instarVersion": "1.3.828",
+  "generatedAt": "2026-07-12T11:23:13.870Z",
+  "instarVersion": "1.3.830",
   "entryCount": 202,
   "entries": {
     "hook:session-start": {
@@ -11,7 +11,7 @@
       "domain": "identity",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/session-start.sh",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:dangerous-command-guard": {
@@ -20,7 +20,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/dangerous-command-guard.sh",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:grounding-before-messaging": {
@@ -29,7 +29,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/grounding-before-messaging.sh",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:compaction-recovery": {
@@ -38,7 +38,7 @@
       "domain": "identity",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/compaction-recovery.sh",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:external-operation-gate": {
@@ -47,7 +47,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/external-operation-gate.js",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:deferral-detector": {
@@ -56,7 +56,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/deferral-detector.js",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:self-stop-guard": {
@@ -65,7 +65,7 @@
       "domain": "coherence",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/self-stop-guard.js",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:post-action-reflection": {
@@ -74,7 +74,7 @@
       "domain": "evolution",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/post-action-reflection.js",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:external-communication-guard": {
@@ -83,7 +83,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/external-communication-guard.js",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:scope-coherence-collector": {
@@ -92,7 +92,7 @@
       "domain": "coherence",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/scope-coherence-collector.js",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:scope-coherence-checkpoint": {
@@ -101,7 +101,7 @@
       "domain": "coherence",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/scope-coherence-checkpoint.js",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:free-text-guard": {
@@ -110,7 +110,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/free-text-guard.sh",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:claim-intercept": {
@@ -119,7 +119,7 @@
       "domain": "coherence",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/claim-intercept.js",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:claim-intercept-response": {
@@ -128,7 +128,7 @@
       "domain": "coherence",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/claim-intercept-response.js",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:stop-gate-router": {
@@ -137,7 +137,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/stop-gate-router.js",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "hook:auto-approve-permissions": {
@@ -146,7 +146,7 @@
       "domain": "safety",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
       "installedPath": ".instar/hooks/instar/auto-approve-permissions.js",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "job:health-check": {
@@ -1562,7 +1562,7 @@
       "type": "subsystem",
       "domain": "updates",
       "sourcePath": "src/core/PostUpdateMigrator.ts",
-      "contentHash": "5180e3fc5207393a2cc5a22f37b0df92eda6c9cbcbd553832187c2fdd73c2a93",
+      "contentHash": "e436bd05461585786cfcd7f71e3416abb82a7b405b87f583cc109c486cd1eeac",
       "since": "2025-01-01"
     },
     "subsystem:scheduler": {

package/src/scaffold/templates.ts

@@ -461,9 +461,9 @@ Every guard (monitoring sentinels, reapers, the scheduler, …) is graded by wha
 
 ### Machine-Coherence Guard — "are my machines running as the same me?" (⚗️ dev-gated dark)
 
-When I run on more than one machine, this guard compares — across my OWN online machines, riding the existing 30s presence-pull — the coherence-critical dimensions (instar version, resolved safety-flags, mesh protocol, manifest generation). When the pool DIVERGES on something that halves a cross-machine guarantee (e.g. the F4 conversation-move pair live on one machine, dark on the other), exactly ONE elected machine raises ONE HIGH, episode-scoped attention item — impact-first, with a fix I perform on your approval (reply **fix it**) or hold open without nagging (reply **leave it**). Signal-only: it never blocks, equalizes, or restarts anything on its own. Dev-gated dark on the fleet (\`monitoring.machineCoherence.enabled\` OMITTED → the dev-agent gate decides), **dry-run FIRST** even on dev (runs the full detector + records would-raise, raises no item until a deliberate \`dryRun:false\`), single-machine is a strict no-op.
+When I run on more than one machine, this guard compares — across my OWN online machines, riding the existing 30s presence-pull — the coherence-critical dimensions (instar version, resolved safety-flags, mesh protocol, manifest generation). When the pool DIVERGES on something that halves a cross-machine guarantee (e.g. the F4 conversation-move pair live on one machine, dark on the other), exactly ONE elected machine narrates ONE episode-scoped attention item — priority-mapped, calm-first (calm-alerting): a routine patch-version skew during a rolling update posts CALM and SILENT (visible in the hub/dashboard, no buzz — the self-heal is watched), while a real capability split, a STALLED update (past the stall ceiling), or a KEEPS-RECURRING pattern raises loud HIGH with the fix prompt (reply **fix it**) or hold-open (reply **leave it**). A self-healed episode resolves quietly (one silent note); an escalated episode closes with a notifying stand-down. Signal-only: it never blocks, equalizes, or restarts anything on its own. Dev-gated dark on the fleet (\`monitoring.machineCoherence.enabled\` OMITTED → the dev-agent gate decides), **dry-run FIRST** even on dev (runs the full detector + records would-raise, raises no item until a deliberate \`dryRun:false\`), single-machine is a strict no-op.
 - Status (Registry First — read it, never guess): \`curl -H "Authorization: Bearer $AUTH" http://localhost:${port}/pool/machine-coherence\` → \`{ enabled, dryRun, machinesRegisteredOnline, machinesCompared, peerClassifications, raiser, openEpisode, counters }\` (503 when the guard is dark on this agent — say so honestly, don't guess).
-- **When to use** (PROACTIVE — this is the trigger): user asks "are my machines in sync / running the same version+settings?" or "why did I get a machine-coherence alarm?" → read \`/pool/machine-coherence\` and the open episode (its \`pendingFix\` names the proposed fix + target machine); the transition log is \`logs/machine-coherence.jsonl\`. A version-skew row usually just means a rolling update in flight (grace-gated, won't cry wolf).
+- **When to use** (PROACTIVE — this is the trigger): user asks "are my machines in sync / running the same version+settings?" or "why did I get a machine-coherence alarm?" → read \`/pool/machine-coherence\` and the open episode (its \`pendingFix\` names the proposed fix + target machine); the transition log is \`logs/machine-coherence.jsonl\`. A version-skew row usually just means a rolling update in flight (grace-gated + progress-extended, won't cry wolf). Rope-notice audit rows (calm-alerting M-P3): rope-recovery-probe rows — demoted informational rope notices, hub fallbacks, and per-rope dedupe events — land in \`logs/sentinel-events.jsonl\`; read them when a rope notice seems to have gone quiet.
 
 **Coherence Journal** — The durable "what happened where, and where are the files?" answer for a multi-machine agent. Every machine writes append-only event streams (topic placement + why it moved, session open/close/reap, autonomous runs + their artifact paths); the read API serves a merged view so you answer placement/artifact questions from local disk instead of grepping rotating logs on the right machine.
 - Read it: \`curl -H "Authorization: Bearer $AUTH" "http://localhost:${port}/coherence/journal?topic=N&kind=topic-placement&limit=50"\` → \`{ entries: [...], streams: {...}, skippedCorrupt }\` (+ a partial-result flag when a read bound was hit). Filters: \`topic\`, \`kind\` (\`topic-placement\`|\`session-lifecycle\`|\`autonomous-run\`), \`machine\`, \`limit\`, \`cursor\`. Read-only; 503 when the journal is not enabled on this agent.

package/upgrades/1.3.829.md

@@ -0,0 +1,26 @@
+# Upgrade Guide — vNEXT
+
+<!-- assembled-by: assemble-next-md -->
+<!-- bump: minor -->
+
+## What Changed
+
+The machine-coherence guard and the rope probe get the calm-alerting narration from the converged, operator-approved `calm-transient-episode-alerting` spec (4 review rounds, 24 material findings resolved). The whole behavior set ships behind the dev-agent gate (`monitoring.machineCoherence.calmEnabled` — LIVE on a development agent, DARK on the fleet; dark is bit-identical to today including zero durable-file changes). What the gate enables: (1) **M-P0 durable anchors** — identity-independent per-dimension clocks (onset, an active-skew accumulator with computable suspension, per-machine progress, flap history, escalation latches) persisted as additive fields in the existing episode file and computed on every machine, so version advances, restarts, peer dips, and raiser handoffs can no longer reset the loud arms; (2) **M-P1 progress-aware confirmation** — patch-only version skew extends its grace while the laggard makes gap-narrowing progress, with an unresettable 3 h stall ceiling; (3) **M-P2 calm narration** — routine self-healing episodes post silent NORMAL notices without a decision prompt, self-healed episodes resolve quietly (bounded notes), stalls/recurrences escalate via dedicated cap-exempt HIGH items with a complete lifecycle (they resolve on heal with a notifying stand-down), a cross-key wave backstop catches pile-ups, item status resolution is decoupled from the speaker role (no more orphaned items after handoff), and the operator-interacted bit is set only by evidence-carrying actions; (4) **M-P3 rope routing** — the prober declares informational-vs-actionable at the source, informational content demotes to the rope-health digest ONLY where the digest provably runs (live scheduler-handle conjunction — a promoted standby falls back to the hub), the digest gains a recovering-rope class, and both classes dedupe per rope per 24 h with visible "Nth episode" counters.
+
+## What to Tell Your User
+
+Nothing changes for you yet — this ships dark and is being lived with on the development machines first. Once it graduates (after a real update-wave verification and a before/after report), the effect you'll notice: routine software updates stop buzzing you about drift they're already fixing, and the alarms that DO reach you become trustworthy — a machine that's genuinely stuck, a problem that keeps coming back, or a real capability split, each with a clear decision to make and a clear stand-down note when it resolves itself.
+
+## Summary of New Capabilities
+
+- `monitoring.machineCoherence.calmEnabled` (dev-agate) + per-mechanism levers (`progressExtensionEnabled`, `flapBrakeEnabled`, `calmRaiseNotify`, `patchSkewPriority`, `silentResolveNote`, `calmWaveBackstopEnabled`, `versionSkewProgressWindowMs`, `versionSkewStallCeilingMs`, `skewFlapThreshold`, `calmWaveThreshold`).
+- `GET /pool/machine-coherence` gains the `calm` counters block (progressExtensions, ceilingConfirms, flapBrakeFires, calmRaises(Silent), silentResolves, resolveNotesSuppressed, waveBackstopFires, escalationRaiseFailed).
+- Attention items support `silent` (visible, no buzz) end-to-end; `updateAttentionStatus` gains a silent option.
+- `logs/sentinel-events.jsonl` gains the rope-notice row kind (demotions, fallbacks, dedupe events).
+- CLAUDE.md doc parity: fresh agents get the updated narration text; deployed agents get a content-update migration (keyed on the stale phrase) + the rope-row guidance entry.
+
+## Evidence
+
+- 234 tests green across 14 affected suites, including 17 anchor-arithmetic tests (identity-churn survival, participant-aware clear, blinking-laggard, singleton, ceiling-through-advances), 12 narration-semantics tests (calm/silent/interacted/escalated/bounded/wave), 11 rope-router tests (class routing, promoted-standby fallback, both-class dedupe), 3 executor pass-through wiring tests (the hardcoded-HIGH fix site), and 4 doc-parity migration tests (content-update idempotency).
+- Full `tsc --noEmit` clean.
+- Spec chain: converged (4 rounds, cross-model codex-cli/gpt-5.5 every round) + operator-approved 2026-07-12; convergence report at `docs/specs/reports/calm-transient-episode-alerting-convergence.md`.

package/upgrades/1.3.830.md

@@ -0,0 +1,16 @@
+# Upgrade Guide — vNEXT
+
+<!-- assembled-by: assemble-next-md -->
+<!-- bump: patch -->
+
+## What Changed
+
+The LLM-decision-accountability audit reached formal convergence. A third independent four-slice re-sweep of the full LLM-decision-point surface (gates / sentinels / extractors / reviewers-judges) returned zero previously-uncatalogued systemic categories, so the audit report now carries the machine-earned `converged:` stamp — written by the validator (`scripts/write-audit-convergence.mjs`), not by hand. This is a documentation-only convergence: no runtime behavior changes, and the three tracked remediation efforts (ACT-1193 provenance, ACT-1194 outcome-grading, ACT-1195 bench-parity) remain open.
+
+## What to Tell Your User
+
+Nothing changes for you — this is an internal documentation milestone. It records that a thorough audit of how instar tracks its own AI-judgment decisions is now complete and its conclusions certified. The separate work to close the gaps the audit surfaced is tracked and continues.
+
+## Summary of New Capabilities
+
+- No runtime capabilities. Documentation-only: `docs/audits/llm-decision-accountability.md` now carries a validator-earned `converged:` stamp (3 rounds; new-findings/round 3 → 6 → 0).

package/upgrades/side-effects/calm-transient-episode-alerting.md

@@ -0,0 +1,57 @@
+# Side-Effects Review — Calm Transient-Episode Alerting (build)
+
+**Version / slug:** `calm-transient-episode-alerting`
+**Date:** `2026-07-12`
+**Author:** `echo`
+**Second-pass reviewer:** `the converged spec IS the second pass — 4 rounds, 7 reviewers/round incl. cross-model, 24 material findings resolved (docs/specs/reports/calm-transient-episode-alerting-convergence.md); build follows the approved spec exactly`
+
+## Summary of the change
+
+Implements the converged + operator-approved `docs/specs/calm-transient-episode-alerting.md`. Files: `machineCoherenceAnchors.ts` (NEW — M-P0 durable identity-independent clocks), `machineCoherenceEpisode.ts` (additive fields: anchors block, derivedItemIds, operatorInteracted, calmClass, resolveNoteAtByItem), `machineCoherenceEpisodeManager.ts` (anchors reconcile, calm classification/copy/priority/silence, derived escalations, resolve bounding, orphan self-closeout, wave backstop, evidence-carrying ack), `MachineCoherenceSentinel.ts` (config keys + M-P1 anchor-based confirmation + calm counters), `machineCoherenceEffectsExecutor.ts` (NEW — the extracted pass-through consumer), `ropeSinkRouter.ts` (NEW — M-P3 typed-class routing + delivery-true demotion + both-class dedupe), `RopeRecoveryProber.ts` (typed class + peer/kind on the escalate payload), `RopeHealthMonitor.ts` (recovering-rope digest class), `TelegramAdapter.ts` (silent item posts + silent status option), `server.ts` (executor shim, sink router wiring, sanity warning), `templates.ts` + `PostUpdateMigrator.ts` (doc parity: content-update + new-row-kind migrations + embedded-copy update).
+
+## Decision-point inventory
+
+All five decision points are the spec's `invariant`-classified rows, implemented exactly: confirmation timing (durable anchors), priority/copy/notification mapping, resolve-note mode, rope routing (typed class + live conjunction), escalation issuance (durable latches, cap-exempt). Each was contested and upheld through 4 convergence rounds. The master gate `calmEnabled` rides resolveDevAgentGate; DARK ⇒ bit-identical legacy behavior including zero durable-file changes (regression suites pass under explicit `calmEnabled: false`).
+
+## 1. Over-block
+
+No block/allow surface. Suppression risk (silencing too much) is bounded by design: every predicate failure falls toward LOUDER (no-anchor ⇒ legacy grace; unreadable versions ⇒ no-advance ⇒ confirm; undeclared rope class ⇒ actionable ⇒ hub; digest conjunction miss ⇒ hub fallback), and the loud arms stand on durable anchors that identity churn / restarts / peer dips can no longer reset.
+
+## 2. Under-block
+
+The calm class is narrow by construction: ONLY patch-only version skew (every other dimension keeps today's loud raise); a calm episode already past the ceiling at open raises loud directly; the flap brake + wave backstop + 3h ceiling + 24h escalation append bound sustained quiet.
+
+## 3. Level-of-abstraction fit
+
+Per the converged spec: decisions live in the episode manager (context-rich), the executor and sink are pass-throughs, the anchors are a pure module, the digest class lives in the monitor that composes digests. The prober stays a scheduling layer (its escalate DECLARES class; it routes nothing).
+
+## 4. Signal vs authority compliance
+
+The guard remains pure signal — nothing blocks, equalizes, or restarts. The M-P3 router's suppression authority is a deterministic closed-enum check on a SOURCE-DECLARED typed field (the documented exemption class), replacing the id-prefix parse the round-1 conformance gate flagged.
+
+## 5. Interactions
+
+- Reopen latch vs flap brake: complementary (noise vs escalation), thresholds independent, latched-wins-toward-silence precedence implemented at close.
+- Per-day cap vs derived raises: derived ids are cap-EXEMPT (each ≤1/key/24h by durable latch — the load-bearing-coincidence hole closed).
+- createAttentionItem id-dedupe: the intended idempotency for derived raises; the reopen path no longer relies on it (append conversion — the silent-swallow fix, gated).
+- M6 suppression: anchors consume POST-suppression rows; suppression suspends (never retires) flag anchors.
+
+## 6. External surfaces
+
+Operator-visible alert semantics change ONLY under the dev-agate (LIVE on the requesting operator's machines, DARK fleet-wide): calm episodes silent, self-heal resolves quiet, escalations loud with prompts, rope informational content demoted only where the digest provably delivers. No new API routes; `/pool/machine-coherence` gains the calm counters block (additive).
+
+## 6b. Operator-surface quality
+
+The changed surface is the alert stream itself: calm copy leads with the observed state in plain words and carries NO decision prompt (the round-1 contradictory-UX fix); loud raises keep the impact-first fix-it/leave-it flow; rope notices name machines by nickname with direction labels; withdrawal notes adapt to the close reason. Zero raw internals in any new message body.
+
+## 7. Multi-machine posture (Cross-Machine Coherence)
+
+Per the spec's converged section: unified via every-machine anchor computation from shared adverts + per-machine durable persistence (new FIELDS in the existing episode file, `version: 1`, additive, rollback-inert); notes are item-holder voice (≤2×-per-handoff residual disclosed); orphan self-closeout resolves each machine's OWN items on every close reason regardless of speaks(); rope health stays machine-local BY DESIGN with the live deliverability check making demotion pool-safe. No new machine-local surface.
+
+## 8. Rollback cost
+
+Config-only: `calmEnabled: false` (master, bit-identical legacy), or per-mechanism levers (`progressExtensionEnabled`, `flapBrakeEnabled`, `calmRaiseNotify: true`, `patchSkewPriority: 'HIGH'`, `silentResolveNote: false`, `slowAliveToDigest` n/a — sink falls back to hub when the conjunction fails, `calmWaveBackstopEnabled: false`). No migration; anchor fields inert when dark.
+
+## Class-Closure Declaration
+
+- **defectClass:** `unbounded-self-action` — **closure: guard.** The change modifies self-triggered notification paths and BOUNDS them structurally: per-key 24 h durable derived-raise latches (restart-proof), per-episode derivedItemIds once-per-class records, resolve-note bounding (one per item per reopenWindowMs; latched-flapping ⇒ jsonl only), wave-notice 24 h dedupe, flap-history 64-event clamp, the existing per-day cap + append budget retained, and the fail-loud `escalationRaiseFailed` invariant. Convergence proven by `tests/unit/machine-coherence-anchors.test.ts` (latch/clamp/dedupe arithmetic) + `tests/unit/machine-coherence-calm-narration.test.ts` (once-per-episode derived raises, bounded resolves, single wave fire) + `tests/unit/rope-sink-router.test.ts` (both-class 24 h dedupe). Every emission settles to a bounded steady state under sustained pressure.