@hominis/fireforge 0.54.0 → 0.60.0

package/dist/src/commands/furnace/create-browser-test.js

@@ -1,179 +0,0 @@
-// SPDX-License-Identifier: EUPL-1.2
-/**
- * Browser-chrome test scaffolding for `furnace create --with-tests`,
- * including the `--test-dir` redirect and collision safety (existing
- * manifests are appended to, and head.js and test implementations are never
- * overwritten). Split out of `create.ts` to keep that command file within
- * the per-file line budget.
- */
-import { join } from 'node:path';
-import { BROWSER_TEST_SCAFFOLD_ROOT, resolveBrowserChromeTestDir, } from '../../core/furnace-constants.js';
-import { recordCreatedDir, snapshotFile, } from '../../core/furnace-rollback.js';
-import { getLicenseHeader } from '../../core/license-headers.js';
-import { registerTestManifest } from '../../core/moz-manifest-register.js';
-import { InvalidArgumentError } from '../../errors/base.js';
-import { toError } from '../../utils/errors.js';
-import { ensureDir, pathExists, readText, writeText } from '../../utils/fs.js';
-import { info, success, warn } from '../../utils/logger.js';
-import { stripEnginePrefix } from '../../utils/paths.js';
-import { browserTestFileName, deriveTestStem } from './test-file-name.js';
-/**
- * Validates the `--test-dir` option against the resolved test style before
- * any writes. Mochikit lives in the upstream toolkit/content/tests/widgets
- * tree, so a redirect makes no sense there.
- */
-export function resolveValidatedTestDir(rawTestDir, testStyle) {
-    if (rawTestDir === undefined)
-        return undefined;
-    if (testStyle === 'none') {
-        throw new InvalidArgumentError('--test-dir requires --with-tests / --test-style.', 'testDir');
-    }
-    if (testStyle === 'mochikit') {
-        throw new InvalidArgumentError('--test-dir is not supported with --test-style=mochikit (the mochikit harness lives in toolkit/content/tests/widgets).', 'testDir');
-    }
-    return resolveTestDirOverride(rawTestDir);
-}
-/**
- * Scaffolds browser mochitest files for a newly created custom component.
- * @param componentName - Custom element tag name
- * @param license - Project license used for generated headers
- * @param forgeConfig - Project config fields needed for test naming
- * @param paths - Resolved project paths used to place test files
- * @param journal - Optional rollback journal that snapshots files before writes
- * @returns Relative test filenames created or updated for the component
- */
-/**
- * Normalizes and validates a `--test-dir` override: engine-relative,
- * under `browser/base/content/test/` (so manifest registration keeps
- * working). Returns the normalized engine-relative directory.
- */
-export function resolveTestDirOverride(raw) {
-    const normalized = stripEnginePrefix(raw).replace(/\/+$/, '');
-    if (!normalized.startsWith(BROWSER_TEST_SCAFFOLD_ROOT) ||
-        normalized === BROWSER_TEST_SCAFFOLD_ROOT.slice(0, -1)) {
-        throw new InvalidArgumentError(`--test-dir must be an engine-relative directory under ${BROWSER_TEST_SCAFFOLD_ROOT} (got "${raw}").`, 'testDir');
-    }
-    return normalized;
-}
-// Exported for direct unit testing of the --test-dir / collision-safety
-// behaviour (the full create command needs a furnace project fixture).
-/**
- * Writes the browser-mochitest scaffold for a component: the test file, its
- * `browser.toml` manifest entry, and the parent `moz.build` registration.
- *
- * Every write is recorded in `journal` when one is supplied, so a failure
- * partway through is rolled back rather than leaving a half-registered test
- * the harness will try to run.
- */
-export async function scaffoldTestFiles(componentName, license, forgeConfig, paths, journal, testDirOverride) {
-    const binaryName = forgeConfig.binaryName;
-    const underscored = deriveTestStem(componentName, binaryName);
-    const testFileName = browserTestFileName(componentName, binaryName);
-    // --test-dir redirects the scaffold: the hardcoded
-    // `.../test/<binaryName>/` target can collide with a test suite owned by a
-    // different patch. The manifest-registration name is the path below
-    // browser/base/content/test/ (nested manifests are supported).
-    const testDirRel = resolveBrowserChromeTestDir(binaryName, testDirOverride);
-    const testDirName = testDirRel.slice(BROWSER_TEST_SCAFFOLD_ROOT.length);
-    const testDir = join(paths.engine, testDirRel);
-    if (journal && !(await pathExists(testDir))) {
-        recordCreatedDir(journal, testDir);
-    }
-    await ensureDir(testDir);
-    const jsHeader = getLicenseHeader(license, 'js');
-    const hashHeader = getLicenseHeader(license, 'hash');
-    const testFiles = [];
-    // browser.toml: create if missing, append entry if existing.
-    const tomlPath = join(testDir, 'browser.toml');
-    if (await pathExists(tomlPath)) {
-        // Defensive guard: only append if the entry is not already present.
-        // With a fresh journal per create, the same test file name cannot be
-        // appended twice in a single run, but retaining the check protects
-        // against accidental re-entrance or a future refactor that reuses the
-        // helper with a stale test directory.
-        const existingToml = await readText(tomlPath);
-        if (!existingToml.includes(`["${testFileName}"]`)) {
-            if (journal)
-                await snapshotFile(journal, tomlPath);
-            await writeText(tomlPath, existingToml.trimEnd() + `\n\n["${testFileName}"]\n`);
-            info(`Appended ["${testFileName}"] to the existing ${testDirRel}/browser.toml — the manifest ` +
-                'is shared; existing entries and support-files were left untouched.');
-        }
-    }
-    else {
-        if (journal)
-            await snapshotFile(journal, tomlPath);
-        const browserToml = `${hashHeader}
-
-[DEFAULT]
-support-files = ["head.js"]
-
-["${testFileName}"]
-`;
-        await writeText(tomlPath, browserToml);
-    }
-    testFiles.push('browser.toml');
-    // head.js: only create if it doesn't exist (shared across components).
-    const headPath = join(testDir, 'head.js');
-    if (!(await pathExists(headPath))) {
-        if (journal)
-            await snapshotFile(journal, headPath);
-        const headJs = `${jsHeader}
-
-"use strict";
-
-/**
- * Wait for a custom element to be defined.
- * @param {string} tag - Custom element tag name
- * @returns {Promise<CustomElementConstructor>}
- */
-async function waitForElement(tag) {
-  document.createElement(tag);
-  return customElements.whenDefined(tag);
-}
-`;
-        await writeText(headPath, headJs);
-        testFiles.push('head.js');
-    }
-    // browser_{binaryName}_{stripped}.js
-    const testJs = `${jsHeader}
-
-"use strict";
-
-add_task(async function test_${underscored}_defined() {
-  const ctor = await waitForElement("${componentName}");
-  Assert.ok(ctor, "${componentName} custom element should be defined");
-  Assert.equal(typeof ctor, "function", "Constructor should be a function");
-});
-`;
-    const testFilePath = join(testDir, testFileName);
-    if (await pathExists(testFilePath)) {
-        // Never clobber an existing test implementation (it may be owned by a
-        // different patch). The manifest entry above is idempotent, so the
-        // existing file simply stays authoritative.
-        warn(`${testDirRel}/${testFileName} already exists — keeping the existing file. ` +
-            'Pass --test-dir to scaffold into a different directory if you wanted a fresh test.');
-    }
-    else {
-        if (journal)
-            await snapshotFile(journal, testFilePath);
-        await writeText(testFilePath, testJs);
-        testFiles.push(testFileName);
-    }
-    // Register in moz.build. The registration helper edits browser/base/moz.build,
-    // so snapshot it first when a journal is supplied. The existing warn-and-continue
-    // contract is preserved so a missing/unparseable moz.build never trips rollback.
-    try {
-        const mozBuildPath = join(paths.engine, 'browser/base/moz.build');
-        if (journal)
-            await snapshotFile(journal, mozBuildPath);
-        const registerResult = await registerTestManifest(paths.engine, testDirName);
-        if (!registerResult.skipped) {
-            success(`Registered test manifest in ${registerResult.manifest}`);
-        }
-    }
-    catch (error) {
-        warn(`Could not register test manifest in moz.build — ${toError(error).message}. Register manually with "fireforge register".`);
-    }
-    return testFiles;
-}

