@hominis/fireforge 0.35.0 → 0.36.0

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

@@ -22,8 +22,9 @@
  */
 import { readdir } from 'node:fs/promises';
 import { dirname, join, relative, resolve } from 'node:path';
+import { applyEdits, modify, parse } from 'jsonc-parser';
 import { FurnaceError } from '../errors/furnace.js';
-import { pathExists, readJson, writeJson } from '../utils/fs.js';
+import { pathExists, readText, writeTextIfChanged } from '../utils/fs.js';
 import { info } from '../utils/logger.js';
 import { normalizePathSlashes } from '../utils/paths.js';
 import { getFurnacePaths } from './furnace-config.js';
@@ -89,9 +90,8 @@ function isManagedEntry(key, value, jsconfigDir, customDir) {
  * writing.
  *
  * The consumer owns the jsconfig file: a missing file is an error with
- * guidance rather than a silent scaffold, and JSONC (comments/trailing
- * commas) is unsupported for the managed file — `readJson` is a strict
- * JSON parser, so the error message says so explicitly.
+ * guidance rather than a silent scaffold. JSONC comments and trailing commas
+ * are preserved; Furnace edits only `compilerOptions.paths`.
  *
  * @param root - Project root directory
  * @param config - Loaded Furnace configuration (must carry `typecheckJsconfig`)
@@ -109,19 +109,31 @@ export async function syncFurnaceJsconfigPaths(root, config, options) {
             `"compilerOptions.paths" entries under ${CHROME_ELEMENTS_URL_PREFIX}*), ` +
             'or remove the setting.');
     }
+    const jsconfigText = await readText(jsconfigAbs);
+    const parseErrors = [];
     let jsconfig;
     try {
-        jsconfig = await readJson(jsconfigAbs);
+        jsconfig = parse(jsconfigText, parseErrors, {
+            allowTrailingComma: true,
+            disallowComments: false,
+        });
     }
     catch (error) {
-        throw new FurnaceError(`Could not parse ${jsconfigRel} as JSON: ${error instanceof Error ? error.message : String(error)}. ` +
-            'Furnace manages paths entries only in plain-JSON jsconfig files — JSONC comments ' +
-            'and trailing commas are not supported for the managed file.');
+        throw new FurnaceError(`Could not parse ${jsconfigRel} as JSONC: ${error instanceof Error ? error.message : String(error)}.`);
     }
+    if (parseErrors.length > 0 ||
+        typeof jsconfig !== 'object' ||
+        jsconfig === null ||
+        Array.isArray(jsconfig)) {
+        throw new FurnaceError(`Could not parse ${jsconfigRel} as JSONC: expected an object jsconfig file.`);
+    }
+    const jsconfigObject = jsconfig;
     const furnacePaths = getFurnacePaths(root);
     const desired = await computeDesiredChromePathEntries(config, furnacePaths.customDir, jsconfigAbs);
     const jsconfigDir = dirname(jsconfigAbs);
-    const currentPaths = { ...(jsconfig.compilerOptions?.paths ?? {}) };
+    const currentPaths = {
+        ...(jsconfigObject.compilerOptions?.paths ?? {}),
+    };
     const nextPaths = {};
     // Preserve every unmanaged entry verbatim; prune managed entries that are
     // no longer desired; update managed entries whose target moved.
