@hominis/fireforge 0.45.0 → 0.46.1

package/docs/testing.md

@@ -3,28 +3,29 @@
 # Running tests
 
 `fireforge test` wraps `mach test`. Most of what follows exists because
-mach's own defaults are wrong for a fork that must know exactly what ran.
+mach's own defaults are wrong for a fork that has to know exactly what ran.
 
 ## Scope is exact
 
-`fireforge test <directory>` runs exactly that directory: FireForge enumerates
-the directory's test files and passes the explicit file list to mach in one
-invocation, so mach's prefix-based path matching cannot silently sweep in
-sibling directories sharing the name prefix. Excluded siblings are echoed with
-their test-file counts.
+`fireforge test <directory>` runs exactly that directory. FireForge
+enumerates the directory's test files and passes the explicit file list to
+mach in one invocation, so mach's prefix-based path matching cannot quietly
+sweep in sibling directories that share the name prefix. Excluded siblings
+are echoed with their test-file counts.
 
-Multiple path arguments run as **sequential shards** by default — one browser
-instance per argument, with a directory argument keeping its files together —
-announced with a notice, since isolated instances do not exercise
-cross-argument state. `--no-shard` restores one combined invocation.
+Multiple path arguments run as sequential shards by default: one browser
+instance per argument, with a directory argument keeping its files together.
+FireForge announces this with a notice, since isolated instances do not
+exercise cross-argument state. `--no-shard` restores one combined
+invocation.
 
 ## Pathless runs must choose a mode
 
 - `--auto` forwards mach's own auto-selection.
 - `--doctor` runs the Marionette preflight only.
 - `--canary [path]` runs one short browser-chrome canary
-  (`test.canaryPath` / `test.canaryTimeoutSeconds` in `fireforge.json`
-  provide defaults).
+  (`test.canaryPath` and `test.canaryTimeoutSeconds` in `fireforge.json`
+  provide the defaults).
 
 ## Build freshness
 
@@ -32,68 +33,66 @@ When packageable engine files changed since the last successful FireForge
 build, `test` fails before launching stale artifacts. Use `--build` to
 refresh, or `--allow-stale-build` only for intentional out-of-band rebuilds.
 
-`--build-only` packages mixed-harness paths once, then each harness half can
-run without `--build`. `--extend-coverage` safely retains prior scoped
-coverage instead of replacing it; it is refused when the build anchor moved
-(engine HEAD, `engine/mozconfig`, or a previously fingerprinted packageable
-file).
+`--build-only` packages mixed-harness paths once, and then each harness half
+can run without `--build`. `--extend-coverage` retains prior scoped coverage
+instead of replacing it. It is refused when the build anchor moved (engine
+HEAD, `engine/mozconfig`, or a previously fingerprinted packageable file).
 
 ### What a pre-test build costs
 
-`test --build` runs `mach build faster`, with two escalations decided by
-comparing build inputs against the **last successful build** recorded in
-`.fireforge/last-build.json` — not against engine HEAD, since a fork's
-worktree is permanently dirty (imported patches, Furnace-applied
-components):
-
-- a changed `moz.build` / `moz.configure` / `Makefile.in` runs
-  `mach configure` first;
-- a changed `jar.mn` escalates the whole build to a full `mach build`
-  (minutes rather than seconds) **only** when it is a NEW manifest
-  (untracked in the engine repo, so no install manifest exists for it yet)
+`test --build` runs `mach build faster`. Two escalations are possible, and
+both are decided by comparing build inputs against the last successful build
+recorded in `.fireforge/last-build.json`, not against engine HEAD, since a
+fork's worktree is permanently dirty from imported patches and
+Furnace-applied components:
+
+- A changed `moz.build`, `moz.configure` or `Makefile.in` runs
+  `mach configure` first.
+- A changed `jar.mn` escalates the whole build to a full `mach build`
+  (minutes rather than seconds), but only when it is a new manifest
+  (untracked in the engine repo, so no install manifest exists for it yet),
   or when its jar declaration carries a bracketed base-directory prefix,
