comisai 1.0.45 → 1.0.46

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-events-attention.js

@@ -1,17 +1,17 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * P5 (Phase 124) attention + audit event payloads for the skills-side structural
- * `TerminalEventBus` (terminal-tools.ts). These mirror the four new core
- * `TerminalEvents` keys (events-terminal.ts, 124-02 site 1) one-for-one so the
+ * Attention + audit event payloads for the skills-side structural
+ * `TerminalEventBus` (terminal-tools.ts). These mirror the core
+ * `TerminalEvents` keys (events-terminal.ts) one-for-one so the
  * daemon's `TypedEventBus` stays structurally compatible with the bus the skills
- * layer emits on (the proven 3-site plumbing — site 2 is the overloads in
+ * layer emits on (the 3-site plumbing — the second site is the overloads in
  * terminal-tools.ts; this file holds their payload types).
  *
  * They live in this sibling rather than terminal-tools.ts because that file is at
  * the 800-line file-size cap (`test/architecture/file-size.test.ts`); the overloads
  * themselves stay on `TerminalEventBus` there.
  *
- * REDACTION-SAFE BY CONSTRUCTION (the `TerminalKeystrokeEvent` precedent, T-124-03):
+ * REDACTION-SAFE BY CONSTRUCTION (the `TerminalKeystrokeEvent` precedent):
  * every payload carries counts / ids / a typed `reason` or `state` + `timestamp`
  * ONLY — there is NO `text`/`keys`/`screen`/`payload` field, so an emit site
  * cannot leak screen contents or a keystroke onto the bus even by mistake. The

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-heartbeat-digest.d.ts

@@ -1,21 +1,21 @@
 /**
- * The pure NOTIFY-02 heartbeat line (design §4 Phase D; CONTEXT I3).
+ * The pure heartbeat line for a promoted drive.
  *
  * `heartbeatLine(j)` builds the user-facing periodic progress one-liner for a PROMOTED
  * (long) drive — `"still working — elapsed Xh, last activity <digest>, N interactions,
  * ~$Y"` — assembled PURELY from the {@link DriveJournal}'s content-free fields
- * (`elapsedMs`, `lastScreenDigest`, `interactions`, `costUsd`). This is NOTIFY-02's
- * spam-free "the 40h drive is still alive" signal, distinct from LIVE-01's INTERNAL
+ * (`elapsedMs`, `lastScreenDigest`, `interactions`, `costUsd`). This is the
+ * spam-free "the 40h drive is still alive" signal, distinct from the INTERNAL
  * liveness tick (which is never a user message).
  *
- * CONTENT-FREE BY CONSTRUCTION (I3): the ONLY screen-derived text in the output is
+ * CONTENT-FREE BY CONSTRUCTION: the ONLY screen-derived text in the output is
  * `lastScreenDigest`, which the woken-turn driver ALREADY ran through `scrubSecretsFromText`
  * + bounded to `DIGEST_EXCERPT_MAX` before it landed on the journal (terminal-wake-turn.ts).
  * This function FORMATS, it does NOT redact and NEVER re-expands or re-reads the screen —
  * the same FORMAT-not-redact layer split `screenDigestLine` documents (terminal-read-digest.ts).
  * Everything else in the line is structural (counts/durations/labels).
  *
- * Architecture invariants (binding — AGENTS.md / 124 house style, mirrors
+ * Architecture invariants (binding — AGENTS.md; mirrors
  * `terminal-read-digest.ts` `screenDigestLine` / `terminal-spend-ceiling.ts`):
  *   - PURE: a free function, NOT a factory. NO clock/timer reads (`elapsedMs` is the
  *     content-free number the CALLER derived from its own injected clock), NO module-global
@@ -31,7 +31,7 @@
  */
 import type { DriveJournal } from "./terminal-drive-journal.js";
 /**
- * The content-free NOTIFY-02 heartbeat one-liner for a promoted drive (I3).
+ * The content-free heartbeat one-liner for a promoted drive.
  *
  * Pure + total: a degenerate journal yields a safe string (`0` hours/interactions/cost, an
  * empty digest → `"(no activity yet)"`); never throws. The line is content-free BY

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-heartbeat-digest.js

@@ -1,22 +1,22 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * The pure NOTIFY-02 heartbeat line (design §4 Phase D; CONTEXT I3).
+ * The pure heartbeat line for a promoted drive.
  *
  * `heartbeatLine(j)` builds the user-facing periodic progress one-liner for a PROMOTED
  * (long) drive — `"still working — elapsed Xh, last activity <digest>, N interactions,
  * ~$Y"` — assembled PURELY from the {@link DriveJournal}'s content-free fields
- * (`elapsedMs`, `lastScreenDigest`, `interactions`, `costUsd`). This is NOTIFY-02's
- * spam-free "the 40h drive is still alive" signal, distinct from LIVE-01's INTERNAL
+ * (`elapsedMs`, `lastScreenDigest`, `interactions`, `costUsd`). This is the
+ * spam-free "the 40h drive is still alive" signal, distinct from the INTERNAL
  * liveness tick (which is never a user message).
  *
- * CONTENT-FREE BY CONSTRUCTION (I3): the ONLY screen-derived text in the output is
+ * CONTENT-FREE BY CONSTRUCTION: the ONLY screen-derived text in the output is
  * `lastScreenDigest`, which the woken-turn driver ALREADY ran through `scrubSecretsFromText`
  * + bounded to `DIGEST_EXCERPT_MAX` before it landed on the journal (terminal-wake-turn.ts).
  * This function FORMATS, it does NOT redact and NEVER re-expands or re-reads the screen —
  * the same FORMAT-not-redact layer split `screenDigestLine` documents (terminal-read-digest.ts).
  * Everything else in the line is structural (counts/durations/labels).
  *
- * Architecture invariants (binding — AGENTS.md / 124 house style, mirrors
+ * Architecture invariants (binding — AGENTS.md; mirrors
  * `terminal-read-digest.ts` `screenDigestLine` / `terminal-spend-ceiling.ts`):
  *   - PURE: a free function, NOT a factory. NO clock/timer reads (`elapsedMs` is the
  *     content-free number the CALLER derived from its own injected clock), NO module-global
@@ -35,7 +35,7 @@ function safeNonNegative(n) {
     return Number.isFinite(n) && n > 0 ? n : 0;
 }
 /**
- * The content-free NOTIFY-02 heartbeat one-liner for a promoted drive (I3).
+ * The content-free heartbeat one-liner for a promoted drive.
  *
  * Pure + total: a degenerate journal yields a safe string (`0` hours/interactions/cost, an
  * empty digest → `"(no activity yet)"`); never throws. The line is content-free BY
@@ -51,7 +51,7 @@ export function heartbeatLine(j) {
     const interactions = Math.floor(safeNonNegative(j.interactions));
     // costUsd is money: a non-finite/negative value is degenerate → 0; two-decimal money format.
     const cost = safeNonNegative(j.costUsd).toFixed(2);
-    // The (already-redacted, already-bounded) digest, VERBATIM — never re-expanded (I3 layer split).
+    // The (already-redacted, already-bounded) digest, VERBATIM — never re-expanded (the format-not-redact layer split).
     const activity = typeof j.lastScreenDigest === "string" && j.lastScreenDigest.length > 0
         ? j.lastScreenDigest
         : "(no activity yet)";

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-ipc.d.ts

@@ -1,5 +1,5 @@
 /**
- * Length-prefixed JSON IPC framing for the Terminal Worker boundary (spec §2.3).
+ * Length-prefixed JSON IPC framing for the Terminal Worker boundary.
  *
  * The worker and the daemon-side registry exchange JSON frames over a pipe.
  * Each frame is `[uint32-BE body-length][utf8 JSON body]`. Requests correlate

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-ipc.js

@@ -1,6 +1,6 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * Length-prefixed JSON IPC framing for the Terminal Worker boundary (spec §2.3).
+ * Length-prefixed JSON IPC framing for the Terminal Worker boundary.
  *
  * The worker and the daemon-side registry exchange JSON frames over a pipe.
  * Each frame is `[uint32-BE body-length][utf8 JSON body]`. Requests correlate

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-key-grammar.d.ts

@@ -1,5 +1,5 @@
 /**
- * The pure named-key grammar (spec §5 send_key).
+ * The pure named-key grammar behind `send_key`.
  *
  * Turns a `send_key` chord (`"C-c"`, `"Up"`, `"S-Tab"`, `"M-x"`) into the exact
  * control/escape byte sequence a PTY consumes. This is a standalone,

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-key-grammar.js

@@ -1,6 +1,6 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * The pure named-key grammar (spec §5 send_key).
+ * The pure named-key grammar behind `send_key`.
  *
  * Turns a `send_key` chord (`"C-c"`, `"Up"`, `"S-Tab"`, `"M-x"`) into the exact
  * control/escape byte sequence a PTY consumes. This is a standalone,

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-loop-guard.d.ts

@@ -1,5 +1,5 @@
 /**
- * The normalized region-scoped loop/stuck guard (spec §4.6; SEC-11).
+ * The normalized region-scoped loop/stuck guard.
  *
  * `createLoopGuard({ nowMs, windowMs?, maxRepeats? })` detects an auto-answer loop on a
  * RE-RENDERED prompt: the same *logical* prompt presented again is caught even when its
@@ -8,16 +8,16 @@
  * (strip the volatile bits, collapse whitespace), hashes the stable remainder, tracks
  * recent (hash, ts) per session in a window, and returns a typed
  * `{ repeat: true, reason: "loop_detected" }` once a normalized hash recurs within the
- * window — otherwise `{ repeat: false }`. The caller (124-09) escalates on a repeat
- * (`terminal:escalated`, reason `loop_detected`).
+ * window — otherwise `{ repeat: false }`. The caller (the woken-turn driver) escalates
+ * on a repeat (`terminal:escalated`, reason `loop_detected`).
  *
- * COMPOSES WITH (does NOT duplicate) the P4 `maxInteractions` cap (terminal-caps.ts):
+ * COMPOSES WITH (does NOT duplicate) the `maxInteractions` cap (terminal-caps.ts):
  * the cap EVICTs the session independently when its interaction budget is spent (via the
  * single audited `registry.evict(..., "max_interactions")` path); this guard is the
  * ADDITIVE detector that catches a tight re-render loop BEFORE the budget runs out, and
  * escalates to a human rather than evicting. Two independent defenses, no shared state.
  *
- * Architecture invariants (binding — AGENTS.md / 124 house style, mirrors
+ * Architecture invariants (binding — AGENTS.md; mirrors
  * `terminal-caps.ts` / `terminal-ipc.ts`):
  *   - NO module-global mutable state. The recent-hash ring is a CLOSURE-local
  *     `Map<sessionId, RecentHash[]>` created inside the factory — two `createLoopGuard`
@@ -51,7 +51,7 @@ export interface LoopGuardDeps {
      */
     maxRepeats?: number;
 }
