@pellux/goodvibes-daemon 1.28.19 → 1.28.20

package/src/runtime/services.ts

@@ -60,7 +60,7 @@ import { createDevicePostureServices } from './device-posture-composition.ts';
 // Re-exported so the daemon entrypoint reaches the housekeeping sweep through
 // the same module it already imports the runtime graph from. `installDevicePosture`
 // is deliberately NOT re-exported: it registers the phone TOOL into a tool
-// registry, and the daemon registers no tools — the sweep is the half it needs.
+// registry, and the daemon registers no tools, the sweep is the half it needs.
 export { startDeviceHousekeeping } from './device-posture-composition.ts';
 import { createClusterServices, startClusterServices } from './cluster-group-composition.ts';
 import { createWorkspaceTrustDecisionAsk, trustGatedApprovalRaiser } from './trust/trust-gated-approvals.ts';
@@ -69,7 +69,7 @@ import type { RuntimeServicesOptions, RuntimeServices } from './runtime-services
 export type { RuntimeServicesOptions, RuntimeServices } from './runtime-services-types.ts';
 
 /**
- * createRuntimeServices — the daemon's service graph.
+ * createRuntimeServices, the daemon's service graph.
  *
  * This is the one composition root the daemon has. Capabilities a client and
  * the daemon both need live in the SDK and are composed from there (memory
@@ -81,7 +81,7 @@ export type { RuntimeServicesOptions, RuntimeServices } from './runtime-services
  */
 export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeServices {
   // The SDK's disposal scope and its all-required poller list, plus the four
-  // pollers only the daemon has — see disposal-wiring.ts.
+  // pollers only the daemon has, see disposal-wiring.ts.
   const disposalScope = createDisposalScope('RuntimeServices');
   const workingDirectory = options.workingDir;
   const homeDirectory = options.homeDirectory;
@@ -105,7 +105,7 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
   // so the scheduler gates and the knowledge background jobs can consult the pause
   // controller before the MemoryGovernor (constructed at the composition tail)
   // drives it. The admission gate is late-bound: expensive entry points capture
-  // this closure now and the governor binds into it at the tail — until then
+  // this closure now and the governor binds into it at the tail, until then
   // everything is admitted (the daemon is still booting).
   const cacheRegistry = new CacheRegistry();
   const pauseController = new PauseController();
@@ -149,7 +149,7 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
   // Launch-tolerant: a provider whose API key is absent from the environment is
   // constructed with a placeholder that is stripped immediately afterwards, so
   // it lands unconfigured instead of throwing during construction. The daemon
-  // has the same must-boot property the agent has — it is a supervised service,
+  // has the same must-boot property the agent has, it is a supervised service,
   // and a constructor that throws on a missing key turns one unset variable into
   // a crash loop with no screen to explain it.
   const providerRegistry = createLaunchTolerantProviderRegistry({
@@ -186,8 +186,8 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
   );
   const hookActivityTracker = new HookActivityTracker();
   // featureFlags is REQUIRED here in practice, even though the SDK types it
-  // optional. isFeatureGateEnabled(null, ...) is permissive by design — a narrow
-  // embed with no manager wired gets the capability rather than a silent off —
+  // optional. isFeatureGateEnabled(null, ...) is permissive by design, a narrow
+  // embed with no manager wired gets the capability rather than a silent off,
   // so omitting it did not disable the watcher framework when watchers.enabled
   // is turned off; it made the setting configure nothing.
   const watcherRegistry = new WatcherRegistry({
@@ -235,9 +235,9 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
       task,
       // Conversation first: a follow-up message in a session gets an answer, not
       // a write-review-fix-confirm chain with a reviewer, quality gates and a
-      // second agent. A chain opens only for an explicit authorization marker —
+      // second agent. A chain opens only for an explicit authorization marker,
       // the channel confirmation the owner gave, or the schedule/trigger that
-      // was confirmed when it was created — or for a follow-up typed on a local
+      // was confirmed when it was created, or for a follow-up typed on a local
       // surface. Both `conversationGate.mode` and the gated-surfaces list are
       // read live.
       ...continuationChainOptions(input, {
@@ -256,7 +256,7 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
       // It also supplies the run's context, which is why the bare
       // `context: shared-session:<id>` line that used to sit below is gone.
       // Spread BEFORE the routing builder so an explicit tool list coming from
-      // a routing intent still wins — that builder emits `tools` only when it
+      // a routing intent still wins, that builder emits `tools` only when it
       // actually has one.
       ...conversationalTurnSpawnOptions(input, { configReader: configManager }),
       // Spawn routing through the SDK's shared model-reference resolver
@@ -286,7 +286,7 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
     // through. Without the secrets manager it cannot resolve a
     // goodvibes://secrets/... credential, so Telegram accepted every inbound
     // message and dropped every reply with "Missing Telegram bot token" while
-    // ntfy — which needs no secret — worked.
+    // ntfy, which needs no secret, worked.
     secretsManager,
     serviceRegistry,
     runtimeBus: options.runtimeBus,
@@ -326,7 +326,7 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
       return record.id;
     },
   });
-  // Knowledge/wiki + home-graph stack (governor backpressure wired in) — see knowledge-services.ts.
+  // Knowledge/wiki + home-graph stack (governor backpressure wired in), see knowledge-services.ts.
   const {
     knowledgeStore, agentKnowledgeStore, homeGraphKnowledgeStore,
     knowledgeSemanticService, homeGraphSemanticService, agentKnowledgeSemanticService,
@@ -382,19 +382,21 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
   });
 
   // Which machines on this network are "us", and which of them reads the shared
-  // inbox. Both inert until startCluster() — no socket, no key material read;
+  // inbox. Both inert until startCluster(), no socket, no key material read;
   // see cluster-group-composition.ts for why they are built together.
   const { clusterGroup, clusterCoordinator } = createClusterServices({
     configManager, shellPaths, secretsManager,
   });
   // Daemon handler surfaces (see daemon-handler-composition.ts); the inbox
-  // poller registers itself with the coordinator rather than starting eagerly.
+  // poller registers itself with the coordinator rather than starting eagerly,
+  // and the payments family stops being a cataloged 501 facade there.
   const daemonHandlers = createDaemonHandlerComposition({
     gatewayMethods,
     secretsManager,
     configManager,
     workingDirectory,
     homeDirectory,
+    shellPaths,
     distributedRuntime,
     clusterCoordinator,
   });
@@ -427,7 +429,7 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
   // ONE router, not two. This was a second ChannelDeliveryRouter built from the
   // same four arguments AutomationDeliveryManager builds its own from, so the
   // router the gateway verbs held and the router replies actually leave through
-  // were different objects — and a delivery strategy registered on one was
+  // were different objects, and a delivery strategy registered on one was
   // invisible to the other. The manager's is the one that replies; it is the one.
   const channelDeliveryRouter = deliveryManager.getDeliveryRouter();
   const processManager = new ProcessManager();
@@ -447,7 +449,7 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
   });
   const codeInjectionOrchestratorDeps = { codeIndex: codeIndexStore, isCodeInjectionSettingEnabled: () => isCodeInjectionSettingEnabled(configManager), codeIndexReindexScheduler };
   // The trigger family: stream watchers, on-exit process triggers, condition