@@ -156,14 +168,10 @@ export async function syncFurnaceJsconfigPaths(root, config, options) {
     result.changed = result.added.length > 0 || result.updated.length > 0 || result.pruned.length > 0;
     if (!result.changed || options?.dryRun === true)
         return result;
-    const nextJsconfig = {
-        ...jsconfig,
-        compilerOptions: {
-            ...(jsconfig.compilerOptions ?? {}),
-            paths: nextPaths,
-        },
-    };
-    await writeJson(jsconfigAbs, nextJsconfig);
+    const edits = modify(jsconfigText, ['compilerOptions', 'paths'], nextPaths, {
+        formattingOptions: { insertSpaces: true, tabSize: 2, eol: '\n' },
+    });
+    await writeTextIfChanged(jsconfigAbs, applyEdits(jsconfigText, edits));
     return result;
 }
 /**
@@ -188,4 +196,3 @@ export async function reportJsconfigPathsSync(root, config, dryRun) {
     info(`${dryRun ? '[dry-run] Would update' : 'Updated'} ${config.typecheckJsconfig} chrome-module paths: ` +
         `+${sync.added.length} added, ~${sync.updated.length} updated, -${sync.pruned.length} pruned`);
 }
-//# sourceMappingURL=furnace-jsconfig.js.map

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

@@ -20,4 +20,3 @@ export function resolveFurnaceMarkerComment(forgeConfig) {
         return forgeConfig.binaryName.toUpperCase();
     return undefined;
 }
-//# sourceMappingURL=furnace-marker.js.map

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

@@ -252,4 +252,3 @@ export function __resetFurnaceOperationStateForTests() {
     nextOperationToken = 1;
     signalRollbackInFlight = false;
 }
-//# sourceMappingURL=furnace-operation.js.map

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

@@ -126,4 +126,3 @@ export async function refreshOverrideFile(engineDir, overridePath, engineRelPath
     }
     return { fileName, status: 'merged' };
 }
-//# sourceMappingURL=furnace-refresh.js.map

package/dist/src/core/furnace-registration-ast.d.ts

@@ -2,6 +2,20 @@
  * AST-based custom element registration updates for customElements.js.
  * Removal logic is in furnace-registration-remove.ts.
  */
+/**
+ * Returns true when `content` already contains a registration for `tagName`.
+ *
+ * Tolerates trailing line comments (e.g. a project marker like `// MYBROWSER:`)
+ * that an operator may have appended to entries written by a previous apply.
+ * Without this, a re-apply would insert a duplicate entry, and the second
+ * `setElementCreationCallback` at window-load would throw `NotSupportedError`.
+ *
+ * Matches any of:
+ *   1. `setElementCreationCallback("tag"` / `setElementCreationCallback('tag'`
+ *   2. Single-line array entry: `["tag", "..."]` — column 0 only, comments allowed after
+ *   3. Multi-line array entry: `"tag",` on its own line, optional trailing `//` comment
+ */
+export declare function isTagAlreadyRegistered(content: string, tagName: string): boolean;
 /**
  * Options that shape the lines `addCustomElementRegistration` writes into
  * `customElements.js`. Kept optional so existing call sites keep working.

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

@@ -26,7 +26,7 @@ import { validateRegistrationPlacement, validateTagName } from './furnace-regist
  *   2. Single-line array entry: `["tag", "..."]` — column 0 only, comments allowed after
  *   3. Multi-line array entry: `"tag",` on its own line, optional trailing `//` comment
  */
