@pellux/goodvibes-daemon 1.28.19 → 1.28.20

package/src/daemon/handlers/routing/inbox-bridge.ts

@@ -9,22 +9,22 @@
 // `getProfileForChannel(surfaceKind, routeId?)` applies the canonical
 // resolution order:
 //
-//   1. exact     — surfaceKind AND routeId both match
-//   2. surface   — surfaceKind matches, route has no routeId
-//   3. wildcard  — a route with surfaceKind === 'any' (no routeId)
+//   1. exact    , surfaceKind AND routeId both match
+//   2. surface  , surfaceKind matches, route has no routeId
+//   3. wildcard , a route with surfaceKind === 'any' (no routeId)
 //
 // This module bridges the two shapes. The bridge maps an inbound item's
 // `provider` to the routing `surfaceKind` and forwards an optional `routeId`
 // refinement; `fromDigest`/`kind` are NOT used as routing keys (the routing
 // store is keyed by surfaceKind + optional routeId only, never by sender digest
-// or message kind — see RoutingChannelRoute). When no binding matches the
+// or message kind, see RoutingChannelRoute). When no binding matches the
 // resolver returns null and the bridge yields `undefined`, so the adapter falls
 // back to leaving the item unrouted (offline/default behaviour intact). The
 // bridge NEVER throws: the underlying resolver is a pure in-memory lookup.
 //
 // The inbox surface is a separate follow-up module, so this bridge declares the
 // minimal `RouteResolver` seam locally rather than importing a sibling that the
-// routing slice does not own — keeping the routing handler layer free of any
+// routing slice does not own, keeping the routing handler layer free of any
 // cross-surface import edge.
 // ---------------------------------------------------------------------------
 

package/src/daemon/handlers/routing/index.ts

@@ -1,5 +1,5 @@
 // ---------------------------------------------------------------------------
-// Channel routing surface — HANDLERS for the SDK-defined methods
+// Channel routing surface, HANDLERS for the SDK-defined methods
 //   - channels.routing.list   (read-only)
 //   - channels.routing.assign (admin, confirmation-gated)
 //   - channels.routing.delete (admin, dangerous, confirmation-gated)

package/src/daemon/handlers/routing/route-store.ts