-  which redirects the install destination away from the default chrome
-  root. An entry added to an existing `dist/bin` manifest no longer
-  escalates. Any probe failure (unreadable manifest, no git) escalates, and
-  the notice names the manifest and the reason.
+  which redirects the install destination away from the default chrome root.
+  An entry added to an existing `dist/bin` manifest no longer escalates. Any
+  probe failure (an unreadable manifest, no git) escalates, and the notice
+  names the manifest and the reason.
 
-Each escalation is paid once per actual content change: a `jar.mn` that is
+Each escalation is paid once per actual content change. A `jar.mn` that is
 dirty against HEAD but byte-identical to what the last full build consumed
 does not escalate again. `fireforge build --ui` is itself a
-`mach build faster` and never escalates; the `jar.mn` record it writes is
-carried forward from the previous full build, so a registration made
-between a `build --ui` and the next `test --build` still triggers the full
-build once.
-
-The open question the 0.44.0 changelog recorded here — whether a full build
-is really required for an entry added to an existing `dist/bin` `jar.mn` —
-was settled downstream by exactly the experiment that entry asked for: two
-clean runs where a jar-only registration of a new content file was
-installed by a plain `fireforge build --ui`
-(`faster/install_dist_bin_browser` named the destination, the file reached
-`dist/bin` and the `.app` bundle) and fetched over `chrome://` by a plain
-`fireforge test`. That case no longer escalates. The two halves the
-experiment did NOT exercise — a new `jar.mn` file, and a non-default
-install destination — still do, for the reason the original entry gives:
-relaxing a stale-artifact guard without evidence trades a slow build for a
-silently wrong test.
+`mach build faster` and never escalates. The `jar.mn` record it writes is
+carried forward from the previous full build, so a registration made between
+a `build --ui` and the next `test --build` still triggers the full build
+once.
+
+The 0.44.0 changelog left an open question here: whether a full build is
+really required for an entry added to an existing `dist/bin` `jar.mn`. It was
+settled downstream by exactly the experiment that entry asked for. In two
+clean runs, a jar-only registration of a new content file was installed by a
+plain `fireforge build --ui` (`faster/install_dist_bin_browser` named the
+destination, and the file reached `dist/bin` and the `.app` bundle) and then
+fetched over `chrome://` by a plain `fireforge test`. That case no longer
+escalates. The two halves the experiment did not cover, a new `jar.mn` file
+and a non-default install destination, still escalate, for the reason the
+original entry gives: relaxing a stale-artifact guard without evidence trades
+a slow build for a silently wrong test.
 
 ## Resilience
 
 - Recognized harness crashes retry up to `--harness-retries <n>` times
   (default 2).
 - `--kill-stale-marionette` terminates recognized stale browsers.
-- Every dispatch runs a **census of orphaned harness helpers** — `xpcshell`
-  (the harness httpd), `pywebsocket`, `ssltunnel`, `moz-http2` — that
-  survived an earlier run in this project's objdir. It runs at preflight,
-  before this run spawns anything, so every hit is a survivor by
-  construction; a match must be objdir-anchored, since `xpcshell` and
-  `server.js` are far too generic to report on their own. Survivors slow
-  every later run without appearing in its output (a three-second suite
-  taking minutes of wall clock is the usual symptom). Report-only by
-  default; `--reap-orphans` terminates them. It never refuses a run.
-  A different shape — reparented Python `multiprocessing` workers — is
-  covered by the `Orphaned harness workers` doctor check.
+- Every dispatch runs a census of orphaned harness helpers (`xpcshell`, the
+  harness httpd, `pywebsocket`, `ssltunnel`, `moz-http2`) that survived an
+  earlier run in this project's objdir. It runs at preflight, before this run
+  spawns anything, so every hit is necessarily a survivor. A match has to be
+  objdir-anchored, since `xpcshell` and `server.js` are far too generic to
+  report on their own. Survivors slow every later run without appearing in
+  its output. The usual symptom is a three-second suite taking minutes of
+  wall clock. The census is report-only by default, and `--reap-orphans`
+  terminates what it finds. It never refuses a run. A different shape,
+  reparented Python `multiprocessing` workers, is covered by the
+  `Orphaned harness workers` doctor check.
 - `--perf-samples <path>` publishes a perf-sample artifact path to the
   harness (exported as `<BINARYNAME>_PERF_SAMPLE_JSON`).
 
