@hominis/fireforge 0.46.0 → 0.46.2

package/dist/src/core/status-classify.d.ts

@@ -7,34 +7,34 @@
  */
 /**
  * Classification buckets for engine file changes:
- * - `patch-backed`: content matches the expected post-patch state — normal
+ * - `patch-backed`: content matches the expected post-patch state. Normal
  *   after `fireforge import`.
  * - `patch-owned-drift`: the file is claimed by exactly one patch, but the
  *   live engine content no longer matches that patch's expected post-apply
  *   content. This includes furnace-prefixed paths: a path can be both
  *   Furnace-managed and patch-claimed (export a deployed component, then
- *   edit the workspace source and `furnace deploy` again — the deployed copy
- *   now has content the patch body lacks). Checking the furnace prefix first
- *   would bucket such files as `furnace` and report the stale patch as
- *   owned.
- * - `unmanaged`: edits not explained by any patch or tool — local drift to
+ *   edit the workspace source and `furnace deploy` again, and the deployed
+ *   copy now has content the patch body lacks). Checking the furnace
+ *   prefix first would bucket such files as `furnace` and report the stale
+ *   patch as owned.
+ * - `unmanaged`: edits not explained by any patch or tool. Local drift to
  *   export or discard.
  * - `branding`: files under tool-managed branding paths, written by
  *   FireForge's branding pipeline.
  * - `furnace`: files under Furnace-managed component prefixes. When exactly
  *   one patch also claims the path, this bucket asserts the live content
- *   matches that patch's expected post-apply content — a mismatch is
+ *   matches that patch's expected post-apply content. A mismatch is
  *   reported as `patch-owned-drift` instead (see above).
  * - `conflict`: the file is claimed by two or more patches in
  *   `patches.json`. The human `--ownership` mode surfaces this bucket as
- *   `CONFLICT`; carrying the classification through the JSON pipeline lets
+ *   `CONFLICT`. Carrying the classification through the JSON pipeline lets
  *   machine consumers detect the same ownership breakage rather than seeing
  *   it rolled into `unmanaged` as routine local drift.
  * - `binary-unsupported`: the file's comparison is binary and the owning
- *   patch body records no usable blob hash to compare against — an honest
- *   "binary — comparison unsupported" instead of a permanent false
- *   `patch-owned-drift`. Deliberately NOT in the default `--check` fail set;
- *   opt in with `--fail-on binary-unsupported`.
+ *   patch body records no usable blob hash to compare against. It reports an
+ *   honest "binary, comparison unsupported" instead of a permanent false
+ *   `patch-owned-drift`. Not in the default `--check` fail set. Opt in
+ *   with `--fail-on binary-unsupported`.
  */
 export type FileClassification = 'patch-backed' | 'patch-owned-drift' | 'unmanaged' | 'branding' | 'furnace' | 'conflict' | 'binary-unsupported';
 export interface StatusFile {
@@ -45,7 +45,7 @@ export interface ClassifiedFile extends StatusFile {
     classification: FileClassification;
     /**
      * Names of patch files that claim this path in `patches.json`.
-     * Populated only when `classification === 'conflict'` — single-claim
+     * Populated only when `classification === 'conflict'`. Single-claim
      * patch-backed entries don't need to expose their owner because the
      * single claim is fully captured by the classification itself.
      */
@@ -54,14 +54,14 @@ export interface ClassifiedFile extends StatusFile {
      * Owning patch filename when exactly one patch claims this path
      * (patch-backed, patch-owned-drift, and single-owner furnace entries).
      * Unset for unowned, branding-generated, unowned-furnace, and conflict
-     * entries — conflicts carry `claimedBy` instead. Exposed through
+     * entries. Conflicts carry `claimedBy` instead. Exposed through
      * `status --json` as the `patch` field.
      */
     owner?: string;
 }
 /**
  * Builds the file → owning-patch-filenames multimap from manifest rows.
- * Single source of truth for cross-patch claim detection — status
+ * Single source of truth for cross-patch claim detection: status
  * classification, verify's cross-claim check, and the ownership table all
  * consume this builder (they used to each rebuild it, one drift away from
  * disagreeing about what "claimed" means).
@@ -72,14 +72,14 @@ export declare function buildPatchClaims(manifestPatches: ReadonlyArray<{
 }>): Map<string, string[]>;
 /**
  * Reduces a two-character porcelain XY status to its primary code.
- * Single source of truth — status-output.ts renders from the same logic.
+ * Single source of truth, and status-output.ts renders from the same logic.
  */
 export declare function getPrimaryStatusCode(status: string): string;
 /**
  * True for the branding paths whose content FireForge generates itself
  * (configure.sh, brand.properties/ftl, browser/moz.configure). Unlike the
  * broader branding-root test, a brand-new unowned file under the branding
- * directory is NOT generated — it is a patch candidate and must stay
+ * directory is not generated: it is a patch candidate and must stay
  * visible as unmanaged (the Assets.car precedent).
  */
 export declare function isGeneratedBrandingPath(file: string, binaryName: string): boolean;

package/dist/src/core/status-classify.js

@@ -17,7 +17,7 @@ import { createPatchedContentContext } from './patch-apply.js';
 import { classifyBinaryOwnedFile } from './status-binary.js';
 /**
  * Builds the file → owning-patch-filenames multimap from manifest rows.
- * Single source of truth for cross-patch claim detection — status
+ * Single source of truth for cross-patch claim detection: status
  * classification, verify's cross-claim check, and the ownership table all
  * consume this builder (they used to each rebuild it, one drift away from
  * disagreeing about what "claimed" means).
@@ -35,7 +35,7 @@ export function buildPatchClaims(manifestPatches) {
 }
 /**
  * Reduces a two-character porcelain XY status to its primary code.
- * Single source of truth — status-output.ts renders from the same logic.
+ * Single source of truth, and status-output.ts renders from the same logic.
  */
 export function getPrimaryStatusCode(status) {
     if (status.includes('?'))
@@ -53,7 +53,7 @@ export function getPrimaryStatusCode(status) {
  * True for the branding paths whose content FireForge generates itself
  * (configure.sh, brand.properties/ftl, browser/moz.configure). Unlike the
  * broader branding-root test, a brand-new unowned file under the branding
- * directory is NOT generated — it is a patch candidate and must stay
+ * directory is not generated: it is a patch candidate and must stay
  * visible as unmanaged (the Assets.car precedent).
  */
 export function isGeneratedBrandingPath(file, binaryName) {
@@ -67,15 +67,15 @@ export function isGeneratedBrandingPath(file, binaryName) {
 /**
  * Compares a single-owner file's live engine content against its owning
  * patch's expected post-apply content. `matchClassification` is what a
- * clean match reports — `patch-backed` for ordinary patch-claimed paths,
+ * clean match reports: `patch-backed` for ordinary patch-claimed paths,
  * `furnace` for furnace-prefixed paths so healthy deployed components
  * keep landing in the pinned furnace bucket. Any mismatch (including a
  * deletion the patch does not expect, or a failed comparison) reports
  * `patch-owned-drift`.
  */
 async function classifySingleOwnerFile(entry, engineDir, patchesDir, matchClassification, owner, ctx) {
-    // Binary comparisons cannot go through the utf-8 content path below —
-    // binary patch bodies parse to zero hunks, so the patched-content
+    // Binary comparisons cannot go through the utf-8 content path below.
+    // Binary patch bodies parse to zero hunks, so the patched-content
     // computation returned HEAD content unchanged and the comparison
     // reported `patch-owned-drift` forever. Settle by blob hash,
     // or classify explicitly as `binary-unsupported` when no hash exists.
@@ -100,7 +100,7 @@ async function classifySingleOwnerFile(entry, engineDir, patchesDir, matchClassi
             owner,
         };
     }
-    // File exists on disk — compare actual vs expected
+    // File exists on disk: compare actual vs expected
     try {
         const [expected, actual] = await Promise.all([
             ctx.computePatched(entry.file),
@@ -130,7 +130,7 @@ async function classifySingleOwnerFile(entry, engineDir, patchesDir, matchClassi
  */
 export async function classifyFiles(files, engineDir, patchesDir, binaryName, furnacePrefixes) {
     // One manifest load + patch discovery + memoized body reads for the
-    // whole batch — the previous per-file computation re-ran all three for
+    // whole batch. The previous per-file computation re-ran all three for
     // every dirty file (O(dirtyFiles × patches) redundant IO on a broad
     // engine edit session).
     const ctx = await createPatchedContentContext(patchesDir, engineDir);
@@ -150,14 +150,14 @@ export async function classifyFiles(files, engineDir, patchesDir, binaryName, fu
         ctx,
     };
     // Bounded pool over per-file classification (each single-owner file
-    // spawns git); order preserved by the mapper. Per-file failures settle
+    // spawns git). Order preserved by the mapper. Per-file failures settle
     // inside classifySingleOwnerFile's catch, so one bad file never rejects
     // the batch.
     return mapWithConcurrency(files, CLASSIFY_CONCURRENCY, (entry) => classifyEntry(entry, deps));
 }
 /** Concurrency bound for per-file classification (matches import's guard). */
 const CLASSIFY_CONCURRENCY = 8;
-/** Classifies one status entry; extracted so the pool worker stays flat. */
+/** Classifies one status entry. Extracted so the pool worker stays flat. */
 async function classifyEntry(entry, deps) {
     const { engineDir, patchesDir, binaryName, furnacePrefixes, patchClaims, ctx } = deps;
     const owners = patchClaims.get(entry.file);
@@ -209,7 +209,7 @@ async function classifyEntry(entry, deps) {
     if (!owners) {
         return { ...entry, classification: 'unmanaged' };
     }
-    // File is claimed by exactly one patch — compare content.
+    // File is claimed by exactly one patch: compare content.
     const owner = owners[0];
     if (owner === undefined) {
         return { ...entry, classification: 'unmanaged' };

package/dist/src/core/test-changed-prefs.d.ts

@@ -1,26 +1,26 @@
 /**
  * Recognizer for the one mochitest failure shape that is a function of run
- * LENGTH rather than of the code under test: the time-driven
+ * length rather than of the code under test: the time-driven
  * changed-preference checks.
  *
  * Separate from `test-harness-crash.ts` because it is not a crash
- * classification — the run failed, and the classifier's verdict is correct.
- * What this adds is which KIND of failure it was, which is a different
+ * classification. The run failed, and the classifier's verdict is correct.
+ * What this adds is which kind of failure it was, which is a different
  * question and one that only grows as more such shapes are recorded.
  */
 /**
- * Describes a failure set that consists ENTIRELY of changed-preference
+ * Describes a failure set that consists entirely of changed-preference
  * checks on {@link TIME_DRIVEN_PREF_NAMES}.
  *
- * Deliberately keyed on the pref NAMES rather than on the harness's phrasing
- * of its changed-preference report: the phrasing is upstream copy that has
- * no stable contract with us, and the names are the part that identifies the
- * shape. A single block that names anything else — a real assertion, a
- * different pref — disqualifies the whole set, because the point is to
- * describe a run whose every failure is this noise, never to explain away
- * one real failure sitting beside it.
+ * Keyed on the pref names rather than on the harness's phrasing of its
+ * changed-preference report: the phrasing is upstream copy that has no
+ * stable contract with us, and the names are the part that identifies the
+ * shape. A single block that names anything else (a real assertion, a
+ * different pref) disqualifies the whole set, so that this describes a run
+ * whose every failure is this noise, and never explains away one real
+ * failure sitting beside it.
  *
- * Pure; returns undefined when the shape does not apply.
+ * Pure. Returns undefined when the shape does not apply.
  *
  * @param output - Combined harness stdout+stderr
  * @returns Operator-facing explanation, or undefined

package/dist/src/core/test-changed-prefs.js

@@ -1,23 +1,23 @@
 // SPDX-License-Identifier: EUPL-1.2
 /**
  * Recognizer for the one mochitest failure shape that is a function of run
- * LENGTH rather than of the code under test: the time-driven
+ * length rather than of the code under test: the time-driven
  * changed-preference checks.
  *
  * Separate from `test-harness-crash.ts` because it is not a crash
- * classification — the run failed, and the classifier's verdict is correct.
- * What this adds is which KIND of failure it was, which is a different
+ * classification. The run failed, and the classifier's verdict is correct.
+ * What this adds is which kind of failure it was, which is a different
  * question and one that only grows as more such shapes are recorded.
  */
 import { collectUnexpectedFailureBlocks } from './test-harness-crash.js';
 /**
- * Preferences that move on their own as a function of how LONG a run takes,
+ * Preferences that move on their own as a function of how long a run takes,
  * not of what it tested.
  *
  * Both are time-driven: a long run crosses the cold-startup check interval
  * and the pref moves under the harness. The observable consequence is that
  * chunk length, not the change under test, decides whether the suite is
- * red — the same work at a smaller `--chunk` passes. FireForge cannot
+ * red. The same work at a smaller `--chunk` passes. FireForge cannot
  * suppress the check (it is the harness's, not ours) but it can stop the
  * pair being indistinguishable from two real assertion failures, which is
  * the whole cost of the shape.
@@ -29,18 +29,18 @@ const TIME_DRIVEN_PREF_NAMES = ['lastColdStartupCheck', 'globalprivacycontrol'];
 /** A failure block that is a changed-preference report rather than an assertion. */
 const CHANGED_PREF_BLOCK_PATTERN = /pref(?:erence)?s?\b/i;
 /**
- * Describes a failure set that consists ENTIRELY of changed-preference
+ * Describes a failure set that consists entirely of changed-preference
  * checks on {@link TIME_DRIVEN_PREF_NAMES}.
  *
- * Deliberately keyed on the pref NAMES rather than on the harness's phrasing
- * of its changed-preference report: the phrasing is upstream copy that has
- * no stable contract with us, and the names are the part that identifies the
- * shape. A single block that names anything else — a real assertion, a
- * different pref — disqualifies the whole set, because the point is to
- * describe a run whose every failure is this noise, never to explain away
- * one real failure sitting beside it.
+ * Keyed on the pref names rather than on the harness's phrasing of its
+ * changed-preference report: the phrasing is upstream copy that has no
+ * stable contract with us, and the names are the part that identifies the
+ * shape. A single block that names anything else (a real assertion, a
+ * different pref) disqualifies the whole set, so that this describes a run
+ * whose every failure is this noise, and never explains away one real
+ * failure sitting beside it.
  *
- * Pure; returns undefined when the shape does not apply.
+ * Pure. Returns undefined when the shape does not apply.
  *
  * @param output - Combined harness stdout+stderr
  * @returns Operator-facing explanation, or undefined
@@ -61,7 +61,7 @@ export function describeChangedPrefNoise(output) {
 /** Failure blocks inspected before the changed-pref shape is abandoned. */
 const CHANGED_PREF_BLOCK_LIMIT = 20;
 /**
- * The RECOGNIZER half of the shape, split from the formatting so a caller
+ * The recognizer half of the shape, split from the formatting so a caller
  * that only needs the yes/no answer does not build the ~500-character
  * explanation to throw it away.
  *

package/dist/src/core/test-harness-crash.d.ts

@@ -8,16 +8,16 @@
  *  - startup crashes from the mozlog resource monitor on macOS
  *    (`AttributeError: 'SystemResourceMonitor' object has no attribute
  *    'poll_interval'`, `host_statistics64(HOST_VM_INFO64) syscall failed`,
- *    `(ipc/mig) array not large enough` — a psutil/macOS mismatch) which
- *    abort the run before any test executes;
+ *    `(ipc/mig) array not large enough`, a psutil/macOS mismatch) which
+ *    abort the run before any test executes.
  *  - hangs after browser startup that die at the no-output timeout yet still
- *    emit a `Passed: 0` summary;
+ *    emit a `Passed: 0` summary.
  *  - post-green shutdown re-entry, where a fully green run stalls on "must
  *    wait for focus" and records "Application shut down (without crashing)
  *    in the middle of a test!" as the only unexpected failure.
  *
- * Classification therefore keys on `TEST-START` presence — summary lines
- * never count as proof that tests ran — and recognizes the crash shapes
+ * Classification therefore keys on `TEST-START` presence, so summary lines
+ * never count as proof that tests ran, and recognizes the crash shapes
  * above so the command layer can retry them with a bounded budget instead of
  * reporting phantom test failures (or phantom passes).
  */
@@ -51,14 +51,14 @@ export interface HarnessRunVerdict extends HarnessSummaryCounts {
     secondaryHarnessSignature?: HarnessCrashSignature;
     /**
      * Set when a non-zero mach exit code was overridden because the output
-     * embeds a completed green summary — the exit code followed harness
+     * embeds a completed green summary, so the exit code followed harness
      * noise, not a test result. Callers should surface a note.
      */
     greenSummaryOverride?: boolean;
     /**
-     * Set when the output embeds a green-LOOKING summary that was REJECTED:
+     * Set when the output embeds a green-looking summary that was rejected:
      * crash or truncation evidence proves the suite never completed, so the
-     * "green" counts only cover the files that ran before the run died — a
+     * "green" counts only cover the files that ran before the run died. A
      * SIGSEGV at the second of eight files leaves a `Passed: 2 / Failed: 0`
      * summary that reads as a pass. Callers must fail the run and surface the
      * evidence.
@@ -66,9 +66,9 @@ export interface HarnessRunVerdict extends HarnessSummaryCounts {
     greenSummaryRejected?: GreenSummaryRejection;
     /**
      * Short parenthetical appended to the `FIREFORGE-VERDICT:` line when the
-     * bare status would under-describe the run — currently "harness teardown
+     * bare status would under-describe the run: currently "harness teardown
      * noise ignored" and the headed display-asleep stall. Advisory text
-     * only; the status and reason keys are unaffected.
+     * only. The status and reason keys are unaffected.
      */
     note?: string;
 }
@@ -85,8 +85,8 @@ export interface GreenSummaryRejection {
  * Strips non-signal noise from captured output before crash-signature
  * matching: resource-monitor degradation warnings, and traceback blocks
  * that mach caught itself (telemetry submission tracebacks are printed but
- * never abort the run). The stripped text is used ONLY as crash evidence —
- * classification of test results still reads the full output.
+ * never abort the run). The stripped text is used only as crash evidence.
+ * Classification of test results still reads the full output.
  */
 export declare function stripNonSignalNoise(output: string): string;
 /**
@@ -96,15 +96,15 @@ export declare function stripNonSignalNoise(output: string): string;
  */
 export declare function findCrashMarkerLine(output: string): string | undefined;
 /**
- * True when the output embeds a COMPLETED, GREEN suite summary: an execution
+ * True when the output embeds a completed, green suite summary: an execution
  * signal, `Unexpected results: 0` (and no non-zero unexpected count), a
- * `SUITE_END` marker, no real `TEST-UNEXPECTED-*` lines — and NO crash
+ * `SUITE_END` marker, no real `TEST-UNEXPECTED-*` lines, and no crash
  * marker. Such a run finished its suite, so any startup-traceback-shaped
- * noise in the same output is by definition non-fatal and this vetoes
- * signature-based crash classification; without the veto, fully green
+ * noise in the same output is non-fatal and this vetoes
+ * signature-based crash classification. Without the veto, fully green
  * sharded runs report `CRASH (N attempts)` because degradation warnings
- * match the psutil signals. A summary printed after a crash marker is NOT
- * "completed" — it only covers the files that ran before the crash.
+ * match the psutil signals. A summary printed after a crash marker is not
+ * "completed": it only covers the files that ran before the crash.
  * Exported for direct unit testing.
  */
 export declare function hasCompletedGreenSummary(output: string): boolean;
@@ -113,11 +113,11 @@ export declare function hasCompletedGreenSummary(output: string): boolean;
  * requested file must produce a start marker, and every started test must
  * produce an end marker (the harness emits both even for failing files).
  *
- * Ends are paired with starts POSITIONALLY (last open start is closed by
- * the next end), not by filename — the xpcshell dialect's `TEST_END: Test
+ * Ends are paired with starts positionally (last open start is closed by
+ * the next end), not by filename: the xpcshell dialect's `TEST_END: Test
  * PASS` lines do not name the file. Requested paths that are not
  * test-file-shaped (directories, manifests) are skipped for the
- * never-started check; the start/end pairing scan covers them regardless.
+ * never-started check. The start/end pairing scan covers them regardless.
  * Exported for direct unit testing.
  */
 export declare function analyzeTestCompleteness(output: string, requestedPaths: readonly string[]): {
@@ -129,7 +129,7 @@ export declare function analyzeTestCompleteness(output: string, requestedPaths:
  * assertion/diff context, one string per block. The shutdown-reentry
  * artifact is excluded (it is harness noise, not a test result). When more
  * than `limit` blocks exist, a final `…(+N more …)` note is appended so the
- * operator knows the echo was truncated. Pure; exported for unit tests.
+ * operator knows the echo was truncated. Pure. Exported for unit tests.
  */
 export declare function collectUnexpectedFailureBlocks(output: string, limit?: number): string[];
 /**
@@ -141,36 +141,36 @@ export declare function detectHarnessCrashSignature(output: string): HarnessCras
  * Classifies a completed harness run. The decision tree, in order:
  *
  * 1. A recognized crash signature wins regardless of exit code (the
- *    shutdown re-entry shape exits non-zero on an otherwise green run;
- *    the hang shape can even exit zero with a `Passed: 0` summary).
- * 2. No execution signal with explicit paths requested means no test ran —
+ *    shutdown re-entry shape exits non-zero on an otherwise green run,
+ *    and the hang shape can even exit zero with a `Passed: 0` summary).
+ * 2. No execution signal with explicit paths requested means no test ran:
  *    `no-tests`, even when the exit code is zero. The execution signal is
  *    a `TEST-START` line (generic `mach test` / browser-chrome dispatch)
- *    OR the suite-specific xpcshell result-summary block (the xpcshell
+ *    or the suite-specific xpcshell result-summary block (the xpcshell
  *    dispatch prints no `TEST-START`). Bare `Passed:`/`Failed:` summary
  *    lines are still not trusted as evidence of execution.
- * 3. Exit code zero with tests started is a pass; anything else is a
- *    test failure for the regular diagnosis chain — except a non-zero
- *    exit whose embedded summary completed green AND shows no crash
+ * 3. Exit code zero with tests started is a pass. Anything else is a
+ *    test failure for the regular diagnosis chain, except a non-zero
+ *    exit whose embedded summary completed green and shows no crash
  *    marker and no truncated/never-started requested file, which is a
  *    pass with a `greenSummaryOverride` note (harness noise owns the
- *    exit code). A green-shaped summary WITH such evidence is rejected
+ *    exit code). A green-shaped summary with such evidence is rejected
  *    (`greenSummaryRejected`) and fails.
  */
 export declare function classifyHarnessRun(exitCode: number, output: string, requestedPaths: readonly string[]): HarnessRunVerdict;
 /**
  * Parses the numeric counts from the harness's embedded result summary
- * (`Ran N checks` / `Unexpected results: N`). The LAST occurrence of each
- * wins — a multi-suite run prints one summary per suite and the final one
+ * (`Ran N checks` / `Unexpected results: N`). The last occurrence of each
+ * wins: a multi-suite run prints one summary per suite and the final one
  * covers the aggregate the operator sees. Absent counts are omitted (the
  * `FIREFORGE-VERDICT:` contract: an absent key means "summary did not
  * print it", never zero).
  */
 export declare function extractSummaryCounts(output: string): HarnessSummaryCounts;
 /**
- * Formats the machine-readable `FIREFORGE-VERDICT:` line — the stable,
+ * Formats the machine-readable `FIREFORGE-VERDICT:` line: the stable,
  * greppable last line every `fireforge test` run prints so harness-verdict
- * consumers stop regexing mach internals. The status follows THIS
+ * consumers stop regexing mach internals. The status follows this
  * classifier, never the raw exit code: a crash-classified run says
  * `FAIL reason=crash` even at exit 0, and a green-summary-override pass
  * says `PASS` despite a non-zero mach exit. Count keys are omitted when
@@ -197,18 +197,18 @@ export declare function buildHarnessCrashMessage(signature: HarnessCrashSignatur
  * `xpcshell return code: -11` with zero output is the signature of an
  * `.sys.mjs` that a packaged module imports but whose `EXTRA_JS_MODULES`
  * registration never landed: the module loader faults before any logging
- * exists, so there is no import error, no stack, no test output — just a
+ * exists, so there is no import error, no stack, no test output, just a
  * dead process. It is indistinguishable from a genuine product crash
  * unless someone names the cause.
  *
- * "Produced no evidence" is deliberately semantic rather than a byte
+ * "Produced no evidence" is semantic rather than a byte
  * budget: no execution signal, no real failure line, and no mozcrash
  * marker. A run that got far enough to start a test, report a failure, or
  * leave a crash dump has evidence of its own, and the regular diagnosis
- * chain reads it — this branch is only for the case where there is
+ * chain reads it. This branch is only for the case where there is
  * nothing else to say.
  *
- * Pure; exported for direct unit testing.
+ * Pure. Exported for direct unit testing.
  *
  * @param exitCode - The harness process exit code
  * @param output - Combined stdout/stderr from the run
@@ -225,7 +225,7 @@ export declare function isSilentSegfault(exitCode: number, output: string): bool
 export declare function buildSilentSegfaultMessage(exitCode: number, requestedPaths: readonly string[]): string;
 /**
  * Builds the message for a run that produced no `TEST-START` despite
- * requesting paths — including exit-code-zero runs whose `Passed: 0`
+ * requesting paths, including exit-code-zero runs whose `Passed: 0`
  * summary would otherwise read as a silent false green.
  */
 export declare function buildNoTestsRanMessage(exitCode: number, requestedPaths: readonly string[]): string;