@pellux/goodvibes-daemon 1.28.19 → 1.28.21

package/src/daemon/pair-command.ts

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

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

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

package/src/daemon/send/channels.ts

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

package/src/daemon/send/command.ts

@@ -1,5 +1,5 @@
 /**
- * command.ts — `goodvibes-daemon send`, the shell's way to put a message on one
+ * command.ts, `goodvibes-daemon send`, the shell's way to put a message on one
  * of the owner's channels.
  *
  * ## Why this exists
@@ -7,7 +7,7 @@
  * Nothing on this machine could send the owner a message from a script. The
  * three binaries exposed no send verb, the daemon's HTTP API answers
  * `401 AUTH_REQUIRED` to the operator token as stored, and driving the agent to
- * do it failed with `Missing Telegram bot token` — because the credential lives
+ * do it failed with `Missing Telegram bot token`, because the credential lives
  * in the DAEMON tier (`~/.goodvibes/daemon/settings.json`) and the agent was
  * reading its own surface silo. So the one process that could always send was
  * the daemon, and only while it was running.
@@ -15,7 +15,7 @@
  * ## Three properties this command is built around
  *
  * 1. **It uses the delivery path, it is not a second sender.** Everything below
- *    ends in `ChannelDeliveryRouter.deliver()` — the same call
+ *    ends in `ChannelDeliveryRouter.deliver()`, the same call
  *    `AutomationDeliveryManager.sendTarget` makes, reaching the same
  *    per-surface strategies in `strategies-core.ts`. Nothing here talks to a
  *    provider API directly.
@@ -26,7 +26,7 @@
  *    was NOT used, deliberately: it returns an empty array when a feature gate
  *    is off and returns failed attempts rather than throwing, so a caller that
  *    did not inspect its result would report success for a message that never
- *    left the machine — the exact false-green this command exists to avoid. The
+ *    left the machine, the exact false-green this command exists to avoid. The
  *    gate check it would have done is done here instead, explicitly, and a gate
  *    that is off produces a refusal naming the settings key rather than silence.
  *
@@ -34,8 +34,8 @@
  *    through `inertBodyFor` for the target surface before it reaches the router,
  *    and there is no flag, env var or code path that skips that. The message
  *    normally comes from the operator's own shell, but the command must not
- *    become the way something else's text — a log line, a captured error, a
- *    remote agent's output piped in — arrives on the owner's phone rendered as
+ *    become the way something else's text, a log line, a captured error, a
+ *    remote agent's output piped in, arrives on the owner's phone rendered as
  *    live markup with a clickable link in it. See inert-text.ts.
  */
 