@@ -102,30 +101,38 @@ silently wrong test.
 Every test run ends with one machine-readable line:
 
 ```
-FIREFORGE-VERDICT: PASS|FAIL reason=… [log=<path>]
+FIREFORGE-VERDICT: PASS|FAIL reason=… [note=<class>] [log=<path>]
 ```
 
-Automation should branch on it rather than on the raw process code, and must
-treat a **missing** verdict as failure. The closed set of `reason=` values and
-the stdout rules around the line are in
-[`machine-output.md`](machine-output.md); `log=` names the run's own complete
+Automation should branch on this line rather than on the raw process code,
+and has to treat a missing verdict as a failure. The closed set of `reason=`
+values and the stdout rules around the line are in
+[`machine-output.md`](machine-output.md). `log=` names the run's own complete
 output, specified in [`run-logs.md`](run-logs.md).
 
+`reason=preflight` covers every gate before the harness, so a refusal that
+can classify itself adds an additive `note=<class>` (`stale-browser`,
+`coverage-replaced`, and so on) naming which gate fired. The refusal's full
+text is written to stdout before the verdict line and into the run log, so a
+redirected run keeps the reason as well as the verdict. See
+[`run-logs.md`](run-logs.md).
+
 Exit code 14 (`INCONCLUSIVE`) is not red: it means `engine/` moved while the
-harness ran and the result was thrown away. Exit 15 (`LOCK_TIMEOUT`) means the
-run never started. See [`exit-codes.md`](exit-codes.md).
+harness ran and the result was thrown away. Exit 15 (`LOCK_TIMEOUT`) means
+the run never started. See [`exit-codes.md`](exit-codes.md).
 
 ## Output verbosity
 
 mozbuild quiets terminal output to warnings and errors when it detects a
 coding agent (`is_running_under_coding_agent()` keys on `CLAUDECODE`). The
-build half of that quieting is useful; the test half removes `TEST_START` and
-console INFO — the lines a hang or stall diagnosis needs, and the ones
-FireForge's own classifier reads (`Ran N checks`, `Unexpected results:`,
-`TEST-UNEXPECTED-*`), so suppression pushes a run toward `reason=no-tests`.
-
-`fireforge test --full-output` unsets the marker for **test dispatches only**;
-the build path stays quiet. It is opt-in rather than automatic because it
+build half of that quieting is useful. The test half removes `TEST_START` and
+console INFO, which are the lines a hang or stall diagnosis needs, and also
+the ones FireForge's own classifier reads (`Ran N checks`,
+`Unexpected results:`, `TEST-UNEXPECTED-*`), so suppression pushes a run
+toward `reason=no-tests`.
+
+`fireforge test --full-output` unsets the marker for test dispatches only,
+and the build path stays quiet. It is opt-in rather than automatic because it
 changes how much a third party prints, and an operator who wants the quieting
 should keep it.
 
