@renzrollon/interlock 1.5.0 → 1.5.1

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "interlock",
   "displayName": "Interlock",
-  "version": "1.5.0",
+  "version": "1.5.1",
   "description": "Spec-driven development for Claude Code, layered on OpenSpec. You read one spec; parallel agents ship it to a tested commit.",
   "author": {
     "name": "Carl Rollon",

package/CHANGELOG.md

@@ -7,6 +7,17 @@ this project adheres to Semantic Versioning 2.0.0.
 
 ## [Unreleased]
 
+## 1.5.1 — 2026-10-11
+
+### Changed
+
+- **`docs/08` is about Interlock's own harness.** It was a survey of OpenClaw, Hermes Agent and DeepSeek Harness. It now maps the parts of the harness, what holds on each host, and what is left out on purpose; the other projects are one comparison table. The page no longer says lane isolation is closed on the Workflow host, which still halts with `LANE BASE MISMATCH` after the first fold.
+- **The README says what the one network call sends.** It said a push happens when `INTERLOCK_NTFY_TOPIC` is set. It now names what goes out (the close summary's first line, the change name and the run id; the change name at the spec checkpoint; the title and body of a `notify` you type), which server receives it, that the topic is the only thing in the request that identifies you, and that no request is made without one. It also says the plugin's `ntfy topic` option reaches the CLI through the session's environment, and that `interlock doctor` reads a model credential by name and never by value. The plugin directory holds a plugin that reads a value from the environment and posts to a server until a reviewer has read this.
+
+### Fixed
+
+- **The session-start hook returns the forward itself.** The `classic.SessionStart` hook in `hooks/mod.mjs` held the forward in a variable, awaited the preflight read, and returned the variable. The plugin directory's reader could not tell that return from a first message or a permission decision of the hook's own, and held the version. The hook now returns the forward call, continued once to read the preflight's report and hand back the value the chain resolved with. Nothing a session sees changes: the read still finishes before the event resolves, and a chain that rejects still skips it. `test/mod/session-start.test.ts` and `test/spine/mod-pins.test.mjs` cover it unchanged.
+
 ## 1.5.0 — 2026-10-11
 
 ### Added

package/README.md

@@ -96,7 +96,7 @@ Most of the category competes on how much structure you write before coding —
 | OpenSpec | the artifact loop and its CLI | the CLI validates artifacts; skills run the loop |
 | **Interlock** | how many decisions the model may not make | a CLI with exit codes, and a runtime with no channel for a question |
 
-It composes OpenSpec rather than replacing it. `openspec init` installs its own skills, and `/interlock:spec` drives the `openspec` CLI directly, so both stay available. Use `/interlock:spec` when you want the gates, and the stock skills when you want the plain artifact loop. What Interlock adds, and when plain OpenSpec is the right call: [03](docs/03-openspec-vs-interlock.md). Where it sits against OpenClaw, Hermes Agent and DeepSeek Harness: [08](docs/08-harness-landscape.md).
+It composes OpenSpec rather than replacing it. `openspec init` installs its own skills, and `/interlock:spec` drives the `openspec` CLI directly, so both stay available. Use `/interlock:spec` when you want the gates, and the stock skills when you want the plain artifact loop. What Interlock adds, and when plain OpenSpec is the right call: [03](docs/03-openspec-vs-interlock.md). What the harness is made of, and where it sits beside OpenClaw, Hermes Agent and DeepSeek Harness: [08](docs/08-harness-landscape.md).
 
 The trade is portability. Claude Code is the **default and supported host**; Cursor and Copilot are not supported. Everything the loop decides lives in a CLI any host can shell out to, so portability means a second host adapter, not thirty prompt templates.
 
@@ -118,7 +118,7 @@ Three zero-dependency Node binaries land on your `PATH`, and they work without t
 | `interlock-graph` | A local, deterministic code knowledge graph. No vector store, no network |
 | `interlock-run` | The experimental runner above |
 
-Everything runs without a model and without the network, with one exception. `interlock notify` and `run close --notify` push a message when a run halts or completes, and only when `INTERLOCK_NTFY_TOPIC` is set; `INTERLOCK_NTFY_URL` points it at a self-hosted server. Reference and every environment variable: [07 — CLI and configuration](docs/07-cli-and-configuration.md).
+Everything runs without a model and without the network, with one exception: an opt-in push for a run that stops while nobody is watching. `run close --notify` sends the close summary's first line, the change name and the run id; the spec checkpoint sends the change name; an `interlock notify` you type sends the title and body you give it. The request goes to the [ntfy](https://ntfy.sh) server named by `INTERLOCK_NTFY_URL`, the public `https://ntfy.sh` by default, under the topic you chose in the plugin's `ntfy topic` option or in `INTERLOCK_NTFY_TOPIC`. Session start copies a set option into the session's environment when the variable is not already set, because the CLI call that pushes is not a hook and the option reaches hooks only. No account, key or token goes with the request: the topic is the only thing in it that identifies you, so treat it as a secret. With no topic set, no request is ever made. Interlock makes no other request. `interlock doctor` reports whether `ANTHROPIC_API_KEY` or `CLAUDE_CODE_OAUTH_TOKEN` is set, by name and never by value, and the vendor CLIs a run spawns inherit the environment as any child process does; what they send is theirs. Reference and every environment variable: [07 — CLI and configuration](docs/07-cli-and-configuration.md).
 
 ## Docs
 
@@ -133,7 +133,7 @@ New here? Start with **[01 — The first hour](docs/01-first-hour.md)**. Only ev
 | [05 — Continuity](docs/05-continuity.md) | When `--continue` may skip the human read |
 | [06 — Why it works](docs/06-why-it-works.md) | The mechanisms, low-level, with the costs stated |
 | [07 — CLI and configuration](docs/07-cli-and-configuration.md) | Every subcommand, environment variable and host |
-| [08 — The harness landscape](docs/08-harness-landscape.md) | OpenClaw, Hermes Agent, DeepSeek Harness, and the spec-driven neighbours |
+| [08 — The Interlock harness](docs/08-harness-landscape.md) | The parts of the harness, what holds on each host, and a short comparison with other harnesses |
 | [09 — From prompt to workflow](docs/09-from-prompt-to-workflow.md) | New to agentic workflows? Every term defined, then why `ship` is a script |
 | [10 — Ship and spec for prompt-only engineers](docs/10-agentic-workflow-ship-and-spec.md) | Primer, review of spec+ship, token and quality tactics |
 | [11 — The indicators](docs/11-the-indicators.md) | What `interlock report` measures and why it gates nothing; whether to commit the run corpora |

package/hooks/mod.mjs

@@ -2125,14 +2125,18 @@ export function register(on) {
   // The kit raises this event; Claude Code 2.1.291 raises no classic event to
   // a module, so there the prompt hook above reads the report instead.
   //
-  // Pass the event on unchanged. The value this hook returns is the forward
-  // itself: no first message, no permission decision. The meter's reset runs
-  // before that chain and the preflight read after it; neither becomes the return.
+  // Pass the event on unchanged. The hook returns the forward call itself,
+  // continued once: when the chain beneath has resolved, the preflight's
+  // report is read, and the continuation hands back the value that chain
+  // resolved with, as it came. No first message and no permission decision
+  // come from this hook. The meter's reset runs before the chain. A chain
+  // that rejects skips the read, and the rejection goes on as it came.
   on('classic.SessionStart', async (meterSessionApi, meterSessionInput, meterSessionForward) => {
     endRunAtBoundary(meterSessionApi, meterSessionInput)
-    const sessionForwarded = meterSessionForward(meterSessionInput)
-    await sessionForwarded.then(() => readPreflightAfterStart(meterSessionApi, meterSessionInput))
-    return sessionForwarded
+    return meterSessionForward(meterSessionInput).then(async started => {
+      await readPreflightAfterStart(meterSessionApi, meterSessionInput)
+      return started
+    })
   })
 
   on('ui.render', { component: 'Spinner' }, ($, e, next) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@renzrollon/interlock",
-  "version": "1.5.0",
+  "version": "1.5.1",
   "description": "Spec-driven development for Claude Code, layered on OpenSpec. You read one spec; parallel agents ship it to a tested commit.",
   "type": "module",
   "engines": {