@hominis/fireforge 0.54.0 → 0.60.0

package/dist/src/core/build-audit-transforms.d.ts

@@ -1,23 +0,0 @@
-/**
- * Returns the expected chrome-tree suffix for an engine-relative POSIX
- * source path when the path falls under a known transform prefix.
- * Returns undefined otherwise.
- *
- * @param source Engine-relative POSIX source path.
- */
-export declare function expectedChromeSuffix(source: string): string | undefined;
-/**
- * Probes the dist tree for the artifact implied by a known
- * source→chrome transform. Returns the first absolute candidate whose
- * POSIX path ends with the expected chrome suffix, or undefined when
- * no transform applies or no candidate matches.
- *
- * The transform check is treated as high-confidence by `build-audit.ts`
- * (callers pass `{ registered: true }` to `evaluateArtifactMtime`), so
- * a match bypasses the structural-relation check that rejects generic
- * basename collisions.
- *
- * @param source Engine-relative POSIX source path.
- * @param searchRoots Absolute roots to probe (dist/, _tests/).
- */
-export declare function resolveArtifactByKnownTransform(source: string, searchRoots: readonly string[]): Promise<string | undefined>;

package/dist/src/core/build-audit-transforms.js

@@ -1,92 +0,0 @@
-// SPDX-License-Identifier: EUPL-1.2
-/*
- * Known source→packaging path transforms for the post-build dist-tree audit.
- *
- * A source at `engine/browser/base/content/foo.js` ships under
- * `chrome/browser/content/browser/foo.js`. If an unrelated patch registers a
- * different `foo.js` elsewhere (say a pref file under
- * `browser/defaults/preferences/`), the basename walker surfaces both, and
- * `scoreCandidate` awards them an identical trailing-overlap score because
- * every intermediate segment is in the generic list. The heuristic then
- * declares the winner "not structurally related" and reports the
- * correctly-packaged chrome resource as missing.
- *
- * The transforms below anchor resolution to the subtree→chrome conventions
- * upstream mozilla-central jar.mn uses. A candidate whose path ends with the
- * implied chrome suffix is a confident match: the scorer never runs and the
- * structural-relation check is bypassed.
- *
- * Scope is narrow: only subtrees whose packaging target is
- * stable across forks. A fork that reroutes a known subtree can still win by
- * adding `(source)` annotations in its own `jar.mn`, which
- * `resolveArtifactByRegistration` consults first.
- */
-import { basename, sep } from 'node:path';
-import { findAllByBasename } from './build-audit-resolve.js';
-import { WIDGETS_DIR } from './furnace-constants.js';
-/**
- * Table of `prefix → chrome-suffix` transforms. Each rule names an
- * engine-relative subtree prefix and produces the expected dist-tree
- * suffix for a file under it. Rules are evaluated in array order and
- * the first-matching prefix wins, so `toolkit/content/widgets/` must
- * precede the looser `toolkit/content/`.
- */
-const KNOWN_TRANSFORMS = [
-    {
-        prefix: 'browser/base/content/',
-        build: (rest) => `chrome/browser/content/browser/${rest}`,
-    },
-    {
-        prefix: `${WIDGETS_DIR}/`,
-        build: (rest) => `chrome/toolkit/content/global/elements/${rest}`,
-    },
-    {
-        prefix: 'toolkit/content/',
-        build: (rest) => `chrome/toolkit/content/global/${rest}`,
-    },
-];
-/**
- * Returns the expected chrome-tree suffix for an engine-relative POSIX
- * source path when the path falls under a known transform prefix.
- * Returns undefined otherwise.
- *
- * @param source Engine-relative POSIX source path.
- */
-export function expectedChromeSuffix(source) {
-    for (const rule of KNOWN_TRANSFORMS) {
-        if (source.startsWith(rule.prefix)) {
-            return rule.build(source.slice(rule.prefix.length));
-        }
-    }
-    return undefined;
-}
-/**
- * Probes the dist tree for the artifact implied by a known
- * source→chrome transform. Returns the first absolute candidate whose
- * POSIX path ends with the expected chrome suffix, or undefined when
- * no transform applies or no candidate matches.
- *
- * The transform check is treated as high-confidence by `build-audit.ts`
- * (callers pass `{ registered: true }` to `evaluateArtifactMtime`), so
- * a match bypasses the structural-relation check that rejects generic
- * basename collisions.
- *
- * @param source Engine-relative POSIX source path.
- * @param searchRoots Absolute roots to probe (dist/, _tests/).
- */
-export async function resolveArtifactByKnownTransform(source, searchRoots) {
-    const suffix = expectedChromeSuffix(source);
-    if (!suffix)
-        return undefined;
-    const name = basename(source);
-    const suffixWithSlash = `/${suffix}`;
-    for (const root of searchRoots) {
-        const candidates = await findAllByBasename(root, name);
-        for (const candidate of candidates) {
-            if (candidate.split(sep).join('/').endsWith(suffixWithSlash)) {
-                return candidate;
-            }
-        }
-    }
-    return undefined;
-}

