@alook/daemon 0.0.160 → 0.1.0

package/README.md

@@ -57,14 +57,17 @@ When a message arrives, what happens depends on the runtime's lifecycle:
 One long-lived process spans many turns. A new message is **written onto the
 still-open input channel** — no restart. This is "steering."
 
-- **`direct`** (codex, kimi, pi): write immediately; the runtime
-  tolerates injection any time.
-- **`gated`** (claude): a raw write mid-stream could collide with an active
-  signed thinking block, so writes are **held until a safe boundary**. Two state
-  machines implement this:
-  - `RuntimeTurnState` (`src/runtime/turnState.ts`) — the instantaneous gate:
-    `canSteerBusy = currentTurnId && !steeringGateActive`. Tool boundary closes
-    the gate; progress / turn-start reopens it.
+The busy-delivery mode is **derived from `lifecycle`** (`busyDeliveryModeOf` /
+`supportsStdinNotificationOf` in `types.ts`) — `lifecycle.stdin` is the single
+source of truth, so a driver's mode can't drift from it (it used to: a driver
+could declare `lifecycle.stdin: "gated"` yet `busyDeliveryMode: "direct"`).
+`persistent+direct → direct`, `persistent+gated → gated`, `per_turn → none`.
+
+- **`direct`** (kimi, pi): write immediately; the runtime tolerates injection
+  any time.
+- **`gated`** (claude, codex): a raw write mid-stream could collide with an active
+  signed thinking block, so writes are **held until a safe boundary**,
+  implemented by:
   - `apmStateMachine` (`src/runtime/apmStateMachine.ts`) — the policy reducers
     that decide *when* to flush queued inbox notices and emit the concrete
     `notify_stdin` / `deliver_stdin` effects (clause `SMR-002`). Flushing is
@@ -93,7 +96,7 @@ message and terminates the process on turn end.
 | Runtime | Lifecycle | Transport / protocol | Steering | Initial input | Output format |
 |---|---|---|---|---|---|
 | **claude** | persistent | child process, stream-json NDJSON | `gated` | `{type:"user",…}` line on stdin | stream-json |
-| **codex** | persistent | child process, JSON-RPC 2.0 (`app-server --listen stdio://`) | `direct` (`turn/steer`) | `initialize` → `thread/start`/`resume` | JSON-RPC notifications |
+| **codex** | persistent | child process, JSON-RPC 2.0 (`app-server --listen stdio://`) | `gated` | `initialize` → `thread/start`/`resume` | JSON-RPC notifications |
 | **kimi** | persistent | child process, JSON-RPC "wire" | `direct` (`steer`) | `initialize` → `prompt` | JSON-RPC events |
 | **pi** | persistent | in-process SDK (`@earendil-works/pi-coding-agent`), multi-provider | `direct` | `session.prompt()` | SDK event callback |
 | **gemini** | per-turn | child process, stream-json | none | prompt on stdin, then close | stream-json |
@@ -130,7 +133,6 @@ src/
   runtime/
     runtimeSession.ts            # ChildProcessRuntimeSession + descriptor
     sdkRuntimeSession.ts         # SdkRuntimeSession (in-process)
-    turnState.ts                 # instantaneous steering gate
     apmStateMachine.ts           # gated-delivery policy reducers (SMR-002)
     progressState.ts             # liveness / stall detection
     notificationState.ts         # inbox-notice de-dup + batching