-function isTagAlreadyRegistered(content, tagName) {
+export function isTagAlreadyRegistered(content, tagName) {
     const escaped = escapeRegex(tagName);
     if (content.includes(`setElementCreationCallback("${tagName}"`) ||
         content.includes(`setElementCreationCallback('${tagName}'`)) {
@@ -403,4 +403,3 @@ export async function validateCustomElementRegistration(engineDir, tagName, modu
         addRegistrationRegexFallback(content, tagName, modulePath, isESModule);
     }
 }
-//# sourceMappingURL=furnace-registration-ast.js.map

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

@@ -220,4 +220,3 @@ export async function removeCustomElementRegistration(engineDir, tagName) {
         await writeText(filePath, next);
     }
 }
-//# sourceMappingURL=furnace-registration-remove.js.map

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

@@ -4,7 +4,7 @@
  * Used after both AST and legacy code paths to avoid duplicating logic.
  */
 import { FurnaceError } from '../errors/furnace.js';
-import { stripJsComments } from '../utils/regex.js';
+import { escapeRegex, stripJsComments } from '../utils/regex.js';
 /**
  * Regex for valid custom element tag names. A valid name is lowercase, starts
  * with a letter, and contains one or more hyphen-separated groups where each
@@ -88,7 +88,3 @@ function isTagInArrayConsumedInsideDOMContentLoaded(content, domContentLoadedIdx
     }
     return false;
 }
-function escapeRegex(value) {
-    return value.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
-}
-//# sourceMappingURL=furnace-registration-validate.js.map

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

@@ -324,4 +324,3 @@ export async function validateJarMnInsertionForFiles(engineDir, tagName, files)
         throw new FurnaceError('Could not find a content/global/ section in jar.mn for element entries. The file may be malformed.', tagName);
     }
 }
-//# sourceMappingURL=furnace-registration.js.map

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

@@ -134,4 +134,3 @@ export async function restoreRollbackJournalOrThrow(journal, context) {
         throw new FurnaceError(`${context}; automatic rollback failed: ${message}`);
     }
 }
-//# sourceMappingURL=furnace-rollback.js.map

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

@@ -237,4 +237,3 @@ export async function isComponentInEngine(engineDir, tagName) {
     const componentDir = join(engineDir, WIDGETS_DIR, tagName);
     return pathExists(componentDir);
 }
-//# sourceMappingURL=furnace-scanner.js.map

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

@@ -55,4 +55,3 @@ export async function warnIfFurnaceStale(projectRoot) {
         verbose('Furnace staleness check skipped due to an error.');
     }
 }
-//# sourceMappingURL=furnace-staleness.js.map

package/dist/src/core/furnace-state-persist.d.ts

@@ -0,0 +1,72 @@
+/**
+ * Single-component furnace state persistence.
+ *
+ * There are exactly two sanctioned ways checksums land in
+ * furnace-state.json:
+ *
+ *  1. The BATCH path inside `applyAllComponents` (persistState: true),
+ *     which replaces `appliedChecksums` wholesale — correct only when the
+ *     run covered every component.
+ *  2. The per-component MERGE in this module, which rewrites only the
+ *     `<type>/<name>/…` keys of the component that was applied.
+ *
+ * Every targeted (named) apply/deploy MUST use path 2 with
+ * `persistState: false`. Routing a named run through the batch path wipes
+ * every other component's checksum state: the batch loops filter to the
+ * named component, so the wholesale replace persists a state file
+ * containing only that component. Downstream, `diffDeletedFiles` and
+ * `findOrphanedEngineFiles` both key on `appliedChecksums`, so the wiped
+ * components' stale engine files become undetectable by apply AND by
+ * `furnace validate` (2026-07-05 review, finding F1 — `furnace apply
+ * <name>` had exactly this bug while `furnace deploy <name>` documented
+ * and avoided it).
+ */
+import { type applyAllComponents } from './furnace-apply.js';
+import { type getFurnacePaths } from './furnace-config.js';
+type ApplyAllResult = Awaited<ReturnType<typeof applyAllComponents>>;
+/**
+ * Counts applied entries that carry at least one BLOCKING step error
+ * (advisory step errors are warnings and never fail a run).
+ */
+export declare function getStepFailureCount(result: ApplyAllResult): number;
+/**
+ * Decides whether a single-component apply/deploy completed cleanly enough
+ * to persist its checksums into furnace-state.json.
+ *
+ * Named runs are atomic: if any apply step fails, the rollback journal
+ * restores the engine to its pre-run state and this helper returns `false`
+ * so state is not touched. The conditions must stay in lock-step with the
+ * rollback trigger in `applyAllComponents` — both read step errors, so a
+ * future refactor cannot drift them apart and accidentally persist partial
+ * state.
+ */
+export declare function shouldPersistSingleComponentState(result: ApplyAllResult, isDryRun: boolean): boolean;
+/**
+ * Validates and narrows the applied entry a named run should persist.
+ *
+ * Guards against future refactors that might reorder or misroute the
+ * applied[] array: a named run persists state under a single component
+ * name, so the first applied entry MUST be that component. Persisting a
+ * different component's checksums would cause the next status/apply run to
+ * mis-report health for both components involved.
+ *
+ * @param commandLabel - Human label for error messages ("Deploy", "Apply")
+ */
+export declare function getPersistableAppliedEntry(commandLabel: string, name: string, appliedEntry: ApplyAllResult['applied'][number] | undefined): {
+    name: string;
+    type: 'override' | 'custom';
+};
+/**
+ * Persists checksum state for a successfully applied named component by
+ * MERGING its `<type>/<name>/…` keys into the existing state — never
+ * replacing the whole map.
+ *
+ * @param projectRoot - Root directory of the project
+ * @param appliedEntry - Applied component descriptor
+ * @param furnacePaths - Resolved Furnace workspace paths
+ */
+export declare function persistSingleComponentState(projectRoot: string, appliedEntry: {
+    name: string;
+    type: 'override' | 'custom';
+}, furnacePaths: ReturnType<typeof getFurnacePaths>): Promise<void>;
+export {};

package/dist/src/core/furnace-state-persist.js

@@ -0,0 +1,118 @@
+// SPDX-License-Identifier: EUPL-1.2
+/**
+ * Single-component furnace state persistence.
+ *
+ * There are exactly two sanctioned ways checksums land in
+ * furnace-state.json:
+ *
+ *  1. The BATCH path inside `applyAllComponents` (persistState: true),
+ *     which replaces `appliedChecksums` wholesale — correct only when the
+ *     run covered every component.
+ *  2. The per-component MERGE in this module, which rewrites only the
+ *     `<type>/<name>/…` keys of the component that was applied.
+ *
+ * Every targeted (named) apply/deploy MUST use path 2 with
+ * `persistState: false`. Routing a named run through the batch path wipes
+ * every other component's checksum state: the batch loops filter to the
+ * named component, so the wholesale replace persists a state file
+ * containing only that component. Downstream, `diffDeletedFiles` and
+ * `findOrphanedEngineFiles` both key on `appliedChecksums`, so the wiped
+ * components' stale engine files become undetectable by apply AND by
+ * `furnace validate` (2026-07-05 review, finding F1 — `furnace apply
+ * <name>` had exactly this bug while `furnace deploy <name>` documented
+ * and avoided it).
+ */
+import { join } from 'node:path';
+import { FurnaceError } from '../errors/furnace.js';
+import { computeComponentChecksums, prefixChecksums, } from './furnace-apply.js';
+import { updateFurnaceState } from './furnace-config.js';
+import { countEntriesWithBlockingStepErrors } from './furnace-step-errors.js';
+/**
+ * Counts applied entries that carry at least one BLOCKING step error
+ * (advisory step errors are warnings and never fail a run).
+ */
+export function getStepFailureCount(result) {
+    return countEntriesWithBlockingStepErrors(result.applied);
+}
+/**
+ * Decides whether a single-component apply/deploy completed cleanly enough
+ * to persist its checksums into furnace-state.json.
+ *
+ * Named runs are atomic: if any apply step fails, the rollback journal
+ * restores the engine to its pre-run state and this helper returns `false`
+ * so state is not touched. The conditions must stay in lock-step with the
+ * rollback trigger in `applyAllComponents` — both read step errors, so a
+ * future refactor cannot drift them apart and accidentally persist partial
+ * state.
+ */
+export function shouldPersistSingleComponentState(result, isDryRun) {
+    if (isDryRun)
+        return false;
+    if (result.errors.length > 0)
+        return false;
+    if (getStepFailureCount(result) > 0)
+        return false;
+    return result.applied.length > 0;
+}
+/**
+ * Validates and narrows the applied entry a named run should persist.
+ *
+ * Guards against future refactors that might reorder or misroute the
+ * applied[] array: a named run persists state under a single component
+ * name, so the first applied entry MUST be that component. Persisting a
+ * different component's checksums would cause the next status/apply run to
+ * mis-report health for both components involved.
+ *
+ * @param commandLabel - Human label for error messages ("Deploy", "Apply")
+ */
+export function getPersistableAppliedEntry(commandLabel, name, appliedEntry) {
+    if (!appliedEntry) {
+        throw new FurnaceError(`${commandLabel} for "${name}" finished without producing an applied component entry; ` +
+            `furnace state was not modified. Run "fireforge doctor --repair-furnace" to ` +
+            `reconcile state, then retry. If this persists, file a bug with the ` +
+            `output of "fireforge doctor".`);
+    }
+    if (appliedEntry.type !== 'override' && appliedEntry.type !== 'custom') {
+        throw new FurnaceError(`${commandLabel} for "${name}" returned an unsupported component type "${appliedEntry.type}"; ` +
+            `furnace state was not modified. Run "fireforge doctor --repair-furnace" to reconcile, ` +
+            `then verify the component with "fireforge furnace validate" before retrying.`);
+    }
+    if (appliedEntry.name !== name) {
+        throw new FurnaceError(`${commandLabel} for "${name}" returned an applied entry for a different component ` +
+            `("${appliedEntry.name}"); refusing to persist mismatched state. ` +
+            `Run "fireforge doctor --repair-furnace" to reconcile, then retry.`);
+    }
+    return {
+        name: appliedEntry.name,
+        type: appliedEntry.type,
+    };
+}
+/**
+ * Persists checksum state for a successfully applied named component by
+ * MERGING its `<type>/<name>/…` keys into the existing state — never
+ * replacing the whole map.
+ *
+ * @param projectRoot - Root directory of the project
+ * @param appliedEntry - Applied component descriptor
+ * @param furnacePaths - Resolved Furnace workspace paths
+ */
+export async function persistSingleComponentState(projectRoot, appliedEntry, furnacePaths) {
+    const componentDir = appliedEntry.type === 'override'
+        ? join(furnacePaths.overridesDir, appliedEntry.name)
+        : join(furnacePaths.customDir, appliedEntry.name);
+    const checksums = await computeComponentChecksums(componentDir);
+    const prefixed = prefixChecksums(checksums, appliedEntry.type, appliedEntry.name);
+    const componentPrefix = `${appliedEntry.type}/${appliedEntry.name}/`;
+    await updateFurnaceState(projectRoot, (current) => ({
+        ...current,
+        appliedChecksums: {
+            ...Object.fromEntries(Object.entries(current.appliedChecksums ?? {}).filter(([key]) => !key.startsWith(componentPrefix))),
+            ...prefixed,
+        },
+        engineChecksums: {
+            ...Object.fromEntries(Object.entries(current.engineChecksums ?? {}).filter(([key]) => !key.startsWith(componentPrefix))),
+            ...prefixed,
+        },
+        lastApply: new Date().toISOString(),
+    }));
+}

package/dist/src/core/furnace-step-errors.d.ts

@@ -0,0 +1,23 @@
+/**
+ * Shared predicates over {@link StepError} lists.
+ *
+ * Step errors come in two severities: BLOCKING (the default — the apply is
+ * considered failed, triggers rollback and a non-zero exit) and ADVISORY
+ * (`advisory: true` — reported as a warning, never blocks; used by the
+ * `.ftl` helpers whose contract is graceful degradation). Every gate that
+ * decides rollback/failure must count only blocking errors; every reporter
+ * should still surface advisory ones. This module is a leaf (types-only
+ * imports) so both `furnace-apply.ts` and its callers can share the
+ * predicates without import cycles.
+ */
+import type { StepError } from '../types/furnace.js';
+/** Narrow shape shared by applied-component entries carrying step errors. */
+export interface HasStepErrors {
+    stepErrors?: StepError[];
+}
+/** Returns only the blocking (non-advisory) step errors. */
+export declare function blockingStepErrors(stepErrors: StepError[] | undefined): StepError[];
+/** True when the entry carries at least one blocking step error. */
+export declare function hasBlockingStepErrors(entry: HasStepErrors): boolean;
+/** Counts applied entries that carry at least one blocking step error. */
+export declare function countEntriesWithBlockingStepErrors(entries: readonly HasStepErrors[]): number;

package/dist/src/core/furnace-step-errors.js

@@ -0,0 +1,25 @@
+// SPDX-License-Identifier: EUPL-1.2
+/**
+ * Shared predicates over {@link StepError} lists.
+ *
+ * Step errors come in two severities: BLOCKING (the default — the apply is
+ * considered failed, triggers rollback and a non-zero exit) and ADVISORY
+ * (`advisory: true` — reported as a warning, never blocks; used by the
+ * `.ftl` helpers whose contract is graceful degradation). Every gate that
+ * decides rollback/failure must count only blocking errors; every reporter
+ * should still surface advisory ones. This module is a leaf (types-only
+ * imports) so both `furnace-apply.ts` and its callers can share the
+ * predicates without import cycles.
+ */
+/** Returns only the blocking (non-advisory) step errors. */
+export function blockingStepErrors(stepErrors) {
+    return (stepErrors ?? []).filter((e) => e.advisory !== true);
+}
+/** True when the entry carries at least one blocking step error. */
+export function hasBlockingStepErrors(entry) {
+    return blockingStepErrors(entry.stepErrors).length > 0;
+}
+/** Counts applied entries that carry at least one blocking step error. */
+export function countEntriesWithBlockingStepErrors(entries) {
+    return entries.filter((entry) => hasBlockingStepErrors(entry)).length;
+}

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

@@ -184,4 +184,3 @@ export async function cleanStories(engineDir) {
     await removeDir(storiesDir);
     return count;
 }
-//# sourceMappingURL=furnace-stories.js.map

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

@@ -55,4 +55,3 @@ export async function validateAccessibility(componentDir, tagName, customConfig)
     }
     return issues;
 }