-  // checks — fed to the fleet below as its trigger supervisor, so a trigger
+  // checks, fed to the fleet below as its trigger supervisor, so a trigger
   // is visible and steerable like every other running thing.
   const triggerManager = createTriggerServices({
     configManager, shellPaths, surfaceRoot: GOODVIBES_DAEMON_SURFACE_ROOT,
@@ -477,7 +479,7 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
     acpHost, // Folds live hosted-agent sessions into the fleet as 'acp' rows
   });
   const modeManager = new ModeManager({ featureFlags }); const fileUndoManager = new FileUndoManager();
-  // Checkpoints, gated on live workspace registration — see workspace-checkpointing.ts.
+  // Checkpoints, gated on live workspace registration, see workspace-checkpointing.ts.
   const checkpointing = createWorkspaceCheckpointing({
     workspaceRoot: workingDirectory, surface, runtimeBus: options.runtimeBus, configManager, shellPaths,
   });
@@ -487,7 +489,7 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
   // admitted (mirrors the SDK's own createRuntimeServices idle gate).
   const { memoryConsolidationScheduler, powerManager, sessionLiveTurnControls } = wireIdlePowerAndLiveTurn({ configManager, memoryRegistry, runtimeBus: options.runtimeBus, isIdle: () => sessionBroker.countBusySessions() === 0 && !pauseController.isPaused('memory-consolidation') && admitExpensiveWork('memory consolidation').allowed, snapshotTick: () => storeSnapshotScheduler.tick(), heartbeat: async () => { await automationManager.triggerHeartbeat({ source: 'wake-catchup' }); }, powerSeam: options.powerSeam });
 