package/dist/src/commands/furnace/create-dry-run.d.ts

@@ -1,49 +0,0 @@
-import type { ResolvedTestStyle } from '../../types/furnace.js';
-export interface DryRunPlanInput {
-    componentName: string;
-    localized: boolean;
-    register: boolean;
-    composes: string[] | undefined;
-    stockAdditions?: string[];
-    /**
-     * Feature-scoped Fluent bundle the component participates in (the same
-     * value that will be written to `furnace.json`'s `sharedFtl`). When set,
-     * the component's own `.ftl` is not scaffolded and the plan preview
-     * reflects that. Omit the key for the default per-component scaffold.
-     */
-    sharedFtl?: string;
-    testStyle: ResolvedTestStyle;
-    description: string;
-    binaryName: string;
-    /**
-     * Resolved `--test-dir` override (engine-relative, already validated by
-     * `resolveValidatedTestDir`). Omit for the default `<binaryName>`-derived
-     * scaffold directory. The formatters must receive the same value the
-     * scaffolders get; recomputing the default from `binaryName` would name a
-     * directory the real run never writes to.
-     */
-    testDir?: string;
-}
-/**
- * Builds the success-note body printed after `furnace create` has applied
- * its mutations. Lives beside the dry-run formatter so the two renderings
- * stay in lock-step when the scaffolded layout changes.
- */
-export declare function formatSuccessNote(args: {
-    componentName: string;
-    files: string[];
-    testFiles: string[];
-    testStyle: ResolvedTestStyle;
-    binaryName: string;
-    /** Resolved `--test-dir` override. See {@link DryRunPlanInput.testDir}. */
-    testDir?: string | undefined;
-}): string;
-/**
- * Builds the planned component + test file list for a dry-run preview.
- *
- * Mirrors the order `writeComponentFiles` and the test-style scaffolders
- * would produce so the dry-run output matches what a real run prints on
- * success. The component directory path is rendered relative to
- * `components/custom/` to match the wording of the real success note.
- */
-export declare function formatDryRunPlan(args: DryRunPlanInput): string;

