@hominis/fireforge 0.46.0 → 0.46.1

package/dist/src/core/furnace-validate-registration.js

@@ -94,7 +94,7 @@ export async function checkRegistrationConsistency(root, name, config, ftlDir) {
     // Check target directory
     const targetDir = join(engineDir, config.targetPath);
     status.targetExists = await pathExists(targetDir);
-    // Compare files (sourceExists is guaranteed true — we early-returned above)
+    // Compare files (sourceExists is guaranteed true, we early-returned above)
     if (status.targetExists) {
         const entries = await readdir(componentDir, { withFileTypes: true });
         for (const entry of entries) {
@@ -110,7 +110,7 @@ export async function checkRegistrationConsistency(root, name, config, ftlDir) {
                 continue;
             }
             // Deploy writes CSS-with-include-directives in fragment-expanded form,
-            // so the drift oracle must compare the *expanded* source — otherwise a
+            // so the drift oracle must compare the *expanded* source. Otherwise a
             // freshly deployed component would read as permanently drifted, and a
             // fragment edit would never read as drifted at all.
             let srcContent = await readText(srcPath);
@@ -119,8 +119,8 @@ export async function checkRegistrationConsistency(root, name, config, ftlDir) {
                     srcContent = (await expandCssFragments(srcContent, furnacePaths.sharedDir)).expanded;
                 }
                 catch {
-                    // Missing fragment: validate reports it as `missing-fragment`;
-                    // for drift purposes fall back to the raw source so the compare
+                    // Missing fragment: validate reports it as `missing-fragment`.
+                    // For drift purposes fall back to the raw source so the compare
                     // still happens deterministically.
                 }
             }
@@ -175,7 +175,7 @@ export async function checkRegistrationConsistency(root, name, config, ftlDir) {
     const cePath = join(engineDir, CUSTOM_ELEMENTS_JS);
     if (await pathExists(cePath)) {
         const ceContent = await readText(cePath);
-        // Structure-aware check shared with the ADD path — a bare substring
+        // Structure-aware check shared with the add path. A bare substring
         // test counted any mention of the tag (a leftover comment, an
         // unrelated string) as "registered", masking genuinely missing
         // registrations from both validate and the re-apply drift oracle.
@@ -267,7 +267,7 @@ const AUTO_DETECT_HOST_DIR = 'browser/base/content';
  * This catches a fork that mounts a custom element from its own top-level
  * chrome document (e.g. `mybrowser.xhtml`) without setting
  * `tokenHostDocuments`: scanning only the stock `browser.xhtml` would miss
- * the tokens CSS link in the ACTUAL host document and false-fire the
+ * the tokens CSS link in the actual host document and false-fire the
  * warning.
  *
  * @param engineDir Absolute engine root.
@@ -280,7 +280,7 @@ const AUTO_DETECT_HOST_DIR = 'browser/base/content';
  * `validateAllComponents` walks every component, and re-parsing
  * `fireforge.json` plus re-scanning every `.xhtml` under the chrome-document
  * directory per component is one config parse and one full directory read
- * PER COMPONENT, for work that depends only on the project and the engine.
+ * per component, for work that depends only on the project and the engine.
  *
  * Keyed by root/engine dir and cleared by
  * {@link resetRegistrationValidationCaches} at the start of each run, so a
@@ -291,9 +291,9 @@ const chromeDocumentCache = new Map();
 /**
  * Whether a batch validation is in flight.
  *
- * The caches are consulted ONLY while this is set. Outside a batch — a direct
+ * The caches are consulted only while this is set. Outside a batch (a direct
  * `validateComponent` call from `furnace status`, from apply's consistency
- * check, or from a test — every read goes to disk, so a caller that mutates
+ * check, or from a test) every read goes to disk, so a caller that mutates
  * the engine between calls can never be served a stale document.
  */
 let batchInFlight = false;
@@ -356,7 +356,7 @@ async function loadChromeDocuments(engineDir) {
     return documents;
 }
 async function autoDetectTokenHostDocuments(engineDir, tagName, already) {
-    // Reads the directory ONCE per run rather than once per component: only the
+    // Reads the directory once per run rather than once per component: only the
     // tag being searched for differs between components.
     const documents = await loadChromeDocuments(engineDir);
     const alreadySet = new Set(already);
@@ -377,10 +377,10 @@ async function autoDetectTokenHostDocuments(engineDir, tagName, already) {
  *
  * Scan set is the union of (a) the configured `tokenHostDocuments` (or
  * the upstream default when unset) and (b) any `browser/base/content/*.xhtml`
- * document that references `tagName` — the auto-detection path catches
+ * document that references `tagName`. The auto-detection path catches
  * forks that mount components from a replacement chrome document without
  * having configured `tokenHostDocuments`. The warning fires only when
- * NONE of the documents in the final scan set link the tokens CSS.
+ * none of the documents in the final scan set link the tokens CSS.
  */
 export async function validateTokenLink(componentDir, tagName, root, tokenPrefix, tokenHostDocuments) {
     const issues = [];
@@ -481,7 +481,7 @@ export async function runPostApplyConsistencyChecks(root, config, result, ftlDir
             }
         }
         catch {
-            // Consistency check is best-effort; failures here should not block apply
+            // Consistency check is best-effort. Failures here should not block apply
         }
     }
 }

package/dist/src/core/furnace-validate-structure.d.ts

@@ -2,7 +2,7 @@ import type { ComponentType, CustomComponentConfig, ValidationIssue } from '../t
 /**
  * Returns true when file content carries unresolved three-way-merge
  * conflict markers (as left behind by `furnace refresh`). Shared between
- * the structure validator and `furnace sync`'s pre-apply gate — both must
+ * the structure validator and `furnace sync`'s pre-apply gate. Both must
  * agree on what "conflicted" means so a file that validate flags can never
  * slip through sync into the engine.
  */

package/dist/src/core/furnace-validate-structure.js

@@ -5,7 +5,7 @@ import { pathExists, readText } from '../utils/fs.js';
 /**
  * Returns true when file content carries unresolved three-way-merge
  * conflict markers (as left behind by `furnace refresh`). Shared between
- * the structure validator and `furnace sync`'s pre-apply gate — both must
+ * the structure validator and `furnace sync`'s pre-apply gate. Both must
  * agree on what "conflicted" means so a file that validate flags can never
  * slip through sync into the engine.
  */
@@ -37,7 +37,7 @@ export async function validateStructure(componentDir, tagName, type, customConfi
             message: `Required file ${tagName}.mjs not found.`,
         });
     }
-    // .css should exist — except for library components (base class + helpers,
+    // .css should exist, except for library components (base class + helpers,
     // no element of their own), which render nothing and need no stylesheet.
     if (!(await pathExists(cssPath)) && customConfig?.kind !== 'library') {
         issues.push({
@@ -52,8 +52,8 @@ export async function validateStructure(componentDir, tagName, type, customConfi
     // localization payload is empty, which is hard to spot in review.
     //
     // Components that declare `sharedFtl` participate in a pre-existing
-    // feature-scoped bundle, so there is no per-component .ftl to require —
-    // the shared file is owned by whoever authored the feature bundle.
+    // feature-scoped bundle, so there is no per-component .ftl to require.
+    // The shared file is owned by whoever authored the feature bundle.
     if (type === 'custom' && customConfig?.localized && !customConfig.sharedFtl) {
         const ftlPath = join(componentDir, `${tagName}.ftl`);
         if (!(await pathExists(ftlPath))) {

package/dist/src/core/furnace-validate.js

@@ -61,8 +61,8 @@ export async function validateComponent(componentDir, tagName, type, config, roo
     if (root) {
         issues.push(...(await validateTokenLink(componentDir, tagName, root, config?.tokenPrefix, config?.tokenHostDocuments)));
     }
-    // CSS fragment checks: missing fragment files are structural errors;
-    // stale deployed expansions are drift the next deploy refreshes.
+    // CSS fragment checks: missing fragment files are structural errors.
+    // Stale deployed expansions are drift the next deploy refreshes.
     if (type === 'custom') {
         const furnacePaths = getFurnacePaths(root ?? join(componentDir, '..', '..', '..'));
         const engineTargetDir = root && config?.custom[tagName]
@@ -81,7 +81,7 @@ export async function validateComponent(componentDir, tagName, type, config, roo
     // When root is provided and this is a custom component with registration,
     // also run registration pattern and jar.mn validation for this component.
     // Skipped when an outer orchestrator (validateAllComponents) will run the
-    // aggregate versions itself; otherwise the same issues are reported twice.
+    // aggregate versions itself. Otherwise the same issues are reported twice.
     if (root && config && type === 'custom' && !options?.skipAggregateChecks) {
         const customConfig = config.custom[tagName];
         if (customConfig?.register) {
@@ -183,7 +183,7 @@ export async function validateAllComponents(root) {
                 continue;
             }
             // Pass root so that per-component token link validation runs.
-            // Skip registration/jar.mn checks inside validateComponent — the aggregate
+            // Skip registration/jar.mn checks inside validateComponent. The aggregate
             // validators below run them exactly once across all components, which both
             // surfaces cross-component issues and avoids double-counting.
             const issues = await validateComponent(componentDir, name, 'custom', config, root, {
@@ -209,7 +209,7 @@ export async function validateAllComponents(root) {
         // `furnace create --with-tests --xpcshell` scaffolds a test directory at
         // `browser/base/content/test/<binary>-xpcshell/<name>/`. A leftover
         // scaffold whose `<name>` is not in furnace.json is almost always the
-        // aftermath of an incomplete `furnace remove` or `rename`; flag it as an
+        // aftermath of an incomplete `furnace remove` or `rename`. Flag it as an
         // `orphan-xpcshell-scaffold` error so operators delete or re-create the
         // scaffold instead of discovering the mismatch at test run time. A
         // missing engine or scaffold parent directory degrades silently, so this
@@ -224,14 +224,14 @@ export async function validateAllComponents(root) {
             }
         }
         catch {
-            // Validation degrades gracefully — the absence of an engine
+            // Validation degrades gracefully: the absence of an engine
             // directory, permission denial reading the scaffold tree, or any
             // other transient fs issue should never cascade into false
             // "orphan" reports.
         }
         // jsconfig chrome-module paths drift: when `typecheckJsconfig` is
-        // configured, deploy maintains a paths mapping per deployed module file;
-        // missing or stale entries mean typed cross-module imports are silently
+        // configured, deploy maintains a paths mapping per deployed module file.
+        // Missing or stale entries mean typed cross-module imports are silently
         // degrading to `any` in the consumer's typecheck.
         if (config.typecheckJsconfig) {
             try {
@@ -256,7 +256,7 @@ export async function validateAllComponents(root) {
             }
             catch {
                 // Drift detection must not break validation when the jsconfig is
-                // missing or unparsable — deploy reports those cases with guidance.
+                // missing or unparsable. Deploy reports those cases with guidance.
             }
         }
         return results;

package/dist/src/core/furnace-version-drift.d.ts

@@ -5,19 +5,19 @@
  * Overrides are forks of Firefox source files taken at a specific point in
  * time. If Firefox moves forward and the override's `baseVersion` is not
  * refreshed, the override may apply against a file whose upstream shape has
- * changed — the single biggest silent failure mode for furnace.
+ * changed, which is the single biggest silent failure mode for furnace.
  *
  * Deliberately pure and string-only: no I/O, and no parsing of Firefox
  * version components. String equality is sufficient because `fireforge.json`
  * stores a canonical version string (e.g. `"140.9.0esr"`) and overrides are
  * created with exactly that string copied from
- * `forgeConfig.firefox.version`. Any mismatch is worth surfacing — even
+ * `forgeConfig.firefox.version`. Any mismatch is worth surfacing: even
  * "140.0" vs "140.9.0esr" is a real drift signal.
  *
- * The result GATES apply/deploy: both warn and then FAIL without --force
+ * The result gates apply/deploy: both warn and then fail without --force
  * (see furnaceApplyCommand / furnaceDeployCommand), and `furnace sync`
  * re-checks it after refresh before applying. Status reports drift alongside
- * the component overview. Keep this doc in sync with the gates — it is not
+ * the component overview. Keep this doc in sync with the gates. It is not
  * advisory.
  */
 import type { FurnaceConfig } from '../types/furnace.js';
@@ -35,7 +35,7 @@ export interface OverrideVersionDrift {
 /**
  * Classifies how severe a version drift is by comparing the numeric
  * components of the two version strings. Falls back to `'major'` when
- * either version is unparseable — this ensures that unusual version
+ * either version is unparseable. This ensures that unusual version
  * formats surface with the highest visibility rather than being silently
  * downgraded.
  */

package/dist/src/core/furnace-version-drift.js

@@ -6,19 +6,19 @@
  * Overrides are forks of Firefox source files taken at a specific point in
  * time. If Firefox moves forward and the override's `baseVersion` is not
  * refreshed, the override may apply against a file whose upstream shape has
- * changed — the single biggest silent failure mode for furnace.
+ * changed, which is the single biggest silent failure mode for furnace.
  *
  * Deliberately pure and string-only: no I/O, and no parsing of Firefox
  * version components. String equality is sufficient because `fireforge.json`
  * stores a canonical version string (e.g. `"140.9.0esr"`) and overrides are
  * created with exactly that string copied from
- * `forgeConfig.firefox.version`. Any mismatch is worth surfacing — even
+ * `forgeConfig.firefox.version`. Any mismatch is worth surfacing: even
  * "140.0" vs "140.9.0esr" is a real drift signal.
  *
- * The result GATES apply/deploy: both warn and then FAIL without --force
+ * The result gates apply/deploy: both warn and then fail without --force
  * (see furnaceApplyCommand / furnaceDeployCommand), and `furnace sync`
  * re-checks it after refresh before applying. Status reports drift alongside
- * the component overview. Keep this doc in sync with the gates — it is not
+ * the component overview. Keep this doc in sync with the gates. It is not
  * advisory.
  */
 /**
@@ -39,7 +39,7 @@ function parseVersionComponents(version) {
 /**
  * Classifies how severe a version drift is by comparing the numeric
  * components of the two version strings. Falls back to `'major'` when
- * either version is unparseable — this ensures that unusual version
+ * either version is unparseable. This ensures that unusual version
  * formats surface with the highest visibility rather than being silently
  * downgraded.
  */

package/dist/src/core/git-base.d.ts

@@ -1,7 +1,7 @@
 /**
  * Environment variable that overrides the monolithic `git add -A` timeout
  * (milliseconds). Operators on slow or loaded filesystems can legitimately
- * exceed the 10-minute default during a baseline indexing pass; making the
+ * exceed the 10-minute default during a baseline indexing pass. Making the
  * cap overridable lets them retry without recompiling.
  */
 export declare const GIT_ADD_TIMEOUT_ENV_VAR = "FIREFORGE_GIT_ADD_TIMEOUT_MS";
@@ -48,7 +48,7 @@ export interface GitStatusEntry {
 }
 /**
  * Ensures git is available in the system. Memoised after the first successful
- * probe; {@link git} calls it, so callers that go through that wrapper do not
+ * probe. {@link git} calls it, so callers that go through that wrapper do not
  * need to.
  * @throws GitNotFoundError if git is not installed
  */
@@ -67,7 +67,7 @@ export declare function git(args: string[], cwd: string, options?: {
  * Splits a pathspec list into chunks whose joined byte length stays well under
  * the OS `ARG_MAX` limit, so a single batched `git` invocation over hundreds of
  * Mozilla-length paths cannot fail with `E2BIG`. The 96 KB budget is
- * deliberately conservative — even the smallest historical `ARG_MAX` (256 KB)
+ * conservative on purpose: even the smallest historical `ARG_MAX` (256 KB)
  * leaves room for the fixed git arguments plus the inherited environment.
  *
  * Chunk boundaries are output-neutral for every batched caller here: each
@@ -93,7 +93,7 @@ export declare function configureGitPerformance(repoDir: string): Promise<void>;
  * rewrites LF to CRLF on checkout and back on staging. FireForge cannot
  * tolerate that: patch bodies are byte diffs of the working tree, and
  * `hashObjectBatch` deliberately delegates to git so `.gitattributes` and
- * `core.autocrlf` DO apply to the hashes `status` compares against. Under the
+ * `core.autocrlf` do apply to the hashes `status` compares against. Under the
  * global default the same tree hashes differently on Windows than everywhere
  * else, so exported patches and drift detection disagree across machines.
  * Setting it per-repository leaves the developer's global config alone.

package/dist/src/core/git-base.js

@@ -5,7 +5,7 @@ import { readOnlyGitIndexEnv } from './git-readonly-index.js';
 /**
  * Environment variable that overrides the monolithic `git add -A` timeout
  * (milliseconds). Operators on slow or loaded filesystems can legitimately
- * exceed the 10-minute default during a baseline indexing pass; making the
+ * exceed the 10-minute default during a baseline indexing pass. Making the
  * cap overridable lets them retry without recompiling.
  */
 export const GIT_ADD_TIMEOUT_ENV_VAR = 'FIREFORGE_GIT_ADD_TIMEOUT_MS';
@@ -46,15 +46,15 @@ export const GIT_ADD_CHUNK_TIMEOUT_MS = resolveTimeoutFromEnv(GIT_ADD_CHUNK_TIME
  * In-flight or settled successful `git` availability probe.
  *
  * The probe spawns `which git` (or `where` on Windows), and every git wrapper
- * in this layer used to run it before each command — dozens of extra spawns
- * per `fireforge export`. Only SUCCESS is cached: a rejection clears the slot
- * so a run that installs git mid-flight (or a test that flips the probe) sees
- * the new answer instead of a sticky refusal.
+ * in this layer used to run it before each command, which meant dozens of
+ * extra spawns per `fireforge export`. Only success is cached: a rejection
+ * clears the slot so a run that installs git mid-flight (or a test that flips
+ * the probe) sees the new answer instead of a sticky refusal.
  */
 let gitAvailability;
 /**
  * Ensures git is available in the system. Memoised after the first successful
- * probe; {@link git} calls it, so callers that go through that wrapper do not
+ * probe. {@link git} calls it, so callers that go through that wrapper do not
  * need to.
  * @throws GitNotFoundError if git is not installed
  */
@@ -86,7 +86,7 @@ export async function git(args, cwd, options) {
     }
     // A read-only command's private-index scope overlays GIT_INDEX_FILE so
     // index refreshes never touch the primary checkout.
-    // Merged UNDER the caller's own env so an explicit override still wins.
+    // Merged under the caller's own env so an explicit override still wins.
     const readOnlyIndexEnv = readOnlyGitIndexEnv(cwd);
     if (options?.env !== undefined || readOnlyIndexEnv !== undefined) {
         execOptions.env = { ...readOnlyIndexEnv, ...options?.env };
@@ -101,7 +101,7 @@ export async function git(args, cwd, options) {
  * Splits a pathspec list into chunks whose joined byte length stays well under
  * the OS `ARG_MAX` limit, so a single batched `git` invocation over hundreds of
  * Mozilla-length paths cannot fail with `E2BIG`. The 96 KB budget is
- * deliberately conservative — even the smallest historical `ARG_MAX` (256 KB)
+ * conservative on purpose: even the smallest historical `ARG_MAX` (256 KB)
  * leaves room for the fixed git arguments plus the inherited environment.
  *
  * Chunk boundaries are output-neutral for every batched caller here: each
@@ -150,7 +150,7 @@ export async function configureGitPerformance(repoDir) {
  * rewrites LF to CRLF on checkout and back on staging. FireForge cannot
  * tolerate that: patch bodies are byte diffs of the working tree, and
  * `hashObjectBatch` deliberately delegates to git so `.gitattributes` and
- * `core.autocrlf` DO apply to the hashes `status` compares against. Under the
+ * `core.autocrlf` do apply to the hashes `status` compares against. Under the
  * global default the same tree hashes differently on Windows than everywhere
  * else, so exported patches and drift detection disagree across machines.
  * Setting it per-repository leaves the developer's global config alone.

package/dist/src/core/git-diff-new-file.d.ts

@@ -9,7 +9,7 @@ export type NewFileContent = {
  * Reads a new (untracked) file and classifies it for patch generation.
  *
  * A file is binary when git's NUL-byte heuristic says so
- * ({@link isBinaryFile}) OR when its bytes are not valid UTF-8 — see the
+ * ({@link isBinaryFile}) or when its bytes are not valid UTF-8. See the
  * module comment for why the second arm exists. Text files come back with
  * their exact decoded content so callers do not read the file twice.
  *
@@ -23,13 +23,13 @@ export declare function readNewFileContent(repoDir: string, filePath: string): P
  * as binary.
  *
  * `git diff --binary` only emits a `GIT binary patch` for a file git itself
- * classifies as binary, and git's classifier is the NUL heuristic — a
- * Latin-1 file passes it and comes out as a TEXT diff whose high bytes are
+ * classifies as binary, and git's classifier is the NUL heuristic, so a
+ * Latin-1 file passes it and comes out as a text diff whose high bytes are
  * then mangled by the UTF-8 decode every subprocess result goes through.
  * The `-diff` attribute is how git is told otherwise, and a throwaway
  * `core.attributesFile` naming just this path is the narrowest way to set it
  * without touching the tree's own `.gitattributes`. (An in-tree attribute
- * that explicitly sets `diff` for the path would still win; the tree's own
+ * that explicitly sets `diff` for the path would still win. The tree's own
  * attributes are its business.)
  *
  * @param filePath - File path (relative to repo root)

package/dist/src/core/git-diff-new-file.js

@@ -1,13 +1,13 @@
 // SPDX-License-Identifier: EUPL-1.2
 /**
- * Decides how a NEW (untracked) file travels inside a patch: as a synthesized
+ * Decides how a new (untracked) file travels inside a patch: as a synthesized
  * `+`-line text body, or as a `GIT binary patch`.
  *
  * The text body is built from a JavaScript string, and the `index` line next
  * to it comes from `git hash-object` over the file's real bytes. Those two
  * agree only when the bytes decode losslessly as UTF-8. A Latin-1
- * `.properties` or `.rc` file has no NUL byte — git's own binary heuristic
- * calls it text — but a UTF-8 decode turns every high byte into U+FFFD, so
+ * `.properties` or `.rc` file has no NUL byte, so git's own binary heuristic
+ * calls it text, but a UTF-8 decode turns every high byte into U+FFFD, so
  * the patch body and its blob hash disagree, `git apply` writes different
  * bytes than the tree holds, and every drift check flags the file forever.
  * A binary patch carries the bytes verbatim, so it is the faithful choice for
@@ -40,7 +40,7 @@ function decodeStrictUtf8(bytes) {
  * Reads a new (untracked) file and classifies it for patch generation.
  *
  * A file is binary when git's NUL-byte heuristic says so
- * ({@link isBinaryFile}) OR when its bytes are not valid UTF-8 — see the
+ * ({@link isBinaryFile}) or when its bytes are not valid UTF-8. See the
  * module comment for why the second arm exists. Text files come back with
  * their exact decoded content so callers do not read the file twice.
  *
@@ -67,7 +67,7 @@ export async function readNewFileContent(repoDir, filePath) {
  * Both escapes are applied in a single pass, keyed on the source character.
  * Escaping in two passes would re-escape the backslashes the first pass just
  * added, and a backslash that is part of the filename would have to be
- * escaped for the glob layer as well as the quoting layer — which a
+ * escaped for the glob layer as well as the quoting layer, which a
  * glob-only first pass cannot tell apart from one it emitted itself.
  *
  * @param filePath - File path (relative to repo root)
@@ -92,13 +92,13 @@ function toLiteralAttributePattern(filePath) {
  * as binary.
  *
  * `git diff --binary` only emits a `GIT binary patch` for a file git itself
- * classifies as binary, and git's classifier is the NUL heuristic — a
- * Latin-1 file passes it and comes out as a TEXT diff whose high bytes are
+ * classifies as binary, and git's classifier is the NUL heuristic, so a
+ * Latin-1 file passes it and comes out as a text diff whose high bytes are
  * then mangled by the UTF-8 decode every subprocess result goes through.
  * The `-diff` attribute is how git is told otherwise, and a throwaway
  * `core.attributesFile` naming just this path is the narrowest way to set it
  * without touching the tree's own `.gitattributes`. (An in-tree attribute
- * that explicitly sets `diff` for the path would still win; the tree's own
+ * that explicitly sets `diff` for the path would still win. The tree's own
  * attributes are its business.)
  *
  * @param filePath - File path (relative to repo root)

package/dist/src/core/git-diff.d.ts

@@ -4,7 +4,7 @@
  * `--binary` is load-bearing: without it git degrades a binary file's section
  * to the informational `Binary files a/x and b/x differ`, which carries none
  * of the bytes and cannot be replayed by `git apply`. It only expands the
- * BINARY section's index line to full hashes (text sections keep their
+ * binary section's index line to full hashes (text sections keep their
  * abbreviated form), so text output stays byte-identical.
  * @param repoDir - Repository directory
  * @param filePath - Path to the file (relative to repo)
@@ -34,9 +34,9 @@ export declare function generateFullFilePatch(repoDir: string, filePath: string)
 /**
  * Gets the diff for all modified files, including untracked (new) files.
  *
- * Tracked binary files round-trip through `git diff --binary`; untracked ones
+ * Tracked binary files round-trip through `git diff --binary`. Untracked ones
  * go through {@link generateBinaryFilePatch} below. Both arms must stay
- * binary-aware — see {@link getFileDiff} for why.
+ * binary-aware. See {@link getFileDiff} for why.
  * @param repoDir - Repository directory
  * @returns Diff content
  */
@@ -44,7 +44,7 @@ export declare function getAllDiff(repoDir: string): Promise<string>;
 /**
  * Builds a combined diff against HEAD for the provided files without touching
  * the real git index. Tracked files use `git diff --binary HEAD` (binary
- * sections included); untracked files use synthesized new-file diffs, or
+ * sections included). Untracked files use synthesized new-file diffs, or
  * {@link generateBinaryFilePatch} when the file is binary.
  *
  * Performance: the work is batched into a handful of `git` invocations (one