@@ -137,39 +144,39 @@ Recent engines can end a run with a Python traceback at harness teardown:
 AttributeError: 'SystemResourceMonitor' object has no attribute 'stop_time'
 ```
 
-(or `poll_interval`), raised from `mozsystemmonitor/resourcemonitor.py`. It is
-an upstream defect in the resource monitor's own shutdown, it is cosmetic, and
-it does not affect any verdict. It matters only because it lands exactly where
-a reader looks for the failure summary.
+(or `poll_interval`), raised from `mozsystemmonitor/resourcemonitor.py`. It
+is an upstream defect in the resource monitor's own shutdown, it is cosmetic,
+and it does not affect any verdict. It matters only because it lands exactly
+where a reader looks for the failure summary.
 
-FireForge recognizes this one signature — and only this one. Recognition
-requires **all** of: an `AttributeError` on `SystemResourceMonitor` naming one
-of those two attributes, a `resourcemonitor.py` stack frame, and (in a test
-run) a preceding `SUITE_END`. A novel attribute, a different exception, or the
-same traceback before shutdown is treated as a real failure and printed
-verbatim, always.
+FireForge recognizes this one signature and no others. Recognition requires
+all of: an `AttributeError` on `SystemResourceMonitor` naming one of those
+two attributes, a `resourcemonitor.py` stack frame, and, in a test run, a
+preceding `SUITE_END`. A novel attribute, a different exception, or the same
+traceback before shutdown is treated as a real failure and always printed
+verbatim.
 
-The two phases handle it differently, deliberately:
+The two phases handle it differently, on purpose:
 
-- **Tests** collapse the traceback in the terminal echo to one labeled
-  `[FireForge]` line. Captures and the run log keep the **raw** traceback, and
-  the classifier reads the raw form — a real failure always outranks this
+- **Tests** collapse the traceback in the terminal echo to one line labeled
+  `[FireForge]`. Captures and the run log keep the raw traceback, and the
+  classifier reads the raw form, so a real failure always outranks this
   signature in diagnosis.
 - **Builds** print it verbatim and add a note naming it. A build has no
-  `SUITE_END` — no boundary separating teardown from work still in progress —
-  so FireForge cannot distinguish cosmetic teardown noise from a real
-  build-time traceback there, and withholding the block would be the wrong
-  risk to take.
+  `SUITE_END`, so there is no boundary separating teardown from work still in
+  progress, and FireForge cannot tell cosmetic teardown noise from a real
+  build-time traceback there. Withholding the block would be the wrong risk
+  to take.
 
 ## Concurrency
 
 A test run holds the engine-session lock and snapshots the engine git
-generation before and after the harness run, failing the verdict as invalid if
-the tree changed mid-run. To verify beside a busy primary checkout instead,
-use a [verification tree](verification-trees.md).
+generation before and after the harness run, failing the verdict as invalid
+if the tree changed mid-run. To verify beside a busy primary checkout
+instead, use a [verification tree](verification-trees.md).
 
 ## Dev-build gotcha
 
 In dev builds, files under `obj-*/dist/bin` may be symlinks back into the
-source tree (notably prefs), so edit source prefs directly and keep a backup
-before bisection experiments.
+source tree (prefs especially), so edit source prefs directly and keep a
+backup before bisection experiments.

package/docs/verification-trees.md

@@ -2,11 +2,11 @@
 
 # Verification trees
 
-For concurrent read-mostly verification beside a busy primary checkout,
-`fireforge tree create <name>` snapshots the project — applied engine tree
-included, `obj-*` excluded — into `.fireforge/trees/<name>` using filesystem
-copy-on-write (APFS `clonefile`, btrfs/XFS reflink). Roughly 3 s for a 156 MB
-applied browser tree.
+To run read-mostly verification beside a busy primary checkout,
+`fireforge tree create <name>` snapshots the project into
+`.fireforge/trees/<name>` using filesystem copy-on-write (APFS `clonefile`,
+btrfs/XFS reflink). The applied engine tree is included and `obj-*` is
+excluded. A 156 MB applied browser tree takes roughly 3 seconds.
 
 ```bash
 npx fireforge tree create verify
@@ -17,32 +17,33 @@ npx fireforge tree remove verify
 
 ## What works inside a tree
 
-Read-only commands and `export`/`re-export` dry runs. **Mutations are
-refused** — a default-deny verdict table, not a blocklist, so a newly added
-mutating command is refused until it is classified. That is invariant 7 in
+Read-only commands, plus `export` and `re-export` dry runs. Mutations are
+refused. The refusal comes from a default-deny verdict table rather than a
+blocklist, so a newly added mutating command is refused until someone
+classifies it. That is invariant 7 in
 [`lifecycle-invariants.md`](lifecycle-invariants.md).
 
-`--with-objdir` adds a safely relocated build, which makes build-less `test`
-possible inside the tree.
+`--with-objdir` adds a safely relocated build, which makes a build-less
+`test` possible inside the tree.
 
 ## Lifecycle
 