-//# sourceMappingURL=furnace-validate-accessibility.js.map

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

@@ -4,4 +4,3 @@ export { validateAccessibility } from './furnace-validate-accessibility.js';
 export { validateCompatibility } from './furnace-validate-compatibility.js';
 export { checkRegistrationConsistency, validateJarMnEntries, validateRegistrationPatterns, validateTokenLink, } from './furnace-validate-registration.js';
 export { validateStructure } from './furnace-validate-structure.js';
-//# sourceMappingURL=furnace-validate-checks.js.map

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

@@ -149,4 +149,3 @@ export async function validateCompatibility(componentDir, tagName, type, config,
     }
     return issues;
 }
-//# sourceMappingURL=furnace-validate-compatibility.js.map

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

@@ -434,4 +434,3 @@ export async function findOrphanedEngineFiles(root, config, tagName, state, ftlD
     }
     return issues;
 }
-//# sourceMappingURL=furnace-validate-helpers.js.map

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

@@ -5,12 +5,13 @@ import { join } from 'node:path';
 import { toError } from '../utils/errors.js';
 import { pathExists, readText } from '../utils/fs.js';
 import { warn } from '../utils/logger.js';
-import { stripJsComments } from '../utils/regex.js';
+import { escapeRegex, stripJsComments } from '../utils/regex.js';
 import { getProjectPaths, loadConfig } from './config.js';
 import { getFurnacePaths } from './furnace-config.js';
 import { CUSTOM_ELEMENTS_JS, FTL_DIR, JAR_MN } from './furnace-constants.js';
 import { expandCssFragments, listFragmentIncludes } from './furnace-css-fragments.js';
 import { findStaleJarMnEntries } from './furnace-registration.js';