package/dist/src/commands/furnace/create-dry-run.js

@@ -1,107 +0,0 @@
-// SPDX-License-Identifier: EUPL-1.2
-/*
- * Dry-run plan formatter for `furnace create`.
- *
- * Lives outside `create.ts` so the authoring command stays under the
- * per-file LOC budget. The formatter is pure (all inputs are already
- * resolved by the command's validation phase), so it can be exercised
- * independently of the mutation plumbing.
- */
-import { BROWSER_TEST_SCAFFOLD_ROOT, resolveBrowserChromeTestDir, resolveXpcshellTestDir, } from '../../core/furnace-constants.js';
-import { deriveTestStem } from './test-file-name.js';
-/**
- * Builds the test-section fragment of the dry-run plan for a given
- * harness choice. Kept separate from the top-level formatter so the
- * switch over `testStyle` does not push the caller over the per-function
- * complexity budget.
- */
-function formatTestSection(args) {
-    const { testStyle, componentName, binaryName, testDir } = args;
-    if (testStyle === 'none')
-        return '';
-    const underscored = deriveTestStem(componentName, binaryName);
-    if (testStyle === 'browser-chrome') {
-        // Same resolver as scaffoldTestFiles: the registration name is the
-        // path below browser/base/content/test/, which under --test-dir is
-        // not the binary name.
-        const testDirRel = resolveBrowserChromeTestDir(binaryName, testDir);
-        const manifestName = testDirRel.slice(BROWSER_TEST_SCAFFOLD_ROOT.length);
-        return (`\n\nWould create test files in engine/${testDirRel}/:\n` +
-            `  browser.toml\n  head.js\n  browser_${binaryName}_${underscored}.js` +
-            `\n\nWould register ${manifestName}/browser.toml in engine/browser/base/moz.build`);
-    }
-    if (testStyle === 'xpcshell') {
-        const testDirRel = resolveXpcshellTestDir(binaryName, componentName, testDir);
-        return `\n\nWould create xpcshell test files in engine/${testDirRel}/`;
-    }
-    // testStyle === 'mochikit' (last remaining branch in ResolvedTestStyle).
-    const testRoot = 'engine/toolkit/content/tests/widgets/';
-    return `\n\nWould create mochikit test file in ${testRoot}`;
-}
-/**
- * Builds the success-note body printed after `furnace create` has applied
- * its mutations. Lives beside the dry-run formatter so the two renderings
- * stay in lock-step when the scaffolded layout changes.
- */
-export function formatSuccessNote(args) {
-    const { componentName, files, testFiles, testStyle, binaryName, testDir } = args;
-    let note = `Files created in components/custom/${componentName}/:\n` +
-        files.map((f) => `  ${f}`).join('\n');
-    if (testFiles.length > 0) {
-        let testRoot;
-        if (testStyle === 'xpcshell') {
-            testRoot = `engine/${resolveXpcshellTestDir(binaryName, componentName, testDir)}/`;
-        }
-        else if (testStyle === 'mochikit') {
-            testRoot = 'engine/toolkit/content/tests/widgets/';
-        }
-        else {
-            testRoot = `engine/${resolveBrowserChromeTestDir(binaryName, testDir)}/`;
-        }
-        note += `\n\nTest files in ${testRoot}:\n` + testFiles.map((f) => `  ${f}`).join('\n');
-    }
-    note +=
-        '\n\n' +
-            'Next steps:\n' +
-            `  1. Edit component files in components/custom/${componentName}/\n` +
-            '  2. Run "fireforge furnace preview" to see it\n' +
-            '  3. Run "fireforge build" to apply and build';
-    return note;
-}
-/**
- * Builds the planned component + test file list for a dry-run preview.
- *
- * Mirrors the order `writeComponentFiles` and the test-style scaffolders
- * would produce so the dry-run output matches what a real run prints on
- * success. The component directory path is rendered relative to
- * `components/custom/` to match the wording of the real success note.
- */
-export function formatDryRunPlan(args) {
-    const { componentName, localized, register, composes, stockAdditions, sharedFtl, testStyle, description, binaryName, testDir, } = args;
-    const componentFiles = [`${componentName}.mjs`, `${componentName}.css`];
-    // A per-component .ftl is scaffolded only when the component does not
-    // opt into a shared feature-scoped bundle. Mirrors writeComponentFiles.
-    if (localized && !sharedFtl)
-        componentFiles.push(`${componentName}.ftl`);
-    let plan = `Would create files in components/custom/${componentName}/:\n` +
-        componentFiles.map((f) => `  ${f}`).join('\n');
-    plan += formatTestSection({ testStyle, componentName, binaryName, testDir });
-    plan += `\n\nWould add custom entry to furnace.json:`;
-    plan += `\n  name: ${componentName}`;
-    plan += `\n  description: ${description || '(empty)'}`;
-    plan += `\n  register: ${register}`;
-    plan += `\n  localized: ${localized}`;
-    if (composes && composes.length > 0) {
-        plan += `\n  composes: ${composes.join(', ')}`;
-    }
-    if (stockAdditions && stockAdditions.length > 0) {
-        plan += `\n\nWould add discovered stock to furnace.json:`;
-        for (const name of stockAdditions) {
-            plan += `\n  ${name}`;
-        }
-    }
-    if (sharedFtl) {
-        plan += `\n  sharedFtl: ${sharedFtl}`;
-    }
-    return plan;
-}