-/** The loop guard's surface — exactly what the woken turn (124-09) consumes. */
+/** The loop guard's surface — exactly what the woken turn consumes. */
 export interface LoopGuard {
     /**
      * Record a settled prompt region and report whether it is a (normalized) repeat

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-loop-guard.js

@@ -1,6 +1,6 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * The normalized region-scoped loop/stuck guard (spec §4.6; SEC-11).
+ * The normalized region-scoped loop/stuck guard.
  *
  * `createLoopGuard({ nowMs, windowMs?, maxRepeats? })` detects an auto-answer loop on a
  * RE-RENDERED prompt: the same *logical* prompt presented again is caught even when its
@@ -9,16 +9,16 @@
  * (strip the volatile bits, collapse whitespace), hashes the stable remainder, tracks
  * recent (hash, ts) per session in a window, and returns a typed
  * `{ repeat: true, reason: "loop_detected" }` once a normalized hash recurs within the
- * window — otherwise `{ repeat: false }`. The caller (124-09) escalates on a repeat
- * (`terminal:escalated`, reason `loop_detected`).
+ * window — otherwise `{ repeat: false }`. The caller (the woken-turn driver) escalates
+ * on a repeat (`terminal:escalated`, reason `loop_detected`).
  *
- * COMPOSES WITH (does NOT duplicate) the P4 `maxInteractions` cap (terminal-caps.ts):
+ * COMPOSES WITH (does NOT duplicate) the `maxInteractions` cap (terminal-caps.ts):
  * the cap EVICTs the session independently when its interaction budget is spent (via the
  * single audited `registry.evict(..., "max_interactions")` path); this guard is the
  * ADDITIVE detector that catches a tight re-render loop BEFORE the budget runs out, and
  * escalates to a human rather than evicting. Two independent defenses, no shared state.
  *
- * Architecture invariants (binding — AGENTS.md / 124 house style, mirrors
+ * Architecture invariants (binding — AGENTS.md; mirrors
  * `terminal-caps.ts` / `terminal-ipc.ts`):
  *   - NO module-global mutable state. The recent-hash ring is a CLOSURE-local
  *     `Map<sessionId, RecentHash[]>` created inside the factory — two `createLoopGuard`

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-notify-policy.d.ts

@@ -1,18 +1,19 @@
 /**
- * The pure NOTIFY-01 `drive.notify` gate (design §4 Phase D; CONTEXT I4).
+ * The pure `drive.notify` gate.
  *
  * `shouldNotifyOutcome(outcome, policy)` answers ONE question over a user-facing terminal
  * outcome: should it reach the user, given the operator's `drive.notify` policy? This is
- * what makes the I4 invariant — "an escalation notifies even under `none`" — RED-pinnable
+ * what makes the invariant — "an escalation notifies even under `none`" — pinnable
  * in isolation, separate from the wake-holder wiring.
  *
- * The contract (the NOTIFY-01 gate table):
- *   - `"needs-you"` (an escalation) → ALWAYS `true`. SEC-12/SEC-11 are NEVER weakened by
+ * The contract (the gate table):
+ *   - `"needs-you"` (an escalation) → ALWAYS `true`. The escalate-always/loop-guard
+ *     security signals are NEVER weakened by
  *     "notify only on terminal outcome": an escalation IS a terminal notification and fires
- *     even under `drive.notify:"none"` (I4 — the load-bearing cell). The caller must NOT
- *     route the escalation through any OTHER suppression (Pitfall 1 — a uniform guard over
- *     every outcome is the I4 regression; `needs-you` here returns `true` unconditionally so
- *     a correct caller can gate all outcomes through this ONE fn safely).
+ *     even under `drive.notify:"none"` (the load-bearing cell). The caller must NOT
+ *     route the escalation through any OTHER suppression (a uniform guard over
+ *     every outcome is the classic regression; `needs-you` here returns `true` unconditionally
+ *     so a correct caller can gate all outcomes through this ONE fn safely).
  *   - `"done"` / `"failed"` → `policy !== "none"`. Suppressed ONLY under `"none"`; they fire
  *     under `"terminal"` (the default) and `"all"`.
  *
@@ -20,23 +21,23 @@
  * a SEPARATE caller decision (a per-wake line is not a terminal `outcome`), NOT this gate;
  * this fn governs only the three terminal outcomes.
  *
- * Architecture invariants (binding — AGENTS.md / 124 house style, mirrors
+ * Architecture invariants (binding — AGENTS.md; mirrors
  * `terminal-spend-ceiling.ts` / `terminal-drive-promote.ts`):
  *   - PURE: a free function, NOT a factory. NO clock/timer reads, NO module-global mutable
  *     state, NO I/O. An (outcome, policy) → boolean response.
  *   - TOTAL / NEVER throws: every pair yields a boolean; the SAFE direction for an
- *     escalation is always-notify (I4 — never silence a security signal).
+ *     escalation is always-notify (never silence a security signal).
  *   - Infra-free: value-imports NOTHING at runtime — no platform runtime packages, no
  *     observability egress (the globals + infra-runtime-scope gates; this file names none).
  *
  * @module
  */
-/** The operator `drive.notify` policy (schema-skills.ts; design §4 Phase D, default `terminal`). */
+/** The operator `drive.notify` policy (schema-skills.ts; default `terminal`). */
 export type NotifyPolicy = "terminal" | "all" | "none";
 /**
- * Should this terminal outcome reach the user, given the `drive.notify` policy? — NOTIFY-01.
+ * Should this terminal outcome reach the user, given the `drive.notify` policy?
  *
- * `"needs-you"` ALWAYS returns `true` (I4 — an escalation notifies even under `"none"`);
+ * `"needs-you"` ALWAYS returns `true` (an escalation notifies even under `"none"`);
  * `"done"`/`"failed"` return `policy !== "none"` (suppressed only under `"none"`). Pure +
  * total; never throws.
  *

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-notify-policy.js

@@ -1,19 +1,20 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * The pure NOTIFY-01 `drive.notify` gate (design §4 Phase D; CONTEXT I4).
+ * The pure `drive.notify` gate.
  *
  * `shouldNotifyOutcome(outcome, policy)` answers ONE question over a user-facing terminal
  * outcome: should it reach the user, given the operator's `drive.notify` policy? This is
- * what makes the I4 invariant — "an escalation notifies even under `none`" — RED-pinnable
+ * what makes the invariant — "an escalation notifies even under `none`" — pinnable
  * in isolation, separate from the wake-holder wiring.
  *
- * The contract (the NOTIFY-01 gate table):
- *   - `"needs-you"` (an escalation) → ALWAYS `true`. SEC-12/SEC-11 are NEVER weakened by
+ * The contract (the gate table):
+ *   - `"needs-you"` (an escalation) → ALWAYS `true`. The escalate-always/loop-guard
+ *     security signals are NEVER weakened by
  *     "notify only on terminal outcome": an escalation IS a terminal notification and fires
- *     even under `drive.notify:"none"` (I4 — the load-bearing cell). The caller must NOT
- *     route the escalation through any OTHER suppression (Pitfall 1 — a uniform guard over
- *     every outcome is the I4 regression; `needs-you` here returns `true` unconditionally so
- *     a correct caller can gate all outcomes through this ONE fn safely).
+ *     even under `drive.notify:"none"` (the load-bearing cell). The caller must NOT
+ *     route the escalation through any OTHER suppression (a uniform guard over
+ *     every outcome is the classic regression; `needs-you` here returns `true` unconditionally
+ *     so a correct caller can gate all outcomes through this ONE fn safely).
  *   - `"done"` / `"failed"` → `policy !== "none"`. Suppressed ONLY under `"none"`; they fire
  *     under `"terminal"` (the default) and `"all"`.
  *
@@ -21,21 +22,21 @@
  * a SEPARATE caller decision (a per-wake line is not a terminal `outcome`), NOT this gate;
  * this fn governs only the three terminal outcomes.
  *
- * Architecture invariants (binding — AGENTS.md / 124 house style, mirrors
+ * Architecture invariants (binding — AGENTS.md; mirrors
  * `terminal-spend-ceiling.ts` / `terminal-drive-promote.ts`):
  *   - PURE: a free function, NOT a factory. NO clock/timer reads, NO module-global mutable
  *     state, NO I/O. An (outcome, policy) → boolean response.
  *   - TOTAL / NEVER throws: every pair yields a boolean; the SAFE direction for an
- *     escalation is always-notify (I4 — never silence a security signal).
+ *     escalation is always-notify (never silence a security signal).
  *   - Infra-free: value-imports NOTHING at runtime — no platform runtime packages, no
  *     observability egress (the globals + infra-runtime-scope gates; this file names none).
  *
  * @module
  */
 /**
- * Should this terminal outcome reach the user, given the `drive.notify` policy? — NOTIFY-01.
+ * Should this terminal outcome reach the user, given the `drive.notify` policy?
  *
- * `"needs-you"` ALWAYS returns `true` (I4 — an escalation notifies even under `"none"`);
+ * `"needs-you"` ALWAYS returns `true` (an escalation notifies even under `"none"`);
  * `"done"`/`"failed"` return `policy !== "none"` (suppressed only under `"none"`). Pure +
  * total; never throws.
  *
@@ -44,7 +45,7 @@
  * @returns `true` to notify the user, `false` to suppress.
  */
 export function shouldNotifyOutcome(outcome, policy) {
-    // I4: an escalation is a security signal — it notifies under EVERY policy, including
+    // An escalation is a security signal — it notifies under EVERY policy, including
     // "none". This is the canary cell; never make it conditional on `policy`.
     if (outcome === "needs-you")
         return true;

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-read-digest.d.ts

@@ -1,6 +1,5 @@
 /**
- * The pure bounded digest/diff read selector (READ-01; design §4 Phase B, §7.1
- * Open-Decision 3 RESOLVED → this plan).
+ * The pure bounded digest/diff read selector.
  *
  * `boundedReadDigest(view, mode, byteCap?)` answers ONE question over a single
  * already-rendered read view (`{screen, diff?}`): what bounded text should a
@@ -21,20 +20,20 @@
  * Every mode passes through {@link capWithBreadcrumb}, modeled on
  * `perceptionScreen`'s bounded tail: an over-cap result is CLIPPED to the cap and
  * carries a `truncations` breadcrumb (the count of dropped bytes) — NEVER a silent
- * trim (I7). The byte cap is {@link READ_DIGEST_BYTE_CAP} (documented like
+ * trim. The byte cap is {@link READ_DIGEST_BYTE_CAP} (documented like
  * `PERCEPTION_RING_TAIL`); the emulator viewport is already `cols×rows`-bounded, so
  * the cap mostly guards a pathological `full`/`ansi` read.
  *
  * `screenDigestLine(view)` derives the content-free one-liner the journal stores as
- * `lastScreenDigest` (DRIVE-01 / I3): `"<rows>r <cols>c, <changed> changed,
+ * `lastScreenDigest`: `"<rows>r <cols>c, <changed> changed,
  * cursor@(x,y)"` plus a SHORT excerpt of the first non-empty line — content-free BY
- * CONSTRUCTION (counts/coords; it never dumps the whole grid, T-164-08). The CALLER
- * (the woken-turn driver, plan 06) runs `scrubSecretsFromText` over the excerpt
+ * CONSTRUCTION (counts/coords; it never dumps the whole grid). The CALLER
+ * (the woken-turn driver) runs `scrubSecretsFromText` over the excerpt
  * before it reaches the journal/notification — the excerpt this module emits is
- * deliberately short, not pre-redacted (redaction is the wiring layer's job, RESEARCH
- * Pattern 4 / Don't Hand-Roll: `scrubSecretsFromText` is the canonical redactor).
+ * deliberately short, not pre-redacted (redaction is the wiring layer's job;
+ * `scrubSecretsFromText` is the canonical redactor — don't hand-roll another).
  *
- * Architecture invariants (binding — AGENTS.md / 124 house style, mirrors
+ * Architecture invariants (binding — AGENTS.md; mirrors
  * `terminal-dialog-detector.ts` / `terminal-settle.ts`'s pure helpers):
  *   - PURE: free functions, NOT factories. NO clock/timer reads, NO module-global
  *     mutable state, NO I/O.
@@ -51,27 +50,26 @@ import type { SnapshotDiff } from "./terminal-render.js";
  * The default read-result byte cap. Modeled on `PERCEPTION_RING_TAIL` (8192) in
  * `terminal-render.ts`: a documented, bounded ceiling so a woken-turn read NEVER
  * offloads / blows context, even on a pathological `full`/`ansi` read. An over-cap
- * read is clipped with a `truncations` breadcrumb — never a silent trim (I7).
+ * read is clipped with a `truncations` breadcrumb — never a silent trim.
  */
 export declare const READ_DIGEST_BYTE_CAP = 8192;
 /**
  * The drive read mode. `"digest"` (the default) is the bounded current screen;
  * `"diff"` is only the changed rows since the last wake; `"full"` is the whole
- * screen (opt-in, still byte-capped). Mirrors the `drive.readMode` config enum
- * (plan 05).
+ * screen (opt-in, still byte-capped). Mirrors the `drive.readMode` config enum.
  */
 export type DriveReadMode = "digest" | "diff" | "full";
 /**
  * The bounded read result. `screen` is the selected text (the bounded current
  * screen for `digest`, only the changed rows for `diff`, the whole screen for
- * `full`) AFTER the byte cap. `truncated` is the I7 breadcrumb flag — `true` iff
+ * `full`) AFTER the byte cap. `truncated` is the breadcrumb flag — `true` iff
  * the byte cap clipped the result; `truncations` is the explicit count of dropped
  * bytes (present only when `truncated`). `mode` echoes the selected mode.
  */
 export interface ReadDigest {
     /** The bounded selected text (capped per the mode). */
     screen: string;
-    /** I7 breadcrumb — `true` when the byte cap clipped the result. */
+    /** The truncation breadcrumb — `true` when the byte cap clipped the result. */
     truncated: boolean;
     /** The count of dropped bytes when clipped (the explicit anti-silent-trim breadcrumb). */
     truncations?: number;
@@ -79,14 +77,14 @@ export interface ReadDigest {
     mode: DriveReadMode;
 }
 /**
- * Select + bound the text a woken drive turn should see this wake — READ-01.
+ * Select + bound the text a woken drive turn should see this wake.
  *
  * `"digest"` ⇒ the current `view.screen` (the bounded viewport). `"diff"` ⇒ only the
  * changed rows `[firstChangedRow..lastChangedRow]` of `view.diff` (split on `"\n"`,
  * sliced); `changed:false` ⇒ an empty result; a missing `view.diff` ⇒ a defensive
  * fall-back to the digest. `"full"` ⇒ the screen as-is. EVERY mode then passes
  * through the byte cap, so an over-cap result is clipped with a `truncations`
- * breadcrumb — never a silent trim (I7).
+ * breadcrumb — never a silent trim.
  *
  * Pure + total: never throws on a degenerate view (`{screen:""}`, a missing diff, an
  * out-of-range changed range) — it yields the safe bounded result.
@@ -103,10 +101,10 @@ export declare function boundedReadDigest(view: {
 }, mode: DriveReadMode, byteCap?: number): ReadDigest;
 /**
  * Derive the content-free one-line screen digest the journal stores as
- * `lastScreenDigest` (DRIVE-01 / I3): `"<rows>r <cols>c, <changed> changed,
+ * `lastScreenDigest`: `"<rows>r <cols>c, <changed> changed,
  * cursor@(x,y)"` plus a SHORT (≤ {@link DIGEST_EXCERPT_MAX}-char) excerpt of the
  * first non-empty line. Content-free BY CONSTRUCTION — counts/coords + a short
- * excerpt, NEVER the whole grid (T-164-08). The CALLER (plan 06) runs
+ * excerpt, NEVER the whole grid. The CALLER (the woken-turn driver) runs
  * `scrubSecretsFromText` over the excerpt before it reaches the journal/notification;
  * this function does not redact (it only bounds), per the layer split.
  *

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-read-digest.js

@@ -1,7 +1,6 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * The pure bounded digest/diff read selector (READ-01; design §4 Phase B, §7.1
- * Open-Decision 3 RESOLVED → this plan).
+ * The pure bounded digest/diff read selector.
  *
  * `boundedReadDigest(view, mode, byteCap?)` answers ONE question over a single
  * already-rendered read view (`{screen, diff?}`): what bounded text should a
@@ -22,20 +21,20 @@
  * Every mode passes through {@link capWithBreadcrumb}, modeled on
  * `perceptionScreen`'s bounded tail: an over-cap result is CLIPPED to the cap and
  * carries a `truncations` breadcrumb (the count of dropped bytes) — NEVER a silent
- * trim (I7). The byte cap is {@link READ_DIGEST_BYTE_CAP} (documented like
+ * trim. The byte cap is {@link READ_DIGEST_BYTE_CAP} (documented like
  * `PERCEPTION_RING_TAIL`); the emulator viewport is already `cols×rows`-bounded, so
  * the cap mostly guards a pathological `full`/`ansi` read.
  *
  * `screenDigestLine(view)` derives the content-free one-liner the journal stores as
- * `lastScreenDigest` (DRIVE-01 / I3): `"<rows>r <cols>c, <changed> changed,
+ * `lastScreenDigest`: `"<rows>r <cols>c, <changed> changed,
  * cursor@(x,y)"` plus a SHORT excerpt of the first non-empty line — content-free BY
- * CONSTRUCTION (counts/coords; it never dumps the whole grid, T-164-08). The CALLER
- * (the woken-turn driver, plan 06) runs `scrubSecretsFromText` over the excerpt
+ * CONSTRUCTION (counts/coords; it never dumps the whole grid). The CALLER
+ * (the woken-turn driver) runs `scrubSecretsFromText` over the excerpt
  * before it reaches the journal/notification — the excerpt this module emits is
- * deliberately short, not pre-redacted (redaction is the wiring layer's job, RESEARCH
- * Pattern 4 / Don't Hand-Roll: `scrubSecretsFromText` is the canonical redactor).
+ * deliberately short, not pre-redacted (redaction is the wiring layer's job;
+ * `scrubSecretsFromText` is the canonical redactor — don't hand-roll another).
  *
- * Architecture invariants (binding — AGENTS.md / 124 house style, mirrors
+ * Architecture invariants (binding — AGENTS.md; mirrors
  * `terminal-dialog-detector.ts` / `terminal-settle.ts`'s pure helpers):
  *   - PURE: free functions, NOT factories. NO clock/timer reads, NO module-global
  *     mutable state, NO I/O.
@@ -48,13 +47,13 @@
  * @module
  */
 // ---------------------------------------------------------------------------
-// Bounds (documented constants, the I7 anti-unbounded guarantee).
+// Bounds (documented constants, the anti-unbounded guarantee).
 // ---------------------------------------------------------------------------
 /**
  * The default read-result byte cap. Modeled on `PERCEPTION_RING_TAIL` (8192) in
  * `terminal-render.ts`: a documented, bounded ceiling so a woken-turn read NEVER
  * offloads / blows context, even on a pathological `full`/`ansi` read. An over-cap
- * read is clipped with a `truncations` breadcrumb — never a silent trim (I7).
+ * read is clipped with a `truncations` breadcrumb — never a silent trim.
  */
 export const READ_DIGEST_BYTE_CAP = 8192;
 /** The max excerpt length the content-free `screenDigestLine` carries (a one-liner, not a grid). */
@@ -67,7 +66,7 @@ const DIGEST_EXCERPT_MAX = 80;
  * Under the cap ⇒ verbatim, `truncated:false`, no breadcrumb. Over the cap ⇒ the
  * leading `byteCap` bytes (clipped on a UTF-8 char boundary so we never emit a split
  * multibyte glyph) with `truncated:true` and `truncations` = the count of dropped
- * bytes — the I7 anti-silent-trim breadcrumb. Pure; never throws (a non-positive cap
+ * bytes — the anti-silent-trim breadcrumb. Pure; never throws (a non-positive cap
  * clips to empty with the full byte count as the breadcrumb).
  *
  * Byte-accurate (not `.length`, which counts UTF-16 code units) because the screen is
@@ -90,7 +89,7 @@ function capWithBreadcrumb(text, byteCap) {
     return { screen: head, truncated: true, truncations: totalBytes - keptBytes };
 }
 // ---------------------------------------------------------------------------
-// The READ-01 selector.
+// The read-mode selector.
 // ---------------------------------------------------------------------------
 /**
  * The number of changed rows a {@link SnapshotDiff} spans (inclusive range), or 0
@@ -102,14 +101,14 @@ function changedRowCount(d) {
     return Math.max(0, d.lastChangedRow - d.firstChangedRow + 1);
 }
 /**
- * Select + bound the text a woken drive turn should see this wake — READ-01.
+ * Select + bound the text a woken drive turn should see this wake.
  *
  * `"digest"` ⇒ the current `view.screen` (the bounded viewport). `"diff"` ⇒ only the
  * changed rows `[firstChangedRow..lastChangedRow]` of `view.diff` (split on `"\n"`,
  * sliced); `changed:false` ⇒ an empty result; a missing `view.diff` ⇒ a defensive
  * fall-back to the digest. `"full"` ⇒ the screen as-is. EVERY mode then passes
  * through the byte cap, so an over-cap result is clipped with a `truncations`
- * breadcrumb — never a silent trim (I7).
+ * breadcrumb — never a silent trim.
  *
  * Pure + total: never throws on a degenerate view (`{screen:""}`, a missing diff, an
  * out-of-range changed range) — it yields the safe bounded result.
@@ -155,14 +154,14 @@ export function boundedReadDigest(view, mode, byteCap = READ_DIGEST_BYTE_CAP) {
     };
 }
 // ---------------------------------------------------------------------------
-// The content-free one-line screen digest (the journal's lastScreenDigest, I3).
+// The content-free one-line screen digest (the journal's lastScreenDigest).
 // ---------------------------------------------------------------------------
 /**
  * Derive the content-free one-line screen digest the journal stores as
- * `lastScreenDigest` (DRIVE-01 / I3): `"<rows>r <cols>c, <changed> changed,
+ * `lastScreenDigest`: `"<rows>r <cols>c, <changed> changed,
  * cursor@(x,y)"` plus a SHORT (≤ {@link DIGEST_EXCERPT_MAX}-char) excerpt of the
  * first non-empty line. Content-free BY CONSTRUCTION — counts/coords + a short
- * excerpt, NEVER the whole grid (T-164-08). The CALLER (plan 06) runs
+ * excerpt, NEVER the whole grid. The CALLER (the woken-turn driver) runs
  * `scrubSecretsFromText` over the excerpt before it reaches the journal/notification;
  * this function does not redact (it only bounds), per the layer split.
  *

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-reap-untasked.d.ts

@@ -1,13 +1,12 @@
 /**
- * Deterministic honest-fail backstop for the unattended-drive flub
- * (`WEBHOOK-CLAUDE-AGENT-DRIVE-RELIABILITY`, webhook-claude-cli-tdd-20260701).
+ * Deterministic honest-fail backstop for the unattended-drive flub.
  *
  * The dominant flub: an UNATTENDED (webhook/cron) agent turn creates a `claude` drive, clears the
  * trust gate, but NEVER delivers the task (no `send_text`) — it hallucinates "I don't have a task"
- * and ends the turn. `cb57b96d` already stops that never-tasked drive from BACKGROUNDING (no
- * resurrec-able wake-state); the wait-tool directive ({@link ./terminal-wait-reply}
+ * and ends the turn. The `everTasked` promotion gate already stops that never-tasked drive from
+ * BACKGROUNDING (no resurrec-able wake-state); the wait-tool directive ({@link ./terminal-wait-reply}
  * `WAIT_TASK_NOT_DELIVERED_NOTE`) best-efforts an in-turn recovery — but was LIVE-PROVEN
- * INSUFFICIENT (the model ignores the JIT directive, guard2 run). This is the DETERMINISTIC floor,
+ * INSUFFICIENT (the model ignores the just-in-time directive). This is the DETERMINISTIC floor,
  * model-independent: at an unattended turn-end the caller reaps every LIVE, never-tasked drive the
  * turn left behind, so the origin records an HONEST failure (the webhook route flips
  * `webhook_delivered` success:false) instead of a silent "success" with a leaked idle drive.

package/node_modules/@comis/skills/dist/tools/builtin/terminal-driver/terminal-reaper.d.ts

@@ -1,5 +1,5 @@
 /**
- * The terminal-driver reaper (spec §4.6).
+ * The terminal-driver reaper.
  *
  * Bounds the per-worker/cgroup session footprint with THREE caps, each evicting
  * with an audited reason:
@@ -73,17 +73,17 @@ export interface ReaperDeps {
     /** Called for every eviction with the audited reason — the registry drops + cleans + emits. */
     onEvict: (sessionId: string, reason: EvictReason) => void;
     /**
-     * OPTIONAL alive-and-busy predicate (ENDURE-01 / I9 — the endurance invariant).
+     * OPTIONAL alive-and-busy predicate (the endurance invariant).
      * When supplied, a session the idle sweep would otherwise reap is EXCLUDED while
      * this returns `true`, so a quiet-but-busy multi-hour compile is never killed for
      * its quietness — the load-bearing fix for the documented pitfall that
      * `lastActivity` does NOT advance for a backgrounded drive that quietly compiles
      * (no tool round-trip lands), making a naive lastActivity-only idle sweep evict a
-     * healthy 2h build. The DECISION lives in `terminal-busy-predicate.ts` (165-02,
-     * `busyOrHung(...) === "busy"`); the daemon (165-07) binds it over the session's
+     * healthy 2h build. The DECISION lives in `terminal-busy-predicate.ts`
+     * (`busyOrHung(...) === "busy"`); the daemon binds it over the session's
      * worker progress and injects it here — the reaper stays a thin sweep and the
-     * heuristic stays unit-testable in isolation. ABSENT ⇒ today's behavior (idle
-     * eviction on quietness alone, I1). It gates ONLY the idle branch — the deliberate
+     * heuristic stays unit-testable in isolation. ABSENT ⇒ the plain behavior (idle
+     * eviction on quietness alone). It gates ONLY the idle branch — the deliberate
      * `wall_clock`/`max_interactions` caps are NOT a quietness signal and STILL fire
      * (a named operator bound, not a mystery).
      */
@@ -161,7 +161,8 @@ export interface RegistryReaperWiring<H extends ReaperSessionHandle> {
  * reuses the registry's `evictInternal` (the kill drop + `cleanupSessionWorkspace`,
  * never duplicated), FORGETS the per-session cap state via `onCapForget` (no
  * SessionCaps Map leak on the reap path), emits the audited reason via
- * `onEvict`, and logs a WARN (`hint` + `errorKind: "resource"`, §2.7). The
+ * `onEvict`, and logs a WARN (`hint` + `errorKind: "resource"`, per the AGENTS.md
+ * logging matrix). The
  * `max_interactions` eviction reuses this exact `evict`. The reaper is undefined when
  * `timers`/`maxSessions` are not both provided — `checkOverflow`/`stop` then no-op.
  */