+import { isTagAlreadyRegistered } from './furnace-registration-ast.js';
 import { isTagInCorrectCustomElementsPlacement } from './furnace-registration-validate.js';
 import { getTokensCssPath } from './token-manager.js';
 /**
@@ -47,9 +48,6 @@ export async function validateRegistrationPatterns(root, config) {
     }
     return issues;
 }
-function escapeRegex(value) {
-    return value.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
-}
 /**
  * Checks registration consistency for a single custom component.
  *
@@ -160,8 +158,11 @@ export async function checkRegistrationConsistency(root, name, config, ftlDir) {
     const cePath = join(engineDir, CUSTOM_ELEMENTS_JS);
     if (await pathExists(cePath)) {
         const ceContent = await readText(cePath);
-        status.customElementsPresent =
-            ceContent.includes(`"${name}"`) || ceContent.includes(`'${name}'`);
+        // 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.
+        status.customElementsPresent = isTagAlreadyRegistered(ceContent, name);
         if (status.customElementsPresent) {
             status.customElementsCorrectBlock = isTagInCorrectCustomElementsPlacement(ceContent, name, true);
         }
@@ -396,4 +397,3 @@ export async function runPostApplyConsistencyChecks(root, config, result, ftlDir
         }
     }
 }
-//# sourceMappingURL=furnace-validate-registration.js.map

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

@@ -1,4 +1,12 @@
 import type { ComponentType, CustomComponentConfig, ValidationIssue } from '../types/furnace.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
+ * agree on what "conflicted" means so a file that validate flags can never
+ * slip through sync into the engine.
+ */
+export declare function containsMergeConflictMarkers(content: string): boolean;
 /**
  * Validates the file structure of a component directory.
  * Checks for required files and naming conventions.

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

@@ -2,6 +2,16 @@
 import { readdir } from 'node:fs/promises';
 import { join } from 'node:path';
 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
+ * agree on what "conflicted" means so a file that validate flags can never
+ * slip through sync into the engine.
+ */
+export function containsMergeConflictMarkers(content) {
+    return /^<{7}\s/m.test(content) || /^>{7}\s/m.test(content) || /^={7}$/m.test(content);
+}
 /**
  * Validates the file structure of a component directory.
  * Checks for required files and naming conventions.
@@ -65,7 +75,7 @@ export async function validateStructure(componentDir, tagName, type, customConfi
             !entry.name.endsWith('.ftl'))
             continue;
         const content = await readText(join(componentDir, entry.name));
-        if (/^<{7}\s/m.test(content) || /^>{7}\s/m.test(content) || /^={7}$/m.test(content)) {
+        if (containsMergeConflictMarkers(content)) {
             issues.push({
                 component: tagName,
                 severity: 'error',
@@ -109,4 +119,3 @@ export async function validateStructure(componentDir, tagName, type, customConfi
     }
     return issues;
 }
-//# sourceMappingURL=furnace-validate-structure.js.map

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

@@ -298,4 +298,3 @@ async function findOrphanXpcshellScaffolds(root, config) {
     }
     return issues;
 }
-//# sourceMappingURL=furnace-validate.js.map

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

@@ -14,9 +14,12 @@
  * copied from `forgeConfig.firefox.version`. Any string mismatch is worth
  * surfacing — even "140.0" vs "140.9.0esr" is a real drift signal.
  *
- * The result is advisory: apply/deploy emit warnings but do not fail, and
- * status reports drift alongside the component overview. Nothing here
- * should be wired into a blocking code path without an operator prompt.
+ * 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 —
+ * an earlier version claimed the result was advisory, which invited
+ * re-breaking the gate.
  */
 import type { FurnaceConfig } from '../types/furnace.js';
 /** Severity of the version drift between an override's base and the current Firefox version. */

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