package/dist/src/commands/furnace/create-features.d.ts

@@ -1,24 +0,0 @@
-/**
- * Feature-flag resolution for `furnace create`. Extracted from
- * `create.ts` so the authoring command stays under the per-file LOC
- * budget. The flag resolver has grown with each new opt-in (`--xpcshell`,
- * `--test-style`, `--shared-ftl`).
- */
-import type { FurnaceCreateOptions } from '../../types/commands/index.js';
-/**
- * Resolves the localized and registration feature flags for a new component.
- *
- * `--shared-ftl` implies `localized` and short-circuits the interactive
- * prompt so the operator is not asked to flip a flag we are about to
- * enforce. `--no-localized` combined with `--shared-ftl` is rejected
- * fast-fail. The cross-field check in furnace-config would catch it
- * too, but later and without a clear command-line message.
- *
- * @param isInteractive - Whether interactive prompts are available
- * @param options - CLI-provided feature flags
- * @returns Final feature selections, or null when creation is cancelled
- */
-export declare function resolveCreateFeatures(isInteractive: boolean, options: FurnaceCreateOptions): Promise<{
-    localized: boolean;
-    register: boolean;
-} | null>;

package/dist/src/commands/furnace/create-features.js

@@ -1,55 +0,0 @@
-// SPDX-License-Identifier: EUPL-1.2
-/**
- * Feature-flag resolution for `furnace create`. Extracted from
- * `create.ts` so the authoring command stays under the per-file LOC
- * budget. The flag resolver has grown with each new opt-in (`--xpcshell`,
- * `--test-style`, `--shared-ftl`).
- */
-import { multiselect } from '@clack/prompts';
-import { InvalidArgumentError } from '../../errors/base.js';
-import { cancel, isCancel } from '../../utils/logger.js';
-/**
- * Resolves the localized and registration feature flags for a new component.
- *
- * `--shared-ftl` implies `localized` and short-circuits the interactive
- * prompt so the operator is not asked to flip a flag we are about to
- * enforce. `--no-localized` combined with `--shared-ftl` is rejected
- * fast-fail. The cross-field check in furnace-config would catch it
- * too, but later and without a clear command-line message.
- *
- * @param isInteractive - Whether interactive prompts are available
- * @param options - CLI-provided feature flags
- * @returns Final feature selections, or null when creation is cancelled
- */
-export async function resolveCreateFeatures(isInteractive, options) {
-    let localized = options.localized ?? false;
-    let register = options.register ?? true;
-    if (options.sharedFtl !== undefined) {
-        if (options.localized === false) {
-            throw new InvalidArgumentError('--shared-ftl requires localization. Remove --no-localized or drop --shared-ftl.', 'sharedFtl');
-        }
-        localized = true;
-    }
-    const featuresPromptSuppressed = options.sharedFtl !== undefined;
-    if (isInteractive &&
-        options.localized === undefined &&
-        options.register === undefined &&
-        !featuresPromptSuppressed) {
-        const features = await multiselect({
-            message: 'Component features:',
-            options: [
-                { value: 'localized', label: 'Fluent localization (data-l10n-id)' },
-                { value: 'register', label: 'Register in customElements.js' },
-            ],
-            initialValues: ['register'],
-        });
-        if (isCancel(features)) {
-            cancel('Create cancelled');
-            return null;
-        }
-        const selected = features;
-        localized = selected.includes('localized');
-        register = selected.includes('register');
-    }
-    return { localized, register };
-}