@@ -51,7 +51,7 @@ import { inertBodyFor } from './inert-text.ts';
 export type SendDeliver = (request: ChannelDeliveryRequest) => Promise<string | undefined>;
 
 export interface SendCommandDeps {
-  /** Built with a `homeDir` so the daemon tier overlays — see channels.ts. */
+  /** Built with a `homeDir` so the daemon tier overlays, see channels.ts. */
   readonly configManager: Pick<ConfigManager, 'get'>;
   readonly deliver: SendDeliver;
   /** Reads the whole of stdin; only called when no message argument was given. */
@@ -93,12 +93,12 @@ const USAGE = [
   '      --list           Show every channel, whether it is on, and where it sends.',
   '  -h, --help           Print this help',
   '',
-  'A channel that is switched off is refused by name and NOTHING is sent — the',
+  'A channel that is switched off is refused by name and NOTHING is sent: the',
   'command never quietly falls back to the default, so a message meant for a',
   'quiet channel cannot end up on a noisy one.',
   '',
   'The message is always delivered as literal text: markup a channel would',
-  'otherwise render — a Discord masked link, a Slack mention — arrives inert.',
+  'otherwise render (a Discord masked link, a Slack mention) arrives inert.',
 ].join('\n');
 
 function parseSendArgs(argv: readonly string[]): ParsedSendArgs {
@@ -153,7 +153,7 @@ function describeConfiguredChannels(config: Pick<ConfigManager, 'get'>): string
     .map((entry) => entry.channel.id);
   return usable.length > 0
     ? `Configured and ready: ${usable.join(', ')}.`
-    : 'No channel is currently both switched on and given a destination — run: goodvibes-daemon send --list';
+    : 'No channel is currently both switched on and given a destination; run: goodvibes-daemon send --list';
 }
 
 function renderChannelList(config: Pick<ConfigManager, 'get'>): string[] {
@@ -304,7 +304,7 @@ export async function runSendCommand(
   };
 
   const preamble = usedDefault
-    ? [`No channel named — using ${channel.id}: ${defaultReason}.`]
+    ? [`No channel named; using ${channel.id}: ${defaultReason}.`]
     : [];
   try {
     const responseId = await deps.deliver(request);

package/src/daemon/send/composition.ts

@@ -1,5 +1,5 @@
 /**
- * composition.ts — the smallest set of services that can put a message on a
+ * composition.ts, the smallest set of services that can put a message on a
  * channel, built from the daemon's own tier.
  *
  * ## Why not `createRuntimeServices`
@@ -7,7 +7,7 @@
  * The daemon's full runtime graph starts a LAN scan, a cluster coordinator, an
  * inbox poller, a fleet tick, a memory governor and a config watch. Composing
  * it to send one message would build a second, competing set of that state on a
- * machine that is already running a daemon — the same reason `cluster …` is
+ * machine that is already running a daemon, the same reason `cluster …` is
  * intercepted before any runtime is constructed (see src/daemon/cli.ts). This
  * builds only the five objects `ChannelDeliveryRouter` needs and starts no
  * timers, binds no sockets and joins no election, so it is safe to run beside a
@@ -18,7 +18,7 @@
  * That was tried before this command existed: the control-plane API answers
  * `401 AUTH_REQUIRED` to the operator token as stored on disk. More importantly
  * an HTTP-backed send would only work while a daemon is up, and the case this
- * command is for — telling the owner that something has stopped — is exactly
+ * command is for, telling the owner that something has stopped, is exactly
  * when it may not be.
  *
  * ## Where the credentials come from
@@ -42,7 +42,7 @@ import { GOODVIBES_DAEMON_SURFACE_ROOT } from '../../config/surface.ts';
 
 export interface SendStackRoots {
   readonly workingDirectory: string;
-  /** The GoodVibes tree root — the directory `.goodvibes/` sits under. */
+  /** The GoodVibes tree root, the directory `.goodvibes/` sits under. */
   readonly homeDirectory: string;
   /** The daemon's own state root, holding the daemon-scoped secret stores. */
   readonly daemonHomeDirectory: string;
@@ -62,7 +62,7 @@ export interface SendStack {
  * roots (goodvibes-tui and goodvibes-agent) omitted it, still type-checked,
  * still delivered on every surface whose credential happens to sit in config or
  * the environment, and failed only on the surfaces that use a secret reference
- * — at send time, as `Missing Telegram bot token`. This composition root does
+ *, at send time, as `Missing Telegram bot token`. This composition root does
  * not repeat that.
  */
 export function createSendStack(roots: SendStackRoots): SendStack {

package/src/daemon/send/failure-text.ts

@@ -1,5 +1,5 @@
 /**
- * failure-text.ts — what the operator is told when a send does not happen.
+ * failure-text.ts, what the operator is told when a send does not happen.
  *
  * ## Why this is not `summarizeError`
  *
@@ -10,10 +10,10 @@
  *
  *     Telegram delivery failed HTTP 401: {"ok":false,"description":"Unauthorized"}
  *
- * it returns `Telegram delivery failed HTTP 401` — its `stripJson` pass removes
+ * it returns `Telegram delivery failed HTTP 401`, its `stripJson` pass removes
  * the `{...}`, which is exactly the part naming what went wrong. Given
  * `connect ECONNREFUSED 149.154.167.220:443` it returns "Cannot connect to the
- * provider. Check whether the service is reachable." — advice in place of the
+ * provider. Check whether the service is reachable.", advice in place of the
  * address that was refused.
  *
  * A person debugging a message that did not arrive needs the provider's own
@@ -39,7 +39,7 @@ import { redactSensitiveData } from '@pellux/goodvibes-sdk/platform/utils';
 
 /**
  * A generous cap. The point of this text is diagnosis, so it is far larger than
- * the 240 characters `summarizeError` allows — but an HTML error page or a
+ * the 240 characters `summarizeError` allows, but an HTML error page or a
  * multi-megabyte body still must not flood the terminal.
  */
 const MAX_FAILURE_TEXT = 2_000;
@@ -47,10 +47,10 @@ const MAX_FAILURE_TEXT = 2_000;
 const URL_CREDENTIAL_PATTERNS: ReadonlyArray<{ readonly pattern: RegExp; readonly replacement: string }> = [
   // Telegram: the bot token IS the path segment.
   { pattern: /\/bot\d{5,}:[A-Za-z0-9_-]{10,}/g, replacement: '/bot[REDACTED_BOT_TOKEN]' },
-  // Any URL carrying `user:password@host` — BlueBubbles, Mattermost and Matrix
+  // Any URL carrying `user:password@host`, BlueBubbles, Mattermost and Matrix
   // base URLs are all operator-supplied and can be written this way.
   { pattern: /(\b[a-z][a-z0-9+.-]*:\/\/)[^/\s:@]+:[^/\s@]+@/gi, replacement: '$1[REDACTED_CREDENTIALS]@' },
-  // A credential passed as a query parameter — BlueBubbles sends `?password=`.
+  // A credential passed as a query parameter, BlueBubbles sends `?password=`.
   {
     pattern: /([?&](?:password|token|secret|access_token|api_?key|auth)=)[^&\s"']+/gi,
     replacement: '$1[REDACTED]',

package/src/daemon/send/inert-text.ts

@@ -1,5 +1,5 @@
 /**
- * inert-text.ts — make a message arrive as LITERAL TEXT on whichever channel
+ * inert-text.ts, make a message arrive as LITERAL TEXT on whichever channel
  * `goodvibes-daemon send` delivers it to.
  *
  * ## What "inert" means here, and why it is per (surface × transport), not
@@ -12,7 +12,7 @@
  *
  *  - Telegram's `sendMessage` CAN parse MarkdownV2, but the strategy sends with
  *    NO `parse_mode`, which is Telegram's plain-text mode. Running a MarkdownV2
- *    escaper over the body on this path would not protect anything — it would
+ *    escaper over the body on this path would not protect anything, it would
  *    put visible backslashes in front of every `.` `-` `!` `(` in the owner's
  *    message. The correct transform is identity, and the property that makes it
  *    correct is asserted by a test against the real wire payload rather than
@@ -29,7 +29,7 @@
  *
  * `escapeDiscordMarkdown` and `escapeSlackMrkdwn` are the escapers written for
  * the inbound-mail structured notices, in the SDK at
- * `packages/sdk/src/platform/email/inbound-notice.ts` — same character classes,
+ * `packages/sdk/src/platform/email/inbound-notice.ts`, same character classes,
  * same zero-width-space mention break, same rationale. They are reproduced here
  * rather than imported for one reason: that module lives on the unmerged
  * `inbound-email-*` branches and is absent from the published
@@ -72,8 +72,8 @@ function breakMentionForms(text: string): string {
  *
  * `[` `]` `(` `)` are escaped too, and this is REQUIRED rather than
  * precautionary: masked links (`[text](url)`) DO render as clickable in
- * bot-sent and webhook messages — which is exactly how this product delivers to
- * Discord — even though they do not render for text a human typed into the
+ * bot-sent and webhook messages, which is exactly how this product delivers to
+ * Discord, even though they do not render for text a human typed into the
  * client.
  *   https://github.com/discord/discord-api-docs/issues/6096
  *   https://gist.github.com/matthewzring/9f7bbfd102003963f9be7dbcf7d40e51
@@ -97,11 +97,11 @@ function escapeDiscordMarkdown(text: string): string {
  * unescaped `<`.
  *
  * Slack has no backslash escape for `* _ ~ \``, so the zero-width break is
- * applied to those as the best available mitigation — stated as a mitigation,
+ * applied to those as the best available mitigation, stated as a mitigation,
  * not a guarantee, because Slack's whitespace-adjacency rule for what breaks a
  * delimiter pair is not publicly specified to that precision. The residual risk
  * is cosmetic (accidental bold/italic); the injection class this exists to
- * close — a clickable link or a real mention — is closed by the entity escaping
+ * close, a clickable link or a real mention, is closed by the entity escaping
  * above.
  */
 function escapeSlackMrkdwn(text: string): string {
@@ -122,8 +122,8 @@ function escapeGoogleChatMarkup(text: string): string {
 
 /**
  * WhatsApp Cloud API text messages render `*bold*`, `_italic_`, `~strike~` and
- * ```` ```mono``` ````. There is no masked-link syntax — a URL in the body is
- * auto-linked showing its real address — so the injection class Discord has
+ * ```` ```mono``` ````. There is no masked-link syntax, a URL in the body is
+ * auto-linked showing its real address, so the injection class Discord has
  * does not exist here and only the delimiters need neutralizing. WhatsApp
  * documents no backslash escape, so the zero-width break is used.
  */
@@ -136,24 +136,24 @@ function escapeWhatsAppMarkup(text: string): string {
  * markup. Every other routable surface is absent DELIBERATELY, and each absence
  * is a checked claim about the strategy, not an oversight:
  *
- *  - `telegram`  — `sendMessage` without `parse_mode`; Telegram's plain-text
+ *  - `telegram` , `sendMessage` without `parse_mode`; Telegram's plain-text
  *                  mode. Escaping here would corrupt, not protect.
- *  - `ntfy`      — `publish` sends the body as `text/plain` and never sets the
+ *  - `ntfy`     , `publish` sends the body as `text/plain` and never sets the
  *                  `Markdown` header, so ntfy renders it literally. The title
  *                  is derived by `titleFromBody` (first non-empty LINE) and
  *                  passed through `toHeaderSafeTitle`, so no line break or
  *                  non-ASCII byte from the body can reach an HTTP header.
- *  - `webhook`   — the body is a JSON string field; the receiver decides what
+ *  - `webhook`  , the body is a JSON string field; the receiver decides what
  *                  to do with it and there is no markup layer to neutralize.
  *
- *  - `signal`    — the strategy posts `text` to a signal bridge. Signal renders
+ *  - `signal`   , the strategy posts `text` to a signal bridge. Signal renders
  *                  no markup in a plain message body; styling travels as
  *                  explicit range metadata the strategy never sends.
  *  - `imessage`,
- *    `bluebubbles` — both end at iMessage, which renders no markup at all.
- *  - `msteams`   — the strategy sends `textFormat: 'plain'` alongside the text,
+ *    `bluebubbles`, both end at iMessage, which renders no markup at all.
+ *  - `msteams`  , the strategy sends `textFormat: 'plain'` alongside the text,
  *                  which is Teams' own instruction not to parse it.
- *  - `matrix`    — `msgtype: 'm.text'` with no `format`/`formatted_body`. A
+ *  - `matrix`   , `msgtype: 'm.text'` with no `format`/`formatted_body`. A
  *                  Matrix event without the HTML format field is rendered
  *                  literally by clients, per the spec.
  *
@@ -161,7 +161,7 @@ function escapeWhatsAppMarkup(text: string): string {
  * `ControlPlaneGateway` in the same process, which a short-lived CLI does not
  * have, so the command does not offer it as a channel at all. `telephony` is
  * absent because a CLI `send` to it would place a phone call or an SMS through
- * a paid carrier — a different act from messaging a channel — and because the
+ * a paid carrier, a different act from messaging a channel, and because the
  * strategy already XML-escapes the voice path itself via `escapeTwiml`.
  */
 const INERT_TRANSFORMS: Partial<Record<ChannelDeliverySurfaceKind, (text: string) => string>> = {
@@ -173,7 +173,7 @@ const INERT_TRANSFORMS: Partial<Record<ChannelDeliverySurfaceKind, (text: string
   'google-chat': escapeGoogleChatMarkup,
   whatsapp: escapeWhatsAppMarkup,
   // Delivered as plain text by the strategy: transforming would corrupt, not
-  // protect. Each of these is a checked claim about the strategy, not a guess —
+  // protect. Each of these is a checked claim about the strategy, not a guess,
   // see the list above.
   telegram: (text) => text,
   ntfy: (text) => text,

package/src/daemon/send/stdin.ts

@@ -1,5 +1,5 @@
 /**
- * stdin.ts — read the whole of stdin as the message body.
+ * stdin.ts, read the whole of stdin as the message body.
  *
  * Kept out of command.ts so the command stays a pure function of its arguments
  * and its injected dependencies: every test drives it with a stub rather than
@@ -10,8 +10,8 @@
  * Read stdin to end, as UTF-8.
  *
  * There is deliberately no timeout. `send` reads stdin only when the operator
- * gave no message argument AND stdin is not a terminal — meaning something is
- * piping into it — so waiting for that producer to finish is the correct
+ * gave no message argument AND stdin is not a terminal, meaning something is
+ * piping into it, so waiting for that producer to finish is the correct
  * behaviour, and cutting it off at an arbitrary deadline would silently
  * truncate a long message.
  */