@pellux/goodvibes-tui 2.0.13 → 2.0.15

package/src/runtime/bootstrap.ts

@@ -94,7 +94,7 @@ export type BootstrapContext = RuntimeContext & {
   lastGitInfoRef: { value: GitHeaderInfo | undefined };
   /** Unsubscribe functions owned by bootstrap (cleared on shutdown). */
   bootstrapUnsubs: Array<() => void>;
-  /** Ref holding the periodic agent-status interval (use ref — not local var — to keep shutdown in sync). */
+  /** Ref holding the periodic agent-status interval (use ref, not local var, to keep shutdown in sync). */
   agentStatusIntervalRef: { value: ReturnType<typeof setInterval> | null };
   /** Mutable refs for viewport/scroll/render functions; main.ts patches these after constructing UI state. */
   orchestratorRefs: { getViewportHeight: () => number; scrollToEnd: (vHeight: number) => void; requestRender: () => void };
@@ -198,7 +198,7 @@ export async function bootstrapRuntime(
     panelManager,
     pluginManager,
   } = services;
-  // A saved custom-provider model must never crash boot — see provider-fallback.ts.
+  // A saved custom-provider model must never crash boot, see provider-fallback.ts.
   await ensureBootModelResolvable(providerRegistry, configManager);
 
   // ── Phase 6: Orchestrator + AcpManager ───────────────────────────────────
@@ -241,7 +241,7 @@ export async function bootstrapRuntime(
       logger.debug('companion handleUserInput safety catch', { error: String(err) });
     });
   };
