@pellux/goodvibes-tui 2.0.14 → 2.0.16

package/src/renderer/terminal-bg-probe.ts

@@ -1,5 +1,5 @@
 /**
- * terminal-bg-probe — OSC 11 terminal-background detection for `auto` theme mode.
+ * terminal-bg-probe, OSC 11 terminal-background detection for `auto` theme mode.
  *
  *. On startup, when appearance is `auto` and stdout is a TTY, we ask
  * the terminal for its background colour with an OSC 11 query and classify the
@@ -7,21 +7,21 @@
  * any timeout, any unparseable reply, any ambiguity resolves to DARK, which is
  * the historical default and keeps headless/unsupported terminals byte-stable.
  *
- * Timing (Option B — render dark first, repaint once if light wins):
+ * Timing (Option B, render dark first, repaint once if light wins):
  *   The probe never blocks startup. The splash renders immediately in dark; if a
  *   light reply arrives within the timeout window the caller flips the active mode
  *   to light and repaints ONCE. Rationale vs. blocking the first paint until the
  *   reply/timeout: blocking would tax EVERY non-responding terminal (tmux without
  *   passthrough, CI, old SSH hosts, dumb terminals) with up to `timeoutMs` of blank
- *   screen on every launch — the common failure case. Option B adds zero startup
+ *   screen on every launch, the common failure case. Option B adds zero startup
  *   latency and costs at most a single dark→light repaint on genuinely light
  *   terminals (rare for this audience, one frame).
  *
  * Stream safety (never corrupt the composer):
  *   The reply arrives on the same stdin the keyboard uses. filterInput() sits at
  *   the very front of the stdin handler (before blocking-input / paste / the
- *   tokenizer). It passes every non-OSC-11 byte straight through — interleaved
- *   keystrokes reach the tokenizer untouched — and consumes ONLY a matched OSC 11
+ *   tokenizer). It passes every non-OSC-11 byte straight through, interleaved
+ *   keystrokes reach the tokenizer untouched, and consumes ONLY a matched OSC 11
  *   reply (whole or split across chunks). On timeout, any buffered reply fragment
  *   is discarded rather than flushed, so partial/garbled response bytes can never
  *   leak into the input pipeline.
@@ -111,7 +111,7 @@ export function parseColorSpec(spec: string): ProbeRgb | null {
  * Classify a background colour as 'light' or 'dark' by relative luminance.
  * Uses the Rec. 601 luma weights (0.299/0.587/0.114) normalized to 0..1 and
  * splits at LUMINANCE_LIGHT_THRESHOLD (0.5): a background at least half as
- * luminous as white reads as light. Conservative by construction — the exact
+ * luminous as white reads as light. Conservative by construction, the exact
  * threshold only matters for mid-grey backgrounds, which are rare.
  */
 export function classifyBackgroundLuminance(rgb: ProbeRgb): ThemeMode {
@@ -130,7 +130,7 @@ interface TerminatorSpan {
  * Returns null if no terminator is present yet (reply still arriving). A lone
  * trailing ESC returns null (wait for the next byte to tell ST from a stray ESC);
  * an ESC followed by a non-'\' byte is treated as the end boundary (malformed
- * terminator — the body before it is still parsed, the stray byte passes through).
+ * terminator, the body before it is still parsed, the stray byte passes through).
  */
 function findTerminator(buffer: string, from: number): TerminatorSpan | null {
   for (let k = from; k < buffer.length; k++) {
@@ -159,7 +159,7 @@ function trailingPrefixLen(buffer: string): number {
 }
 
 // ---------------------------------------------------------------------------
-// TerminalBackgroundProbe — the stateful stream filter + timing
+// TerminalBackgroundProbe, the stateful stream filter + timing
 // ---------------------------------------------------------------------------
 
 export interface ProbeResolution {
@@ -177,7 +177,7 @@ export interface TerminalBackgroundProbeOptions {
 /**
  * Stateful OSC 11 reply filter. feed() takes a raw stdin chunk and returns the
  * bytes that should continue down the input pipeline (everything except a matched
- * OSC 11 reply). Resolves once — on the first complete reply or on timeout.
+ * OSC 11 reply). Resolves once, on the first complete reply or on timeout.
  */
 export class TerminalBackgroundProbe {
   /** True until resolved. filterInput() only calls feed() while active. */
@@ -259,7 +259,7 @@ export class TerminalBackgroundProbe {
       clearTimeout(this.timer);
       this.timer = null;
     }
-    // Any bytes still buffered here are an incomplete/garbled reply fragment —
+    // Any bytes still buffered here are an incomplete/garbled reply fragment,
     // discard them so they can never leak into the composer.
     this.buffer = '';
     this.onResolve({ mode, reason });

package/src/renderer/terminal-escapes.ts

@@ -1,5 +1,5 @@
 /**
- * terminal-escapes — the raw control sequences main.ts writes to enter/leave the
+ * terminal-escapes, the raw control sequences main.ts writes to enter/leave the
  * TUI's terminal mode (alt screen, mouse, cursor, keyboard-extension, paste, and
  * focus reporting). Extracted from main.ts as plain constants so the entry file
  * stays within the source-file line-count gate; behaviour is unchanged.

package/src/renderer/theme-mode-config.ts

@@ -1,9 +1,9 @@
 /**
- * theme-mode-config — the appearance/theme-mode preference, TUI-side.
+ * theme-mode-config, the appearance/theme-mode preference, TUI-side.
  *
  * The preference lives at the config key `display.themeMode` (auto | dark |
  * light, default auto), stored under the existing SDK `display` section
- * alongside `display.theme` (the color palette — a separate, independent
+ * alongside `display.theme` (the color palette, a separate, independent
  * concept: theme picks the palette, themeMode picks light/dark appearance).
  *
  * `display.themeMode` is a real CONFIG_SCHEMA entry (SDK 2.0.0+); this module
@@ -28,7 +28,7 @@ export const THEME_MODE_CONFIG_KEY: ConfigKey = 'display.themeMode';
 /**
  * Default when unset: probe the terminal background on startup. Matches the
  * CONFIG_SCHEMA default for display.themeMode (module-private: nothing
- * outside this file needs the default value directly — callers read the
+ * outside this file needs the default value directly, callers read the
  * resolved mode via coerceThemeModeSetting/resolveConfiguredThemeMode).
  */
 const THEME_MODE_DEFAULT: ThemeModeSetting = 'auto';

package/src/renderer/theme.ts

@@ -1,5 +1,5 @@
 /**
- * theme.ts — Semantic colour token layer.
+ * theme.ts, Semantic colour token layer.
  *
  * Defines named tokens for every colour decision in the markdown/compositor/
  * conversation-rendering pipeline, resolved to concrete hex or ANSI-256 values
@@ -16,7 +16,7 @@
  * Differentiate inline code via inlineCodeFg + bold only; bg inherits terminal.
  *
  * resolveUiTones(mode) is the sibling read path for CHROME tokens (UI_TONES
- * in ui-primitives.ts — panel/modal/overlay/fullscreen backgrounds, borders,
+ * in ui-primitives.ts, panel/modal/overlay/fullscreen backgrounds, borders,
  * status colours). It composes the same ThemeMode dimension so that
  * DEFAULT_PANEL_PALETTE, DEFAULT_STYLE, FULLSCREEN_PALETTE and
  * DEFAULT_OVERLAY_PALETTE all read through ONE mode-resolved path instead of
@@ -26,7 +26,7 @@
 
 import { UI_TONES } from './ui-primitives.ts';
 
-/** Background mode — dark is the safe default for an unprobed terminal. */
+/** Background mode, dark is the safe default for an unprobed terminal. */
 export type ThemeMode = 'dark' | 'light';
 
 /** Resolved semantic colour tokens (concrete hex strings or ANSI-256 indices). */
@@ -35,7 +35,7 @@ export interface ThemeTokens {
   heading1: string;
   /** H2 heading foreground */
   heading2: string;
-  /** H3 heading foreground (ANSI-256 — falls back to nearest on ansi256 terminals) */
+  /** H3 heading foreground (ANSI-256, falls back to nearest on ansi256 terminals) */
   heading3: string;
   /** Inline code foreground (bold is applied separately by caller) */
   inlineCodeFg: string;
@@ -69,7 +69,7 @@ export interface ThemeTokens {
   modelNameDim: string;
   /** Tool name foreground in tool-result event line */
   toolNameFg: string;
-  /** Diff block accent — marker, label, and collapsed-prefix foreground */
+  /** Diff block accent, marker, label, and collapsed-prefix foreground */
   diffAccent: string;
 }
 
@@ -103,13 +103,13 @@ const DARK: ThemeTokens = {
 // Light palette
 //
 // Rationale per token:
-//   heading1/2:        Deep teal (#0077aa) — readable on white/cream terminals
+//   heading1/2:        Deep teal (#0077aa), readable on white/cream terminals
 //   heading3:          ANSI-256 #244 equivalent on light bg → use 24 (dark cyan)
-//   inlineCodeFg:      Dark orange (#b45309) — distinguishable without a box bg
-//   link:              Standard blue (#0055cc) — matches browser convention
-//   searchMatchBg:     Muted yellow (#ffe066) — visible on light bg
+//   inlineCodeFg:      Dark orange (#b45309), distinguishable without a box bg
+//   link:              Standard blue (#0055cc), matches browser convention
+//   searchMatchBg:     Muted yellow (#ffe066), visible on light bg
 //   searchMatchFg:     Black (#000000)
-//   searchCurrentBg:   Strong amber (#f59e0b) — current match is more vivid
+//   searchCurrentBg:   Strong amber (#f59e0b), current match is more vivid
 //   searchCurrentFg:   Black (#000000)
 //   strikethrough:     Medium gray (ANSI-256 244 stays; light terminals map it fine)
 //   blockquote:        Dim blue-gray (ANSI-256 67)
@@ -117,11 +117,11 @@ const DARK: ThemeTokens = {
 //   reasoningAccent:   Dark purple (#7c3aed)
 //   toolAccent:        Dark sky (#0369a1)
 //   collapsedBodyBg:   Very light gray (#f3f4f6)
-//   checkboxChecked:   Forest green (#15803d) — AA on white (contrast ~5.2:1 on #fff)
-//   errorBarBg:        Soft rose (#fee2e2) — light error bar bg, legible text on top
-//   modelNameDim:      Slate-500 (#64748b) — dim label; contrast ~4.6:1 on #fff
-//   toolNameFg:        Slate-800 (#334155) — strong enough for tool names
-//   diffAccent:        Amber-700 (#b45309) — darker amber, contrast ~4.7:1 on #fff
+//   checkboxChecked:   Forest green (#15803d), AA on white (contrast ~5.2:1 on #fff)
+//   errorBarBg:        Soft rose (#fee2e2), light error bar bg, legible text on top
+//   modelNameDim:      Slate-500 (#64748b), dim label; contrast ~4.6:1 on #fff
+//   toolNameFg:        Slate-800 (#334155), strong enough for tool names
+//   diffAccent:        Amber-700 (#b45309), darker amber, contrast ~4.7:1 on #fff
 // ---------------------------------------------------------------------------
 const LIGHT: ThemeTokens = {
   heading1:        '#0077aa',
@@ -147,10 +147,10 @@ const LIGHT: ThemeTokens = {
 };
 
 /**
- * resolveTheme — Return the semantic token set for the given background mode.
+ * resolveTheme, Return the semantic token set for the given background mode.
  *
  * Call with the session's resolved mode; 'dark' is the safe default for a
- * caller that has none. The returned object is frozen — do not mutate it.
+ * caller that has none. The returned object is frozen, do not mutate it.
  */
 export function resolveTheme(mode: ThemeMode): Readonly<ThemeTokens> {
   return mode === 'light' ? LIGHT : DARK;
@@ -163,15 +163,15 @@ Object.freeze(LIGHT);
 
 /**
  * Default dark-mode token set, exported for convenience.
- * Frozen — do not mutate.
+ * Frozen, do not mutate.
  */
 export const DARK_THEME: Readonly<ThemeTokens> = DARK;
 
 // ---------------------------------------------------------------------------
-// Chrome tokens (UI_TONES) — mode-resolved sibling to resolveTheme().
+// Chrome tokens (UI_TONES), mode-resolved sibling to resolveTheme().
 //
 // UI_TONES (ui-primitives.ts) is the dark entry. The light entry mirrors
-// dark for every role that has no light-appropriate equivalent yet — the
+// dark for every role that has no light-appropriate equivalent yet, the
 // deliverable is the mode dimension and single read path, not a
 // shipped light chrome theme (see module doc comment above).
 // ---------------------------------------------------------------------------
@@ -184,19 +184,19 @@ type DeepWidenToString<T> = T extends string ? string : { [K in keyof T]: DeepWi
 export type UiToneTokens = DeepWidenToString<typeof UI_TONES>;
 
 //
-// chrome.* — persistent header/footer/thinking foregrounds that paint on the
+// chrome.*, persistent header/footer/thinking foregrounds that paint on the
 // TRANSPARENT terminal background (see the chrome group's doc in
 // ui-primitives.ts). Unlike fg.muted/fg.dim (which stay light for the opaque
 // dark modal/panel boxes), these invert toward dark so they read on a light
 // terminal. Contrast ratios below are against a white terminal (#ffffff),
 // matching the discipline of the LIGHT ThemeTokens above:
-//   label: Slate-500 (#64748b) — header title; ~4.9:1 on #fff (matches modelNameDim)
-//   faint: Slate-400 (#94a3b8) — version/rule/clean-git; ~2.7:1 on #fff, deliberately
+//   label: Slate-500 (#64748b), header title; ~4.9:1 on #fff (matches modelNameDim)
+//   faint: Slate-400 (#94a3b8), version/rule/clean-git; ~2.7:1 on #fff, deliberately
 //          faint (mirrors the low-contrast intent of the dark fg.dim role)
-//   warn:  Amber-700 (#b45309) — dirty git / pending risk; ~5.0:1 on #fff (matches diffAccent)
-//   bad:   Red-600  (#dc2626) — DANGER banner / shell risk (bold); ~5.3:1 on #fff
-//   good:  Forest-700 (#15803d) — tool-call ✓ status; ~5.02:1 on #fff (matches checkboxChecked)
-//   remote: Violet-700 (#6d28d9) — risk:remote marker / plain status; ~7.10:1 on #fff,
+//   warn:  Amber-700 (#b45309), dirty git / pending risk; ~5.0:1 on #fff (matches diffAccent)
+//   bad:   Red-600  (#dc2626), DANGER banner / shell risk (bold); ~5.3:1 on #fff
+//   good:  Forest-700 (#15803d), tool-call ✓ status; ~5.02:1 on #fff (matches checkboxChecked)
+//   remote: Violet-700 (#6d28d9), risk:remote marker / plain status; ~7.10:1 on #fff,
 //          deliberately distinct from reasoningAccent (#7c3aed) so the remote-risk cue
 //          never reads as a reasoning accent on a light terminal
 const UI_TONES_LIGHT: UiToneTokens = {
@@ -229,11 +229,11 @@ Object.freeze(UI_TONES_LIGHT.chrome);
 Object.freeze(UI_TONES_LIGHT);
 
 /**
- * resolveUiTones — Return the chrome (panel/modal/overlay/fullscreen) token
+ * resolveUiTones, Return the chrome (panel/modal/overlay/fullscreen) token
  * set for the given background mode. Single read path for UI_TONES; the
  * 'dark' resolution is byte-identical to the UI_TONES constant.
  *
- * Prefer activeUiTones() at call sites — resolveUiTones is the pure per-mode
+ * Prefer activeUiTones() at call sites, resolveUiTones is the pure per-mode
  * resolver underneath it.
  */
 export function resolveUiTones(mode: ThemeMode): Readonly<UiToneTokens> {
@@ -243,8 +243,8 @@ export function resolveUiTones(mode: ThemeMode): Readonly<UiToneTokens> {
 // ===========================================================================
 // Active-mode runtime.
 //
-// The mode is decided ONCE at startup — from appearance config (display.themeMode
-// forced dark/light) or the terminal-background probe (auto) — and is then stable
+// The mode is decided ONCE at startup, from appearance config (display.themeMode
+// forced dark/light) or the terminal-background probe (auto), and is then stable
 // for the session. Two read shapes exist because the two token layers are
 // consumed differently:
 //
@@ -277,7 +277,7 @@ const themeRefreshers: Array<() => void> = [];
  * Register an in-place palette rebuild to run whenever the active mode changes.
  * Base-palette owners register at their own module-eval time (before any
  * extendPalette-derived palette, which depends on the base), so refreshers run
- * base-first — the ordering the extended palettes require to re-merge correctly.
+ * base-first, the ordering the extended palettes require to re-merge correctly.
  */
 export function registerThemeRefresh(rebuild: () => void): void {
   themeRefreshers.push(rebuild);
@@ -293,12 +293,12 @@ export function setActiveThemeMode(mode: ThemeMode): void {
   for (const rebuild of themeRefreshers) rebuild();
 }
 
-/** Transcript tokens for the active mode — read live, per render. */
+/** Transcript tokens for the active mode, read live, per render. */
 export function activeTheme(): Readonly<ThemeTokens> {
   return resolveTheme(activeMode);
 }
 
-/** Chrome tokens for the active mode — used to build (and rebuild) palettes. */
+/** Chrome tokens for the active mode, used to build (and rebuild) palettes. */
 export function activeUiTones(): Readonly<UiToneTokens> {
   return resolveUiTones(activeMode);
 }

package/src/renderer/thinking.ts

@@ -8,7 +8,7 @@ export function renderThinkingBlock(text: string, width: number): Line[] {
   // terminal background (renderConversationNotice passes no bodyBg), so both
   // colors resolve per-render through activeUiTones() to stay legible on a
   // light terminal. Dark values are byte-identical to the prior static reads
-  // (state.reasoning for the accent, chrome.faint — which equals fg.dim — for
+  // (state.reasoning for the accent, chrome.faint, which equals fg.dim, for
   // the body text).
   const t = activeUiTones();
   return renderConversationNotice(

package/src/renderer/tool-call.ts

@@ -198,9 +198,9 @@ export function renderToolCallBlock(
 
 
   // Status icon. 'pending' means the tool is still awaiting a decision
-  // (e.g. an approval prompt) and has NOT run yet — it uses the hollow idle
+  // (e.g. an approval prompt) and has NOT run yet, it uses the hollow idle
   // glyph so a not-yet-run tool never shows the completed green ✓ (2c).
-  // 'cancelled' means the user stopped THIS call mid-flight — the blocked glyph
+  // 'cancelled' means the user stopped THIS call mid-flight, the blocked glyph
   // in the warn tone, distinct from both success and a real error.
   const icon = status === 'done' ? TOOL_STATUS.SUCCESS_ICON
     : status === 'error' ? TOOL_STATUS.FAIL_ICON
@@ -233,8 +233,8 @@ export function renderToolCallBlock(
     : contentEnd;
   let col: number = leftStart;
 
-  // In tree mode the status glyph goes in the bullet column — the same column
-  // as the `●` of the `● assistant` header this row hangs under — so a turn's
+  // In tree mode the status glyph goes in the bullet column, the same column
+  // as the `●` of the `● assistant` header this row hangs under, so a turn's
   // markers read as that bullet's column continuing down the turn. The row's
   // own text then starts at its depth's text column with no inline icon slot.
   if (inTree) {
@@ -246,7 +246,7 @@ export function renderToolCallBlock(
     col += 2; // icon + space
   }
 
-  // Tool name — extract short name for long MCP tool names, but keep a readable dynamic width.
+  // Tool name, extract short name for long MCP tool names, but keep a readable dynamic width.
   const rawName = toolCall.name.includes('__')
     ? toolCall.name.split('__').pop()!
     : toolCall.name;

package/src/renderer/tool-result-expanded-lines.ts

@@ -1,10 +1,10 @@
 /**
- * tool-result-expanded-lines.ts — the single source of truth for how many
+ * tool-result-expanded-lines.ts, the single source of truth for how many
  * screen lines a tool-result message's EXPANDED form actually renders to.
  *
  * Tool-result content gets pretty-printed (JSON.stringify(parsed, null, 2))
  * or diff-rendered before display, so the raw message's `content.split('\n')`
- * length is not what the user sees once expanded — a one-line JSON blob can
+ * length is not what the user sees once expanded, a one-line JSON blob can
  * pretty-print to 50 lines. Both the per-block "N lines" badge
  * (conversation-rendering.ts) and the folded-group total (conversation-tool-
  * groups.ts) must count the SAME post-render lines, or the two disagree with
@@ -41,7 +41,7 @@ export function renderExpandedToolResultLines(content: string, width: number): L
       const parsed = JSON.parse(contentToRender);
       contentToRender = `\`\`\`json\n${JSON.stringify(parsed, null, 2)}\n\`\`\``;
     } catch {
-      // Leave invalid JSON as-is — falls through to the plain markdown render below.
+      // Leave invalid JSON as-is, falls through to the plain markdown render below.
     }
   }
   return renderMarkdownTracked(contentToRender, width).lines;

package/src/renderer/tool-result-summary.ts

@@ -1,12 +1,12 @@
 /**
- * summarizeToolResult — one-line human summaries for tool RESULTS, so the
+ * summarizeToolResult, one-line human summaries for tool RESULTS, so the
  * transcript (and the fleet attach view, which shares the same rendering seam
  * in conversation-rendering.ts) shows "wrote haiku.txt (532 B)" instead of a
  * raw `{"files_written":1,"bytes_written":532,...}` JSON blob. The full payload
- * stays reachable behind the existing collapse/expand toggle — this only
+ * stays reachable behind the existing collapse/expand toggle, this only
  * changes the collapsed preview line, never destroys data. (item 3.)
  *
- * Returning `null` means "no honest summary for this shape" — the caller then
+ * Returning `null` means "no honest summary for this shape", the caller then
  * falls back to the previous raw-first-line preview, so an unrecognised tool or
  * an unexpected payload is never mis-summarised.
  */
@@ -95,7 +95,7 @@ function summarizeEdit(obj: Record<string, unknown>): string | null {
 
 // The credential scrub's withheld_env report stays OUT of the collapsed line
 // entirely. It withholds the same standing set of names on every spawn, so any
-// per-result rendering repeats identical env-var noise all session long — the
+// per-result rendering repeats identical env-var noise all session long, the
 // dominant transcript spam for anyone with several keys exported. The report
 // only matters when a command fails because a needed credential was scrubbed,
 // and for that case the full name list is one expand away in the raw payload.
@@ -104,7 +104,7 @@ function summarizeEdit(obj: Record<string, unknown>): string | null {
  * Compact per-command exec-sandbox suffix: `sandboxed` fields are present
  * only when the sandbox was active for the run (SDK's attachSandboxMeta stays
  * quiet otherwise), so absence here means "ran unsandboxed" and the suffix is
- * empty — never a fabricated claim either way.
+ * empty, never a fabricated claim either way.
  *
  *   sandboxed, network disabled            -> " · sandboxed (net off)"
  *   sandboxed, network enabled, escalation -> " · sandboxed (net on, +1 escalation)"
@@ -151,7 +151,7 @@ function summarizeExec(obj: Record<string, unknown>): string | null {
     const failed = obj.commands.filter(
       (c) => c && typeof c === 'object' && (c as Record<string, unknown>).success === false,
     ).length;
-    // Count sandboxed commands across the batch — a compact "N sandboxed" beats
+    // Count sandboxed commands across the batch, a compact "N sandboxed" beats
     // repeating each command's full boundary detail on the collapsed line.
     const sandboxedCount = obj.commands.filter(
       (c) => c && typeof c === 'object' && (c as Record<string, unknown>).sandboxed === true,

package/src/renderer/turn-injection.ts

@@ -15,7 +15,7 @@
  * Reality check (since updated): the TUI's main interactive
  * session DOES route through this engine. The SDK `Orchestrator` runs per-turn
  * passive injection on the evolving primary conversation and records each turn
- * on its own bounded ring, exposed via `Orchestrator.getTurnInjections()` — the
+ * on its own bounded ring, exposed via `Orchestrator.getTurnInjections()`, the
  * main-session counterpart to `AgentRecord.turnInjections` (there is no
  * AgentRecord for the primary conversation). `buildMainSessionTurnInjectionsText`
  * renders that ring for `/recall injections` with no agent id. Spawned agents
@@ -55,18 +55,18 @@ function codeSkipNote(entry: TurnInjectionEntry): string {
 export function formatTurnInjectionEntry(entry: TurnInjectionEntry): string {
   const backendTag = entry.embeddingBackend === 'fallback-lexical' ? ' [lexical fallback]' : '';
   if (entry.injectedIds.length === 0) {
-    // Honest empty state: the engine ran this turn but injected nothing —
+    // Honest empty state: the engine ran this turn but injected nothing,
     // distinct from "the engine never ran" (see buildTurnInjectionsText).
     const reasonText = entry.reason === 'no records cleared relevance floor'
-      ? 'nothing injected this turn — nothing cleared the relevance floor'
-      : `nothing injected this turn — ${entry.reason ?? 'unknown reason'}`;
+      ? 'nothing injected this turn: nothing cleared the relevance floor'
+      : `nothing injected this turn: ${entry.reason ?? 'unknown reason'}`;
     const codeConsidered = entry.codeCandidatesConsidered ? `, code considered ${entry.codeCandidatesConsidered}` : '';
     return `  turn ${entry.turn}: ${reasonText}${backendTag} (considered ${entry.candidatesConsidered}${codeConsidered}, floor ${entry.relevanceFloor})${codeSkipNote(entry)}`;
   }
   const droppedStr = entry.droppedForBudget.length > 0
     ? `, dropped for budget: ${entry.droppedForBudget.join(', ')}`
     : '';
-  // The retrieval query is part of the record's honesty contract — without it
+  // The retrieval query is part of the record's honesty contract, without it
   // an injected line can't be traced back to WHY those ids were retrieved
   // (a replay finding flagged the omission). Truncated to keep the line scannable.
   const queryStr = entry.query ? ` for ${JSON.stringify(truncateQuery(entry.query))}` : '';
@@ -87,7 +87,7 @@ function truncateQuery(query: string): string {
  *
  * An empty `entries` array is deliberately ambiguous about WHY it's empty
  * (flag disabled, no turn with new input has run yet, or every turn's token
- * budget had no headroom) — the SDK does not distinguish these cases in the
+ * budget had no headroom), the SDK does not distinguish these cases in the
  * ring itself, so this renders all three possibilities rather than guessing.
  */
 export function buildTurnInjectionsText(agentId: string, entries: readonly TurnInjectionEntry[]): string {
@@ -95,7 +95,7 @@ export function buildTurnInjectionsText(agentId: string, entries: readonly TurnI
     return (
       `[recall] No per-turn injection records for agent ${agentId} yet. This means one of: ` +
       'passive knowledge injection is disabled, no turn with new input has run yet, or the ' +
-      'token budget had no headroom on every turn so far — there is no record either way.'
+      'token budget had no headroom on every turn so far; there is no record either way.'
     );
   }
   const lines = [`[recall] Per-turn knowledge injections for agent ${agentId} (${entries.length}, most recent first):`];
@@ -114,7 +114,7 @@ export function buildTurnInjectionsText(agentId: string, entries: readonly TurnI
  *
  * As with the agent path, an empty `entries` array is deliberately ambiguous
  * about WHY it's empty (flag disabled, no turn with new input has run yet, or
- * every turn's token budget had no headroom) — the ring does not distinguish
+ * every turn's token budget had no headroom), the ring does not distinguish
  * these, so this renders all three possibilities rather than guessing.
  */
 export function buildMainSessionTurnInjectionsText(entries: readonly TurnInjectionEntry[]): string {
@@ -122,7 +122,7 @@ export function buildMainSessionTurnInjectionsText(entries: readonly TurnInjecti
     return (
       '[recall] No per-turn injection records for the main session yet. This means one of: ' +
       'passive knowledge injection is disabled, no turn with new input has run yet, or the ' +
-      'token budget had no headroom on every turn so far — there is no record either way.'
+      'token budget had no headroom on every turn so far; there is no record either way.'
     );
   }
   const lines = [`[recall] Per-turn knowledge injections for the main session (${entries.length}, most recent first):`];