package/dist/src/commands/furnace/create-mochikit.d.ts

@@ -1,29 +0,0 @@
-/**
- * MochiKit (chrome://mochikit) test-harness scaffolder for
- * `fireforge furnace create --test-style=mochikit`.
- *
- * Browser-chrome mochitests require a `tabbrowser` in the top-level chrome
- * document, so forks with a bespoke chrome document that omits one cannot
- * run them. MochiKit tests load the component module directly via
- * `chrome://global/` and assert against `customElements`, so they work
- * against any fork that registers the upstream toolkit test manifest tree,
- * including those without a tabbrowser.
- */
-import { type RollbackJournal } from '../../core/furnace-rollback.js';
-import type { ProjectLicense } from '../../types/config.js';
-/**
- * Scaffolds a MochiKit test for a newly created custom component under
- * `engine/toolkit/content/tests/widgets/`. Mirrors the layout stock
- * Firefox widgets (moz-button, moz-toggle, etc.) use, so an operator who
- * already added the `widgets/` tree to their test-manifest registration
- * picks the new test up automatically.
- *
- * Appends a per-test entry to the existing `chrome.toml` when present,
- * writes a fresh `[DEFAULT]`-headed one otherwise. The caller is still
- * responsible for ensuring the `toolkit/content/tests/widgets/chrome.toml`
- * path is registered somewhere in the moz.build tree. Most forks inherit
- * this from upstream via `TEST_HARNESS_FILES += [...]`.
- */
-export declare function scaffoldMochikitTestFiles(componentName: string, license: ProjectLicense, paths: {
-    engine: string;
-}, journal?: RollbackJournal): Promise<string[]>;