@@ -15,9 +15,12 @@
  * copied from `forgeConfig.firefox.version`. Any string mismatch is worth
  * surfacing — even "140.0" vs "140.9.0esr" is a real drift signal.
  *
- * The result is advisory: apply/deploy emit warnings but do not fail, and
- * status reports drift alongside the component overview. Nothing here
- * should be wired into a blocking code path without an operator prompt.
+ * 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 —
+ * an earlier version claimed the result was advisory, which invited
+ * re-breaking the gate.
  */
 /**
  * Parses a version string into its major, minor, and patch numeric
@@ -98,4 +101,3 @@ export function formatOverrideBaseVersionDriftError(entries) {
         'update baseVersion in furnace.json to acknowledge the new baseline, ' +
         'or pass --force to proceed despite the drift.');
 }
-//# sourceMappingURL=furnace-version-drift.js.map

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

@@ -117,4 +117,3 @@ export async function configureGitPerformance(repoDir) {
     await git(['config', 'core.fsmonitor', 'false'], repoDir);
     await git(['config', 'feature.manyFiles', 'true'], repoDir);
 }
-//# sourceMappingURL=git-base.js.map

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

@@ -476,4 +476,3 @@ export async function generateBinaryFilePatch(repoDir, filePath) {
         }
     });
 }
-//# sourceMappingURL=git-diff.js.map

package/dist/src/core/git-file-ops.js

@@ -228,4 +228,3 @@ export async function isBinaryFile(repoDir, filePath) {
         return false;
     }
 }
-//# sourceMappingURL=git-file-ops.js.map

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

@@ -12,9 +12,22 @@ export declare function parsePorcelainStatus(output: string): GitStatusEntry[];
  * @returns Parsed git status entries
  */
 export declare function getWorkingTreeStatus(repoDir: string): Promise<GitStatusEntry[]>;
+/**
+ * Resolves the per-directory expansion cap, honoring the same
+ * FIREFORGE_MAX_UNTRACKED_FILES override the status command documents.
+ */
+export declare function resolveMaxUntrackedFilesPerDir(): number;
 /**
  * Expands collapsed untracked directory entries into individual file entries.
  * Git status may report "?? dir/" instead of listing each file underneath.
+ *
+ * Expansion is capped per directory (FIREFORGE_MAX_UNTRACKED_FILES, default
+ * 5000) with a warning on overflow. The cap used to exist only in the
+ * status command's private expander; this shared one — used by reset,
+ * discard, verify, lint, export-all — was unbounded, so e.g. `reset
+ * --dry-run` after an interrupted download (unborn HEAD, the entire ~300k
+ * file tree untracked) enumerated and printed every file.
+ *
  * @param repoDir - Repository directory
  * @param entries - Parsed status entries
  * @returns Status entries with untracked directories expanded to individual files