-- `tree list` reports staleness (`--json`; see
+- `tree list` reports staleness (`--json`, see
   [`machine-output.md`](machine-output.md)).
-- `tree remove` deletes, refusing an active lock and a lock of unknown
-  ownership.
-- `tree exec <name> -- <cmd>` runs a command inside a tree, sealing its stdout
-  so exactly one verdict line survives, last.
+- `tree remove` deletes a tree, and refuses when a lock is active or its
+  ownership is unknown.
+- `tree exec <name> -- <cmd>` runs a command inside a tree and seals its
+  stdout, so exactly one verdict line survives, last.
 
 ## Filesystems without CoW
 
-Refused unless `--force-copy` explicitly accepts a full physical copy. The
-refusal is the point: a silent full copy of an applied browser tree is not
-the operation anyone asked for.
+These are refused unless `--force-copy` explicitly accepts a full physical
+copy. The refusal is there on purpose: a silent full copy of an applied
+browser tree is not the operation anyone asked for.
 
 ## The tree marker
 
-`.fireforge/tree.json` is tri-state: absent (primary), valid (snapshot), or
-**corrupt**. A corrupt marker refuses every command, because an unreadable
-marker leaves it unknown whether this is a snapshot or the primary tree.
-`--ignore-corrupt-tree-marker` overrides that deliberately.
+`.fireforge/tree.json` has three states: absent (this is the primary), valid
+(this is a snapshot), or corrupt. A corrupt marker refuses every command,
+because an unreadable marker leaves it unknown whether this is a snapshot or
+the primary tree. `--ignore-corrupt-tree-marker` overrides that.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hominis/fireforge",
-  "version": "0.45.0",
+  "version": "0.46.1",
   "description": "FireForge — a build tool for customizing Firefox",
   "type": "module",
   "main": "./dist/src/index.js",
@@ -25,6 +25,7 @@
     "lint:fix": "eslint src/ bin/ scripts/ eslint-rules/ eslint.config.js vitest.config.ts vitest.pack.config.ts --fix",
     "typecheck": "tsc --noEmit -p tsconfig.json",
     "deadcode:check": "knip",
+    "deadcode:check:production": "knip --production --config knip.production.json",
     "cycles:check": "dpdm --no-output --no-tree --no-warning --exit-code circular:1 src/index.ts bin/fireforge.ts",
     "test": "vitest run",
     "test:package": "npm run pack:verify",
@@ -34,11 +35,11 @@
     "whitespace:check": "node ./scripts/check-worktree-whitespace.mjs",
     "pack:verify": "vitest run --config vitest.pack.config.ts",
     "pack:dry-run": "npm pack --dry-run --json --silent",
-    "format": "prettier --write --ignore-unknown \"src/**/*.ts\" \"bin/**/*.ts\" \"scripts/**/*.mjs\" \"eslint-rules/**/*.js\" \"package.json\" \"eslint.config.js\" \"vitest.config.ts\" \"vitest.pack.config.ts\" \"tsconfig.json\" \"tsconfig.build.json\" \".lintstagedrc.json\" \".prettierignore\" \".prettierrc\" \".gitignore\" \"README.md\" \"CHANGELOG.md\" \"docs/**/*.md\" \"knip.json\"",
-    "format:check": "prettier --check --ignore-unknown \"src/**/*.ts\" \"bin/**/*.ts\" \"scripts/**/*.mjs\" \"eslint-rules/**/*.js\" \"package.json\" \"eslint.config.js\" \"vitest.config.ts\" \"vitest.pack.config.ts\" \"tsconfig.json\" \"tsconfig.build.json\" \".lintstagedrc.json\" \".prettierignore\" \".prettierrc\" \".gitignore\" \"README.md\" \"CHANGELOG.md\" \"docs/**/*.md\" \"knip.json\"",
+    "format": "prettier --write --ignore-unknown \"src/**/*.ts\" \"bin/**/*.ts\" \"scripts/**/*.mjs\" \"eslint-rules/**/*.js\" \"package.json\" \"eslint.config.js\" \"vitest.config.ts\" \"vitest.pack.config.ts\" \"tsconfig.json\" \"tsconfig.build.json\" \".lintstagedrc.json\" \".prettierignore\" \".prettierrc\" \".gitignore\" \"README.md\" \"CHANGELOG.md\" \"docs/**/*.md\" \"knip.json\" \"knip.production.json\"",
+    "format:check": "prettier --check --ignore-unknown \"src/**/*.ts\" \"bin/**/*.ts\" \"scripts/**/*.mjs\" \"eslint-rules/**/*.js\" \"package.json\" \"eslint.config.js\" \"vitest.config.ts\" \"vitest.pack.config.ts\" \"tsconfig.json\" \"tsconfig.build.json\" \".lintstagedrc.json\" \".prettierignore\" \".prettierrc\" \".gitignore\" \"README.md\" \"CHANGELOG.md\" \"docs/**/*.md\" \"knip.json\" \"knip.production.json\"",
     "prepare": "node -e \"import('./scripts/prepare.mjs').catch((error) => { if (error && typeof error === 'object' && 'code' in error && error.code === 'ERR_MODULE_NOT_FOUND') process.exit(0); throw error; })\"",
     "prepack": "npm run build && node ./scripts/generate-build-info.mjs --loud",
-    "release:check": "npm run format:check && npm run whitespace:check && npm run lint:ci && npm run typecheck && npm run deadcode:check && npm run cycles:check && npm run test:coverage && npm run pack:verify",
+    "release:check": "npm run format:check && npm run whitespace:check && npm run lint:ci && npm run typecheck && npm run deadcode:check && npm run deadcode:check:production && npm run cycles:check && npm run test:coverage && npm run pack:verify",
     "prepublishOnly": "npm run release:check"
   },
   "files": [
@@ -65,7 +66,7 @@
   "devDependencies": {
     "@eslint/js": "^10.0.0",
     "@types/estree": "^1.0.8",
-    "@types/node": "^26.0.0",
+    "@types/node": "^22.0.0",
     "@vitest/coverage-v8": "^4.1.2",
     "dpdm": "4.3.0",
     "eslint": "^10.0.0",
@@ -74,7 +75,7 @@
     "eslint-plugin-simple-import-sort": "^14.0.0",
     "fast-check": "^4.6.0",
     "husky": "^9.1.7",
-    "knip": "6.32.2",
+    "knip": "6.32.3",
     "lint-staged": "^17.0.4",
     "prettier": "3.9.6",
     "tsx": "^4.7.0",

package/dist/src/commands/rebase.d.ts

@@ -1,4 +0,0 @@
-/**
- * `fireforge rebase` — re-exports from `./rebase/` sub-modules.
- */
-export { rebaseCommand, registerRebase } from './rebase/index.js';

package/dist/src/commands/rebase.js

@@ -1,5 +0,0 @@
-// SPDX-License-Identifier: EUPL-1.2
-/**
- * `fireforge rebase` — re-exports from `./rebase/` sub-modules.
- */
-export { rebaseCommand, registerRebase } from './rebase/index.js';

package/dist/src/core/patch-artifact-normalize.d.ts

@@ -1,21 +0,0 @@
-/**
- * Normalizes generated patch files before they are written to disk.
- *
- * Currently the identity function, kept as a narrow chokepoint for future
- * artifact-level fixes so every export path (`commitExportedPatch`,
- * `commitPlacementExport`, `updatePatch`, `patch split`) funnels through one
- * place.
- *
- * **Do not reintroduce whitespace trimming here.** Stripping marker lines
- * whose payload is pure whitespace (`/^[ +-]\s+$/` → bare marker) corrupts
- * real content: Firefox sources contain whitespace-only lines, so a ` `/`-`
- * line whose payload was e.g. two spaces no longer matches the pristine tree
- * (the freshly exported patch fails `git apply --check`), and a `+` line
- * silently changes what the patch produces, making re-import diverge from
- * the engine state it was exported from. The repository whitespace check
- * already excludes `patches/*.patch`
- * (scripts/check-worktree-whitespace.mjs). Patch bodies are written
- * byte-for-byte as git produced them, including the single-space rendering
- * of blank context lines, which `re-export.integration.test.ts` pins.
- */
-export declare function normalizePatchArtifact(content: string): string;

package/dist/src/core/patch-artifact-normalize.js

@@ -1,24 +0,0 @@
-// SPDX-License-Identifier: EUPL-1.2
-/**
- * Normalizes generated patch files before they are written to disk.
- *
- * Currently the identity function, kept as a narrow chokepoint for future
- * artifact-level fixes so every export path (`commitExportedPatch`,
- * `commitPlacementExport`, `updatePatch`, `patch split`) funnels through one
- * place.
- *
- * **Do not reintroduce whitespace trimming here.** Stripping marker lines
- * whose payload is pure whitespace (`/^[ +-]\s+$/` → bare marker) corrupts
- * real content: Firefox sources contain whitespace-only lines, so a ` `/`-`
- * line whose payload was e.g. two spaces no longer matches the pristine tree
- * (the freshly exported patch fails `git apply --check`), and a `+` line
- * silently changes what the patch produces, making re-import diverge from
- * the engine state it was exported from. The repository whitespace check
- * already excludes `patches/*.patch`
- * (scripts/check-worktree-whitespace.mjs). Patch bodies are written
- * byte-for-byte as git produced them, including the single-space rendering
- * of blank context lines, which `re-export.integration.test.ts` pins.
- */
-export function normalizePatchArtifact(content) {
-    return content;
-}

package/dist/src/core/patch-lint-reexports.d.ts

@@ -1,7 +0,0 @@
-/**
- * Public re-exports for {@link ./patch-lint.ts}. Split out so the
- * orchestrator stays within the ESLint `max-lines` budget.
- */
-export { buildPatchQueueContext, collectForwardImportEdges, collectNewFileCreatorsByPath, extractImportSpecifiers, extractImportSpecifiersWithLines, findForwardImportIgnoreLines, FORWARD_IMPORT_IGNORE_MARKER, isForwardImportableFile, lintPatchQueue, lintPatchQueueDuplicateCreations, lintPatchQueueForwardImports, type PatchQueueContext, type PatchQueueEntry, } from './patch-lint-cross.js';
-export { buildModifiedFileAdditionsFromDiff, detectNewFilesInDiff } from './patch-lint-diff.js';
-export { lintPatchQueueModuleRegistrations } from './patch-lint-module-registration.js';

package/dist/src/core/patch-lint-reexports.js

@@ -1,8 +0,0 @@
-// SPDX-License-Identifier: EUPL-1.2
-/**
- * Public re-exports for {@link ./patch-lint.ts}. Split out so the
- * orchestrator stays within the ESLint `max-lines` budget.
- */
-export { buildPatchQueueContext, collectForwardImportEdges, collectNewFileCreatorsByPath, extractImportSpecifiers, extractImportSpecifiersWithLines, findForwardImportIgnoreLines, FORWARD_IMPORT_IGNORE_MARKER, isForwardImportableFile, lintPatchQueue, lintPatchQueueDuplicateCreations, lintPatchQueueForwardImports, } from './patch-lint-cross.js';
-export { buildModifiedFileAdditionsFromDiff, detectNewFilesInDiff } from './patch-lint-diff.js';
-export { lintPatchQueueModuleRegistrations } from './patch-lint-module-registration.js';

package/dist/src/core/wire-targets.d.ts

@@ -1,7 +0,0 @@
-/**
- * Wire targets barrel — re-exports all wiring target modules.
- */
-export { addDestroyToBrowserInit } from './wire-destroy.js';
-export { addDomFragment } from './wire-dom-fragment.js';
-export { addInitToBrowserInit } from './wire-init.js';
-export { addSubscriptToBrowserMain } from './wire-subscript.js';

package/dist/src/core/wire-targets.js

@@ -1,8 +0,0 @@
-// SPDX-License-Identifier: EUPL-1.2
-/**
- * Wire targets barrel — re-exports all wiring target modules.
- */
-export { addDestroyToBrowserInit } from './wire-destroy.js';
-export { addDomFragment } from './wire-dom-fragment.js';
-export { addInitToBrowserInit } from './wire-init.js';
-export { addSubscriptToBrowserMain } from './wire-subscript.js';