package/dist/src/commands/furnace/create-mochikit.js

@@ -1,75 +0,0 @@
-// SPDX-License-Identifier: EUPL-1.2
-/**
- * MochiKit (chrome://mochikit) test-harness scaffolder for
- * `fireforge furnace create --test-style=mochikit`.
- *
- * Browser-chrome mochitests require a `tabbrowser` in the top-level chrome
- * document, so forks with a bespoke chrome document that omits one cannot
- * run them. MochiKit tests load the component module directly via
- * `chrome://global/` and assert against `customElements`, so they work
- * against any fork that registers the upstream toolkit test manifest tree,
- * including those without a tabbrowser.
- */
-import { join } from 'node:path';
-import { recordCreatedDir, snapshotFile, } from '../../core/furnace-rollback.js';
-import { getLicenseHeader } from '../../core/license-headers.js';
-import { ensureDir, pathExists, readText, writeText } from '../../utils/fs.js';
-import { warn } from '../../utils/logger.js';
-import { generateMochikitChromeTomlEntry, generateMochikitChromeTomlSkeleton, generateMochikitTestContent, mochikitTestFileName, } from './create-templates.js';
-/**
- * Scaffolds a MochiKit test for a newly created custom component under
- * `engine/toolkit/content/tests/widgets/`. Mirrors the layout stock
- * Firefox widgets (moz-button, moz-toggle, etc.) use, so an operator who
- * already added the `widgets/` tree to their test-manifest registration
- * picks the new test up automatically.
- *
- * Appends a per-test entry to the existing `chrome.toml` when present,
- * writes a fresh `[DEFAULT]`-headed one otherwise. The caller is still
- * responsible for ensuring the `toolkit/content/tests/widgets/chrome.toml`
- * path is registered somewhere in the moz.build tree. Most forks inherit
- * this from upstream via `TEST_HARNESS_FILES += [...]`.
- */
-export async function scaffoldMochikitTestFiles(componentName, license, paths, journal) {
-    const testDir = join(paths.engine, 'toolkit/content/tests/widgets');
-    if (journal && !(await pathExists(testDir))) {
-        recordCreatedDir(journal, testDir);
-    }
-    await ensureDir(testDir);
-    const hashHeader = getLicenseHeader(license, 'hash');
-    const writtenFiles = [];
-    const testFileName = mochikitTestFileName(componentName);
-    const testFilePath = join(testDir, testFileName);
-    if (await pathExists(testFilePath)) {
-        // Never clobber an existing test implementation, matching the
-        // browser-chrome and xpcshell scaffolds.
-        warn(`toolkit/content/tests/widgets/${testFileName} already exists — keeping the existing file.`);
-    }
-    else {
-        if (journal)
-            await snapshotFile(journal, testFilePath);
-        await writeText(testFilePath, generateMochikitTestContent(componentName));
-        writtenFiles.push(testFileName);
-    }
-    // chrome.toml: append an entry if the file already exists, otherwise
-    // write a fresh skeleton + entry. Idempotency: if the entry is already
-    // present the manifest is left untouched so re-runs don't double-register.
-    const manifestPath = join(testDir, 'chrome.toml');
-    const entry = generateMochikitChromeTomlEntry(componentName);
-    if (await pathExists(manifestPath)) {
-        const existing = await readText(manifestPath);
-        if (!existing.includes(`["${testFileName}"]`)) {
-            if (journal)
-                await snapshotFile(journal, manifestPath);
-            await writeText(manifestPath, existing.trimEnd() + '\n\n' + entry);
-        }
-    }
-    else {
-        if (journal)
-            await snapshotFile(journal, manifestPath);
-        await writeText(manifestPath, generateMochikitChromeTomlSkeleton(hashHeader) + entry);
-        writtenFiles.push('chrome.toml');
-    }
-    warn(`MochiKit scaffold written under toolkit/content/tests/widgets/. ` +
-        'Ensure `toolkit/content/tests/widgets/chrome.toml` is reachable from an existing test-harness registration (upstream TEST_HARNESS_FILES entries handle this by default).');
-    return writtenFiles;
-}

