chainlesschain 0.162.198 → 0.163.0

package/src/data/changelog.json

@@ -1,6 +1,45 @@
 {
   "source": "CHANGELOG.md",
   "releases": [
+    {
+      "productVersion": null,
+      "cliVersion": "0.163.0",
+      "cliVersions": ["0.162.200", "0.163.0"],
+      "date": "2026-08-08",
+      "title": "",
+      "sections": [
+        {
+          "heading": "Fixed — cc CLI 0.163.0: macOS PTY launch and native host validation",
+          "body": "> `chainlesschain` **0.162.200 → 0.163.0** (release candidate,\n> 2026-08-08). CLI-only release metadata;\n> `@chainlesschain/personal-data-hub` remains **0.4.57** and\n> `@chainlesschain/agent-sdk` remains **0.1.7**.\n\n- **macOS PTY installation repair**: `node-pty@1.1.0` publishes its macOS\n  `spawn-helper` prebuilds without executable bits, which made fresh ARM64 and\n  Intel installs fail with `posix_spawnp failed`. The CLI postinstall now\n  repairs and verifies that narrowly resolved regular file, rejects symlinked\n  helpers, and the reliability workflow fails early if the executable bit is\n  missing before running a real PTY scenario.\n- **Real native target hosts**: the standalone native release matrix now maps\n  Linux, Windows, and macOS x64/ARM64 targets to six matching GitHub-hosted\n  runners and requires each artifact to execute on its own architecture. The\n  previous cross-target smoke-test skip is removed. This improves native\n  evidence readiness but does not claim signing, notarization, or public native\n  distribution is complete.\n- **Second command-observation cycle starts**: `0.163.0` begins the second minor\n  release cycle for lifecycle telemetry. All 25 deprecated compatibility\n  aliases remain retained because representative opt-in collector coverage,\n  per-command sample floors, and the `0.164.0` removal floor are not yet met.\n- **Pre-release evidence**: implementation SHA `38cd849ed16f` passed\n  [CLI Strict Sandbox](https://github.com/chainlesschain/chainlesschain/actions/runs/31202334570)\n  on Ubuntu, Windows, and macOS. This final version commit must independently\n  pass exact-SHA `CLI CI` and `CLI Strict Sandbox` before publication."
+        }
+      ]
+    },
+    {
+      "productVersion": null,
+      "cliVersion": "0.162.200",
+      "cliVersions": ["0.162.198", "0.162.200"],
+      "date": "2026-08-07",
+      "title": "",
+      "sections": [
+        {
+          "heading": "Fixed — cc CLI 0.162.200: release-gate isolation and carried reliability fixes",
+          "body": "> `chainlesschain` **0.162.198 → 0.162.200** (published,\n> 2026-08-07 from exact SHA `dbb06e16fef0`.\n> `0.162.199` failed before npm upload and its tag remains\n> immutable). CLI-only release metadata; `@chainlesschain/personal-data-hub`\n> remains **0.4.57** and `@chainlesschain/agent-sdk` remains **0.1.7**.\n\n- **Carries the complete 0.162.199 candidate**: command lifecycle telemetry and\n  alias observation policy, canonical session authority, fixed MCP package\n  capsules, native update recovery, and portable reliability gates are all\n  included because `0.162.199` never reached npm.\n- **Release-gate isolation**: the Agent SDK real-CLI E2E now places its\n  rollback-resistant security anchor beside, rather than inside,\n  `CHAINLESSCHAIN_HOME`. The fixture therefore matches the production\n  fail-closed layout after redirecting `HOME` and no longer hides the `agent`\n  command behind compatibility registration.\n- **Pre-release evidence**: implementation SHA `bf6924013d1c` passed the full\n  [npm release dry-run](https://github.com/chainlesschain/chainlesschain/actions/runs/31189959290),\n  including core packages, Agent SDK real-CLI E2E, Personal Data Hub, Web Panel,\n  the complete CLI suite, and credential-free npm package validation. The final\n  `0.162.200` version commit must pass the exact-SHA CLI CI and CLI Strict\n  Sandbox matrices before tag `v-npm-0-162-200` is created."
+        }
+      ]
+    },
+    {
+      "productVersion": null,
+      "cliVersion": "0.162.199",
+      "cliVersions": ["0.162.198", "0.162.199"],
+      "date": "2026-08-07",
+      "title": "",
+      "sections": [
+        {
+          "heading": "Fixed — cc CLI 0.162.199: session authority, MCP capsules, and recovery reliability",
+          "body": "> `chainlesschain` **0.162.198 → 0.162.199** (not published, 2026-08-07;\n> the release workflow failed before package creation or npm upload and tag\n> `v-npm-0-162-199` remains immutable). CLI-only release metadata;\n> `@chainlesschain/personal-data-hub` remains **0.4.57** and\n> `@chainlesschain/agent-sdk` remains **0.1.7**.\n\n- **Command lifecycle telemetry**: manifest-driven lifecycle metadata now\n  records legacy and replacement routes, aggregates usage without changing\n  aliases automatically, and keeps compatibility entries until their stated\n  observation window and release-cycle requirements are satisfied.\n- **Canonical session authority**: host leases, transcript witnesses,\n  anti-rollback anchors, compare-and-swap persistence, bounded cleanup, and\n  descendant retirement harden concurrent resume and long-running session\n  behavior across the covered CLI, background, and remote-host paths.\n- **Fixed MCP package execution**: approved JavaScript launchers are resolved\n  to exact npm versions and complete transitive closures, then bundled into a\n  guarded, content-addressed Node capsule. Runtime execution no longer depends\n  on a live dynamic package launcher or mutable `node_modules` entrypoint.\n- **Native update recovery**: Windows and POSIX installer/OTA generations can\n  recover interrupted activation, rollback, and rescue state while preserving\n  exact lineage, owner-private locks, and Windows path/handle identity under\n  Node 22.12 device projection.\n- **Portable reliability gates**: disk/pipe failure injection, process-tree\n  cleanup, resource accounting, session stress, and platform path aliases are\n  covered by the release matrices. Real hardware, terminal, SSH, and extended\n  soak observations remain ongoing evidence rather than compatibility claims.\n- **Candidate evidence**: implementation SHA `7e7ce9182746` passed\n  [CLI CI](https://github.com/chainlesschain/chainlesschain/actions/runs/31181229942),\n  [CLI Strict Sandbox](https://github.com/chainlesschain/chainlesschain/actions/runs/31181328955),\n  [CLI Background Interaction E2E](https://github.com/chainlesschain/chainlesschain/actions/runs/31181258842),\n  and [CLI Session Host Consistency](https://github.com/chainlesschain/chainlesschain/actions/runs/31181258424)\n  on Ubuntu, Windows, and macOS. Final SHA `23bd2e6e5758` also passed the\n  exact-SHA release gates, but the\n  [dedicated npm release](https://github.com/chainlesschain/chainlesschain/actions/runs/31187599603)\n  stopped before package creation because its Agent SDK fixture placed the\n  security anchor inside the redirected CLI home."
+        }
+      ]
+    },
     {
       "productVersion": null,
       "cliVersion": "0.162.198",
@@ -10,7 +49,7 @@
       "sections": [
         {
           "heading": "Fixed — cc CLI 0.162.198: interactive streaming and release portability",
-          "body": "> `chainlesschain` **0.162.197 → 0.162.198** (release candidate, 2026-08-06).\n> CLI-only release metadata; `@chainlesschain/personal-data-hub` remains\n> **0.4.57** and `@chainlesschain/agent-sdk` remains **0.1.7**.\n\n- **Interactive output backpressure**: REPL, headless streaming, provider\n  pacing, and TTY writers now wait for saturated output streams to drain and\n  clean up pending listeners across completion, interruption, and session\n  transitions instead of allowing unbounded interactive writes.\n- **Canonical session controls**: the CLI-owned session projection and bounded\n  reply routes now support the completed VS Code and JetBrains workbench and\n  rewind journeys while preserving CLI authority over persisted mutations.\n- **Portable release gates**: Windows path-alias fixtures, state-path mocks,\n  Skill metadata fixtures, POSIX executable-bit setup, and the deprecated\n  agent-core shim are aligned with the three-platform CLI CI and Strict\n  Sandbox contracts.\n- **Release readback hardening**: public npm verification remains independent\n  of undeclared runtime dependencies, retries bounded registry propagation,\n  and binds provenance and registry bytes to the immutable publish artifact.\n- **Candidate evidence**: merged implementation SHA `0b7a5471e7a9` passed\n  [CLI CI](https://github.com/chainlesschain/chainlesschain/actions/runs/31071519048)\n  and [CLI Strict Sandbox](https://github.com/chainlesschain/chainlesschain/actions/runs/31071522429)\n  on Ubuntu, Windows, and macOS. The final `0.162.198` version commit must pass\n  both gates again on its own exact SHA before tag `v-npm-0-162-198` is\n  created; local, older-SHA, and partial results remain supplementary only."
+          "body": "> `chainlesschain` **0.162.197 → 0.162.198** (published, 2026-08-06).\n> CLI-only release metadata; `@chainlesschain/personal-data-hub` remains\n> **0.4.57** and `@chainlesschain/agent-sdk` remains **0.1.7**.\n\n- **Interactive output backpressure**: REPL, headless streaming, provider\n  pacing, and TTY writers now wait for saturated output streams to drain and\n  clean up pending listeners across completion, interruption, and session\n  transitions instead of allowing unbounded interactive writes.\n- **Canonical session controls**: the CLI-owned session projection and bounded\n  reply routes now support the completed VS Code and JetBrains workbench and\n  rewind journeys while preserving CLI authority over persisted mutations.\n- **Portable release gates**: Windows path-alias fixtures, state-path mocks,\n  Skill metadata fixtures, POSIX executable-bit setup, and the deprecated\n  agent-core shim are aligned with the three-platform CLI CI and Strict\n  Sandbox contracts.\n- **Release readback hardening**: public npm verification remains independent\n  of undeclared runtime dependencies, retries bounded registry propagation,\n  and binds provenance and registry bytes to the immutable publish artifact.\n- **Exact release evidence**: tag `v-npm-0-162-198` points to final release SHA\n  [`3c0f62fa17242cfa3123ab502a9bf5d1cbed8481`](https://github.com/chainlesschain/chainlesschain/commit/3c0f62fa17242cfa3123ab502a9bf5d1cbed8481).\n  The same SHA passed [CLI CI](https://github.com/chainlesschain/chainlesschain/actions/runs/31078499968)\n  and [CLI Strict Sandbox](https://github.com/chainlesschain/chainlesschain/actions/runs/31078499270)\n  on Ubuntu, Windows, and macOS. The\n  [dedicated npm release](https://github.com/chainlesschain/chainlesschain/actions/runs/31081337370)\n  completed the exact-SHA gate, immutable tarball, CycloneDX SBOM, Trusted\n  Publishing, signed provenance, registry readback, and npmmirror sync; the\n  [independent public readback](https://github.com/chainlesschain/chainlesschain/actions/runs/31082366544)\n  re-downloaded the package and matched registry bytes and publishing identity."
         }
       ]
     },

package/src/gateways/ws/session-protocol.js

@@ -6,6 +6,7 @@ import {
 } from "../../runtime/runtime-events.js";
 import { createSessionRecord } from "../../runtime/contracts/session-record.js";
 import { loadSideEffectLedger } from "../../lib/side-effect-ledger-store.js";
+import { acquireSessionHostLease } from "../../lib/session-host-lease.js";
 import { reconcileSideEffects } from "../../lib/side-effect-ledger.js";
 import {
   formatMcpLedgerRecoveryNotice,
@@ -532,11 +533,20 @@ async function ensureSessionHandler(server, ws, session) {
     });
   } else {
     const { WSAgentHandler } = await import("./ws-agent-handler.js");
-    handler = new WSAgentHandler({
-      session,
-      interaction: session.interaction,
-      db: server.sessionManager.db,
+    const sessionHostLease = acquireSessionHostLease(session.id, {
+      hostKind: "ws",
     });
+    try {
+      handler = new WSAgentHandler({
+        session,
+        interaction: session.interaction,
+        db: server.sessionManager.db,
+        sessionHostLease,
+      });
+    } catch (error) {
+      sessionHostLease.release();
+      throw error;
+    }
   }
 
   server.sessionHandlers.set(session.id, handler);

package/src/gateways/ws/ws-agent-handler.js

@@ -79,6 +79,7 @@ export class WSAgentHandler {
     approvalGate,
     agentLoop: runAgentLoop,
     canonicalSessionStore,
+    sessionHostLease = null,
   }) {
     this.session = session;
     this.interaction = interaction;
@@ -86,6 +87,25 @@ export class WSAgentHandler {
     this._processing = false;
     this._abortController = null;
     this._activeRequestId = null;
+    this._sessionHostLease = sessionHostLease;
+    this._onSessionHostLeaseAbort = null;
+    if (sessionHostLease?.signal) {
+      this._onSessionHostLeaseAbort = () => {
+        const reason =
+          sessionHostLease.signal.reason ||
+          createAbortError("Session host lease was lost");
+        if (this._abortController && !this._abortController.signal.aborted) {
+          this._abortController.abort(reason);
+        }
+        this.interaction?.rejectAllPending?.(reason);
+      };
+      sessionHostLease.signal.addEventListener(
+        "abort",
+        this._onSessionHostLeaseAbort,
+        { once: true },
+      );
+      if (sessionHostLease.signal.aborted) this._onSessionHostLeaseAbort();
+    }
     // P0-2: monotonic sequence for crash-safe side-effect ledger op ids. The
     // session id + a per-op nonce keep ids unique across turns and processes.
     this._sideEffectSeq = 0;
@@ -486,6 +506,7 @@ export class WSAgentHandler {
 
     try {
       const { session } = this;
+      this._sessionHostLease?.assert?.();
 
       if (session.canonicalJsonlSession === true) {
         canonicalTurn = this._claimCanonicalTurn(userMessage, requestId);
@@ -648,6 +669,7 @@ export class WSAgentHandler {
                     })
                     .start(opId);
                   persistSideEffectLedger(session.id, sideEffectLedger);
+                  this._sessionHostLease?.assert?.();
                 }
               }
               break;
@@ -884,6 +906,15 @@ export class WSAgentHandler {
         reason: "session_closed",
       });
     }
+    if (this._sessionHostLease?.signal && this._onSessionHostLeaseAbort) {
+      this._sessionHostLease.signal.removeEventListener(
+        "abort",
+        this._onSessionHostLeaseAbort,
+      );
+    }
+    this._onSessionHostLeaseAbort = null;
+    this._sessionHostLease?.release?.();
+    this._sessionHostLease = null;
   }
 
   /**