@pellux/goodvibes-tui 2.0.14 → 2.0.16

package/src/input/commands/profile-runtime.ts

@@ -1,7 +1,7 @@
 /**
  * profile-runtime.ts
  *
- * `/profile` — the owner profile in the TUI: what the platform knows about the
+ * `/profile`, the owner profile in the TUI: what the platform knows about the
  * person who owns it, kept as one hand-editable Markdown file at daemon scope
  * (docs/owner-profile.md).
  *
@@ -14,13 +14,13 @@
  *
  * plus `set`, `note`, `undo` and `status` so a correction, a note, a recovery
  * and a diagnosis do not require leaving the terminal or hand-editing the file
- * (which remains allowed, and authoritative — §4.5).
+ * (which remains allowed, and authoritative, §4.5).
  *
  * ## Why it goes over the operator wire
  *
  * Same reason `/principals`, `/ci` and `/checkin` do (see operator-rpc.ts): the
  * `profile.*` family ships in the operator contract and has not been promoted to
- * the in-process `OperatorClient` facade. Surfaces never open the profile file —
+ * the in-process `OperatorClient` facade. Surfaces never open the profile file,
  * the daemon is the single writer, which is what makes its rename-based atomic
  * writes sufficient with no lock (§3, §5.4). This command therefore has no file
  * path, no parser and no writer of its own, and could not corrupt the document
@@ -30,7 +30,7 @@
  *
  * Values reach exactly one place: the string handed to `ctx.print`. This module
  * imports no logger, builds no diagnostic payload, and never puts a value in an
- * error message — a failed call renders `describeOperatorRpcError`, which
+ * error message, a failed call renders `describeOperatorRpcError`, which
  * describes the transport, not the content. A write prints the daemon's
  * one-line disclosure and the field names that changed, never the value that was
  * just recorded (§8.2). The `People` section is third-party personal data and is
@@ -80,7 +80,7 @@ const USAGE = [
   '  in the file (e.g. "shipping address") once that field is recorded. /profile show',
   '  prints each field id beside its value.',
   '',
-  '  Notes in People, Places, Work and Notes have no field id — forget those with',
+  '  Notes in People, Places, Work and Notes have no field id; forget those with',
   '  --section and the line as /profile show prints it. The leading "-" is optional;',
   '  the rest must match, and if two notes read the same nothing is removed.',
 ].join('\n');
@@ -118,7 +118,7 @@ export interface ProfileCommandDeps {
 const DEFAULT_DEPS: ProfileCommandDeps = { resolveRpc: getOperatorRpc };
 
 function unrecognizedResponse(verb: string): string {
-  return `${PROFILE_TAG} the daemon answered ${verb} with a response this build does not recognise — it is probably running a different platform version. Nothing was read or written.`;
+  return `${PROFILE_TAG} the daemon answered ${verb} with a response this build does not recognise; it is probably running a different platform version. Nothing was read or written.`;
 }
 
 /**
@@ -126,7 +126,7 @@ function unrecognizedResponse(verb: string): string {
  *
  * A dotted token is already an id and is passed through untouched. A bare label
  * ("shipping address") is matched against the labels in the live `profile.read`
- * response — deliberately NOT against a copy of the SDK's field registry, which
+ * response, deliberately NOT against a copy of the SDK's field registry, which
  * would be a second list to keep in step with the first. A label that matches
  * nothing is passed through unchanged so the daemon answers with its own message
  * naming what is wrong, rather than this command guessing.
@@ -205,7 +205,7 @@ async function runWrite<TVerb extends ProfileWriteVerb, TBody extends ProfileInp
 /**
  * `--section <name>` followed by free text, shared by `/profile note` and
  * `/profile forget`. Section defaults to Notes, which is only meaningful for
- * `note` — `forget` calls this solely when `--section` was given.
+ * `note`, `forget` calls this solely when `--section` was given.
  */
 function parseSectionArgs(args: readonly string[]): { section: string; text: string } {
   if (args[1] === '--section' && typeof args[2] === 'string' && args[2].length > 0) {
@@ -235,12 +235,12 @@ export function registerProfileRuntimeCommands(
       //
       // where/forget/undo take the whole remainder as the field, so a label
       // written with a space ("shipping address") works unquoted. `set` cannot
-      // do that — everything after the first token is the value — so a label
+      // do that, everything after the first token is the value, so a label
       // there must be one word, or the field id.
       const fieldToken = sub === 'set' ? args[1] : args.slice(1).join(' ').trim();
 
       // `/profile forget --section <name> <text>` removes a prose bullet, which
-      // is the only way to forget a line in People, Places, Work or Notes —
+      // is the only way to forget a line in People, Places, Work or Notes,
       // those sections have no mechanical fields at all (§4.3), so without this
       // "forget that" would answer for a shipping address but not for a note
       // about a person. The line is named by its exact text, never by position:
@@ -272,7 +272,7 @@ export function registerProfileRuntimeCommands(
         return;
       }
       // `methodId as string` is what picks the generic overload, so the result
-      // stays `unknown` and has to go through a checker — see ProfileInvoke.
+      // stays `unknown` and has to go through a checker, see ProfileInvoke.
       const invoke: ProfileInvoke = (methodId, input) =>
         rpc.sdk.operator.invoke(methodId as string, input as unknown as Record<string, unknown>);
       const print = (text: string): void => { ctx.print(text); };
@@ -309,8 +309,8 @@ export function registerProfileRuntimeCommands(
         // outright. An earlier build defaulted it to owner-direct instead, and
         // stating the claim rather than leaning on that default is precisely
         // why this command kept working when it was tightened. It is the only
-        // gate `forget` and `undo` have — layers 2 and 3 do not apply to a
-        // removal — so it is not a field to leave to anyone else's default.
+        // gate `forget` and `undo` have, layers 2 and 3 do not apply to a
+        // removal, so it is not a field to leave to anyone else's default.
         //
         // This surface can hardcode it; the agent must not. The TUI's only
         // input is the owner at his own keyboard, whereas the agent can be

package/src/input/commands/profile-types.ts

@@ -6,7 +6,7 @@
  *
  * ## The shapes come from the contract, not from a copy of it
  *
- * Every type below is derived from `OperatorMethodOutput<'profile.…'>` — the
+ * Every type below is derived from `OperatorMethodOutput<'profile.…'>`, the
  * types generated from the SDK's own output schemas
  * (`platform/control-plane/method-catalog-owner-profile.ts`). Nothing here
  * restates a field name, so this file cannot drift from the contract: if a
@@ -20,11 +20,11 @@
  * matching exported Zod schema and `buildSchemaRegistry` silently skips the
  * rest. Measured against the installed contracts package: 5 of 452 method ids
  * have one, and no `profile.*` verb is among them. So response validation is
- * not a safety net this command can lean on — for these verbs or for most
+ * not a safety net this command can lean on, for these verbs or for most
  * others.
  *
- * So a daemon on a different version — or a 200 from something that is not this
- * daemon at all — would otherwise reach a renderer and throw on a missing array,
+ * So a daemon on a different version, or a 200 from something that is not this
+ * daemon at all, would otherwise reach a renderer and throw on a missing array,
  * which in a slash command means a stack trace instead of an answer. Each `toX`
  * function does the cast to `Record<string, unknown>` in ONE place, checks every
  * property a renderer will read, and returns {@link MALFORMED} when anything is
@@ -66,16 +66,16 @@ type UnionKeys<T> = T extends unknown ? keyof T : never;
  * carries alone. Four ways a stale key can arrive, all compiled against this
  * repo's TypeScript with a `profile.forget`-shaped input:
  *
- *   1. written inline in a fresh literal      — parameter typing already rejects
- *   2. written inline BESIDE a spread         — parameter typing already rejects
- *   3. body built as a variable first         — SLIPS PAST parameter typing
- *   4. carried in by the spread source's type — SLIPS PAST parameter typing
+ *   1. written inline in a fresh literal     , parameter typing already rejects
+ *   2. written inline BESIDE a spread        , parameter typing already rejects
+ *   3. body built as a variable first        , SLIPS PAST parameter typing
+ *   4. carried in by the spread source's type, SLIPS PAST parameter typing
  *
  * A spread literal is not uniformly unchecked, which is the easy thing to get
  * wrong: anything written inline in one is still checked normally, and only what
  * arrives THROUGH the spread escapes, because it belongs to the source's type
  * rather than to the literal. Rows 3 and 4 are the two nothing else catches, and
- * this guard rejects both with TS2345 — measured, not reasoned about.
+ * this guard rejects both with TS2345, measured, not reasoned about.
  *
  * That is not hypothetical: `profile.forget` really did retire `lineIndex`, and
  * a body built one line earlier would have carried it silently past a correctly
@@ -83,7 +83,7 @@ type UnionKeys<T> = T extends unknown ? keyof T : never;
  * to seed; this closes the shape.
  *
  * There is a second reason it earns its place here. The SDK's `invoke` is
- * OVERLOADED — a typed signature plus a loose
+ * OVERLOADED, a typed signature plus a loose
  * `invoke<T = unknown>(methodId: string, input?: Record<string, unknown>)`. At a
  * bare call site a body the typed overload rejects does not raise an
  * excess-property error at all; overload resolution simply falls through to the
@@ -107,7 +107,7 @@ export type ExactProfileInput<TVerb extends ProfileVerb, TBody> =
 export type ProfileDocumentView = OperatorMethodOutput<'profile.read'>;
 
 /**
- * Load state — what `profile.status` answers, and the `state` half of a read.
+ * Load state, what `profile.status` answers, and the `state` half of a read.
  *
  * `kind` is `loaded` | `unavailable` | `disabled`. The counts belong to
  * `loaded` and `reason` to `unavailable`. There is no value property anywhere
@@ -124,7 +124,7 @@ export type ProfileWriteResultView = OperatorMethodOutput<'profile.set'>;
 
 /** One `## ` section, with the tier its content belongs to. */
 export type ProfileSectionView = ProfileDocumentView['sections'][number];
-/** One mechanical field. `valid: false` still carries the value — see §4.3. */
+/** One mechanical field. `valid: false` still carries the value, see §4.3. */
 export type ProfileFieldView = ProfileSectionView['fields'][number];
 /** One prose line, preserved as written. */
 export type ProfileLineView = ProfileSectionView['prose'][number];
@@ -355,7 +355,7 @@ export function toProfileProvenanceReport(value: unknown): Checked<ProfileProven
   const superseded = checkedArray(record.superseded, toSuperseded);
   if (superseded === MALFORMED) return MALFORMED;
   // Platform runtime 2.0.8: the contract declares provenance nullable and
-  // always present — null IS the answer for a hand-edited field.
+  // always present, null IS the answer for a hand-edited field.
   return { fieldId, present, handEdited, provenance: provenance ?? null, superseded };
 }
 

package/src/input/commands/provider-accounts-runtime.ts

@@ -25,7 +25,7 @@ function findProviderAccountRecord(
 /**
  * Present a record's recommended actions as executable rows. A recommended
  * action that carries a structured command becomes a press-Enter row that RUNS
- * that command through the command registry — never a line the user has to
+ * that command through the command registry, never a line the user has to
  * retype. Actions with no command are genuinely out-of-product steps, so they
  * stay as plain (non-executing) rows. When there is no interactive selection
  * surface, each action is printed honestly instead.
@@ -68,7 +68,7 @@ export function presentRecommendedActions(
         if (action.command) {
           const args = [...action.command.args];
           void (ctx.executeCommand?.(action.command.name, args)
-            ?? Promise.resolve(ctx.print(`Cannot run /${action.command.name} — command execution is unavailable here.`)));
+            ?? Promise.resolve(ctx.print(`Cannot run /${action.command.name}: command execution is unavailable here.`)));
           return;
         }
         ctx.print(action.description);
@@ -81,7 +81,7 @@ export function presentRecommendedActions(
     'Recommended actions:',
     ...actions.map((action) => (
       action.command
-        ? `  • ${action.description} — /${action.command.name}${action.command.args.length > 0 ? ` ${action.command.args.join(' ')}` : ''}`
+        ? `  • ${action.description}: /${action.command.name}${action.command.args.length > 0 ? ` ${action.command.args.join(' ')}` : ''}`
         : `  • ${action.description} (manual step)`
     )),
   ].join('\n'));
@@ -155,9 +155,9 @@ export function registerProviderAccountsRuntimeCommands(registry: CommandRegistr
           ...(record.fallbackRoute ? [`  fallbackRoute: ${record.fallbackRoute}`] : []),
           ...(record.fallbackRisk ? [`  fallbackRisk: ${record.fallbackRisk}`] : []),
           ...(record.expiresAt ? [`  expiresAt: ${new Date(record.expiresAt).toISOString()}`] : []),
-          ...record.routeRecords.map((route) => `  route ${route.route}: usable=${route.usable ? 'yes' : 'no'} freshness=${route.freshness} — ${route.detail}`),
+          ...record.routeRecords.map((route) => `  route ${route.route}: usable=${route.usable ? 'yes' : 'no'} freshness=${route.freshness}; ${route.detail}`),
           ...record.routeRecords.flatMap((route) => route.issues.map((issue) => `    issue: ${issue}`)),
-          ...record.usageWindows.map((entry) => `  window: ${entry.label} — ${entry.detail}`),
+          ...record.usageWindows.map((entry) => `  window: ${entry.label}; ${entry.detail}`),
           ...record.issues.map((issue) => `  issue: ${issue}`),
           ...record.notes.map((note) => `  note: ${note}`),
         ].join('\n'));

package/src/input/commands/provider.ts

@@ -3,11 +3,11 @@
  *
  * Implements the Provider Optimizer panel commands:
  *
- *   /provider optimizer on|off   — Enable or disable the provider optimizer
- *   /provider route auto|manual  — Set optimizer routing mode
- *   /provider explain-route      — Print current route explanation
- *   /provider pin <provider:model> — Pin routing to a specific provider/model
- *   /provider fallback test      — Simulate the fallback chain
+ *   /provider optimizer on|off  , Enable or disable the provider optimizer
+ *   /provider route auto|manual , Set optimizer routing mode
+ *   /provider explain-route     , Print current route explanation
+ *   /provider pin <provider:model>, Pin routing to a specific provider/model
+ *   /provider fallback test     , Simulate the fallback chain
  *
  * When the optimizer is disabled, commands report its status and
  * explain-route still works (reads current model capabilities).
@@ -112,7 +112,7 @@ function handleOptimizerToggle(
     context.print('  Provider selection returns to manual-only mode. No automatic failover.');
     context.print('  Pinned targets and fallback log are preserved; re-enable to resume.');
   } else {
-    context.print(`[provider] Optimizer already ${enable ? 'enabled' : 'disabled'} — no change.`);
+    context.print(`[provider] Optimizer already ${enable ? 'enabled' : 'disabled'}; no change.`);
   }
 }
 
@@ -136,7 +136,7 @@ function handleRoute(
 
   if (!optimizer.enabled) {
     context.print(
-      '[provider] Optimizer is off — routing mode recorded but failover will not fire until optimizer is enabled.',
+      '[provider] Optimizer is off: routing mode recorded but failover will not fire until optimizer is enabled.',
     );
     context.print('  Enable with: /provider optimizer on');
   }
@@ -273,7 +273,7 @@ async function handlePin(
   // Enable optimizer if it's off
   if (!optimizer.enabled) {
     optimizer.setEnabled(true);
-    context.print('⚠ Optimizer was disabled — enabling it for pin to take effect.');
+    context.print('⚠ Optimizer was disabled: enabling it for pin to take effect.');
   }
 
   optimizer.pin(match.providerId, match.modelId);
@@ -299,7 +299,7 @@ function handleFallbackTest(
     return;
   }
 
-  context.print('[provider] Simulating fallback chain (empty request profile — no requirements)...');
+  context.print('[provider] Simulating fallback chain (empty request profile; no requirements)...');
 
   const result: FallbackTestResult = optimizer.testFallback();
 
@@ -360,7 +360,7 @@ function handleFallbackTest(
 // ---------------------------------------------------------------------------
 
 /**
- * providerCommand — The `/provider` slash command.
+ * providerCommand, The `/provider` slash command.
  *
  * Routes to subcommand handlers based on args[0].
  */

package/src/input/commands/qrcode-runtime.ts

@@ -7,7 +7,7 @@ import { openModalCommand } from './runtime-services.ts';
  * `/qrcode` (no args, aliases /qr /pair) opens the device-pairing modal: a QR of
  * the `#pair=<token>` deep link plus the offer set. Each open mints its own
  * named per-device token, so `/qrcode regenerate` no longer rotates a shared
- * token — it simply re-opens the modal, which mints a fresh token and QR. The
+ * token, it simply re-opens the modal, which mints a fresh token and QR. The
  * previously-shown token stays valid until you revoke it in
  * /settings → security → devices.
  */
@@ -22,9 +22,9 @@ export function registerQrcodeRuntimeCommands(registry: CommandRegistry): void {
       if (args[0]?.toLowerCase() === 'regenerate') {
         // Each pairing-modal open mints its own token, so "regenerate" is just a
         // fresh open: the re-pull mints a new named token + QR in place. The
-        // prior token is not rotated out from under a live device — revoke it
+        // prior token is not rotated out from under a live device, revoke it
         // explicitly in /settings → security → devices when you no longer need it.
-        ctx.print('Opening a fresh pairing QR — it mints a new device token. Revoke old ones in /settings → security → devices.');
+        ctx.print('Opening a fresh pairing QR; it mints a new device token. Revoke old ones in /settings → security → devices.');
         openModalCommand(ctx, 'pairing-modal');
         return;
       }

package/src/input/commands/queue-runtime.ts

@@ -1,12 +1,12 @@
 import type { CommandRegistry } from '../command-registry.ts';
 
 // ---------------------------------------------------------------------------
-// /queue — the mid-turn message queue as an editable list.
+// /queue, the mid-turn message queue as an editable list.
 //
 // Messages typed while a turn is streaming are QUEUED (they deliver after the
 // turn). Until a message is delivered it stays editable and deletable via the
 // SDK's editQueuedMessage / deleteQueuedMessage verbs; a delivered message has
-// left the queue and is no longer listed — delivery is immutability. This
+// left the queue and is no longer listed, delivery is immutability. This
 // command is the editable interface over the same list the composer renders.
 // ---------------------------------------------------------------------------
 
@@ -14,7 +14,7 @@ export function registerQueueRuntimeCommands(registry: CommandRegistry): void {
   registry.register({
     name: 'queue',
     aliases: ['q'],
-    description: 'Mid-turn message queue — list, edit, or delete still-undelivered messages',
+    description: 'Mid-turn message queue: list, edit, or delete still-undelivered messages',
     usage: '[list | edit <n> <text> | delete <n>]',
     argsHint: '[list|edit <n> <text>|delete <n>]',
     handler(args, ctx) {
@@ -26,7 +26,7 @@ export function registerQueueRuntimeCommands(registry: CommandRegistry): void {
           ctx.print('No queued messages. (Messages typed while a turn is streaming queue here until it finishes.)');
           return;
         }
-        const lines = [`Queued messages (${list.length}) — editable until delivered:`];
+        const lines = [`Queued messages (${list.length}): editable until delivered:`];
         list.forEach((m, i) => lines.push(`  ${i + 1}. ${m.text}`));
         lines.push('Use /queue edit <n> <new text> or /queue delete <n>.');
         ctx.print(lines.join('\n'));
@@ -47,7 +47,7 @@ export function registerQueueRuntimeCommands(registry: CommandRegistry): void {
         const ok = ctx.deleteQueuedMessage?.(target.id) ?? false;
         ctx.print(ok
           ? `Deleted queued message #${n}.`
-          : `Could not delete message #${n} — it was already delivered (delivered messages are immutable).`);
+          : `Could not delete message #${n}; it was already delivered (delivered messages are immutable).`);
         return;
       }
 
@@ -60,7 +60,7 @@ export function registerQueueRuntimeCommands(registry: CommandRegistry): void {
         const ok = ctx.editQueuedMessage?.(target.id, text) ?? false;
         ctx.print(ok
           ? `Edited queued message #${n}.`
-          : `Could not edit message #${n} — it was already delivered (delivered messages are immutable).`);
+          : `Could not edit message #${n}; it was already delivered (delivered messages are immutable).`);
         return;
       }
 

package/src/input/commands/recall-files-config.ts

@@ -1,8 +1,8 @@
 /**
- * recall-files-config.ts — TUI-local synthetic setting for the memory file
+ * recall-files-config.ts, TUI-local synthetic setting for the memory file
  * projection directory (`memory.projection.dir`).
  *
- * `memory.projection.dir` is not in the SDK's ConfigKey union — same
+ * `memory.projection.dir` is not in the SDK's ConfigKey union, same
  * situation as worktree.setup.commands (see worktree-setup-config.ts, which
  * this file mirrors): a brand-new top-level config section with no
  * DEFAULT_CONFIG entry, so ConfigManager.get()/set() path resolution can
@@ -10,7 +10,7 @@
  * degrades a resolution failure into an honest "Save failed" message.
  *
  * Default: `.goodvibes/memory/projection`, relative to the project working
- * directory — under the project's own `.goodvibes/` control directory,
+ * directory, under the project's own `.goodvibes/` control directory,
  * alongside the (separate) KV-state memory directory used by the state tool.
  */
 import type { ConfigKey, ConfigManager, ConfigSetting } from '@pellux/goodvibes-sdk/platform/config';
@@ -24,7 +24,7 @@ export const MEMORY_PROJECTION_DIR_SYNTHETIC_SETTING: ConfigSetting = {
   key: MEMORY_PROJECTION_DIR_CONFIG_KEY,
   type: 'string',
   default: MEMORY_PROJECTION_DIR_DEFAULT,
-  description: '/recall files sync writes one markdown file per standing (project/team-scope) memory record here, and commits the directory when it sits inside a git repository. Relative paths resolve against the project working directory. /recall files review reads user edits back from this directory as proposals — a file edit or deletion never mutates the store directly.',
+  description: '/recall files sync writes one markdown file per standing (project/team-scope) memory record here, and commits the directory when it sits inside a git repository. Relative paths resolve against the project working directory. /recall files review reads user edits back from this directory as proposals; a file edit or deletion never mutates the store directly.',
 };
 
 /** Read the configured projection directory, falling back to the default for an absent/malformed value. */

package/src/input/commands/recall-files-git.ts

@@ -1,10 +1,10 @@
 /**
- * recall-files-git.ts — the git seam for memory file projection.
+ * recall-files-git.ts, the git seam for memory file projection.
  *
  * The SDK owns the production seam now (`createMemoryProjectionGit`,
  * platform/state): it shells out to the system git, commits with a neutral
  * projection identity (never the operator's), tolerates an unchanged tree,
- * and — through `projectMemoryToFiles`'s ownership gate — only ever commits
+ * and, through `projectMemoryToFiles`'s ownership gate, only ever commits
  * to a repository whose toplevel IS the projection directory, initializing
  * one there when needed. A projection directory nested inside some other
  * checkout can never pollute that checkout. This module is a thin local
@@ -13,7 +13,7 @@
 import { createMemoryProjectionGit } from '@pellux/goodvibes-sdk/platform/state';
 import type { MemoryProjectionGit } from '@pellux/goodvibes-sdk/platform/state';
 
-/** The projection git seam (see module note — SDK-owned behavior). */
+/** The projection git seam (see module note, SDK-owned behavior). */
 export function createSyncGitSeam(): MemoryProjectionGit {
   return createMemoryProjectionGit();
 }

package/src/input/commands/recall-files.ts

@@ -1,14 +1,14 @@
 /**
- * recall-files.ts — `/recall files sync|review|apply`, the git-backed markdown
+ * recall-files.ts, `/recall files sync|review|apply`, the git-backed markdown
  * projection surface for standing (project/team-scope) memory records.
  *
  * Round-trip:
- *   sync   — project store records to `<dir>/<id>.md`, git-commit the directory
+ *   sync  , project store records to `<dir>/<id>.md`, git-commit the directory
  *            when it sits inside a repo. Read-only against the store.
- *   review — diff the on-disk projection against the current store and print
+ *   review, diff the on-disk projection against the current store and print
  *            the resulting proposals (a file edit -> 'update', a deleted file
- *            for an in-scope record -> 'delete'). PURE — no store writes.
- *   apply  — re-diff fresh, then mutate the store ONLY for the proposal ids
+ *            for an in-scope record -> 'delete'). PURE, no store writes.
+ *   apply , re-diff fresh, then mutate the store ONLY for the proposal ids
  *            the caller explicitly names (or --all), through the memory spine
  *            client's own update/delete. Never a silent write.
  *
@@ -17,14 +17,14 @@
  * snapshot from an earlier `review` call.
  *
  * Routes through `getMemorySpine` (not the host-only `knowledgeApi.memory`)
- * per the SDK's memory-wire-full-detach decision — same as every other
+ * per the SDK's memory-wire-full-detach decision, same as every other
  * mutating `/recall` subcommand, so this fully detaches from the local store
  * file when a daemon has been adopted.
  *
  * The memory spine's wire `MemoryUpdatePatch` (SDK platform/runtime/memory-spine)
- * now carries validFrom/validUntil alongside scope/summary/detail/tags — a
+ * now carries validFrom/validUntil alongside scope/summary/detail/tags, a
  * number sets the bound, `null` clears it, and an omitted field leaves it
- * unchanged — so a proposal whose `desired` changes ONLY the temporal window
+ * unchanged, so a proposal whose `desired` changes ONLY the temporal window
  * applies for real over the wire, the same as any other field change.
  */
 import { existsSync } from 'node:fs';
@@ -61,7 +61,7 @@ export async function handleRecallFilesSync(args: string[], context: CommandCont
 
   try {
     // The SDK's ownership gate commits only to a repository whose toplevel IS
-    // the projection directory (initializing one there when needed) — never
+    // the projection directory (initializing one there when needed), never
     // to a checkout the directory merely sits inside.
     const report = projectMemoryToFiles(records, dir, { git: createSyncGitSeam() });
     context.print(`[recall] Projected ${report.written.length} record(s) to ${report.dir}`);
@@ -102,7 +102,7 @@ export async function handleRecallFilesReview(args: string[], context: CommandCo
   if (proposals === null) return;
 
   if (proposals.length === 0) {
-    context.print(`[recall] No changes — ${dir} matches the store.`);
+    context.print(`[recall] No changes: ${dir} matches the store.`);
     return;
   }
   context.print(`[recall] ${proposals.length} proposal(s) from ${dir}:`);
@@ -116,7 +116,7 @@ export async function handleRecallFilesApply(args: string[], context: CommandCon
 
   const applyAll = args.includes('--all') || args.includes('all');
   const ids = new Set(args.filter((a) => a !== '--all' && a !== 'all' && a !== '--dir' && !a.startsWith('.') && !a.startsWith('/')));
-  // --dir's value (the token right after it) is not a proposal id — drop it.
+  // --dir's value (the token right after it) is not a proposal id, drop it.
   const dirIdx = args.indexOf('--dir');
   if (dirIdx !== -1 && args[dirIdx + 1]) ids.delete(args[dirIdx + 1]!);
 
@@ -178,5 +178,5 @@ export async function handleRecallFilesApply(args: string[], context: CommandCon
 
   context.print(`[recall] Applied ${applied.length}, skipped ${skipped.length}, failed ${failed.length}.`);
   for (const proposal of applied) context.print(`  applied  ${proposal.id} [${proposal.kind}]`);
-  for (const { proposal, reason } of failed) context.print(`  failed   ${proposal.id} [${proposal.kind}] — ${reason}`);
+  for (const { proposal, reason } of failed) context.print(`  failed   ${proposal.id} [${proposal.kind}]: ${reason}`);
 }

package/src/input/commands/recall-query.ts

@@ -5,7 +5,7 @@ import type { MemorySearchFilter } from '@pellux/goodvibes-sdk/platform/state';
 import { VALID_CLASSES, VALID_SCOPES, isValidClass, isValidScope, temporalStatusLabel } from './recall-shared.ts';
 
 /**
- * The local, host-only `MemoryApi` — kept for `/recall explain` and `/recall
+ * The local, host-only `MemoryApi`, kept for `/recall explain` and `/recall
  * vector` only. Both are ruled explicitly out of the wire catalog in
  * docs/decisions/2026-07-06-memory-wire-full-detach.md (SDK repo): `explain`
  * is a client-side projection over whatever read surface is active, not a
@@ -24,7 +24,7 @@ export function getMemoryApi(context: CommandContext): MemoryApi | null {
 }
 
 /**
- * The cross-surface memory spine client — routes local when offline/embedded,
+ * The cross-surface memory spine client, routes local when offline/embedded,
  * over the wire when a daemon has been adopted, never both. `/recall`'s
  * browse/link/queue/export/import subcommands use this so they never read a
  * divergent local copy while a daemon owns the canonical store.
@@ -196,7 +196,7 @@ export async function handleRecallLink(args: string[], context: CommandContext):
   }
   const link = await memory.link(fromId, toId, relation);
   if (!link) {
-    context.print('[recall] Link failed — check that both IDs exist.');
+    context.print('[recall] Link failed: check that both IDs exist.');
     return;
   }
   context.print(`[recall] Linked: ${fromId} -> ${toId} [${relation}]`);

package/src/input/commands/recall-review.ts

@@ -40,7 +40,7 @@ export async function handleRecallQueue(args: string[], context: CommandContext)
   }
   context.print(`[recall] Review queue (${queue.length}):`);
   for (const record of queue) {
-    const reason = record.staleReason ? ` — ${record.staleReason}` : '';
+    const reason = record.staleReason ? `: ${record.staleReason}` : '';
     context.print(`  ${record.id} [${record.scope}/${record.cls}] ${record.reviewState} ${record.confidence}%  ${record.summary}${reason}${temporalStatusLabel(record)}`);
   }
 }
@@ -107,13 +107,13 @@ export function handleRecallExplain(args: string[], context: CommandContext): vo
  * Per-turn passive knowledge injection inspectability.
  *
  * With an explicit agent id, reads `AgentRecord.turnInjections`
- * via `context.ops.agentManager.exportState()` — the CommandContext-exposed
+ * via `context.ops.agentManager.exportState()`, the CommandContext-exposed
  * `ShellAgentManagerService` doesn't have a `getStatus`/`list` pair, but
  * `exportState()` returns the same full `AgentRecord[]` (it's what
  * compactConversation() already uses for the same reason).
  *
  * With NO agent id (wiring), renders the MAIN interactive session's own
- * per-turn injection ring — `Orchestrator.getTurnInjections()`, threaded onto
+ * per-turn injection ring, `Orchestrator.getTurnInjections()`, threaded onto
  * the command context as `session.getMainSessionTurnInjections`. As of the
  * main session DOES route through the passive-injection engine, so this is the
  * honest main-session default (previously there was no record source, so the

package/src/input/commands/recall-shared.ts

@@ -23,7 +23,7 @@ export function resolveBundlePath(pathArg: string, shellPaths: ShellPathService)
 }
 
 /**
- * Compact inline label for a record's temporal validity window — appended
+ * Compact inline label for a record's temporal validity window, appended
  * wherever `/recall` lists records, so an out-of-window record is visibly
  * `[pending]`/`[expired]` rather than silently indistinguishable from an
  * always-valid one. Empty string for 'active' (the common case; no window,

package/src/input/commands/relay-runtime.ts

@@ -4,7 +4,7 @@ import { generateQrMatrix, renderQrToString } from '@pellux/goodvibes-sdk/platfo
 import { RELAY_STATE_NOT_READABLE_HERE } from '../../runtime/relay-reachability-bridge.ts';
 
 /**
- * Register the /relay command — the relay's configuration, its reachability
+ * Register the /relay command, the relay's configuration, its reachability
  * state, and a QR-encodable pairing payload for the SDK's outbound
  * zero-knowledge relay (relay.* settings, gated by the `relay-connect` feature
  * flag).
@@ -12,7 +12,7 @@ import { RELAY_STATE_NOT_READABLE_HERE } from '../../runtime/relay-reachability-
  * The CONFIGURATION half is read here, from this terminal's own config. The
  * LIVE half is not: registration state and pairing live in the running daemon's
  * memory (`DaemonServer.getRelayReachability()`), and no verb exposes either to
- * a client — so both read 'unavailable' with the reason said out loud rather
+ * a client, so both read 'unavailable' with the reason said out loud rather
  * than a state this terminal is in no position to know. See
  * relay-reachability-bridge.ts.
  */
@@ -43,20 +43,20 @@ async function renderStatus(ctx: CommandContext): Promise<void> {
   const state = live === 'registered' || live === 'disabled' || live === 'unavailable' ? live : 'offline';
   ctx.print([
     `Relay: ${state}`,
-    `  rendezvous id: ${cfg.rendezvousId || '(not yet minted — start the daemon to generate one)'}`,
+    `  rendezvous id: ${cfg.rendezvousId || '(not yet minted; start the daemon to generate one)'}`,
     `  url: ${cfg.url || '(not set)'}`,
     `  label: ${cfg.label || '(not set)'}`,
     state === 'unavailable'
       ? `  ${RELAY_STATE_NOT_READABLE_HERE}`
       : `  live connection state: ${live}`,
-    '  The relay operator sees only ciphertext and connection metadata — self-host your own relay for full control.',
+    '  The relay operator sees only ciphertext and connection metadata; self-host your own relay for full control.',
   ].join('\n'));
 }
 
 async function renderPair(ctx: CommandContext): Promise<void> {
   const cfg = relayConfigured(ctx);
   if (!cfg.enabled || !cfg.flagOn) {
-    ctx.print('Relay is disabled — turn on relay.enabled in /config relay first.');
+    ctx.print('Relay is disabled: turn on relay.enabled in /config relay first.');
     return;
   }
   const externalServices = ctx.platform.externalServices;

package/src/input/commands/remote-runtime.ts

@@ -132,7 +132,7 @@ export function registerRemoteRuntimeCommands(registry: CommandRegistry): void {
           '  capabilities:',
           ...selected.capabilities.map((capability) => `    ${capability.id}: ${capability.supported ? 'yes' : 'no'} (${capability.detail})`),
           '  recovery:',
-          ...selected.recovery.map((action) => `    ${action.command} — ${action.reason}`),
+          ...selected.recovery.map((action) => `    ${action.command}: ${action.reason}`),
         ].join('\n'));
         return;
       }
@@ -157,7 +157,7 @@ export function registerRemoteRuntimeCommands(registry: CommandRegistry): void {
           `  trustClass: ${selected.negotiation.trustClass}`,
           '  capabilities:',
           ...selected.capabilities.map((capability) => (
-            `    ${capability.id}: ${capability.supported ? 'supported' : 'missing'} — ${capability.detail}`
+            `    ${capability.id}: ${capability.supported ? 'supported' : 'missing'}; ${capability.detail}`
           )),
         ].join('\n'));
         return;
@@ -190,7 +190,7 @@ export function registerRemoteRuntimeCommands(registry: CommandRegistry): void {
           ...(selected.lastError ? [`  lastError: ${selected.lastError}`] : []),
           ...(selected.taskId ? [`  bound task: ${selected.taskId}`] : []),
           '  actions:',
-          ...nextSteps.map((action) => `    ${action.command} — ${action.reason}`),
+          ...nextSteps.map((action) => `    ${action.command}: ${action.reason}`),
         ].join('\n'));
         return;
       }