package/dist/src/commands/furnace/create-readback.d.ts

@@ -1,22 +0,0 @@
-/**
- * Defensive read-back helper for `furnace create`. Extracted from
- * `create.ts` so the authoring command stays under the per-file LOC
- * budget.
- */
-/**
- * Asserts that the just-written furnace.json contains the expected custom
- * component entry.
- *
- * A `furnace create` that reports success and writes the component files
- * while the next `furnace status` finds `custom: {}` is an invariant
- * violation with no obvious smoking gun in the code path. This defensive
- * readback is the recovery contract: if the new entry is not visible on the
- * next load, throw a `FurnaceError` so the rollback journal restores the
- * pre-command state and the operator sees the failure instead of a phantom
- * success.
- *
- * @param projectRoot - Root of the FireForge project
- * @param componentName - Custom-element tag name that must be present in
- *   `config.custom` after the write. Throws when absent.
- */
-export declare function assertCustomEntryPersisted(projectRoot: string, componentName: string): Promise<void>;

package/dist/src/commands/furnace/create-readback.js

@@ -1,32 +0,0 @@
-// SPDX-License-Identifier: EUPL-1.2
-/**
- * Defensive read-back helper for `furnace create`. Extracted from
- * `create.ts` so the authoring command stays under the per-file LOC
- * budget.
- */
-import { loadFurnaceConfig } from '../../core/furnace-config.js';
-import { FurnaceError } from '../../errors/furnace.js';
-/**
- * Asserts that the just-written furnace.json contains the expected custom
- * component entry.
- *
- * A `furnace create` that reports success and writes the component files
- * while the next `furnace status` finds `custom: {}` is an invariant
- * violation with no obvious smoking gun in the code path. This defensive
- * readback is the recovery contract: if the new entry is not visible on the
- * next load, throw a `FurnaceError` so the rollback journal restores the
- * pre-command state and the operator sees the failure instead of a phantom
- * success.
- *
- * @param projectRoot - Root of the FireForge project
- * @param componentName - Custom-element tag name that must be present in
- *   `config.custom` after the write. Throws when absent.
- */
-export async function assertCustomEntryPersisted(projectRoot, componentName) {
-    const persisted = await loadFurnaceConfig(projectRoot);
-    if (!(componentName in persisted.custom)) {
-        throw new FurnaceError(`Wrote furnace.json but "${componentName}" is missing from config.custom on read-back. ` +
-            'This should not happen — please report the issue. As a workaround, ' +
-            're-run the command, or add the entry to furnace.json by hand.', componentName);
-    }
-}