@@ -96,7 +96,7 @@ const SCHEMA: string[] = [
     updatedAt TEXT NOT NULL
   )`,
   `CREATE INDEX IF NOT EXISTS idx_routes_surface_route ON routes (surfaceKind, routeId)`,
-  // Enforce one assignment per channel — the upsert path relies on this.
+  // Enforce one assignment per channel, the upsert path relies on this.
   `CREATE UNIQUE INDEX IF NOT EXISTS idx_routes_channel ON routes (channelId)`,
 ];
 

package/src/daemon/handlers/routing/routing-resolver.ts

@@ -9,9 +9,9 @@ export const WILDCARD_SURFACE = 'any';
  * order as the agent-side `getProfileForChannel()` so offline and online
  * routing produce identical results:
  *
- *   1. exact match    — surfaceKind AND routeId both match
- *   2. surface-only   — surfaceKind matches, route has no routeId
- *   3. wildcard       — a route with surfaceKind === 'any' (no routeId)
+ *   1. exact match   , surfaceKind AND routeId both match
+ *   2. surface-only  , surfaceKind matches, route has no routeId
+ *   3. wildcard      , a route with surfaceKind === 'any' (no routeId)
  *
  * Returns the matching profileId, or `null` when nothing matches.
  */

package/src/daemon/handlers/sqlite-store.ts

@@ -1,6 +1,6 @@
 /// <reference types="@pellux/goodvibes-sdk/sql-js" />
 // `sql.js` ships no types. The declaration is SDK-owned and reaches here
-// through that reference — there is no local copy to keep in step.
+// through that reference, there is no local copy to keep in step.
 
 import { mkdir, rename, writeFile } from 'node:fs/promises';
 import { readFileSync, readdirSync, renameSync, rmSync, statSync } from 'node:fs';
@@ -23,7 +23,7 @@ export interface SqliteStoreOptions {
 
 /**
  * The 16 bytes every SQLite file begins with ("SQLite format 3" + NUL). A file
- * that does not start with these is not a database, whatever its extension —
+ * that does not start with these is not a database, whatever its extension,
  * which is exactly what a crash mid-create, a zero-fill, or a partially
  * restored backup leaves behind.
  */
@@ -93,7 +93,7 @@ export class HandlerSqliteStore {
   /**
    * Move a database file that cannot be opened aside instead of deleting it, so
    * an operator still has something to salvage, and return the quarantine path.
-   * Returns null when the move itself failed — in which case the caller starts
+   * Returns null when the move itself failed, in which case the caller starts
    * fresh in memory and the bad file is left exactly where it was rather than
    * being overwritten on the next save.
    */
@@ -110,8 +110,8 @@ export class HandlerSqliteStore {
   /**
    * Bound the quarantine directory: drop `.corrupt-*` copies of THIS store that
    * are past the TTL or beyond the keep-newest count. Best-effort and
-   * idempotent — a file another process already removed is success, not an
-   * error — so two daemons opening the same store at once cannot fight.
+   * idempotent, a file another process already removed is success, not an
+   * error, so two daemons opening the same store at once cannot fight.
    * Returns how many were reclaimed.
    */
   private reapCorruptQuarantines(nowMs: number): number {
@@ -158,7 +158,7 @@ export class HandlerSqliteStore {
 
     // Validate the file by its CONTENT, not by existsSync. `save()` writes
     // through a pid-and-timestamp temp file and an atomic rename, so it cannot
-    // itself leave a half-written database — but a zero-filled file recovered
+    // itself leave a half-written database, but a zero-filled file recovered
     // by a filesystem, a truncated restore, or a copy interrupted by something
     // outside this process all produce a path that exists and holds no usable
     // database. Handing those bytes to `new SQL.Database(...)` throws out of
@@ -200,7 +200,7 @@ export class HandlerSqliteStore {
         }
       } catch (error) {
         // Header present but the body does not hold up: a truncated or damaged
-        // database. Same treatment — set aside, disclose, start clean.
+        // database. Same treatment, set aside, disclose, start clean.
         quarantineReason = `database would not open: ${error instanceof Error ? error.message : String(error)}`;
         this.db = null;
         quarantined = this.quarantineUnreadable();
@@ -215,7 +215,7 @@ export class HandlerSqliteStore {
     // Disclosure: starting a store from scratch is data loss from the user's
     // point of view, so it is never allowed to happen quietly.
     if (quarantineReason) {
-      logger.warn('daemon store could not be opened — starting a fresh one', {
+      logger.warn('daemon store could not be opened; starting a fresh one', {
         store: this.options.fileName,
         path: this.resolvedPath,
         reason: quarantineReason,
@@ -266,7 +266,7 @@ export class HandlerSqliteStore {
    * saves of the same store in the SAME millisecond produced the same temp path
    * before it did: both wrote it, the first rename moved it away, and the
    * second failed with ENOENT on a file it had just written. That is not a
-   * hypothetical race — the inbox poller flushes once per provider and polls
+   * hypothetical race, the inbox poller flushes once per provider and polls
    * every provider concurrently, so it hit on an ordinary two-provider startup,
    * and the failure surfaced as a provider reporting a filesystem error for its
    * feed. Every store on this base shares the hazard, so the counter lives here.

package/src/daemon/handlers/triage/index.ts

@@ -5,7 +5,7 @@
 // runtime composition root calls. It DECORATES the inbox surface's
 // `channels.inbox.list` handler (overlaying persisted triage metadata) and
 // returns the poller-facing pipeline + tagger. inbox.triage.* are NOT published
-// catalog methods — this surface registers no triage method id.
+// catalog methods, this surface registers no triage method id.
 // ---------------------------------------------------------------------------
 
 export {

package/src/daemon/handlers/triage/integration.ts

@@ -12,12 +12,12 @@
 //      overlaid with the persisted triageScore/triageTags via
 //      enrichItemsWithTriage(). Every other registration passes straight
 //      through to the real catalog. The inbox descriptor/schema/id is never
-//      re-authored — only its handler is wrapped.
+//      re-authored, only its handler is wrapped.
 //   2. It exposes the triage pipeline + tagger (`runInboxTriage`, `tagger`) for
 //      the daemon-internal poller, which scores items and persists them to the
 //      co-located inbox-triage.sqlite store the decorator reads from.
 //   3. inbox.triage.* are intentionally NOT registered on the catalog (they are
-//      a daemon-internal pipeline, not published methods) — so this module
+//      a daemon-internal pipeline, not published methods), so this module
 //      makes ZERO catalog.register call for any triage id.
 //
 // Reads in the decorator are best-effort and degrade to the raw item when no
@@ -51,7 +51,7 @@ import { summarizeError } from '@pellux/goodvibes-sdk/platform/utils';
 
 /**
  * Canonical id of the inbox list method whose handler we decorate. This is the
- * SDK's published id — referenced as a plain string for matching during
+ * SDK's published id, referenced as a plain string for matching during
  * registration; no descriptor or schema is authored here.
  */
 export const INBOX_LIST_METHOD_ID = 'channels.inbox.list';

package/src/daemon/handlers/triage/pipeline.ts

@@ -57,7 +57,7 @@ export interface RunInboxTriageOptions {
   scorer?: TriageScorerOptions;
   /** Inject a store (tests). When omitted, a triage store is opened/closed. */
   store?: HandlerSqliteStore;
-  /** When true, do not persist — only compute (used by inbox.triage.list). */
+  /** When true, do not persist, only compute (used by inbox.triage.list). */
   dryRun?: boolean;
   /** Clock injection for deterministic updatedAt in tests. */
   now?: () => Date;
@@ -254,7 +254,7 @@ export function enrichItemsWithTriage<T extends { id: string }>(
   items: readonly T[],
 ): Array<T & TriageOverlay> {
   if (items.length === 0) return [];
-  // Single batched read (`WHERE id IN (...)`) instead of one SELECT per item —
+  // Single batched read (`WHERE id IN (...)`) instead of one SELECT per item,
   // this is a hot read path (every channels.inbox.list call), so the N+1 is
   // collapsed to one query keyed by id.
   const byId = readTriageMetadataBatch(

package/src/daemon/handlers/triage/scorer.ts

@@ -3,7 +3,7 @@
 //
 // Pure, dependency-free heuristic + naive-Bayes-style spam/priority scoring
 // over an InboundChannelItem's textual surface (subject + snippet). No I/O,
-// no credentials, no network — safe to run on every polled item.
+// no credentials, no network, safe to run on every polled item.
 //
 // The score is a normalized 0..1 confidence in the assigned label. The label
 // is one of 'spam' | 'priority' | 'normal'. Scoring is deterministic so the
@@ -247,7 +247,7 @@ export function scoreInboundItem(
   // A trailing question mark suggests an awaited answer.
   if (/\?\s*$/.test(raw)) priorityLL += 0.5;
 
-  // Spam strongly suppresses priority — promotional text is rarely urgent.
+  // Spam strongly suppresses priority, promotional text is rarely urgent.
   priorityLL -= spam * 2.5;
 
   const priority = clamp01(sigmoid(priorityLL));

package/src/daemon/handlers/triage/tagger/discord.ts

@@ -1,10 +1,10 @@
 // ---------------------------------------------------------------------------
-// Triage tagger — Discord provider.
+// Triage tagger, Discord provider.
 //
 // Two paths, in priority order:
 //   1. REAL thread tags: when the item targets a forum/media-channel thread and
 //      a forum-tag mapping resolves >=1 tag id, PATCH the thread's applied_tags
-//      (read-then-merge — never blind overwrite). Exact fidelity to the
+//      (read-then-merge, never blind overwrite). Exact fidelity to the
 //      contract's "Discord thread tags".
 //   2. Reaction analog: Discord has no arbitrary per-message tags, so otherwise
 //      add a unicode reaction (PUT .../reactions/{emoji}/@me).
@@ -114,7 +114,7 @@ async function applyDiscordThreadTags(
   // DATA-LOSS GUARD: we PATCH the thread's full applied_tags array, so we must
   // first read the EXISTING tags and merge. If that read fails (network error
   // OR a non-ok HTTP status), we have no idea what tags are currently on the
-  // thread — PATCHing with only our new ids would silently destroy whatever
+  // thread, PATCHing with only our new ids would silently destroy whatever
   // forum tags were already applied. Abort instead of overwriting.
   const existing = await fetchDiscordAppliedTags(url, token, fetchImpl, ctx);
   if (existing === null) {

package/src/daemon/handlers/triage/tagger/imap.ts

@@ -1,5 +1,5 @@
 // ---------------------------------------------------------------------------
-// Triage tagger — IMAP provider.
+// Triage tagger, IMAP provider.
 //
 // Applies a triage label as an IMAP keyword flag (STORE +FLAGS) over a minimal
 // IMAP4rev1-over-TLS client. Credentials are resolved per-apply from the daemon
@@ -63,7 +63,7 @@ export type ImapConnect = (opts: {
   servername: string;
 }) => ImapSocketLike;
 
-/** Production connector — a real IMAP4rev1-over-TLS socket via node:tls. */
+/** Production connector, a real IMAP4rev1-over-TLS socket via node:tls. */
 export const tlsImapConnect: ImapConnect = (opts) =>
   tlsConnect(opts, () => {
     /* greeting handled in the data pump */
@@ -128,7 +128,7 @@ export class ImapStoreError extends Error {
  * in a value destined for an IMAP command line. CR/LF are the dangerous ones:
  * an unescaped CRLF would terminate the current command and let an attacker
  * inject a second IMAP command (CRLF injection). IMAP's quoted-string syntax
- * has no escape for these control chars — backslash only escapes `\` and `"` —
+ * has no escape for these control chars, backslash only escapes `\` and `"`,
  * so the only safe handling is to refuse the value outright.
  */
 function assertImapSafe(value: string, field: string): void {
@@ -155,8 +155,8 @@ function quoteImap(value: string): string {
 // A concrete UID sequence-set: one or more comma-separated single UIDs or
 // numeric ranges (`12`, `3:9`, `1,4,7:9`). RFC 3501 also permits `*` (the
 // largest UID in the mailbox) and ranges to `*`, but a wildcard would let a
-// single value like `1:*` apply the flag to the ENTIRE mailbox — never the
-// intent when tagging one triaged item — so `*` is rejected outright.
+// single value like `1:*` apply the flag to the ENTIRE mailbox, never the
+// intent when tagging one triaged item, so `*` is rejected outright.
 const IMAP_UID_SET = /^[0-9]+(:[0-9]+)?(,[0-9]+(:[0-9]+)?)*$/;
 
 // An IMAP flag: an optional leading `\` (system flag, e.g. `\Seen`) followed by
@@ -187,7 +187,7 @@ function assertImapUid(value: string): void {
  * UNQUOTED into the `+FLAGS (...)` list. assertImapSafe only blocks control
  * chars; a flag containing a space (e.g. `\Seen Junk`) would still pass that
  * guard and inject a second flag atom. This is the boundary check that
- * prevents it — independent of any upstream normalizer.
+ * prevents it, independent of any upstream normalizer.
  */
 function assertImapFlag(value: string): void {
   if (!IMAP_FLAG.test(value)) {
@@ -313,7 +313,7 @@ export function imapStoreFlagOverTls(
           finish();
         }
       } else {
-        // NO/BAD: deterministic protocol rejection — do not retry.
+        // NO/BAD: deterministic protocol rejection, do not retry.
         current.reject(new ImapStoreError(`IMAP command failed: ${status}`, false));
       }
     };

package/src/daemon/handlers/triage/tagger/index.ts

@@ -159,7 +159,7 @@ export function createTriageTagger(
         return { ...base, reason: 'autotag-disabled' };
       }
 
-      // Provider-side mutation is effectful — require explicit confirmation.
+      // Provider-side mutation is effectful, require explicit confirmation.
       if (request.confirm !== true || request.explicitUserRequest !== true) {
         throw new HandlerError(
           'Provider-side triage tagging requires explicit user confirmation.',

package/src/daemon/handlers/triage/tagger/shared.ts

@@ -1,5 +1,5 @@
 // ---------------------------------------------------------------------------
-// Triage tagger — shared types and provider-agnostic helpers.
+// Triage tagger, shared types and provider-agnostic helpers.
 //
 // Provider config shapes, the apply request/result contract, and the tag
 // normalization helpers used by the IMAP/Slack/Discord modules. No I/O here.
@@ -17,7 +17,7 @@ export interface TaggerProviderConfig {
    * optional forum-tag mapping. When `forumTagIds` maps a GoodVibes triage tag
    * (e.g. 'GoodVibes/Spam') to a forum tag SNOWFLAKE id, items that target a
    * forum/media-channel thread get that REAL thread tag applied (PATCH
-   * applied_tags) — exact fidelity to the contract's "Discord thread tags".
+   * applied_tags), exact fidelity to the contract's "Discord thread tags".
    * Without a mapping (or for non-thread messages) tagging degrades to a
    * unicode reaction analog.
    */
@@ -29,7 +29,7 @@ export interface ApplyTagsRequest {
   /** Provider-side tags to apply. Defaults to [labelToTag(label)] when omitted. */
   tags?: readonly string[];
   label?: TriageLabel;
-  /** Must be true — provider-side mutation requires explicit confirmation. */
+  /** Must be true, provider-side mutation requires explicit confirmation. */
   confirm?: boolean;
   /** Mirror of the operator invocation context flag. */
   explicitUserRequest?: boolean;

package/src/daemon/handlers/triage/tagger/slack.ts

@@ -1,5 +1,5 @@
 // ---------------------------------------------------------------------------
-// Triage tagger — Slack provider.
+// Triage tagger, Slack provider.
 //
 // Applies a triage label as a Slack message reaction (reactions.add). The bot
 // token is resolved per-apply from the daemon credential store and is never

package/src/daemon/handlers/triage/types.ts

@@ -5,7 +5,7 @@
 // and the triage pipeline scores. It is NOT an SDK catalog contract: the
 // published `channels.inbox.list` output schema (CHANNEL_INBOX_ITEM_SCHEMA) is
 // owned by the SDK and never re-declared here. This is the internal poller
-// item per the handoff doc — it carries `fromDigest` (never a raw sender id),
+// item per the handoff doc, it carries `fromDigest` (never a raw sender id),
 // `subjectPreview`/`bodyPreview` (PII-stripped, length-bounded) and an opaque
 // `metadata` bag the tagger reads provider targeting from (imapUid, channelId,
 // Slack ts, Discord messageId/threadId).
@@ -31,7 +31,7 @@ export interface InboundChannelItem {
   /** Handoff-facing provider id ("slack" | "discord" | "email" | ...). */
   readonly provider?: string;
   readonly kind?: 'dm' | 'thread' | 'mention' | 'reaction';
-  /** SHA-256 first-N of sender external id — NEVER a raw identifier. */
+  /** SHA-256 first-N of sender external id, NEVER a raw identifier. */
   readonly fromDigest?: string;
   /** Conversation id (Slack/Discord channel, IMAP mailbox-scoped). */
   readonly conversationId?: string;

package/src/daemon/lifecycle.ts

@@ -1,5 +1,5 @@
 /**
- * lifecycle.ts — resolve THIS binary's update-artifact identity for the SDK
+ * lifecycle.ts, resolve THIS binary's update-artifact identity for the SDK
  * DaemonServer facade's auto-update lifecycle.
  *
  * The SDK facade now runs the entire self-update loop itself when handed a
@@ -7,12 +7,12 @@
  * version against the release tags (no longer the version-blind sdk-package
  * comparison that used to restart-loop), swaps only at an idle moment, keeps
  * the outgoing file at `<path>.previous`, and leaves a receipt in the store it
- * serves on /status. When the artifact is ABSENT, updates are host-managed —
+ * serves on /status. When the artifact is ABSENT, updates are host-managed,
  * the facade runs no loop (the safe embedded default).
  *
  * The one guard the facade does NOT apply is install-kind: it must never swap a
  * dev `bun run daemon` interpreter or a bun-global package install. This helper
- * is that guard — it hands the facade an artifact ONLY for a compiled binary
+ * is that guard, it hands the facade an artifact ONLY for a compiled binary
  * install, so a dev run resolves to `undefined` (host-managed, no loop) and
  * only a real self-contained binary self-updates.
  */
@@ -23,13 +23,13 @@ import { detectInstallKind } from '../runtime/update-check.ts';
 export interface ResolveDaemonUpdateArtifactOptions {
   /** The executable to identify; defaults to process.execPath. */
   readonly execPath?: string;
-  /** Injectable so tests pin a fixture version — never the live build VERSION. */
+  /** Injectable so tests pin a fixture version, never the live build VERSION. */
   readonly version?: string;
 }
 
 /**
  * The update-artifact identity to hand the DaemonServer facade, or `undefined`
- * for a non-binary install (dev/source or bun-global package) — in which case
+ * for a non-binary install (dev/source or bun-global package), in which case
  * the facade keeps updates host-managed and runs no swap loop.
  */
 export function resolveDaemonUpdateArtifact(

package/src/daemon/local-daemon-state.ts

@@ -1,5 +1,5 @@
 /**
- * local-daemon-state.ts — the two files a daemon writes about ITSELF.
+ * local-daemon-state.ts, the two files a daemon writes about ITSELF.
  *
  * `status` and `update` want to report things no control-plane verb answers:
  * how long the daemon has been up, whether the last start followed a crash,
@@ -11,7 +11,7 @@
  *   <control-plane config dir>/control-plane/daemon-receipts.json
  *
  * They are READ here and never written, and the receipts are never marked
- * delivered — `/status?receipts=consume` hands each receipt to the first
+ * delivered, `/status?receipts=consume` hands each receipt to the first
  * consuming reader exactly once, and a status command that quietly consumed
  * them would take them away from the surface they were written for.
  *
@@ -22,7 +22,7 @@
  * The SDK owns the writers (`platform/daemon/lifecycle-marker.ts`,
  * `platform/daemon/receipts.ts`) and its readers are not exported from the
  * published package this repository pins, so the readers below are this
- * repository's own — bounded and content-validated the same way, and no more
+ * repository's own, bounded and content-validated the same way, and no more
  * trusting of the file than the SDK is. The shared-piece lane can re-point them
  * at the SDK's own readers once those are exported.
  */
@@ -42,7 +42,7 @@ export interface DaemonLifecycleMarker {
   readonly pid: number | undefined;
   readonly failedStarts: number;
   readonly version: string | undefined;
-  /** The version an automatic rollback moved AWAY from — the build that crash looped. */
+  /** The version an automatic rollback moved AWAY from, the build that crash looped. */
   readonly rejectedVersion: string | undefined;
   /** When an automatic rollback last restored the kept previous binary. */
   readonly autoRollbackAt: number | undefined;
@@ -164,7 +164,7 @@ export function readDaemonReceipts(
 }
 
 export interface LocalDaemonState {
-  /** False when the caller asked about another machine — nothing below was read. */
+  /** False when the caller asked about another machine, nothing below was read. */
   readonly available: boolean;
   /** Why it is unavailable, when it is. */
   readonly unavailableReason: string | undefined;
@@ -195,7 +195,7 @@ export function describeLocalDaemonState(input: DescribeLocalDaemonStateInput):
     return {
       available: false,
       unavailableReason:
-        'the uptime, update receipts and rollback state are read from files on the daemon\'s own host — '
+        'the uptime, update receipts and rollback state are read from files on the daemon\'s own host; '
         + 'run this command on that machine to see them',
       marker: null,
       receipts: [],
@@ -219,7 +219,7 @@ export function describeLocalDaemonState(input: DescribeLocalDaemonStateInput):
   };
 }
 
-/** `3d 4h`, `4h 12m`, `12m 3s`, `9s` — two units, never more. */
+/** `3d 4h`, `4h 12m`, `12m 3s`, `9s`, two units, never more. */
 export function formatDuration(milliseconds: number): string {
   const totalSeconds = Math.max(0, Math.floor(milliseconds / 1000));
   const days = Math.floor(totalSeconds / 86_400);

package/src/daemon/pair-command.ts

@@ -1,9 +1,9 @@
 /**
- * pair-command.ts — `goodvibes-daemon pair`.
+ * pair-command.ts, `goodvibes-daemon pair`.
  *
  * Two forms.
  *
- * LOCAL FORM — `pair` with no `--host`, or one naming this machine — reprints
+ * LOCAL FORM, `pair` with no `--host`, or one naming this machine, reprints
  * the pairing block a daemon prints once as it starts: the web origin, the
  * offers a new device can accept, what it will be able to do, and a QR code
  * encoding the deep link that opens the web app already signed in. It reads
@@ -12,13 +12,13 @@
  * resolve to) and reprints the EXISTING token rather than minting a new one,
  * so a link printed here and the one printed at boot are the same link.
  *
- * REMOTE FORM — `pair --host <name> [--port] [--token]` — asks THAT daemon to
+ * REMOTE FORM, `pair --host <name> [--port] [--token]`, asks THAT daemon to
  * MINT A NEW per-device pairing token over `pairing.handoff.create` and prints
  * the pairing block for it. Minting is a different act than reprinting: it is
  * a fresh token, and every token that daemon already issued (its own shared
  * token included) is left exactly as it was. Because it changes state on a
  * daemon that may not be this process's own, it states the plan and asks for
- * confirmation before acting — `-y`/`--yes` satisfies that non-interactively,
+ * confirmation before acting, `-y`/`--yes` satisfies that non-interactively,
  * the same convention `migrate-service` uses. An unreachable daemon, a
  * rejected token, and a daemon too old to serve the verb are each refused by
  * name (see `callDaemonWsVerb`), never a stack trace.
@@ -84,7 +84,7 @@ function failure(error: string, fix: string, json: boolean): DaemonCommandResult
 /**
  * The web origin a remote handoff's deep link opens, recovered from the link
  * itself. `buildPairingHandoffLink` in the SDK builds the link as exactly
- * `<webOrigin, trailing slashes stripped>/#<params>` — so slicing at the
+ * `<webOrigin, trailing slashes stripped>/#<params>`, so slicing at the
  * first `/#` is the precise inverse, and feeding the result back into
  * `renderPairingBanner` (which rebuilds the SAME link from origin + token +
  * offers) reproduces byte-for-byte what the remote daemon already returned.
@@ -103,19 +103,19 @@ interface PairingHandoffOfferDetail {
   readonly available?: boolean;
 }
 
-/** The shape `pairing.handoff.create` returns — see routes/pairing-handoff.ts. */
+/** The shape `pairing.handoff.create` returns, see routes/pairing-handoff.ts. */
 interface PairingHandoffCreateResult {
   readonly token: {
     readonly id: string;
     readonly name: string;
-    /** The plaintext secret — returned exactly once. */
+    /** The plaintext secret, returned exactly once. */
     readonly token: string;
     readonly createdAt: number;
   };
   readonly offers: readonly PairingHandoffOfferDetail[];
-  /** `#pair=<token>&offers=...` — present even when no web origin is configured. */
+  /** `#pair=<token>&offers=...`, present even when no web origin is configured. */
   readonly fragment: string;
-  /** `<webOrigin>/#pair=...` — present only when that daemon has a web origin configured. */
+  /** `<webOrigin>/#pair=...`, present only when that daemon has a web origin configured. */
   readonly deepLink?: string;
 }
 
@@ -127,7 +127,7 @@ function runLocalReprint(input: RunPairCommandInput): DaemonCommandResult {
   if (token === undefined) {
     return failure(
       'no operator token was found for this machine, so there is no link to print',
-      'start the daemon once — it creates the token as it starts: goodvibes-daemon serve',
+      'start the daemon once; it creates the token as it starts: goodvibes-daemon serve',
       flags.json,
     );
   }
@@ -175,7 +175,7 @@ function mintPlanResult(target: RemoteDaemonTarget, json: boolean): DaemonComman
     `pair --host: this will MINT A NEW per-device pairing token on the daemon at ${target.baseUrl}`,
     'and print the pairing link/QR for that new token.',
     '',
-    "That daemon's existing tokens — its shared token and every other paired device — are",
+    "That daemon's existing tokens (its shared token and every other paired device) are",
     'left exactly as they are: minting is a different act than reprinting, and this is a',
     'fresh token, not a link to one that already exists.',
     '',
@@ -208,15 +208,15 @@ async function runRemoteMint(input: RunPairCommandInput, target: RemoteDaemonTar
   const mintedLine = `minted a new per-device pairing token ("${data.token.name}") on the daemon at ${target.baseUrl}.`;
 
   if (data.deepLink === undefined) {
-    // Honest degraded path: the mint itself succeeded — the token is real and
-    // usable — but that daemon has no web origin configured, and this process
+    // Honest degraded path: the mint itself succeeded, the token is real and
+    // usable, but that daemon has no web origin configured, and this process
     // has no way to read or fabricate one for it. `resolvePairingWebOrigin` is
     // what the local form reads instead, and it is exactly the thing this
     // process cannot ask a REMOTE daemon for outside this verb's own reply.
     const lines = [
       mintedLine,
       '',
-      'that daemon has no web origin configured, so no deep link or QR could be built — only',
+      'that daemon has no web origin configured, so no deep link or QR could be built; only',
       'the raw token and pairing fragment:',
       '',
       `  token:    ${data.token.token}`,

package/src/daemon/provision-wake-model.ts

@@ -1,11 +1,11 @@
 // ---------------------------------------------------------------------------
-// provision-wake-model.ts — `goodvibes-daemon provision-wake-model`.
+// provision-wake-model.ts, `goodvibes-daemon provision-wake-model`.
 //
 // WHAT THIS IS FOR
 //
 // The curl installer needs to put the wake-word model on the machine, and it must
 // not hold the pinned URLs, byte counts or checksums to do it. Those live in ONE
-// place — the SDK's wake-word manifest — and a shell script that copied them
+// place, the SDK's wake-word manifest, and a shell script that copied them
 // would be a second copy of a pin, drifting silently the first time the model is
 // retrained. So the installer runs the binary it just installed and lets the SDK
 // do what the SDK owns.
@@ -14,8 +14,8 @@
 //
 // The caller is an installer. A wake-word model is not a reason to fail installing
 // a coding tool, and an installer that aborts half-way through is worse than one
-// that finishes without a wake word. The outcome is printed either way — one plain
-// line naming what happened and how to retry — and a running daemon retries at
+// that finishes without a wake word. The outcome is printed either way, one plain
+// line naming what happened and how to retry, and a running daemon retries at
 // every boot. `--strict` is there for a caller that genuinely wants the exit code
 // to carry the result (a test, a provisioning script that is checking); the
 // installer does not pass it.
@@ -66,7 +66,7 @@ export async function runProvisionWakeModelCommand(
     const message = error instanceof Error ? error.message : String(error);
     return {
       exitCode: strict ? 1 : 0,
-      lines: [`wake-word model: skipped — ${message}`],
+      lines: [`wake-word model: skipped: ${message}`],
     };
   }
   const outcome = await provision({

package/src/daemon/send/channels.ts

@@ -1,5 +1,5 @@
 /**
- * channels.ts — which channels `goodvibes-daemon send` can reach, and which one
+ * channels.ts, which channels `goodvibes-daemon send` can reach, and which one
  * it uses when the operator names none.
  *
  * The surface list, labels and required-setup keys are IMPORTED from
@@ -7,7 +7,7 @@
  * list` and `goodvibes-daemon send --list` can never disagree about what a
  * channel is called or what it needs. What this module adds on top is the two
  * facts that command needs and `SURFACE_CONFIGS` does not carry: the routable
- * `ChannelDeliverySurfaceKind` for each surface id (they differ in case —
+ * `ChannelDeliverySurfaceKind` for each surface id (they differ in case,
  * `googleChat` vs `google-chat`), and the settings key holding each surface's
  * default destination.
  */
@@ -18,7 +18,7 @@ import { SURFACE_CONFIGS } from '../../cli/surface-catalog.ts';
 import { canRenderInert } from './inert-text.ts';
 
 /**
- * The settings key holding each supported surface's default destination — the
+ * The settings key holding each supported surface's default destination, the
  * chat, channel, topic or URL a message goes to when `--to` is not given.
  *
  * These are the SAME keys the delivery strategies in the SDK's
@@ -58,7 +58,7 @@ const SURFACE_KIND_BY_ID: Readonly<Record<string, ChannelDeliverySurfaceKind>> =
  * This is naming, not a scheme: `--to` becomes `ChannelDeliveryTarget.address`,
  * which is the first thing every strategy in `strategies-core.ts`,
  * `strategies-bridge.ts` and `strategies-enterprise.ts` already checks before
- * falling back to its configured default. Nothing new is invented — the label
+ * falling back to its configured default. Nothing new is invented, the label
  * exists so `--list` and the help can say "topic" where the channel says topic
  * and "chat id" where it says chat id, rather than making the operator work out
  * what an "address" is for ntfy.
@@ -120,7 +120,7 @@ export const SEND_CHANNELS: readonly SendChannel[] = SURFACE_CONFIGS
 
 /**
  * Look a channel up by the id an operator typed, accepting either the settings
- * id (`googleChat`) or the routable kind (`google-chat`) — the two spellings
+ * id (`googleChat`) or the routable kind (`google-chat`), the two spellings
  * are both visible in this product's own output, and making the operator
  * remember which one this command wants would be a trap.
  */
@@ -172,7 +172,7 @@ export type DefaultChannelResolution =
 /**
  * Which channel a `send` with no `--channel` goes to.
  *
- * A channel qualifies when it is switched on AND has a destination configured —
+ * A channel qualifies when it is switched on AND has a destination configured,
  * "enabled" alone is not enough, because an enabled surface with a blank
  * destination is a channel that would throw at the provider rather than deliver.
  *
@@ -180,7 +180,7 @@ export type DefaultChannelResolution =
  * no non-arbitrary winner, and this command has an outward effect: sending the
  * owner's message to the wrong one of his channels is worse than printing the
  * list and exiting non-zero. There is deliberately no priority order here to
- * silently break that tie — a preference ordering baked into this file would be
+ * silently break that tie, a preference ordering baked into this file would be
  * an invisible decision about where his messages go.
  */
 export function resolveDefaultChannel(config: Pick<ConfigManager, 'get'>): DefaultChannelResolution {