-  // Construct + start the MemoryGovernor (default ON — a safety feature) with the
+  // Construct + start the MemoryGovernor (default ON, a safety feature) with the
   // standard KNOWN cache adapters (knowledge stores + shared session broker),
   // then late-bind the admission gate the expensive entry points captured
   // earlier. The SDK owns this wiring.
@@ -514,7 +516,7 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
   });
   admitExpensiveWorkRef.current = (label) => memoryGovernor.admitExpensiveWork(label);
 
-  // Managed local-voice provisioning (voice.local.status/install) — single-flight
+  // Managed local-voice provisioning (voice.local.status/install), single-flight
   // one-act install + no-network status.
   const { voiceSetup, stopWakeHousekeeping } = wireVoiceSetup({ configManager, shellPaths, voiceProviders, admitExpensiveWork,
     // Boot provisioning of the wake-word model + its recovery sweep, opted into
@@ -543,11 +545,11 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
     // to the owner principal instead of unknown.
     channelPolicy,
     approvalBroker, requestApproval: (input) => approvalBroker.requestApproval(input),
-    // approvals.raise — a surface CREATING an ask in this broker. Without it the
+    // approvals.raise, a surface CREATING an ask in this broker. Without it the
     // verb is cataloged and unhandled, and a client whose prompt runs outside
     // this process has no way to raise one.
     approvalRaise: approvalBroker,
-    // credentials.set / credentials.delete — a credential written THROUGH the
+    // credentials.set / credentials.delete, a credential written THROUGH the
     // control plane, so a client with no access to the daemon's settings file can
     // configure one. The value lands in the daemon's secret tier and the verb
     // never echoes it back.
@@ -573,15 +575,15 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
   const execPromptAnswerHandler = buildExecPromptAnswerHandler({ requestApproval: (input) => approvalBroker.requestApproval(input) });
   // Tool asks from the runs this daemon HOSTS. Without a manager here, the
   // background permission gate short-circuits to approved and every hosted
-  // write, command and delegation ran ungated — the workspace trust decision
+  // write, command and delegation ran ungated, the workspace trust decision
   // was read by nobody in this process.
   //
   // The ask seam is the trust gate wrapping the approval broker: a workspace
   // with no decision yet has the question raised as an approval record and
-  // answered by whichever surface is attached (trust-gated-approvals.ts) —
+  // answered by whichever surface is attached (trust-gated-approvals.ts),
   // there is no screen here to show a modal on, so the raise replaces it. The
-  // manager's own layers — permission mode, policy, session cache, durable
-  // user rules — still run first and are unchanged.
+  // manager's own layers, permission mode, policy, session cache, durable
+  // user rules, still run first and are unchanged.
   const permissionManager = createBrokeredPermissionManager({
     requestApproval: trustGatedApprovalRaiser(
       workspaceTrustManager,
@@ -648,7 +650,7 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
   // whole high-churn 'ops' domain, and sent over the SAME WebhookNotifier the
   // notification verbs keep live and boot-tasks attaches to the bus. There is
   // no panel notification router here: its targets are all screen targets and
-  // this product has no screen — see notification-dispatch.ts.
+  // this product has no screen, see notification-dispatch.ts.
   wireMemoryPressureChannelNotice(options.runtimeBus, webhookNotifier);
 
   // In-process config changes become key-level events on the `config` domain, so
@@ -780,7 +782,7 @@ export function createRuntimeServices(options: RuntimeServicesOptions): RuntimeS
     // Cancels the agent runs this graph was hosting. By dispose() time the fleet
     // registry, orchestration engine, process registry and bus these runs report
     // through are already down, so a run still described as "running" is orphaned
-    // rather than preserved — and this is the only shutdown-reachable way to
+    // rather than preserved, and this is the only shutdown-reachable way to
     // abort its in-flight provider call instead of letting it sleep out a retry
     // backoff nobody is waiting on.
     cancelHostedAgentRuns: () => cancelAllAgentRuns(agentManager),

package/src/runtime/trigger-services.ts

@@ -11,7 +11,7 @@ import type { ShellPathService } from '@/runtime/index.ts';
  *
  * This daemon composes the full family and feeds the manager to the fleet as
  * its trigger supervisor, so a trigger defined against the daemon fires
- * reliably. The daemon is the right process to own it — it is the one that
+ * reliably. The daemon is the right process to own it, it is the one that
  * stays running.
  *
  * Two things about the shape are load-bearing:

package/src/runtime/trust/checkpoint-eligibility.ts

@@ -23,7 +23,7 @@ import {
  *
  * This read is synchronous by design. The decision is made per lifecycle event,
  * inside a subscription callback that cannot await, and it has to reflect the
- * store as it is on disk RIGHT NOW — registering a workspace while the daemon is
+ * store as it is on disk RIGHT NOW, registering a workspace while the daemon is
  * running has to take effect on the next eligible event, not on the next
  * restart. The SDK's resolver is pure, so the only I/O is one small JSON read
  * plus a single git worktree probe amortized at construction.
@@ -32,13 +32,13 @@ import {
 export type StoreShellPaths = Pick<ShellPathService, 'resolveUserPath' | 'homeDirectory'>;
 
 /**
- * Path of the shared store's JSON document — the same path the SDK's gateway
+ * Path of the shared store's JSON document, the same path the SDK's gateway
  * verb group constructs its own store over.
  *
  * "The same path" is the whole contract, and it is why this goes through the
  * SDK's resolver rather than spelling any location out. goodvibes-agent reads
  * and writes this same file directly and the SDK's gateway writes it, so the
- * register is cross-product state rather than the daemon's own — it lives in
+ * register is cross-product state rather than the daemon's own, it lives in
  * the shared tier (~/.goodvibes/shared/), which takes no surface root, so all
  * three resolve one identical path. Until the boot fold has moved it, the
  * resolver falls back to the pre-split location read-only, so this reader never
@@ -92,7 +92,7 @@ interface SharedRegistrationSnapshot {
 /**
  * Synchronous read of the shared store's on-disk JSON, mirroring the store's own
  * validation exactly (version 1, workspaces[], declines[]). A missing or
- * unparsable file reads as empty — never throws.
+ * unparsable file reads as empty, never throws.
  */
 export function readSharedWorkspaceRegistrationSnapshotSync(shellPaths: StoreShellPaths): SharedRegistrationSnapshot {
   const path = sharedWorkspaceRegistrationStorePath(shellPaths);
@@ -116,7 +116,7 @@ export function readSharedWorkspaceRegistrationSnapshotSync(shellPaths: StoreShe
 }
 
 /**
- * Resolve `path` against ONLY the checkpoint-eligible registrations — the
+ * Resolve `path` against ONLY the checkpoint-eligible registrations, the
  * boundary the automatic and explicit checkpoint gates consume. Worktree-link
  * inheritance still applies: a linked worktree of a checkpoint-eligible main
  * repository resolves as covered.

package/src/runtime/trust/trust-gated-approvals.ts

@@ -1,11 +1,11 @@
 /**
- * trust-gated-approvals.ts — how a headless daemon asks the workspace trust
+ * trust-gated-approvals.ts, how a headless daemon asks the workspace trust
  * question, and how the answer reaches the runs it hosts.
  *
  * The terminal app composes the trust gate at the permission machinery's final
  * ask layer and raises the question as a modal on its own screen. The daemon
- * has the same gate — `trustGatedAsk` next door, reading the same
- * `<cwd>/.goodvibes/<surface>/trust.json` the terminal app writes — and no
+ * has the same gate, `trustGatedAsk` next door, reading the same
+ * `<cwd>/.goodvibes/<surface>/trust.json` the terminal app writes, and no
  * screen to raise anything on. Before this module it therefore
  * did neither: the gate was constructed, never loaded, never consulted, and no
  * hosted run passed through it.
@@ -16,7 +16,7 @@
  *     ordinary approval record. That is the whole point of the approval-raise
  *     path: a process with no screen states the question, publishes it on
  *     `approval-update`, and whichever surface is attached answers it. Approved
- *     means "trusted", denied means "restricted" — a real decision either way,
+ *     means "trusted", denied means "restricted", a real decision either way,
  *     persisted by the gate, and never asked again for this workspace.
  *
  *  2. `trustGatedApprovalRaiser` puts the gate in front of the raiser the
@@ -30,8 +30,8 @@
  *
  * What the daemon does NOT do here is decide by default. An untrusted
  * workspace's hosted run neither runs as if trusted nor fails as if refused: it
- * asks. If the ask cannot be answered — nothing attached, or the broker itself
- * failed — the workspace stays undecided and this run is refused, with the
+ * asks. If the ask cannot be answered, nothing attached, or the broker itself
+ * failed, the workspace stays undecided and this run is refused, with the
  * reason in the log rather than in a silence. A refusal that records nothing is
  * the failure mode this whole seam exists to remove.
  */
@@ -44,7 +44,7 @@ type WorkspaceTrustLevel = operations.WorkspaceTrustLevel;
 type WorkspaceTrustManager = operations.WorkspaceTrustManager;
 
 /**
- * The extra fields a raise carries beside the request itself — the attribution
+ * The extra fields a raise carries beside the request itself, the attribution
  * routing/metadata a background-agent ask is stamped with before it reaches the
  * broker. The gate only reads `request.category`, so these ride around it.
  */
@@ -73,7 +73,7 @@ export const WORKSPACE_TRUST_ASK_TIMEOUT_MS = 10 * 60 * 1000;
 
 export interface WorkspaceTrustDecisionAskDeps {
   readonly requestApproval: ApprovalRaise;
-  /** The workspace the question is about — it names the directory being trusted. */
+  /** The workspace the question is about, it names the directory being trusted. */
   readonly workingDirectory: string;
   readonly timeoutMs?: number | undefined;
 }
@@ -118,7 +118,7 @@ export function createWorkspaceTrustDecisionAsk(
       return decision.approved ? 'trusted' : 'restricted';
     } catch (error) {
       // Nothing attached, or the broker failed. Say so and leave the workspace
-      // undecided — the next run asks again rather than inheriting a decision
+      // undecided, the next run asks again rather than inheriting a decision
       // nobody made.
       logger.warn('Workspace trust question could not be answered; this run is refused and the workspace stays undecided', {
         workspace: deps.workingDirectory,

package/src/runtime/update-check.ts

@@ -4,7 +4,7 @@
  *
  * Version comparison and the release-tag lookup are re-exported from the
  * SDK's canonical update policy module (platform/runtime/self-update), which
- * was hoisted from this file's semantics — one mechanism everywhere.
+ * was hoisted from this file's semantics, one mechanism everywhere.
  * Install-kind detection stays local: it encodes how THIS package is
  * installed (compiled binary vs bun/npm package vs source run) and what
  * command replaces a swap for each kind.
@@ -27,14 +27,14 @@ export {
  * How this running process was installed, detected honestly from
  * process.execPath rather than assumed:
  *   - "binary": a standalone `bun build --compile` executable with no
- *     package-manager ancestry — the scripts/install.sh install path.
+ *     package-manager ancestry, the scripts/install.sh install path.
  *     Swappable in place.
  *   - "bun-global-package": running the vendored binary shipped inside an
  *     npm/bun-managed package install (execPath contains a "node_modules"
- *     path segment — true for both `bun add -g` and a local project
+ *     path segment, true for both `bun add -g` and a local project
  *     dependency). Managed by the package manager; swapping the vendored
  *     file in place would fight the next `bun add -g` upgrade, so this is
- *     never swapped — the user re-runs their package manager instead.
+ *     never swapped, the user re-runs their package manager instead.
  *   - "source": running directly via the `bun` interpreter (`bun run
  *     src/main.ts`), not a compiled binary at all.
  */

package/src/runtime/workspace-checkpointing.ts

@@ -17,19 +17,19 @@ import { createWorkspaceRegistrationLiveChecker, type StoreShellPaths } from './
  * runtime bus, so building it without one for an unregistered workspace would
  * mean registering that workspace mid-run had no effect until a restart. It is
  * always built WITH the bus and each individual automatic snapshot attempt is
- * refused instead — by overriding this one instance's own `create`, since the
+ * refused instead, by overriding this one instance's own `create`, since the
  * manager has no predicate hook and `create` is the single seam both the
  * automatic subscription and every explicit caller pass through.
  */
 
 export interface WorkspaceCheckpointing {
-  /** The manager itself — automatic snapshots gated, explicit creates unrestricted. */
+  /** The manager itself, automatic snapshots gated, explicit creates unrestricted. */
   readonly manager: WorkspaceCheckpointManager;
   /**
    * The narrower surface handed to the `checkpoints.*` gateway verbs: identical
    * except that an explicit create refuses, with an actionable message, when the
    * workspace is not checkpoint-eligible. Reads (list/diff/sessionChanges) and
-   * restore stay unrestricted — they operate over checkpoints that may already
+   * restore stay unrestricted, they operate over checkpoints that may already
    * exist, including from a since-unregistered workspace.
    */
   readonly gatewayManager: Pick<WorkspaceCheckpointManager, 'list' | 'create' | 'diff' | 'restore' | 'sessionChanges' | 'workspaceRoot'>;
@@ -69,7 +69,7 @@ export function createWorkspaceCheckpointing(opts: {
   });
 
   // Automatic snapshots ('turn' | 'agent-run', fired by the manager's own bus
-  // subscription) resolve to null quietly when the workspace is not eligible —
+  // subscription) resolve to null quietly when the workspace is not eligible,
   // there is no caller to throw to, and the manager already documents a null
   // return as the cheap no-op for an unchanged tree. Explicit ('manual') creates
   // are NOT re-gated here: they go through the gateway surface below, which
@@ -82,7 +82,7 @@ export function createWorkspaceCheckpointing(opts: {
 
   // Eagerly initialize so the automatic-snapshot subscription is live before the
   // first turn completes. If init() rejects, the manager caches that rejection
-  // forever and every later call re-throws it — the catch here only prevents an
+  // forever and every later call re-throws it, the catch here only prevents an
   // unhandled rejection at startup; the checkpoint verbs report the failure to
   // whoever calls them.
   void manager.init().catch((error: unknown) => {
@@ -104,7 +104,7 @@ export function createWorkspaceCheckpointing(opts: {
         );
       }
       // Default the session stamp from the live resolver when the caller omits
-      // it — the resolveSessionId hook only auto-stamps automatic snapshots, so
+      // it, the resolveSessionId hook only auto-stamps automatic snapshots, so
       // without this an explicit checkpoint made this launch would be written
       // unstamped and excluded by the session-scoped restore lookup.
       const sessionId = createOpts.sessionId ?? opts.resolveSessionId?.({});

package/src/testing/daemon-fixture.ts

@@ -1,5 +1,5 @@
 /**
- * daemon-fixture.ts — a real, running daemon, composed the way this product
+ * daemon-fixture.ts, a real, running daemon, composed the way this product
  * composes one, for a test to drive.
  *
  * ── Why this is a shipped module and not a test helper ────────────────────
@@ -8,7 +8,7 @@
  * and each of them hand-builds a composition to test against: a stub session
  * broker here, a fake approval broker there, a catalog with the handlers
  * somebody remembered to attach. They are large (several hundred lines each),
- * they duplicate each other, and — the part that matters — they are each a
+ * they duplicate each other, and, the part that matters, they are each a
  * SECOND idea of what a daemon is. A client contract test passing against a
  * hand-rolled stand-in tells you the stand-in agrees with the client, which is
  * the one agreement that was never in doubt.
@@ -43,19 +43,19 @@
  * can do for itself:
  *
  *   1. A NAMED ENTRY POINT. `goodvibes-daemon/testing` instead of the deep
- *      path. That means adding an `exports` map to package.json — and adding
+ *      path. That means adding an `exports` map to package.json, and adding
  *      one is not additive: an `exports` map REPLACES path-based resolution, so
  *      every existing deep import into this package (its own `bin` shim
  *      included) stops resolving unless the map enumerates them. That is a
  *      packaging change with a blast radius, made once, deliberately, by
- *      whoever owns distribution — not a side effect of adding a test helper.
+ *      whoever owns distribution, not a side effect of adding a test helper.
  *
  *   2. THE CONSUMER DEPENDENCY. A consumer repo has to depend on
  *      `goodvibes-daemon` to import this at all. Today the agent does (it is
  *      what makes its own install fail against an unpublished version); the
  *      terminal app and the webui do not. For the terminal app that is a
  *      devDependency and a version pin. For the webui, whose suites run in a
- *      browser context, the fixture cannot run in-process at all — it needs a
+ *      browser context, the fixture cannot run in-process at all, it needs a
  *      launcher script that starts the fixture in a node process and hands the
  *      Playwright suite `baseUrl` and `token`. That launcher does not exist and
  *      should be written on the webui side, where its runner lives.
@@ -65,12 +65,12 @@
  *      per test file pays about a second each and must `stop()` every one; the
  *      three hand-built stand-ins it replaces cost nothing and leak nothing.
  *      The honest guidance is one fixture per FILE (`beforeAll`/`afterAll`),
- *      which is how this repository's own suites use it — not one per test.
+ *      which is how this repository's own suites use it, not one per test.
  *
  *   4. WHAT IT DOES NOT REPLACE. A stand-in is still the right tool for
  *      driving a client through a daemon state that is hard to reach for real:
  *      a wedged session, a specific 500, a torn connection. This fixture
- *      replaces the stand-ins that exist only to answer normally — which is
+ *      replaces the stand-ins that exist only to answer normally, which is
  *      most of the several hundred lines in each consumer, and all of the part
  *      that silently drifts. The refusal shapes it cannot easily produce live
  *      are exported separately and pinned against the real engine; see
@@ -145,7 +145,7 @@ export interface DaemonFixtureOptions {
 }
 
 export interface DaemonFixture {
-  /** The composed runtime graph — the same object `DaemonServer` was handed. */
+  /** The composed runtime graph, the same object `DaemonServer` was handed. */
   readonly services: RuntimeServices;
   /** The running server. */
   readonly daemon: DaemonServer;
@@ -159,7 +159,7 @@ export interface DaemonFixture {
   fetch(path: string, init?: RequestInit): Promise<Response>;
   /**
    * Fetch a path with NO credential. A route that exists answers 401; a path
-   * nothing serves answers 404 — which is what makes this the side-effect-free
+   * nothing serves answers 404, which is what makes this the side-effect-free
    * way to ask whether a route exists, even for a write verb.
    */
   fetchAnonymous(path: string, init?: RequestInit): Promise<Response>;
@@ -170,7 +170,7 @@ export interface DaemonFixture {
 }
 
 /**
- * Compose and start a daemon. Always `await fixture.stop()` — the runtime graph
+ * Compose and start a daemon. Always `await fixture.stop()`, the runtime graph
  * starts pollers while it builds, and abandoning it leaves every one of them
  * firing for the rest of the process.
  */
@@ -234,7 +234,7 @@ export async function startDaemonFixture(options: DaemonFixtureOptions = {}): Pr
     // What the real entrypoint states, for the same reason it states it: the
     // hosted-session verbs are registered by this composition and by nothing
     // else, so a fixture that leaves it out is a daemon a client cannot start a
-    // session on — and every contract test written against it would agree.
+    // session on, and every contract test written against it would agree.
     ...(options.hostSessions === false ? {} : { hostedSessions: createHostedSessionOptions(services) }),
   });
 

package/src/testing/hosted-session-failures.ts

@@ -1,5 +1,5 @@
 /**
- * hosted-session-failures.ts — what `sessions.hosted.*` answers when it refuses.
+ * hosted-session-failures.ts, what `sessions.hosted.*` answers when it refuses.
  *
  * ── Why this is a shipped module ─────────────────────────────────────────
  *
@@ -19,7 +19,7 @@
  * These are the three refusals a client has to handle and could not previously
  * mock. They are declared here rather than hand-written in each consumer, and
  * `src/test/daemon/gateway-hosted-session-failures.test.ts` drives the REAL
- * engine to produce each one and asserts it still matches — so a fixture that
+ * engine to produce each one and asserts it still matches, so a fixture that
  * drifts from the daemon fails in this repository, not in a consumer's CI six
  * weeks later.
  */
@@ -28,7 +28,7 @@
 export interface HostedSessionFailureFixture {
   /** The verb whose refusal this is. */
   readonly methodId: string;
-  /** Machine-readable code — the field a client branches on. */
+  /** Machine-readable code, the field a client branches on. */
   readonly code: string;
   /** HTTP status the control plane maps this refusal to. */
   readonly status: number;
@@ -65,7 +65,7 @@ export const HOSTED_SESSION_UNAVAILABLE: HostedSessionFailureFixture = {
 
 /**
  * At the configured cap. 429: the request is well-formed and the daemon is not
- * broken — there is no room. Retrying after a kill succeeds.
+ * broken, there is no room. Retrying after a kill succeeds.
  */
 export const HOSTED_SESSION_LIMIT_REACHED: HostedSessionFailureFixture = {
   methodId: 'sessions.hosted.create',

package/src/version.ts

@@ -13,14 +13,14 @@ try {
   // compiled binary resolves import.meta.dir to a virtual root where the
   // `../package.json` path can land on a DIFFERENT package.json (a bundled
   // dependency's, or the embedded runtime's) that reports a placeholder like
-  // "0.0.0" — exactly the wrong-version banner a bare daemon launch showed in
+  // "0.0.0", exactly the wrong-version banner a bare daemon launch showed in
   // the field. Guarding on the package name means the prebuild-baked fallback
   // above wins in that case instead of a stray version.
   if (pkg?.name === 'goodvibes-daemon' && typeof pkg.version === 'string' && pkg.version.length > 0) {
     _version = pkg.version;
   }
 } catch {
-  // Compiled binary or missing package.json — use fallback
+  // Compiled binary or missing package.json, use fallback
 }
 
 export const VERSION = _version;