package/dist/src/core/build-audit.d.ts

@@ -1,93 +0,0 @@
-import { type AuditSkipReason, type UnpackagedDeclaration } from './build-audit-skip.js';
-import type { BuildBaseline } from './build-baseline-types.js';
-/**
- * True for the build-input manifests the build consumes but never packages
- * (`jar.mn`, `moz.build`, `moz.configure`, `Makefile.in`, `mozbuild.in`).
- * Excluded from the packaging audit and from `packageableFingerprints`.
- * Fingerprinted separately as `buildInputFingerprints` so `build-prepare`
- * can tell "dirty against HEAD" from "changed since the last successful
- * build".
- *
- * @param sourcePath Engine-relative POSIX path.
- */
-export declare function isBuildInputPath(sourcePath: string): boolean;
-/**
- * True for a chrome packaging manifest (`jar.mn`). Its install-manifest
- * destinations are the one build input whose change escalates a pre-test
- * `mach build faster` to a full build, and whose fingerprint is therefore
- * refreshed only by a full build.
- *
- * @param sourcePath Engine-relative POSIX path.
- */
-export declare function isJarManifestPath(sourcePath: string): boolean;
-/** Result of a single artifact lookup. */
-export interface AuditEntry {
-    /** Engine-relative source file path (POSIX separators). */
-    source: string;
-    /**
-     * Resolved artifact path inside the dist tree, or undefined when no
-     * candidate bundle location was found. An entry with an undefined path
-     * and status "missing" means the source was packageable but nothing
-     * that looked like its artifact showed up in the bundle.
-     */
-    artifact: string | undefined;
-    /**
-     * updated: an artifact exists and is at least as new as the source.
-     * stale:   artifact exists but is older than the source (probable packaging drop).
-     * missing: no artifact with a matching basename was found anywhere under dist/.
-     * skipped: the file was not audited. `skipReason` says why.
-     */
-    status: 'updated' | 'stale' | 'missing' | 'skipped';
-    /**
-     * Why a `skipped` entry was skipped. Present only for `skipped`. The
-     * reason lets the counts distinguish a structural non-input from an
-     * unregistered file an operator must act on, so the summary line never
-     * reports skips as misses.
-     */
-    skipReason?: AuditSkipReason;
-}
-/** Summary counts for the "Packaged:" end-of-build line. */
-export interface AuditSummary {
-    updated: number;
-    stale: number;
-    missing: number;
-    skipped: number;
-    /** Per-class skip counts, so the summary can name what it dismissed. */
-    skippedByReason: Record<AuditSkipReason, number>;
-    entries: AuditEntry[];
-}
-/**
- * Decides whether a source path should be packaged. Returns true for paths
- * whose extension or directory fragment matches a known-packaged pattern,
- * after excluding build inputs (`jar.mn`, `moz.build`, etc.) which are
- * consumed by the build but never themselves packaged.
- *
- * @param sourcePath Engine-relative POSIX path (for example browser/app/profile/pref.js).
- * @returns True when the path implies packaging.
- */
-export declare function isPackageablePath(sourcePath: string): boolean;
-/**
- * Decides whether a source path is an XPCOM static-component manifest,
- * i.e. a file whose registrations are baked into the compiled
- * StaticComponents table at full-build time rather than packaged into
- * `dist/`. This basename check is the single extension point for that
- * classification. Parsing `moz.build` `XPCOM_MANIFESTS` entries to follow
- * renamed manifests is out of scope.
- *
- * @param sourcePath Engine-relative POSIX path.
- * @returns True when the path is a `components.conf` manifest.
- */
-export declare function isXpcomManifestPath(sourcePath: string): boolean;
-/**
- * Runs the post-build audit. Emits per-file warnings for missing or
- * stale artifacts and a summary info line at the end. Always returns
- * the summary. Never throws on audit failure (the audit itself must
- * never fail a successful build).
- * @param projectRoot Root of the project (reserved for future fork-specific rules).
- * @param engineDir Path to the engine directory.
- * @param baseline Optional previous-build baseline marker.
- * @returns Summary of artifact status counts.
- */
-export declare function auditBuildArtifacts(projectRoot: string, engineDir: string, baseline: BuildBaseline | undefined, options?: {
-    unpackaged?: readonly UnpackagedDeclaration[];
-}): Promise<AuditSummary>;