@pellux/goodvibes-tui 2.0.14 → 2.0.15

package/src/cli/tui-startup.ts

@@ -22,10 +22,10 @@ export type FirstOpenTrustLevel = 'trusted' | 'restricted';
 
 /**
  * What `resumeNamedSessionWithRecoveryCheck` needs to actually APPLY an
- * accepted crash-recovery snapshot — the same shape `buildRecoveryOfferWiring`
+ * accepted crash-recovery snapshot, the same shape `buildRecoveryOfferWiring`
  * (runtime/recovery-offer-wiring.ts) takes, minus `surface` and
  * `commandContext` which this module already has in scope. Optional: a caller
- * that omits it (or a snapshot-free boot) gets exactly today's behavior —
+ * that omits it (or a snapshot-free boot) gets exactly today's behavior,
  * straight resume from the durable store, no modal.
  */
 export interface TuiStartupRecoveryDeps {
@@ -37,7 +37,7 @@ export interface TuiStartupRecoveryDeps {
 }
 
 /**
- * resumeNamedSessionWithRecoveryCheck — the pre-resume guard for `--continue`
+ * resumeNamedSessionWithRecoveryCheck, the pre-resume guard for `--continue`
  * and the bare `--resume` (pointer) path.
  *
  * Resuming a named session straight from its durable store is exactly the
@@ -47,13 +47,13 @@ export interface TuiStartupRecoveryDeps {
  * read-only probe for that; when it finds one, this routes through the same
  * ask-then-retire modal flow the general boot offer uses
  * (runtime/recovery-prompt.ts), scoped to this one session via
- * `targetSessionId` — never auto-applied.
+ * `targetSessionId`, never auto-applied.
  *
  *   - No live snapshot (or `recovery` deps not wired): straight resume, same
  *     as before this check existed.
  *   - Resume chosen: the snapshot is applied (via `buildRecoveryOfferWiring`'s
  *     `applySnapshot`, which rebinds the runtime session id and replays any
- *     journal tail) and the plain store resume is skipped — the snapshot IS
+ *     journal tail) and the plain store resume is skipped, the snapshot IS
  *     the more complete copy.
  *   - "Not now" (or a dismissal, or a failed load): falls through to the
  *     plain store resume, after the follow-up Keep/Remove question the
@@ -63,7 +63,7 @@ export interface TuiStartupRecoveryDeps {
  * `scheduleRecoveryOffer`'s own reasoning: `applyInitialTuiCliState` runs
  * before the shell's first render, so asking a question here synchronously
  * would draw it at a blank terminal. The synchronous `checkRecoveryForSession`
- * probe above needs no such deferral — only opening the modal does.
+ * probe above needs no such deferral, only opening the modal does.
  */
 async function resumeNamedSessionWithRecoveryCheck(options: {
   readonly sessionId: string;
@@ -124,7 +124,7 @@ async function resumeNamedSessionWithRecoveryCheck(options: {
 }
 
 /**
- * decodeFirstOpenChoice — pure mapping from a chosen selection-item id (or
+ * decodeFirstOpenChoice, pure mapping from a chosen selection-item id (or
  * null on Escape/enter-through) to the trust decision. Kept pure so the
  * consequence-time trust prompt's semantics (raised by trustGatedAsk, wired
  * in main.ts's trustPromptRef.requestTrustDecision) are unit-testable
@@ -137,16 +137,16 @@ export function decodeFirstOpenChoice(id: string | null): FirstOpenTrustLevel {
 
 /**
  * Build the selection rows for the trust prompt. This used to also offer a
- * "register this directory?" half (a combined 2x2 when both were needed) —
+ * "register this directory?" half (a combined 2x2 when both were needed),
  * that half is gone: registration self-records (see
  * selfRecordWorkspaceRegistration below) rather than ever asking a question
  * about a registry the user hasn't met yet.
  */
 export function buildFirstOpenItems(): { readonly title: string; readonly items: SelectionItem[] } {
   return {
-    title: 'New workspace — choose a trust level',
+    title: 'New workspace: choose a trust level',
     items: [
-      { id: 'trusted', label: 'Trust this workspace', detail: 'Full capability — all tools may run', primaryAction: 'select' },
+      { id: 'trusted', label: 'Trust this workspace', detail: 'Full capability: all tools may run', primaryAction: 'select' },
       { id: 'restricted', label: 'Keep restricted (read-only)', detail: 'Explore safely; writes and commands are denied until trusted', primaryAction: 'select' },
     ],
   };
@@ -155,8 +155,8 @@ export function buildFirstOpenItems(): { readonly title: string; readonly items:
 /**
  * Registration self-records: a workspace the user actually works in becomes
  * its own registry entry with no question ever asked (the former "Register
- * this directory as a workspace?" prompt — sometimes a four-option 2x2 when
- * trust was undecided too — is gone entirely).
+ * this directory as a workspace?" prompt, sometimes a four-option 2x2 when
+ * trust was undecided too, is gone entirely).
  *
  * "Actually works in" is anchored to TRUST, not mere directory-open: this is
  * only ever called for a workspace that is (or has just become) trusted,
@@ -167,7 +167,7 @@ export function buildFirstOpenItems(): { readonly title: string; readonly items:
  * checkpoint-owning consumer's boundary. That boundary now reads the SAME
  * shared registration store this writes to, gated by each record's
  * `checkpointEligible` flag (absent means false). So the separation is no
- * longer "a separate list the agent owns" — it is one store, and this self
+ * longer "a separate list the agent owns", it is one store, and this self
  * record stays out of scope by stamping its `origin` ('tui') for honest
  * provenance while NEVER setting `checkpointEligible`. Only the consumer that
  * owns checkpointing re-stamps its own roots eligible on boot.
@@ -188,7 +188,7 @@ export function applyInitialTuiCliState(options: {
   readonly commandContext: CommandContext;
   readonly shellPaths: TuiStartupShellPaths;
   /**
-   * The app's declare-once session-storage handle — the SAME one the runtime
+   * The app's declare-once session-storage handle, the SAME one the runtime
    * writes the last-session pointer through. `--continue` and bare `--resume`
    * read that pointer below; deriving its path independently here is exactly
    * how this read used to land on a file nothing ever wrote.
@@ -199,7 +199,7 @@ export function applyInitialTuiCliState(options: {
    * Enables the crash-recovery check ahead of `--continue` / bare `--resume`
    * (see `resumeNamedSessionWithRecoveryCheck` above). Omitted, the two flags
    * resume straight from the durable store exactly as before this check
-   * existed — main.ts always wires this; only tests that don't care about
+   * existed, main.ts always wires this; only tests that don't care about
    * recovery snapshots leave it out.
    */
   readonly continueRecovery?: TuiStartupRecoveryDeps;
@@ -208,7 +208,7 @@ export function applyInitialTuiCliState(options: {
   const globalOnboardingMarker = readOnboardingCheckMarker(shellPaths, 'user');
 
   // Registration self-records on every launch of an already-trusted
-  // workspace (fire-and-forget — never blocks or gates startup, never a
+  // workspace (fire-and-forget, never blocks or gates startup, never a
   // modal). A workspace that is undecided or restricted is never
   // self-registered here; for one that becomes trusted just now (via the
   // consequence-time trust prompt), main.ts's trustPromptRef wiring calls
@@ -233,7 +233,7 @@ export function applyInitialTuiCliState(options: {
     }
   } else if (cli.flags.continueLast) {
     // --continue: resume the last session tracked by the pointer file. Checked
-    // for a live crash-recovery snapshot first — see
+    // for a live crash-recovery snapshot first, see
     // resumeNamedSessionWithRecoveryCheck's doc comment.
     const lastId = readLastSessionPointer({ surface });
     if (lastId) {
@@ -263,7 +263,7 @@ export function applyInitialTuiCliState(options: {
   } else if (!globalOnboardingMarker.exists) {
     // Fast path: get a brand-new user to a working session in the fewest steps.
     // Falls back to the full wizard when the surface can't detect providers.
-    // Trust stays undecided here on purpose — the first non-read tool
+    // Trust stays undecided here on purpose, the first non-read tool
     // request is what raises the trust question now (see main.ts's
     // trustPromptRef), not this startup branch.
     startOnboardingFastPath({ input, commandContext, shellPaths, render });
@@ -288,17 +288,17 @@ export function applyInitialTuiCliState(options: {
     }
     // Returning user, no wizard to resume, nothing else to do at startup:
     // trust (if still undecided) is asked at the first non-read tool
-    // request, not here — see main.ts's trustPromptRef wiring.
+    // request, not here, see main.ts's trustPromptRef wiring.
   }
 }
 
 /**
- * reportFatalStartupError — the main() catch handler. A bare Error
+ * reportFatalStartupError, the main() catch handler. A bare Error
  * JSON-serializes to {} in structured logs, and background timers keep the
- * process alive after a boot failure — the historical result was a blank
+ * process alive after a boot failure, the historical result was a blank
  * screen and a useless `Fatal error {"error": {}}` log line. Log real
  * fields, tell the user what broke, and exit. Both writes are individually
- * best-effort — a failing logger or torn-down stderr must never hide the
+ * best-effort, a failing logger or torn-down stderr must never hide the
  * original launch failure.
  */
 export function reportFatalStartupError(err: unknown): void {
@@ -314,7 +314,7 @@ export function reportFatalStartupError(err: unknown): void {
     // process.stderr to keep the rendered screen clean
     // (runtime/terminal-output-guard.ts), so a replaced writer that records
     // instead of printing would swallow the one line explaining why the screen
-    // is blank — and a stream write issued immediately before the exit below
+    // is blank, and a stream write issued immediately before the exit below
     // can still be in flight when the process stops existing. The descriptor
     // write is neither interceptable nor droppable. See
     // daemon/fatal-boot-report.ts.

package/src/config/run-daemon-config-migration.ts

@@ -1,19 +1,19 @@
 /**
- * run-daemon-config-migration.ts — the one call every TUI composition root
+ * run-daemon-config-migration.ts, the one call every TUI composition root
  * makes before constructing its `ConfigManager`.
  *
  * Daemon-owned configuration now has exactly one home:
  * `~/.goodvibes/daemon/settings.json`. Before this migration, every product
  * wrote every key (including daemon-only ones like `surfaces.telegram.*`)
  * into its own per-surface silo, and the daemon only ever read
- * `~/.goodvibes/tui/settings.json` — so a value written by, say, the agent
+ * `~/.goodvibes/tui/settings.json`, so a value written by, say, the agent
  * surface reported a successful save and configured nothing the daemon could
  * see.
  *
  * `migrateDaemonOwnedConfig` (SDK, `platform/config`) is idempotent and cheap
  * on the fast path (one file read + JSON parse), so it is safe and correct to
  * call this at every composition root that is about to construct a
- * `ConfigManager` — not just the first one to run in a given process. It
+ * `ConfigManager`, not just the first one to run in a given process. It
  * must never abort startup: any failure is caught, logged with the marker
  * path so the failure is diagnosable, and startup continues on whatever
  * config state already exists.

package/src/config/secret-config.ts

@@ -4,21 +4,21 @@ import type { SecretScope, SecretStorageMedium } from './secrets.ts';
 
 export const SECRET_CONFIG_KEYS = new Set<ConfigKey>([
   // Mailbox and CalDAV credentials. Their own CONFIG_SCHEMA descriptions read
-  // "Stored in the daemon secret tier, never in config" — and until they were
+  // "Stored in the daemon secret tier, never in config", and until they were
   // listed here that sentence was aspirational: the settings modal wrote them
   // as plain strings into a config JSON file, because membership in this set is
   // the thing that routes an edit through the secret manager instead.
   //
   // The daemon reads each of these back with
   // resolveConfigSecret('<key>') → GOODVIBES_<KEY>, which is exactly the store
-  // key buildGoodVibesSecretKey() writes — see
+  // key buildGoodVibesSecretKey() writes, see
   // daemon/handlers/inbox/providers/email.ts.
   'surfaces.email.password',
   'surfaces.email.imapPassword',
   'surfaces.email.imap.password',
   'surfaces.email.smtp.password',
   'surfaces.calendar.caldavPassword',
-  // Telephony delivery credentials — same shape, same file, same gap.
+  // Telephony delivery credentials, same shape, same file, same gap.
   'surfaces.telephony.authToken',
   'surfaces.telephony.token',
   'surfaces.telephony.webhookSecret',
@@ -43,7 +43,7 @@ export const SECRET_CONFIG_KEYS = new Set<ConfigKey>([
   'surfaces.mattermost.botToken',
   'surfaces.matrix.accessToken',
   // TUI-local synthetic sub-keys, one level under the SDK's real `payments`
-  // section (not a scalar CONFIG_SCHEMA entry — same situation as
+  // section (not a scalar CONFIG_SCHEMA entry, same situation as
   // behavior.notifyAfterSeconds and the other synthetics in
   // settings-modal-data.ts), hence the cast. See input/payments-config.ts for why these are named flat
   // (payments.cardNumber, not payments.card.number): a flat one-level leaf is
@@ -131,14 +131,14 @@ export function buildSecretBackedConfigUpdate(configKey: ConfigKey, rawValue: st
  * A daemon-owned config key (`surfaces.*`, `payments.*`, `controlPlane.*`, ...)
  * names a credential the DAEMON executes with, not this interactive client, so
  * its secret material belongs in the daemon-scoped tier the daemon actually
- * reads — the same rule the SDK's config-ownership.ts already applies to the
+ * reads, the same rule the SDK's config-ownership.ts already applies to the
  * `goodvibes://` reference that points at it.
  *
  * Defaulting these to 'user' (the historical behavior here) split the pair: the
  * reference landed in the daemon's own settings file, because ConfigManager
  * routes daemon-owned keys there, while the value it pointed at sat in a tier
  * the daemon never resolves. The surface reported success and the daemon found
- * nothing. For the mailbox password that is the whole feature failing silently —
+ * nothing. For the mailbox password that is the whole feature failing silently,
  * the daemon is the process that polls IMAP and answers over Telegram, and it
  * does so with every surface closed. A payment card entered through
  * /payments card is the same shape of failure at purchase time.
@@ -153,7 +153,7 @@ export function defaultSecretBackedScope(configKey: ConfigKey): SecretScope {
  * One call, not two: `credentials.set` derives the store key, writes the value,
  * reads it back to verify, and only then points the config key at it. Doing
  * those halves separately from here would leave a window where the config
- * names a reference that resolves to nothing — which every reader treats as a
+ * names a reference that resolves to nothing, which every reader treats as a
  * configured-but-broken credential.
  */
 export interface DaemonCredentialWriter {
@@ -173,7 +173,7 @@ export async function persistSecretBackedConfigValue(
 
   // A daemon-scoped credential is the daemon's to store, and the daemon does
   // the whole reference-and-value sequence atomically. This surface neither
-  // writes the config key nor the secret in that case — it would be writing
+  // writes the config key nor the secret in that case, it would be writing
   // both into a tree the daemon never reads.
   if (scope === 'daemon' && options.daemonWriter) {
     const trimmed = rawValue.trim();
@@ -182,7 +182,7 @@ export async function persistSecretBackedConfigValue(
       return '';
     }
     // Already a reference: the caller pasted one rather than a secret, so there
-    // is nothing to store — the config value is the whole write.
+    // is nothing to store, the config value is the whole write.
     if (isSecretReferenceValue(trimmed)) return trimmed;
     await options.daemonWriter.set(configKey, rawValue);
     return update.configValue;
@@ -198,7 +198,7 @@ export async function persistSecretBackedConfigValue(
     await secretsManager.set(update.secretKey, update.secretValue, { scope, medium });
   }
 
-  // 3. Clear old secret — pass the same medium so plaintext-medium secrets are found for deletion.
+  // 3. Clear old secret, pass the same medium so plaintext-medium secrets are found for deletion.
   if (update.clearSecretKey && secretsManager?.delete) {
     await secretsManager.delete(update.clearSecretKey, { scope, medium });
   }

package/src/config/surface.ts

@@ -1,5 +1,5 @@
 /**
- * surface.ts — the TUI's single surface-root identifier.
+ * surface.ts, the TUI's single surface-root identifier.
  *
  * Every piece of the TUI's own on-disk state (sessions, the last-session
  * pointer, recovery snapshots, checkpoints, the transcript journal, the

package/src/config/tui-extension-settings.ts

@@ -1,10 +1,10 @@
 /**
- * TUI-extension settings — config namespaces the TUI reads that are NOT part
+ * TUI-extension settings, config namespaces the TUI reads that are NOT part
  * of the SDK's ConfigManager schema.
  *
  * The SDK owns settings.json's typed schema (its `ConfigKey` union), but its
  * loader deep-merges user JSON over the defaults and only strips unknown
- * `permissions.tools` keys — every other unknown top-level key survives load
+ * `permissions.tools` keys, every other unknown top-level key survives load
  * and round-trips through `save()`. That lets the TUI keep its own namespaces
  * (e.g. `checkpoints.*`) in the same settings.json file and read them back
  * here via `getRaw()`.
@@ -45,7 +45,7 @@ function readNonEmptyString(src: RawRecord, key: string): string | undefined {
   return trimmed.length > 0 ? trimmed : undefined;
 }
 
-// ─── statusline.* — scriptable status line ───────────────────────────────────
+// ─── statusline.*, scriptable status line ───────────────────────────────────
 
 /**
  * User-settable scriptable status line. When `command` is present it is run as
@@ -63,7 +63,7 @@ export const STATUSLINE_DEFAULT_TIMEOUT_MS = 2000;
 const STATUSLINE_MIN_TIMEOUT_MS = 100;
 const STATUSLINE_MAX_TIMEOUT_MS = 15_000;
 
-// ─── session.* — session behavior ────────────────────────────────────────────
+// ─── session.*, session behavior ────────────────────────────────────────────
 
 /** User-settable session behavior. */
 export interface SessionSettings {
@@ -99,7 +99,7 @@ export function readStatuslineSettings(configManager: Pick<ConfigManager, 'getRa
   return out;
 }
 
-// ─── update.* — launch-time self-update behavior ─────────────────────────────
+// ─── update.*, launch-time self-update behavior ─────────────────────────────
 
 /**
  * User-settable launch-time self-update behavior. The feature itself (check at
@@ -140,7 +140,7 @@ export function readUpdateSettings(configManager: Pick<ConfigManager, 'getRaw'>)
   return out;
 }
 
-// ─── checkpoints.* — workspace checkpoint root-guard options ─────────────────
+// ─── checkpoints.*, workspace checkpoint root-guard options ─────────────────
 
 /**
  * User-settable root-guard options for the SDK's WorkspaceCheckpointManager.
@@ -165,12 +165,12 @@ export interface CheckpointGuardSettings {
  * WorkspaceCheckpointManager options object.
  *
  * NOTE: the pinned platform SDK's WorkspaceCheckpointManager may predate these
- * root-guard options — an older constructor reads only
+ * root-guard options, an older constructor reads only
  * workspaceRoot/checkpointDir/runtimeBus/retention/now and silently ignores the
  * rest, making the guard keys INERT. They become effective the moment the SDK
  * is upgraded to a build whose options type declares them (preferGitRoot,
  * allowBroadRoot, allowLargeFirstSnapshot, maxFirstSnapshotFiles,
- * autoRetention) — no code change needed here. The return type intersects the
+ * autoRetention), no code change needed here. The return type intersects the
  * base with CheckpointGuardSettings so the extra keys flow through structurally
  * without an unsafe cast.
  */

package/src/core/active-model-identity.ts

@@ -1,5 +1,5 @@
 /**
- * active-model-identity.ts — the single answer to "which backend is serving
+ * active-model-identity.ts, the single answer to "which backend is serving
  * this session right now, and is that what the user chose?"
  *
  * Two shell surfaces used to answer that question independently and could
@@ -13,8 +13,8 @@
  *
  * Both surfaces now resolve through resolveActiveModelDisplay() so they are
  * computed from one comparison of serving-vs-configured. Divergence is
- * detected structurally — by comparing the live registry key against the
- * configured selection — not by trusting a flag, so ANY path that moves the
+ * detected structurally, by comparing the live registry key against the
+ * configured selection, not by trusting a flag, so ANY path that moves the
  * registry off the user's choice is surfaced, not just the failover path that
  * sets the record below.
  *
@@ -46,11 +46,11 @@ export interface FailoverTurnState {
   current(): FailoverTurnRecord | null;
   /**
    * Record a failover switch. On a second switch within the same turn the
-   * originally-configured key is preserved — divergence is always reported
+   * originally-configured key is preserved, divergence is always reported
    * against the user's own selection.
    */
   begin(record: FailoverTurnRecord): void;
-  /** Drop the record — called only after serving is actually back on the configured selection. */
+  /** Drop the record, called only after serving is actually back on the configured selection. */
   clear(): void;
 }
 
@@ -76,7 +76,7 @@ export interface ServingModelIdentity {
 }
 
 export interface ActiveModelInputs {
-  /** Live registry answer — who is actually serving right now. */
+  /** Live registry answer, who is actually serving right now. */
   readonly serving: ServingModelIdentity;
   /** The user's configured selection as a registry key (config `provider.model`). */
   readonly configuredRegistryKey: string | undefined;
@@ -100,7 +100,7 @@ export interface ActiveModelDisplay {
   /**
    * Divergence marker naming the configured selection, e.g.
    * `failover from abacusai:route-llm`. Empty string when serving is the
-   * configured selection — in that case both surfaces render exactly as they
+   * configured selection, in that case both surfaces render exactly as they
    * did before this resolver existed.
    */
   readonly divergenceNote: string;

package/src/core/approval-alert.ts

@@ -1,9 +1,9 @@
 /**
- * approval-alert — fires an unfocused-user alert the moment a tool call
+ * approval-alert, fires an unfocused-user alert the moment a tool call
  * becomes a real, user-blocking permission prompt.
  *
  * Anchor: `PERMISSION_REQUESTED` (SDK events/permissions.ts) is the wrong
- * signal — it fires for every policy-evaluation step, including ones
+ * signal, it fires for every policy-evaluation step, including ones
  * auto-resolved by allow-lists/yolo-mode in milliseconds. The only place a
  * request becomes an actual user-facing prompt is where main.ts assigns
  * `permissionPromptRef.requestPermission`. There is no `permissions` feed on
@@ -14,7 +14,7 @@
  * wrapped promise settles) so it reflects "a prompt just appeared", not
  * "a prompt was just resolved".
  *
- * PRIVACY: message content is tool name + permission category only — no
+ * PRIVACY: message content is tool name + permission category only, no
  * args, no file contents, no command strings (mirrors long-task-notifier's
  * privacy guarantee).
  */
@@ -43,7 +43,7 @@ export interface ApprovalAlertDeps {
  * Wrap a PermissionRequestHandler so every call also fires an unfocused-user
  * alert (subject to the behavior.notifyOnApprovalPending / notifyOnlyWhenUnfocused
  * gates). The wrapped handler's behavior (what it resolves to) is completely
- * unchanged — this only adds a side effect at call time.
+ * unchanged, this only adds a side effect at call time.
  */
 export function wrapRequestPermissionWithAlert(
   original: PermissionRequestHandler,
@@ -65,7 +65,7 @@ function fireApprovalAlert(request: PermissionPromptRequest, deps: ApprovalAlert
 
   if (!shouldFireAlert(deps.focusTracker, deps.configGet, 'behavior.notifyOnApprovalPending')) return;
 
-  const title = 'GoodVibes — approval needed';
+  const title = 'GoodVibes: approval needed';
 
   try {
     notifyCompletion(title, message, FORCE_NOTIFY_DURATION_MS);

package/src/core/bookmark-navigation.ts

@@ -1,12 +1,12 @@
 /**
- * bookmark-navigation.ts — fallback resolution for a bookmark whose direct
+ * bookmark-navigation.ts, fallback resolution for a bookmark whose direct
  * BlockMeta lookup misses.
  *
  * A bookmark stores a block's collapseKey at the time it was set (see
  * handler-content-actions.ts's handleBookmark). A tool-result message that is
  * a non-owning member of a folded tool-result group (see
  * conversation-tool-groups.ts) pushes no BlockMeta of its own while the group
- * stays collapsed — its own collapseKey (`msg_<absoluteIdx>`) never appears
+ * stays collapsed, its own collapseKey (`msg_<absoluteIdx>`) never appears
  * in getBlockRegistry() until the group is expanded. A direct
  * find(entry => entry.collapseKey === key) then reports "not found", even
  * though the message is still present in the transcript, just folded under
@@ -18,7 +18,7 @@
  * for a folded group member, already resolves to the group's own header line
  * rather than the position of whatever renders next (see getMessageLine's
  * doc and conversation-rendering.ts / conversation-line-cache.ts, which
- * anchor a folded member's registered line at its group's header) — landing
+ * anchor a folded member's registered line at its group's header), landing
  * on the header is an honest, reachable result rather than a false
  * "not found".
  */

package/src/core/budget-breach-notifier.ts

@@ -1,5 +1,5 @@
 /**
- * budget-breach-notifier — fires an unfocused-user alert the moment session
+ * budget-breach-notifier, fires an unfocused-user alert the moment session
  * cost crosses the configured budget threshold (behavior.budgetAlertUsd).
  *
  * One-shot semantics: fires exactly once on the false→true edge (crossing
@@ -12,12 +12,12 @@
  * Delivery mirrors long-task-notifier.ts: desktop notification
  * (notifyCompletion) + outbound webhook (WebhookNotifier), both gated by
  * the shared focus/config gating in alert-gating.ts. Skips evaluation
- * entirely when the session model is unpriced — a $0 placeholder cost must
+ * entirely when the session model is unpriced, a $0 placeholder cost must
  * never be reported as a real breach (mirrors CostTrackerPanel's "unpriced"
  * display convention).
  *
  * PRIVACY: message text is built from cost/threshold numbers and the
- * session id prefix only — no conversation content.
+ * session id prefix only, no conversation content.
  */
 import { notifyCompletion } from '@pellux/goodvibes-sdk/platform/utils';
 import { logger } from '@pellux/goodvibes-sdk/platform/utils';
@@ -40,7 +40,7 @@ export interface BudgetBreachNotifierDeps {
   readonly sessionId: string;
 }
 
-/** Stateful edge-trigger checker — construct once per session, call on every TURN_COMPLETED. */
+/** Stateful edge-trigger checker, construct once per session, call on every TURN_COMPLETED. */
 export interface BudgetBreachNotifier {
   /**
    * Evaluate current usage against the configured threshold and fire an
@@ -57,7 +57,7 @@ export function createBudgetBreachNotifier(deps: BudgetBreachNotifierDeps): Budg
   return {
     check(usage, sessionModel, budgetThresholdUsd) {
       if (budgetThresholdUsd !== lastThreshold) {
-        // Threshold raised, lowered, or cleared since the last check — re-arm
+        // Threshold raised, lowered, or cleared since the last check, re-arm
         // the latch so a breach against the new threshold can fire again.
         lastThreshold = budgetThresholdUsd;
         notified = false;
@@ -85,7 +85,7 @@ export function createBudgetBreachNotifier(deps: BudgetBreachNotifierDeps): Budg
 function fireBudgetBreachAlert(deps: BudgetBreachNotifierDeps, sessionCost: number, budgetThresholdUsd: number): void {
   if (!shouldFireAlert(deps.focusTracker, deps.configGet, 'behavior.notifyOnBudgetBreach')) return;
 
-  const title = 'GoodVibes — budget breach';
+  const title = 'GoodVibes: budget breach';
   const message = `session cost $${sessionCost.toFixed(2)} exceeded budget $${budgetThresholdUsd.toFixed(2)}  ·  session ${deps.sessionId.slice(0, 8)}`;
 
   try {

package/src/core/compaction-receipt.ts

@@ -4,14 +4,14 @@
  * The SDK emits a mandatory COMPACTION_RECEIPT event after every automatic (and
  * the manual) compaction path, so a compaction is never silent. This module
  * turns that receipt into a distinct, multi-line `[Compaction]` block for the
- * transcript. It is a pure formatter — no state, no I/O — so it is unit-testable
+ * transcript. It is a pure formatter, no state, no I/O, so it is unit-testable
  * and the wiring layer only has to route the returned string.
  *
  * Why a visible receipt: automatic behavior (the orchestrator's post-turn
  * auto-compaction) previously ran without any transcript trace. The receipt
  * makes the audit trail visible: what was compacted, the quality the guard
  * computed, whether the standing-instruction chain was re-injected, and the
- * outcome — applied, kept-original (quality guard rejected it), or failed.
+ * outcome, applied, kept-original (quality guard rejected it), or failed.
  *
  * The `[Compaction]` prefix is one of the FORCE_CONVERSATION_PREFIXES the
  * system-message router always surfaces inline (see system-message-router.ts),
@@ -41,7 +41,7 @@ export interface CompactionReceiptInput {
   readonly detail?: string | undefined;
   /**
    * The strategy the caller REQUESTED (from `behavior.compactionStrategy`),
-   * present only when it differs from `strategy` — i.e. a distiller→structured
+   * present only when it differs from `strategy`, i.e. a distiller→structured
    * fallback happened. `strategy` always names what actually ran.
    */
   readonly requestedStrategy?: string | undefined;
@@ -57,11 +57,11 @@ function fmtN(n: number): string {
 function describeOutcome(outcome: CompactionReceiptInput['outcome']): string {
   switch (outcome) {
     case 'applied':
-      return 'applied — compacted context committed';
+      return 'applied: compacted context committed';
     case 'kept-original':
-      return 'kept original — quality guard rejected the summary, conversation retained';
+      return 'kept original: quality guard rejected the summary, conversation retained';
     case 'failed':
-      return 'failed — compaction did not produce a usable result';
+      return 'failed: compaction did not produce a usable result';
     default:
       return outcome;
   }
@@ -80,7 +80,7 @@ export function buildCompactionReceiptBlock(receipt: CompactionReceiptInput): st
     : 0;
 
   const lines: string[] = [];
-  lines.push(`[Compaction] Receipt — ${triggerWord.toLowerCase()} compaction, outcome: ${describeOutcome(receipt.outcome)}`);
+  lines.push(`[Compaction] Receipt: ${triggerWord.toLowerCase()} compaction, outcome: ${describeOutcome(receipt.outcome)}`);
 
   // Only report the size delta when the summary was actually applied; on
   // kept-original / failed the "after" counts describe the retained original,
@@ -99,7 +99,7 @@ export function buildCompactionReceiptBlock(receipt: CompactionReceiptInput): st
   const qualitySuffix = receipt.lowQuality ? ' (below the quality bar)' : '';
   lines.push(`  Quality: ${gradeStr}${Math.round(receipt.qualityScore)}/100${qualitySuffix} · strategy: ${receipt.strategy || 'unknown'}.`);
 
-  // Only present on a distiller→structured fallback — say plainly what was
+  // Only present on a distiller→structured fallback, say plainly what was
   // requested, what actually ran, and why, so the fallback is never silent.
   if (receipt.requestedStrategy && receipt.requestedStrategy !== receipt.strategy) {
     const reasonSuffix = receipt.strategyFallbackReason ? `: ${receipt.strategyFallbackReason}` : '';

package/src/core/composer-state.ts

@@ -22,7 +22,7 @@ export function deriveComposerState(input: ComposerStateInput): ComposerState {
 
   // An approval wait is the dominant composer state and owns the single honest
   // status tag: `risk:approval-wait`. It is therefore NOT also duplicated as a
-  // `approval` flag, and (below) it suppresses the competing `state:` turn tag —
+  // `approval` flag, and (below) it suppresses the competing `state:` turn tag,
   // the turn is blocked on the user, not really streaming. Precedence:
   // approval-wait > live turn state. (item 4.)
   const approvalWait = input.pendingApproval === true;
@@ -53,7 +53,7 @@ export function deriveComposerState(input: ComposerStateInput): ComposerState {
     }
   })();
   // 'idle' is suppressed by the footer renderer, so an approval wait shows only
-  // `risk:approval-wait` — one honest tag, not three spellings of the wait.
+  // `risk:approval-wait`, one honest tag, not three spellings of the wait.
   const statusLabel = approvalWait ? 'idle' : turnStatus;
 
   return {

package/src/core/context-usage.ts

@@ -6,7 +6,7 @@
  * hand-rolled copies.
  *
  * IMPORTANT: compaction-preview.ts intentionally displays usage > 100%
- * ("exceeds window") — callers that need the unclamped value must use
+ * ("exceeds window"), callers that need the unclamped value must use
  * rawRatio, not clampedRatio / pct.
  */
 

package/src/core/conversation-compaction-render.ts

@@ -1,5 +1,5 @@
 /**
- * conversation-compaction-render.ts — folds a compaction-continuation user
+ * conversation-compaction-render.ts, folds a compaction-continuation user
  * message (the instruction block the compactor re-injects after an automatic
  * compaction) to one header + preview line.
  *
@@ -16,7 +16,7 @@ import type { BlockMeta } from './conversation-types.ts';
 
 /**
  * The slice of the render context this module needs, declared structurally
- * rather than imported from conversation-rendering.ts — that import would form
+ * rather than imported from conversation-rendering.ts, that import would form
  * a 2-file cycle the architecture check rejects, and this module only ever
  * touches these three fields.
  */
@@ -62,7 +62,7 @@ export function renderCompactionContinuationMessage(
 
   if (isCollapsed) {
     // One row. This used to be the header PLUS a framed fragment holding a
-    // single static sentence — three rows of chrome to say what the label and
+    // single static sentence, three rows of chrome to say what the label and
     // the badge already said. The distinguishing half of that sentence folds
     // onto the header instead.
     context.history.addLine(renderConversationFoldedRow(

package/src/core/conversation-event-navigation.ts

@@ -1,5 +1,5 @@
 /**
- * conversation-event-navigation.ts — resolving "jump to the next/previous
+ * conversation-event-navigation.ts, resolving "jump to the next/previous
  * transcript event" into a history-buffer line number.
  *
  * Extracted from ConversationManager (core/conversation.ts), which is at its
@@ -8,7 +8,7 @@
  *
  * The rule both directions share: take the events of the requested kind, map
  * each to the line its message was rendered at, drop the ones that were never
- * rendered (a message with no registry entry), sort ascending, then wrap —
+ * rendered (a message with no registry entry), sort ascending, then wrap,
  * searching forward past `currentLine` falls back to the first line, searching
  * backward falls back to the last. -1 means there is nowhere to go.
  */