-  // Shared payload (single source of truth, includes the memoryRegistry —
+  // Shared payload (single source of truth, includes the memoryRegistry,
   // see orchestrator-core-services.ts) plus this site's cacheHitTracker.
   orchestrator.setCoreServices({
     ...buildSharedOrchestratorCoreServices({ services, configManager, providerRegistry }),
@@ -311,7 +311,7 @@ export async function bootstrapRuntime(
   const commandContext = shell.commandContext;
   // Boot resume notice (item 1): after rehydrate() so chain history is ready, before
   // the operator can type anything. Fire-and-forget, same as main.ts's non-blocking
-  // `void workspaceCheckpointManager.init().catch(() => {})` — local file I/O only,
+  // `void workspaceCheckpointManager.init().catch(() => {})`, local file I/O only,
   // resolves well before a human can react to the first rendered frame.
   void announceResumeState({
     surface: services.surface,
@@ -321,7 +321,7 @@ export async function bootstrapRuntime(
     memoryAvailable: Boolean(commandContext.clients?.knowledgeApi?.memory),
     router: systemMessageRouter,
   }).catch(() => {
-    // Best-effort — never let the resume notice block or crash boot.
+    // Best-effort, never let the resume notice block or crash boot.
   });
   announceInstallHealth(systemMessageRouter);
   const { gitStatusProvider, inputHistory, lastGitInfoRef } = shell;
@@ -352,7 +352,7 @@ export async function bootstrapRuntime(
   const deferredStartup = createDeferredStartupCoordinator();
 
   // Adopting a daemon: session identity, the inbound steer path, the
-  // cross-surface union read, and the memory spine — see client/spine-adoption.ts.
+  // cross-surface union read, and the memory spine, see client/spine-adoption.ts.
   const syncSessionSpineToHostStatus = createSpineAdoptionSync({
     sessionSpine,
     memorySpine: services.memorySpine,
@@ -384,7 +384,7 @@ export async function bootstrapRuntime(
       httpListenerPortInUse: hostServiceIsBlocked(httpListenerStatus),
       daemonStatus,
       httpListenerStatus,
-      // Honest session-spine posture, independent of daemonRunning — degrades to 'offline'
+      // Honest session-spine posture, independent of daemonRunning, degrades to 'offline'
       // when adopted-but-unreachable even though daemonRunning might still read a stale
       // handle as true; sessionSpine.status() alone is activity-gated, so it's derived
       // together with the union cache's 5s liveness probe (one signal, no new timer).
@@ -396,13 +396,13 @@ export async function bootstrapRuntime(
   // ADOPT ONLY. This app never constructs a DaemonServer or an HttpListener: the
   // daemon is a separate product with its own binary and its own service unit.
   // The factories carry the shared bearer and the daemon's state directory so an
-  // adopted daemon is authenticated the same way it always was — no factory that
+  // adopted daemon is authenticated the same way it always was, no factory that
   // BUILDS anything is passed, and `adoptOnly` makes the SDK refuse to start one
   // even if a future caller did.
   //
   // `daemonRuntimeDir` names the daemon's own STATE directory
   // (`<home>/.goodvibes/daemon`), which is where operator-tokens.json,
-  // auth-users.json and daemon-settings.json live — not the home above it. Every
+  // auth-users.json and daemon-settings.json live, not the home above it. Every
   // reader in this repository resolves it that way.
   const createExternalServiceFactories = (token: string): ExternalServiceFactories => ({
     sharedDaemonToken: token,
@@ -458,7 +458,7 @@ export async function bootstrapRuntime(
   platformExternalServices.externalServices = {
     // The relay is a DAEMON feature and reading an adopted daemon's relay state
     // is a verb this contract does not carry, so these two report 'unavailable'
-    // rather than a state this process is in no position to know — see
+    // rather than a state this process is in no position to know, see
     // relay-reachability-bridge.ts.
     ...relayReadAccessors,
     inspect: inspectExternalServices,
@@ -488,7 +488,7 @@ export async function bootstrapRuntime(
     },
   };
   // Attaching to a daemon settles both build floors and its undelivered
-  // receipts off one /status read — see client/daemon-attach-handshake.ts.
+  // receipts off one /status read, see client/daemon-attach-handshake.ts.
   const daemonHandshake = createDaemonAttachHandshake({
     clientBuildGuard: services.clientBuildGuard,
     readDaemonStatus: () => externalServices.daemonStatus,
@@ -509,8 +509,8 @@ export async function bootstrapRuntime(
       // Plugin loading stays here: a plugin's commands, tools, providers, voice
       // and media providers and embedding providers all reach things a turn
       // needs in THIS process. Three of the eleven registries a plugin can
-      // reach are the daemon's now — gateway methods, channel plugins and
-      // delivery strategies — and a registration into those reaches nothing
+      // reach are the daemon's now, gateway methods, channel plugins and
+      // delivery strategies, and a registration into those reaches nothing
       // from here. No plugin is affected today (none is installed, and this
       // package bundles none); the classification and the open question about
       // where a daemon-side plugin is loaded are recorded in
@@ -549,7 +549,7 @@ export async function bootstrapRuntime(
       const companionTokenRecord = resolveDaemonCompanionToken(daemonHomeDir, GOODVIBES_TUI_SURFACE_ROOT);
       // Fix (TUI 0.19.20): remove stale pre-0.21.28 workspace-scoped operator
       // token files so only the canonical <daemonHomeDir>/operator-tokens.json survives.
-      // The prune is best-effort — it silently skips missing files, no-ops when tokens
+      // The prune is best-effort, it silently skips missing files, no-ops when tokens
       // already match, and records un-deletable candidates in `failedPaths` for logging.
       // See `pruneStaleOperatorTokens` in the SDK for semantics.
       const prune = pruneStaleOperatorTokens({
@@ -710,12 +710,12 @@ export async function bootstrapRuntime(
       runtimeUnsubs.forEach((fn) => fn());
       runtimeUnsubs.length = 0;
       forensicsCollector.dispose();
-      // Honest close on exit — fire-and-forget (never blocks shutdown);
+      // Honest close on exit, fire-and-forget (never blocks shutdown);
       // a no-op when the spine was never activated (embedded/local-only topology).
       sessionSpine.close(runtime.sessionId);
       sessionSpine.dispose();
       sessionInboundInputs.dispose(); sessionUnionCache.dispose(); // stop the inbound-steer poll and the wire-refresh interval on exit
-      // Quitting has to SAY it is leaving: a hosted session's detach policy applies when the LAST client detaches, so an exit that never detaches leaves a kill-policy session (the shipped default) alive, attached to a process that is gone. Bounded and non-throwing — see client/hosted-exit.ts.
+      // Quitting has to SAY it is leaving: a hosted session's detach policy applies when the LAST client detaches, so an exit that never detaches leaves a kill-policy session (the shipped default) alive, attached to a process that is gone. Bounded and non-throwing, see client/hosted-exit.ts.
       await Promise.all([leaveHostedSessionOnExit({ configManager, homeDirectory: services.homeDirectory }), deferredStartup.drain(100)]);
       if (externalServicesPromise) {
         try {

package/src/runtime/client/approval-updates.ts

@@ -1,12 +1,12 @@
 /**
- * approval-updates.ts — this terminal's subscription to approval decisions made
+ * approval-updates.ts, this terminal's subscription to approval decisions made
  * somewhere else.
  *
  * ── What this replaces ────────────────────────────────────────────────────
  *
  * The SDK's client raiser (approval-raiser.ts) raises an ask on the daemon and
  * prompts locally at the same time, and then has to learn about a decision made
- * on another surface — a phone, the web UI, a second terminal. Without a push
+ * on another surface, a phone, the web UI, a second terminal. Without a push
  * channel wired it learns by RE-READING the record on an interval, which is
  * both slower than it needs to be and the thing the `control.approval_update`
  * event exists to end. Wiring this seam makes a remote decision arrive in the
@@ -17,7 +17,7 @@
  * a connection) still has to be able to answer a tool call. `watchApprovalUpdates`
  * reports failure by returning null rather than throwing, and the raiser then
  * behaves exactly as it did before this seam existed. Push is the fast path, not
- * a new dependency — and the raiser's own discipline of doing one immediate read
+ * a new dependency, and the raiser's own discipline of doing one immediate read
  * after subscribing stays intact, because a decision can land between the raise
  * and the subscription and no push channel can deliver what happened before it
  * opened.

package/src/runtime/client/build-floors.ts

@@ -1,5 +1,5 @@
 /**
- * build-floors.ts — the two build floors this terminal and the daemon hold
+ * build-floors.ts, the two build floors this terminal and the daemon hold
  * against each other.
  *
  * ── Forward: the daemon's floor on this client ────────────────────────────
@@ -8,7 +8,7 @@
  * running the build it started with: same rules, same bugs, still registered in
  * the shared session store, still able to execute shared-session work. That is
  * how a behavioral fix can land in the daemon, be verified present in the
- * installed binaries, and still not change what the owner observes — an older
+ * installed binaries, and still not change what the owner observes, an older
  * terminal beside the new daemon simply keeps doing the old thing.
  *
  * So the daemon publishes the minimum client build it will let participate, as
@@ -22,15 +22,15 @@
  * to a daemon it did not start, over a base URL that may point at another
  * machine, and every capability it has is something the daemon performs on its
  * behalf. A verb it depends on may simply not exist in the build that answers,
- * and what the owner sees then is a 400 or a 404 on one call — which reads as a
+ * and what the owner sees then is a 400 or a 404 on one call, which reads as a
  * broken feature rather than as an old daemon. So this terminal declares the
  * oldest daemon build it can work against and checks it on attach against the
  * `version` `/status` already returns, refusing to adopt a daemon below it.
  *
  * ── Where these rules live ────────────────────────────────────────────────
  *
- * Both comparisons — the header name, the verdict shapes, the version ordering
- * — are owned by the SDK (platform/control-plane/client-compatibility.ts and
+ * Both comparisons, the header name, the verdict shapes, the version ordering
+ *, are owned by the SDK (platform/control-plane/client-compatibility.ts and
  * daemon-compatibility.ts) and imported below rather than duplicated. What
  * stays here is this process's own state: the forward latch, the reverse
  * announce-once, and the daemon floor this product declares. The agent holds
@@ -73,7 +73,7 @@ export interface ClientBuildGuardOptions {
  * later read that fails to see the header (a restart, a truncated response)
  * must not silently re-enable work.
  *
- * The notice sink is attached after construction — this guard is built in the
+ * The notice sink is attached after construction, this guard is built in the
  * services composition root, and the surface that renders its one line is wired
  * in the bootstrap tail. A verdict reached before the sink attaches is held and
  * delivered on attach, the same buffered-until-attach idiom the daemon receipt
@@ -134,7 +134,7 @@ export class ClientBuildGuard {
  * the problem once instead of on every poll.
  *
  * Unlatched, unlike the forward guard: a daemon CAN become new enough while
- * this terminal runs — that is exactly what a daemon update does — and the
+ * this terminal runs, that is exactly what a daemon update does, and the
  * attach that sees the newer build must adopt it. What is remembered is only
  * which sentence has already been said.
  */

package/src/runtime/client/daemon-attach-handshake.ts

@@ -1,5 +1,5 @@
 /**
- * daemon-attach-handshake.ts — attaching to a daemon is a handshake, not a
+ * daemon-attach-handshake.ts, attaching to a daemon is a handshake, not a
  * pointer swap.
  *
  * ONE `/status` read carries the three things this terminal has to settle
@@ -8,7 +8,7 @@
  *
  *  - The DAEMON's own build. Every capability here is something the daemon
  *    performs on this terminal's behalf, so a daemon below this build's floor
- *    is refused rather than adopted — otherwise a verb it does not serve
+ *    is refused rather than adopted, otherwise a verb it does not serve
  *    surfaces as one broken feature instead of as an old daemon, and the
  *    terminal keeps running half-working against a peer it has no reason to
  *    suspect. Refused means local-only, which is a state this app already
@@ -17,7 +17,7 @@
  *    and the continuation runner stops taking shared-session work.
  *  - Its undelivered receipts (update applied, restarted after a crash,
  *    settings migrated), read from `/status?receipts=consume` where delivery is
- *    destructive — so the read that consumed them is the read that renders
+ *    destructive, so the read that consumed them is the read that renders
  *    them.
  *
  * Every one of those is decided from the same response, which is why this is
@@ -37,7 +37,7 @@ import { readExternalDaemonAttach } from '../daemon-attach-notices.ts';
 import { ClientBuildGuard, DaemonBuildFloor } from './build-floors.ts';
 
 export interface DaemonAttachHandshakeDeps {
-  /** The forward floor's latch — fed the floor this daemon announces. */
+  /** The forward floor's latch, fed the floor this daemon announces. */
   readonly clientBuildGuard: ClientBuildGuard;
   /** The daemon this terminal is currently pointed at. Re-read on every attach. */
   readonly readDaemonStatus: () => HostServiceStatus;
@@ -89,7 +89,7 @@ export function createDaemonAttachHandshake(deps: DaemonAttachHandshakeDeps): Da
         authToken: daemonToken,
         consumeReceipts: true,
       });
-      // Nothing was read, so nothing is known — adopt as before and leave a
+      // Nothing was read, so nothing is known, adopt as before and leave a
       // daemon that is not answering to the spine's own reachability handling.
       // Refusing on a failed read would turn one dropped request into a lost
       // mirror.

package/src/runtime/client/fleet-union.ts

@@ -1,5 +1,5 @@
 /**
- * fleet-union.ts — the Fleet panel shows everything running, not just what this
+ * fleet-union.ts, the Fleet panel shows everything running, not just what this
  * terminal started.
  *
  * ── What moved to the SDK, and what stays here ────────────────────────────
@@ -15,14 +15,14 @@
  * interface (interrupt/resume/kill/steer/archive, subscribe, snapshots) and
  * `buildFleetSnapshot`, the tree-builder + honest cost/token aggregator this
  * repo's Fleet panel renders from. Rebuilding through the SAME builder the
- * local view uses — rather than summing two halves — is what keeps the
+ * local view uses, rather than summing two halves, is what keeps the
  * rollups, the cost/token totals and the blocked-on-user ordering computed
  * once, over the whole fleet.
  *
  * ── Who wins ──────────────────────────────────────────────────────────────
  *
  * Local rows are AUTHORITATIVE for processes this terminal spawned. They are
- * live — the registry pushes on every state change, with sub-second latency —
+ * live, the registry pushes on every state change, with sub-second latency,
  * and they carry the capabilities that make a row actionable here (interrupt,
  * resume, kill, steer all reach a real child process). The daemon's copy of
  * the same row, arriving over a poll, is necessarily staler; where both
@@ -31,7 +31,7 @@
  * ── Acting on a row you do not own ────────────────────────────────────────
  *
  * `interrupt`/`resume`/`kill`/`steer` reach this process's own children. A
- * daemon row has no child here to signal, so those refuse — and `steer`,
+ * daemon row has no child here to signal, so those refuse, and `steer`,
  * which has a reason channel, says why rather than returning a bare false
  * that reads as "the agent ignored you". The panel's own act surface
  * (fleet-gateway.ts) already drives the daemon's verbs for the acts the
@@ -56,7 +56,7 @@ export { DEFAULT_FLEET_REFRESH_MS, daemonOnlyFleetActRefusal, mergeFleetNodes, r
 export type { DaemonFleetRows, DaemonFleetRowsPoller, DaemonFleetRowsPollerOptions };
 
 export interface FleetUnionOptions {
-  /** This surface's own live registry view — authoritative for what it spawned. */
+  /** This surface's own live registry view, authoritative for what it spawned. */
   readonly local: FleetReadModel;
   readonly verbs: DaemonVerbCaller;
   readonly refreshIntervalMs?: number;
@@ -78,7 +78,7 @@ const SURFACE_LABEL = 'this terminal';
  * daemon's rows, over the SDK's poll/merge/refusal policy.
  *
  * Inert until the first poll lands: before then, and whenever the daemon
- * cannot answer, the snapshot is exactly the local one — which is the honest
+ * cannot answer, the snapshot is exactly the local one, which is the honest
  * answer, not a degraded one. A daemon that stops answering keeps its LAST
  * known rows rather than dropping them (the poller's own retention), so a
  * momentary blip does not make half the fleet blink out and back.
@@ -96,7 +96,7 @@ export function createFleetUnionReadModel(options: FleetUnionOptions): FleetUnio
     for (const listener of listeners) listener();
   });
 
-  /** Ids this surface owns right now — the set the daemon's copy defers to. */
+  /** Ids this surface owns right now, the set the daemon's copy defers to. */
   const localNodeIds = (snapshot: FleetSnapshot): Set<string> =>
     new Set(snapshot.rows.map((row) => row.node.id));
   const isLocalId = (id: string): boolean => localNodeIds(local.getSnapshot()).has(id);

package/src/runtime/client/host-service-status.ts

@@ -1,5 +1,5 @@
 /**
- * host-service-status.ts — reading a background service's posture.
+ * host-service-status.ts, reading a background service's posture.
  *
  * Three questions the composition root asks about the daemon and the webhook
  * listener, none of which need anything from the composition itself: what URL
@@ -61,7 +61,7 @@ export function hostServiceIsActive(status: HostServiceStatus): boolean {
 }
 
 /**
- * The configured port is held and unusable by this terminal — either by an
+ * The configured port is held and unusable by this terminal, either by an
  * unverified process ('blocked') or by a GoodVibes daemon this build refused to
  * adopt ('incompatible': a wire-version mismatch, or a daemon below this
  * build's own floor).

package/src/runtime/client/hosted-exit.ts

@@ -1,12 +1,12 @@
 /**
- * hosted-exit.ts — leaving a hosted session because the terminal is closing.
+ * hosted-exit.ts, leaving a hosted session because the terminal is closing.
  *
  * ── Why this exists at all ────────────────────────────────────────────────
  *
  * The detach policy is applied when the LAST attached client detaches. A
  * terminal that simply exits never detaches: the daemon keeps this window in
- * `attachedClients` forever, so a `kill`-policy session — the shipped default,
- * and the behavior closing a client has always had — would quietly NOT be
+ * `attachedClients` forever, so a `kill`-policy session, the shipped default,
+ * and the behavior closing a client has always had, would quietly NOT be
  * killed, and would sit there attached to a process that no longer exists.
  *
  * That is not a cosmetic gap. The owner's ruling is that the capability lands
@@ -52,7 +52,7 @@ export async function leaveHostedSessionOnExit(
 ): Promise<'none' | 'detached' | 'failed'> {
   const feed = options.feed ?? getSharedHostedSessionFeed();
   const record = feed.getState().record;
-  // Closing the socket is this process's own business and is done either way —
+  // Closing the socket is this process's own business and is done either way,
   // an already-terminated session has nothing to detach from, but the stream
   // watching it is still open.
   feed.closeStream();

package/src/runtime/client/hosted-roster.ts

@@ -1,9 +1,9 @@
 /**
- * hosted-roster.ts — the last answer the daemon gave about what it is hosting.
+ * hosted-roster.ts, the last answer the daemon gave about what it is hosting.
  *
  * The session picker is where a person goes to ask "what sessions are there?",
  * and the honest answer includes conversations running inside the
- * daemon — not only this terminal's saved transcripts and the cross-surface
+ * daemon, not only this terminal's saved transcripts and the cross-surface
  * union. The picker is a synchronous render over modal state, though, and
  * `sessions.hosted.list` is a round trip. This roster is the seam between them:
  * it holds the last list the daemon answered with, refreshes on demand, and
@@ -22,7 +22,7 @@
  * The picker is constructed in the input layer, which has no config manager and
  * no home directory to resolve a daemon from. The composition root
  * (runtime/services.ts) has both and already builds the verb caller, so it binds
- * the client here once — the same shape the shared notification feed uses for a
+ * the client here once, the same shape the shared notification feed uses for a
  * surface that two unrelated layers read.
  */
 import type { HostedSessionRecord, HostedSessionsClient } from './hosted-sessions.ts';
@@ -64,7 +64,7 @@ export class HostedSessionRoster {
   }
 
   /**
-   * Ask the daemon again. Never throws and never runs twice at once — a picker
+   * Ask the daemon again. Never throws and never runs twice at once, a picker
    * opened repeatedly must not stack round trips.
    */
   async refresh(): Promise<void> {

package/src/runtime/client/hosted-session-stream.ts

@@ -1,17 +1,17 @@
 /**
- * hosted-session-stream.ts — watching a conversation that is running somewhere
+ * hosted-session-stream.ts, watching a conversation that is running somewhere
  * else.
  *
  * A hosted session's loop is the ORDINARY Orchestrator, composed inside the
- * daemon. So it emits exactly what a local turn emits — STREAM_DELTA, tool
- * starts, tool results, turn transitions — on the `turn` and `tools` runtime
+ * daemon. So it emits exactly what a local turn emits, STREAM_DELTA, tool
+ * starts, tool results, turn transitions, on the `turn` and `tools` runtime
  * domains, and the control-plane forwards those domains to any subscriber with
  * the session id stamped on every envelope. There is no hosted-only token
  * stream to consume and this file does not invent one: it opens the same event
  * stream a client already uses and keeps the frames whose id matches the
  * session it was told to watch.
  *
- * The third domain is `session`, which carries `hosted-session-update` — the
+ * The third domain is `session`, which carries `hosted-session-update`, the
  * lifecycle channel: created, attached, detached, turn started, turn ended,
  * terminated, restored. That is how an attached terminal learns its session was
  * killed from another surface, or that a turn started that it did not begin.
@@ -114,7 +114,7 @@ export function readHostedLifecycleNotice(payload: unknown): HostedSessionUpdate
  *
  * Resolves to null when the stream could not be opened; the reason is logged
  * once rather than thrown into a keystroke path, and the caller keeps whatever
- * it had (the verbs still work — the conversation is simply not being watched).
+ * it had (the verbs still work, the conversation is simply not being watched).
  */
 export async function watchHostedSession(
   options: WatchHostedSessionOptions,

package/src/runtime/client/hosted-sessions.ts

@@ -1,5 +1,5 @@
 /**
- * hosted-sessions.ts — this terminal's handle on a conversation the DAEMON runs.
+ * hosted-sessions.ts, this terminal's handle on a conversation the DAEMON runs.
  *
  * A local session's loop lives in this process: the orchestrator, the tools and
  * the permission gate are all here, and closing the terminal ends the work. A
@@ -18,7 +18,7 @@
  *
  * It is not the stream. The hosted loop is the ordinary Orchestrator, so its
  * tokens, tool calls and turn transitions arrive on the `turn` and `tools`
- * event domains stamped with the hosted session's id — see
+ * event domains stamped with the hosted session's id, see
  * hosted-session-stream.ts, which watches exactly what a local session watches
  * and filters on the id `attach` handed back.
  *
@@ -27,7 +27,7 @@
  * Every `sessions.hosted.*` verb is declared `transport: ['ws']` with no REST
  * path of its own, so `sdk.operator.invoke` refuses them before making a
  * request. `createDaemonVerbCaller` (operator-endpoint.ts) already handles that
- * exact class by falling through to the generic gateway route — which IS the
+ * exact class by falling through to the generic gateway route, which IS the
  * binding for a ws-declared verb reached over HTTP.
  */
 import { hostname } from 'node:os';
@@ -59,7 +59,7 @@ export interface HostedSessionAttachment {
  * terminals on one machine, because the detach policy is applied when the LAST
  * client leaves: two windows sharing one id would make the first `detach` look
  * like the last one. Host + pid is both, and it is readable in
- * `attachedClients` — a person reading the record can tell which terminal that
+ * `attachedClients`, a person reading the record can tell which terminal that
  * is.
  */
 let cachedClientId: string | null = null;
@@ -70,18 +70,18 @@ export function terminalHostedClientId(): string {
 
 /** The narrow client the command layer and the panel share. */
 export interface HostedSessionsClient {
-  /** This terminal's attach identity — the same string the records carry. */
+  /** This terminal's attach identity, the same string the records carry. */
   readonly clientId: string;
   list(options?: { readonly includeTerminated?: boolean }): Promise<readonly HostedSessionRecord[]>;
   create(input: Omit<CreateHostedSessionInput, 'clientId'>): Promise<HostedSessionRecord>;
   attach(sessionId: string): Promise<HostedSessionAttachment>;
   detach(sessionId: string): Promise<HostedSessionRecord>;
   kill(sessionId: string): Promise<HostedSessionRecord>;
-  /** Send a message into a running hosted session — the ordinary steer verb. */
+  /** Send a message into a running hosted session, the ordinary steer verb. */
   steer(sessionId: string, body: string): Promise<void>;
-  /** Queue a message for after the current turn — the ordinary follow-up verb. */
+  /** Queue a message for after the current turn, the ordinary follow-up verb. */
   followUp(sessionId: string, body: string): Promise<void>;
-  /** Cancel one in-flight tool call — the ordinary live-turn verb. */
+  /** Cancel one in-flight tool call, the ordinary live-turn verb. */
   cancelToolCall(sessionId: string, callId: string): Promise<boolean>;
 }
 

package/src/runtime/client/operator-endpoint.ts

@@ -1,19 +1,19 @@
 /**
- * operator-endpoint.ts — the one place this product resolves "the daemon I talk
+ * operator-endpoint.ts, the one place this product resolves "the daemon I talk
  * to", for every seam that talks to it.
  *
  * The terminal app is a pure client: it runs its own conversation loop and asks
  * a separately-running daemon for everything else. Every one of those asks is
  * an operator verb over HTTP, and every one of them needs the same three
- * things — is the daemon enabled, what base URL does it answer on, and what
+ * things, is the daemon enabled, what base URL does it answer on, and what
  * bearer token proves this surface may call it. Resolving that in each seam is
  * how the old composition ended up with a DirectTransport in one place and a
  * real fetch in another.
  *
  * `resolveOperatorRpc` was previously the command layer's private helper
  * (input/commands/operator-rpc.ts). It moved here unchanged in behaviour so the
- * runtime seams — approvals, config, credentials, sessions, fleet, tasks,
- * devices, checkpoints — reach the daemon through the SAME resolution the
+ * runtime seams, approvals, config, credentials, sessions, fleet, tasks,
+ * devices, checkpoints, reach the daemon through the SAME resolution the
  * commands already used, and the command module now re-exports it.
  *
  * Refusals are values, never throws: a disabled daemon or an underivable base
@@ -25,7 +25,7 @@
  * Auth is the loopback file-token bootstrap: the token
  * is read (or minted) from the daemon's own state directory. A daemon on
  * another machine is reached by the network-adopt path, which writes that
- * daemon's bearer into the same file — so this resolution covers both.
+ * daemon's bearer into the same file, so this resolution covers both.
  */
 import { join } from 'node:path';
 import { createGoodVibesSdk } from '@pellux/goodvibes-sdk';
@@ -77,7 +77,7 @@ export function resolveControlPlaneBaseUrl(configManager: ConfigManager): string
   return null;
 }
 
-/** The daemon's own state directory — where the shared bearer token lives. */
+/** The daemon's own state directory, where the shared bearer token lives. */
 export function resolveDaemonStateDirectory(homeDirectory: string): string {
   return join(homeDirectory, '.goodvibes', 'daemon');
 }
@@ -85,14 +85,14 @@ export function resolveDaemonStateDirectory(homeDirectory: string): string {
 /**
  * Resolve (or honestly refuse to resolve) an operator SDK client wired to this
  * workspace's control-plane daemon, from just the two things the resolution
- * actually needs — the config manager and the home directory.
+ * actually needs, the config manager and the home directory.
  */
 export function resolveOperatorRpc(deps: {
   readonly configManager: ConfigManager;
   readonly homeDirectory: string | (() => string);
 }): OperatorRpc {
   const { configManager } = deps;
-  // A refusal is a VALUE here, never a throw — that is the whole contract of
+  // A refusal is a VALUE here, never a throw, that is the whole contract of
   // this function, and callers rely on it to print an honest line rather than
   // crash a keystroke. A context whose config manager cannot answer (a narrow
   // embed, a partially-wired test double) is one more case of "no daemon can be
@@ -101,13 +101,13 @@ export function resolveOperatorRpc(deps: {
     return { available: false, reason: 'no config manager is wired here, so no control-plane daemon can be resolved.' };
   }
   if (!resolveDaemonEnabled(configManager)) {
-    return { available: false, reason: 'the daemon is disabled (daemon.enabled=false) — no operator surface to reach. Enable it in /settings, then retry.' };
+    return { available: false, reason: 'the daemon is disabled (daemon.enabled=false): no operator surface to reach. Enable it in /settings, then retry.' };
   }
   const baseUrl = resolveControlPlaneBaseUrl(configManager);
   if (!baseUrl) {
-    return { available: false, reason: 'no control-plane base URL is configured (controlPlane.publicBaseUrl / controlPlane.host+port) — cannot reach the operator surface.' };
+    return { available: false, reason: 'no control-plane base URL is configured (controlPlane.publicBaseUrl / controlPlane.host+port): cannot reach the operator surface.' };
   }
-  // Resolve the home directory only AFTER the static refusals — a caller whose
+  // Resolve the home directory only AFTER the static refusals, a caller whose
   // shell paths are not wired (a disabled-daemon path) must still get the honest
   // unavailable reason above, never a "shell paths not wired" throw.
   const homeDirectory = typeof deps.homeDirectory === 'function' ? deps.homeDirectory() : deps.homeDirectory;
@@ -124,7 +124,7 @@ export function resolveOperatorRpc(deps: {
 export function describeOperatorRpcError(error: unknown): string {
   if (error instanceof GoodVibesSdkError) {
     if (error.status === 404) {
-      return 'the connected daemon returned 404 — this operator verb is not wired up on that daemon yet.';
+      return 'the connected daemon returned 404; this operator verb is not wired up on that daemon yet.';
     }
     if (error.status === 401 || error.status === 403) {
       return `the connected daemon rejected the request (${error.status}): ${error.message}`;
@@ -139,8 +139,8 @@ export function describeOperatorRpcError(error: unknown): string {
  * WEBSOCKET binding only.
  *
  * This matters more than it looks. `sdk.operator.invoke` resolves a method's
- * declared `http` route and refuses — with a contract error, before any request
- * is made — when the method has none. A large part of what this client needs is
+ * declared `http` route and refuses, with a contract error, before any request
+ * is made, when the method has none. A large part of what this client needs is
  * exactly that class: `approvals.raise`, `credentials.set`/`delete`,
  * `checkpoints.*`, `rewind.*` and the `fleet.*` reads are all `transport: ws`
  * in the operator contract, with no REST path of their own.

package/src/runtime/client/spine-adoption.ts

@@ -1,15 +1,15 @@
 /**
- * spine-adoption.ts — wiring this surface's session and memory spines to the
+ * spine-adoption.ts, wiring this surface's session and memory spines to the
  * daemon it adopted, over the SDK's adoption policy.
  *
  * ── What moved to the SDK, and what stays here ────────────────────────────
  *
  * The SDK's `@pellux/goodvibes-sdk/platform/runtime/client` now owns WHEN the
  * wire comes up and goes down: idempotent per base URL, torn down on a
- * change, the one-time legacy-store fold. This module owns WHAT the wire is —
+ * change, the one-time legacy-store fold. This module owns WHAT the wire is,
  * this terminal's own `createHttpTransport` + `createTuiSpineTransport` +
  * `createTuiMemorySpineTransport`, injected as the SDK's `connect(baseUrl,
- * authToken)` callback — because building the actual HTTP client is the same
+ * authToken)` callback, because building the actual HTTP client is the same
  * connection-resolution concern the verb caller already keeps product-side.
  *
  * `activation: 'adopt-on-status'` is passed explicitly: this terminal gates
@@ -20,19 +20,19 @@
  * ── What crosses the wire ──────────────────────────────────────────────────
  *
  * Session IDENTITY, not session execution. The conversation itself runs here;
- * what the daemon holds is the register —
+ * what the daemon holds is the register,
  * which sessions exist, which surface is live on each, and the inputs queued
  * against them. Concretely, on adoption this wires:
  *
- *   - `sessions.register` / `sessions.close` — the identity mirror, deliberately
+ *   - `sessions.register` / `sessions.close`, the identity mirror, deliberately
  *     fire-and-forget so a slow daemon never shows up in a keystroke.
- *   - `sessions.inputs.list` / `sessions.inputs.deliver` — the inbound steer
+ *   - `sessions.inputs.list` / `sessions.inputs.deliver`, the inbound steer
  *     path, so a message another surface queued for THIS session lands in the
  *     turn machinery here and is acknowledged on the wire.
- *   - `sessions.list` — the cross-surface union the panels read, interval-
+ *   - `sessions.list`, the cross-surface union the panels read, interval-
  *     refreshed and served synchronously.
  *   - the memory spine's wire transport, folded into the same handler by the
- *     SDK — this module's own `syncMemorySpineToHostStatus` call is retired;
+ *     SDK, this module's own `syncMemorySpineToHostStatus` call is retired;
  *     supplying `memoryTransport` in the bundle and `memorySpine` in the
  *     options is what activates it now.
  *