mr-onion

Phase 48 Decision Record — The Rename to Mr Onion (D39)

Date: 2026-11-08 Scope:

Status: Complete 2026-11-12: merged to main as 2861a4c (2026-11-11); the first scheduled nightly on main green (run 43191298031); v0.3.0 tagged on 49431af and pushed, with the owner’s confirmation (Decision 13), and released: v0.3.0 (2026-11-12). Locked (Emil, 2026-11-08). In progress on branch phase-48-mr-onion: TFP-275 done (46e3994), TFP-276 done (621dd8a); TFP-277 done (9844233); Gate A independently verified and passed (Emil, 2026-11-09). TFP-278 done (48604dc, baseline 8892b7e), independently verified (2026-11-09). TFP-279 done (d4f10cf, c35217d). TFP-280 done (276f7b5); its allowlist accepted at Gate B (Emil, 2026-11-11). Gate B passed (Emil, 2026-11-11); TFP-281 (the repo rename and merge) next. Tracking issue #25; draft PR #23.

Context

What carries the name today (main at 4459382, 2026-11-08):

Decisions

  1. The display name is “Mr Onion”. (Emil, 2026-10-30; D39)
    • Written “Mr Onion”, without a full stop, in UI, reports, docs and the README. The tagline is “Mr Onion: peel back every layer” (D39).
  2. The technical name is mr-onion; settings use MRONION_. (Emil, 2026-11-08)
    • Repo emil3663/mr-onion; package mr-onion; command mr-onion (mr-onion run); bin file bin/mr-onion.mjs; image ghcr.io/emil3663/mr-onion (TFP-247); plugin mr-onion-skills, marketplace mr-onion-skills-marketplace; --out default ./mr-onion-out.
    • Settings: every TESTFORGE_X becomes MRONION_X, the rest of the name unchanged. Code identifiers use mrOnion / MrOnion where a name is needed.
    • Data folder: %LOCALAPPDATA%\MrOnion, ~/Library/Application Support/MrOnion, $XDG_DATA_HOME/mr-onion (~/.local/share/mr-onion).
    • Rejected: mronion everywhere, which gives one spelling but reads as “mro-nion”. A hyphen is valid in every place mr-onion goes; it isn’t valid in environment variable names, hence MRONION_.
  3. What is renamed. (Emil, 2026-11-08, the planning brief)
    • The visible name: the UI header, help panel, page titles and Open Graph (seo.ts), report pages, report footer and CLI messages.
    • The package name, the command, the bin/ entry and the npm script.
    • The GitHub repo (Decision 10).
    • README.md, CONTRIBUTING.md, SECURITY.md, CHANGELOG.md (a new entry; past entries keep the name they were written under), THIRD_PARTY_NOTICES.md, docs/ living docs (the “Docs that must stay true” table in WORKING_AGREEMENTS.md, plus docs/README.md, LOCAL_MODEL_SETUP.md, AUTOMATED_ACCOUNT_SETUP.md, GENERATOR_COMPARISON.md and APPLICATION_OVERVIEW.md), CLAUDE.md, the decisions index, the roadmap and the register’s open items.
    • The JUnit <testsuites name> and its fallback suite name become “Mr Onion”.
    • Every TESTFORGE_* setting, including the child-process protocol names and the TESTFORGE_PROGRESS marker.
    • The plugin and marketplace names.
    • Workflow step names, and the nightly’s secret (Decision 9). Amended 2026-11-08 (Emil): the secret keeps its name (Decision 9).
    • [for Emil] The generated suite’s own text: the header comment, the setting it checks and names in skip reasons, and the test data and markers it sends to a target (probe paths, Mr Onion check <time>, sample addresses, fixture names, the probe attribute and the window global). A site owner reading their logs sees the tool’s real name. The template check proves only the name moved (Decision 11).
    • [for Emil] The system prompt (“You are Mr Onion”) and the local model’s tag: a new ollama/Modelfile.mr-onion-qwen7b and default tag mr-onion-qwen7b. When that tag is missing and testforge-qwen7b is present, the old tag is used, and the generation record says so (ollama cp testforge-qwen7b mr-onion-qwen7b is the documented fix, with no rebuild).
    • [for Emil] Test file names under tests/regression/ (testforge.*.spec.ts), so the leftover-name check needs no allowance for them.
  4. What stays. (Emil, 2026-11-08, the planning brief)
    • The TFP- ticket prefix, and every test-case and test ID prefix (TFFU-, TFSE- and the rest, the test plan’s area prefixes). Reports, baselines and history refer to them.
    • Dated decision records, measurement reports and their historical mentions; benchmarks/ and examples/ (frozen evidence, never edited: WORKING_AGREEMENTS.md, “Where names still belong”); past CHANGELOG.md entries; git history and the v0.2.0 tag and release.
    • Existing run folders, saved runs (run.json), site suites, candidates and library entries, which keep the text they were written with (Decision 8).
    • The MIT licence: “Copyright (c) 2026 emil3663” doesn’t name the project (owner decision, 2026-11-08).
    • [for Emil] The mailboxes testforgeapp@gmail.com and its +ci and +<site> aliases: the nightly email’s sender display name becomes “Mr Onion nightly”. A new mailbox is D44.
    • [for Emil] Local folder names on the owner’s machine (source\repos\testforge, WSL’s ~/testforge-wsl): they aren’t user-facing, and renaming them breaks the owner’s tooling paths for no gain. Changing the remote URL is enough (Decision 10).
  5. Old names keep working until 1.0, with a deprecation notice. (Emil, 2026-11-08)
    • testforge stays a second bin entry, and npm run testforge stays a script. Both print one line on stderr: “testforge is now mr-onion; the old name stops working at 1.0.” Then they run the same CLI, with the same exit code.
    • Every setting is read as MRONION_X, then TESTFORGE_X. When the old name supplied the value, the app prints one notice per process naming both, on the server log or CLI stderr. When both are set and differ, the new one wins and the notice says so. Amended 2026-11-09 (Emil, owner decision): a blank MRONION_X (empty or only spaces) doesn’t hide a TESTFORGE_X that has a value: the old value is used, and the notice says the new name is blank. A pipeline that templates in an empty new variable keeps its old one. A blank MRONION_X on its own stays as it was: returned blank, which each reader treats as unset.
    • Removal of the old command and the old user-set names is planned with 1.0 (the versioning rule, TFP-257: 1.0 after Phase 47 declares the CLI and report stable). The removal needs its own ticket at that time.
    • Rejected: two minor releases (could fall before 1.0 and break pinned pipelines mid-0.x); a fixed date (the project versions by phase, not calendar).
  6. The data folder moves once. (Emil, 2026-11-08)
    • On the first start that resolves the data folder: if the new default folder doesn’t exist and the old default does, the old folder is renamed to the new one (same parent, so a rename, not a copy), and one notice says where it went.
    • A data folder the user set (MRONION_DATA_DIR, TESTFORGE_DATA_DIR or --data-dir) is never moved: it is used where it is.
    • [for Emil] When both default folders exist, the new one is used, nothing is merged, and the notice names the old folder as left in place.
    • [for Emil] When the rename fails (a file held open, a permission error), the old folder is used for that process, the notice says why, and the next start tries again. A run never starts with an empty folder because a move failed.
    • Rejected: copying (doubles the disk, and two copies drift); reading the old folder forever (the old name stays on disk with no end).
  7. Saved runs and baselines keep working across the rename. (Emil, 2026-11-08, the planning brief)
    • A run.json, run folder or site suite written by 0.2.x loads, diffs and serves as --baseline <id> and --baseline latest unchanged. Nothing in their format is renamed.
    • The report footer names the product by the version that ran: a run stamped below 0.3.0 says “TestForge ", and later runs say "Mr Onion ". A report never claims a past run was made by a name it didn't have.
  8. Saved suites aren’t rewritten; their child processes get both names. [for Emil]
    • A reused site-suite unit or library entry keeps its text, so it may check TESTFORGE_INTERACTIVE. Every run’s child environment sets each protocol and gate setting under both names, with the same value. An old saved suite therefore runs exactly as before, interactive tests included.
    • This child-side double setting does not end at 1.0 with Decision 5’s removals. It ends only when saved units carrying old names are regenerated or rewritten (D43). Until then, the 1.0 removal ticket leaves it alone.
    • Rejected: rewriting saved suites in the data folder (it changes the tester’s files, breaks writtenHash’s hand-edit detection, and edits promotion evidence).
  9. The nightly’s secret is renamed with a fallback. [for Emil]
    • nightly.yml reads secrets.MRONION_SMTP_PASSWORD || secrets.TESTFORGE_SMTP_PASSWORD. The owner adds the new secret in GitHub’s settings (an owner action, outside the repo), and deletes the old one after the first green nightly on main sends the email. Both steps are confirmation required.
    • A repo rename keeps secrets, issues, Actions history, Dependabot and CodeQL settings.

    Amended 2026-11-08 (Emil): the secret is not renamed in this phase. TESTFORGE_SMTP_PASSWORD is only the label GitHub stores the mailbox’s app password under; it isn’t user-facing, and the mailbox itself stays (Decision 4). It keeps its name until a new mailbox is decided (D44), so there is no fallback expression and no owner step in GitHub’s settings. check:old-name’s allowlist carries it, with this reason. The sender display name still becomes “Mr Onion nightly”.

  10. The GitHub repo is renamed at the merge, by the owner. [for Emil]
    • Sequence: the branch passes Gate B; the owner renames emil3663/testforge to emil3663/mr-onion in GitHub’s settings (confirmation required); Claude Code runs git remote set-url origin https://github.com/emil3663/mr-onion.git (repo-local config) and merges at once.
    • The branch’s links already say emil3663/mr-onion. They resolve from the moment of the rename, and old links and clones redirect.
    • GitHub keeps the redirect only while no repository takes the old name. Nothing is ever created again as emil3663/testforge: this is recorded in SECURITY.md’s maintainer notes and in the register.
    • Rejected: renaming the repo first, weeks before the merge (main’s docs would say “TestForge” under a repo called mr-onion); renaming after the merge (main would briefly link to a repo name that doesn’t exist yet).
  11. “Identical except the name” is measured, not read. [for Emil]
    • check:template-unchanged gains --rename-map <file>, a committed list of literal old → new replacements (scripts/template-unchanged/rename-map.json). It applies the map to the base ref’s output, then compares byte for byte with the head’s. Exit 0 only when every fixed input is identical.
    • Without the map, the same comparison shows the raw differences, kept in the ticket’s evidence.
    • The map holds only name tokens (TestForge → Mr Onion, TESTFORGE_ → MRONION_, testforge- → mr-onion-, __testforge → __mrOnion and so on). A token that isn’t a name is a review finding.
  12. No domain for now. (Emil, 2026-11-08)
    • The rename depends on no domain; the GitHub repo is the home page.
    • Found 2026-11-08: mronion.com serves a live site, and mronion.dev answers (robots.txt present). Both look taken; a registry lookup wasn’t possible from the planning session. A listed Taiwanese company, Mr. Onion Corp. (catering, TPEx 2740), joins the Chinese restaurant chain already in D39’s trademark notes.
    • Before one is bought (later, its own owner decision, money spent: confirmation required):
      1. An RDAP or registrar lookup for each candidate: mr-onion.dev, mronion.app, mr-onion.app, mr-onion.io, mronion.io, and mronion.co.za for the home market.
      2. What any taken one serves: a business in classes 9 or 42 rules out its siblings.
      3. The candidate is checked against the trademark filing’s class 9/42 search at the time, since the mark is to be registered in the EU or US (owner decision, 2026-11-03).
      4. Whether the name can be bought as .dev or .app, both HTTPS-only TLDs, which suits a security-minded tool.
  13. Where it sits: Phase 48, between TFP-246 and TFP-247. (Emil, 2026-10-30 and 2026-11-08)
    • Phase 47 is paused at TFP-247, which waits for this phase. TFP-247 then publishes ghcr.io/emil3663/mr-onion and never a testforge image. Outside pipelines pin the image name, so it must be right the first time (D39 item 5).
    • Amendment to Phase 47’s record, on lock: “Amended 2026-11-08 (Phase 48): TFP-247 and TFP-248 publish and document mr-onion (image ghcr.io/emil3663/mr-onion, command mr-onion run); they start after Phase 48 merges.”
    • [for Emil] The phase completes as 0.3.0: the versioning rule bumps the minor version per completed phase. v0.3.0 is tagged on main after the merge, and the tag push is confirmation required, as with v0.2.0.
  14. The branch, and what happens on main meanwhile. [for Emil]
    • Branch phase-48-mr-onion, from main at the lock. The name follows phase-16-local-first.
    • A draft pull request to main is opened with the first ticket, so PR Validation and CodeQL run on every push. It is marked ready only at Gate B.
    • Each ticket is committed and pushed to the branch as it is verified (the handover’s rule, applied to the branch). main gets no code commits while the branch is open: Phase 47 is paused, and Dependabot PRs wait. Docs-only commits from planning sessions may land on main.
    • Before Gate B, main is merged into the branch (a merge, never a rebase or force-push: those are confirmation required).
    • The merge to main is a merge commit (--no-ff), so each ticket’s Conventional Commit and its evidence stay in main’s history. Rejected: squash (loses the per-ticket reasoning the commit bodies carry); rebase-merge (no single commit to point at or revert).
    • Nightly: the schedule keeps running on main, unchanged. On the branch, the nightly is dispatched by hand (workflow_dispatch, ref phase-48-mr-onion) once after TFP-278’s baseline commit and once at Gate B, both green.
    • Rollback: before the repo rename, nothing has left the branch: the PR is closed and the branch kept. After the merge, `git revert -m 1 ` undoes the code in one commit, and the repo can be renamed back. A moved data folder isn't moved back by a revert. 0.2.x reads only the old default folder, so a user who rolls back sets `TESTFORGE_DATA_DIR` to the moved folder. This goes in the changelog's migration notes.

Acceptance Criteria

  1. Behaviour unchanged before any name changes (TFP-275).
    • check:template-unchanged against the lock’s main: every fixed input identical, with no map.
    • The unit, self-test and regression suites pass in full. No direct process.env.TESTFORGE_* read remains outside the settings module (a grep, quoted).
  2. Old and new settings and commands (TFP-276).
    • Each setting works under MRONION_X, and under TESTFORGE_X alone with exactly one notice per process. With both set and different, the new value is used and the notice says so. Unit tests show each case, seen failing first.
    • mr-onion run and testforge run give the same exit code, JUnit and report.json (apart from run id and timings) against local Toolshop clean and with-bugs. testforge prints the deprecation line on stderr, and mr-onion prints nothing extra.
    • A run’s child environment carries every protocol and gate setting under both names (a test records the child’s environment).
    • The template check is still identical with no map (the generated text doesn’t change in this ticket).
  3. The data folder (TFP-277), Gate A.
    • On Windows, with only %LOCALAPPDATA%\TestForge present (runs, a site suite, a candidate): the first start renames it to MrOnion, prints the notice once, and the UI lists the same runs. --baseline latest takes the same run as on 0.2.0. A saved site suite is reused, not regenerated. Amended 2026-11-09 (Gate A; the criterion was written from Phase 47’s context line, which the code doesn’t bear out): the default data folder holds site suites, candidates and gap-writer settings, not the UI’s runs. Runs are in the repo’s runs/ (RUNS_ROOT) unless the runs folder is set inside the data folder, as --data-dir does. So the criterion reads: the UI’s candidate list is unchanged, and a run kept in the data folder (via --data-dir) serves as --baseline latest after the move. The repo’s runs/ isn’t touched.
    • The same on Linux (~/.local/share/testforge → mr-onion), in the WSL clone. macOS is covered by unit tests only, stated as a limit.
    • Both folders present: the new one is used, nothing is moved, and the notice names the old one. A held-open file in the old folder (Windows): the old folder is used, the notice gives the reason, and the next start moves it.
    • A user-set data folder (either setting name, or --data-dir) is never moved.
    • A 0.2.0 run.json diffs against a new run and serves as --baseline with the same known/new/fixed split as before the rename.
  4. The generated suite (TFP-278).
    • check:template-unchanged <before> <after> --rename-map …: every fixed input identical. Without the map, the raw diff is attached, and every changed line is a name token.
    • A mutant (one non-name character changed in one helper) makes the mapped check exit non-zero: shown red.
    • A site suite saved by 0.2.0 that holds an interactive test runs it with MRONION_INTERACTIVE=1 and skips it without (Decision 8).
    • TEMPLATE_BASELINE is re-recorded in nightly.yml in its own commit. A dispatched nightly on the branch is green.
    • With only testforge-qwen7b present, local generation uses it, and the generation record names the fallback.
  5. The visible name (TFP-279).
    • The built app’s pages, an exported Standard report and a Comprehensive report, the CLI’s --help and error output, and junit.xml contain no “testforge” in any case. The exceptions are the deprecation notice, a pre-0.3.0 run’s footer (Decision 7) and the target’s own content. A script renders each one and greps it; its output is quoted.
    • Page titles and Open Graph read “Mr Onion” (<title>, og:site_name).
    • The JUnit <testsuites name> is “Mr Onion”, and a record with no suite falls back to “Mr Onion”. The counts equal report.json’s, as in Phase 47 criterion 2.
    • The plugin installs as mr-onion-skills from the renamed marketplace, and its skills load.
  6. No old name left in living text (TFP-280).
    • npm run check:old-name greps tracked files case-insensitively and exits 0 only when every hit is in its allowlist (scripts/old-name/allowlist.json). Each entry is a path or pattern with a reason, and it covers only: dated records and reports in docs/decisions/, benchmarks/, examples/, past CHANGELOG.md entries, the compatibility code and its tests, the rename map, the nightly’s TESTFORGE_SMTP_PASSWORD secret name (Decision 9, amended), and LICENSE’s absence of the name. The allowlist is reviewed line by line at Gate B.
    • The check runs in PR Validation.
    • CHANGELOG.md’s 0.3.0 entry states the new names, the old names’ end at 1.0, the data-folder move, the plugin reinstall and the rollback note (Decision 14).
  7. The merge (TFP-281), Gate B and after.
    • Before the merge, on the branch with main merged in: every criterion above re-checked by an independent verifying session; unit, self-test and regression suites in full; PR Validation and CodeQL green; a dispatched nightly green.
    • After the merge, on main: the merge commit’s tree is identical to the branch’s last verified commit, plus nothing (git diff --stat empty, quoted). The scheduled nightly is green and its email arrives (Decision 9). The old URL github.com/emil3663/testforge redirects (web and git ls-remote). The template check against the branch’s baseline is identical. check:old-name passes. Added 2026-11-11 (Emil): once the Pages build after the merge finishes, the <title> of emil3663.github.io/mr-onion/ reads Mr Onion (“Mr Onion | mr-onion”, the second half being the repo name), with no old name, quoted.
    • The register’s D39 is marked done with the merge hash; the record’s status line, the roadmap and the decisions index say “Complete”.

Regression Policy

Each is added to deferred-work-register.md in the same change as this lock:

Dependencies and order

Backlog

TFP-275 - One settings reader

TFP-276 - The new names, with the old ones as fallback

TFP-277 - The data folder’s one-time move — Gate A

TFP-278 - The generated suite’s text and the local model’s tag

TFP-279 - The visible name, JUnit, plugin and workflows

TFP-280 - Docs, changelog and the leftover-name check

TFP-281 - Merge to main — Gate B

  1. Lock this record; the branch phase-48-mr-onion and its draft PR.
  2. TFP-275.
  3. TFP-276.
  4. TFP-277 — Gate A.
  5. TFP-278 (baseline moves; nightly dispatched on the branch).
  6. TFP-279.
  7. TFP-280.
  8. TFP-281 — Gate B; repo rename; merge; post-merge checks; v0.3.0.
  9. Phase 47 resumes at TFP-247, under mr-onion.

Suggested Milestone Gates

Gate A — Nobody loses anything

Gate A verification (planning session, 2026-11-09): every checked criterion met. The owner’s ruling: passed (Emil, 2026-11-09). The planning session verified it independently. It designed the record but built none of TFP-275 to TFP-277.

Check How Result
Commits exist and are pushed git log, git show --stat, git ls-remote origin 506c5b5, 9844233, 69142d0, 81e239a on phase-48-mr-onion; the remote branch is at 81e239a; main is at cf501ad
Scope git show --stat The move, the store’s old-path mapping, the footer rule and their tests; plus the self-test server’s temporary data folder (a real isolation defect found while building, fixed in the ticket per the standing policy: kept)
Template unchanged (criteria 1-3) check:template-unchanged cf501ad, in a fresh clone of the branch 172 inputs, 172 identical, 0 different, exit 0
Data-dir, settings and version tests Re-run, Linux, Node 22, temporary XDG_DATA_HOME/LOCALAPPDATA 34 passed, 0 failed, 1 skipped (needs Chromium)
The move on a real filesystem A probe calling dataDir() twice per process, in temporary folders Old only: renamed, file intact, one notice. Both: new used, old left, one notice. Rename refused (read-only parent, EACCES): old used, notice gives the reason; the next start moved it. MRONION_DATA_DIR or TESTFORGE_DATA_DIR set: that folder used, the default old folder not moved (the old name’s deprecation notice printed)
The owner’s real folder Listing of %LOCALAPPDATA% TestForge present, no MrOnion
Code read against Decision 6 data-dir.ts, store.ts, text.ts Matches, including the two review fixes (a process left on the old folder follows a later move; a pre-move record’s suite path maps to the new folder)

Not checked here, with where they are checked:

Rulings:

  1. Criterion 3’s runs line is amended (above): the criterion was wrong about where runs live, and the build’s check is the right one.
  2. The 0.3.0 bump goes in TFP-279 (Emil, 2026-11-09). The changelog entry and tag stay after it, as before.
  3. The owner’s own folder (Emil, 2026-11-09): the owner backs up %LOCALAPPDATA%\TestForge before running the branch himself, then lets it move as it will for every user after the merge. Claude Code’s checks keep using copies under a temporary folder.

Gate B — Ready for main

Gate B verification, part 1: the branch (planning session, 2026-11-11). Every criterion checked here is met, except the three doc findings below, which are fixed in the working tree. The planning session built none of TFP-279 or TFP-280. The owner’s ruling: pending.

Check How Result
Commits exist and are pushed git log, git show --stat, git ls-remote origin d4f10cf, c35217d, 7d59b4e, 276f7b5, d9a7853 on phase-48-mr-onion; the remote branch is at d9a7853
main merged in git merge-base main phase-48-mr-onion cf501ad, which is main’s head: main hasn’t moved since the lock, so the branch already contains it
Package package.json "name": "mr-onion", "version": "0.3.0"
Leftover names (criterion 6) npm run check:old-name, in a fresh clone 16,838 hits in 1,175 files, all allowed by 52 of 52 entries, exit 0
The allowlist All 52 entries read Each has a reason, and each falls in one of five groups: frozen evidence and dated records (1-9); compatibility code and its tests (10-36); the owner’s decisions to keep a name (37-40); history lines inside living files, matched line by line (41-52). Nothing user-facing found behind an entry. Whole-file entries are used only for compatibility code and dated documents
Template, no map (criteria 4-5) check:template-unchanged 48604dc 172 inputs, 172 identical, exit 0
Template, mapped (criterion 4) check:template-unchanged 3c742e8 --rename-map … 172 inputs, 172 identical, exit 0
Types tsc --noEmit -p . exit 0
Changelog’s 0.3.0 entry (criterion 6) Read New names, old names until 1.0, the data-folder move, the plugin reinstall (four commands), the repo, and going back to 0.2.x: all present

Findings, fixed in the working tree by the planning session (doc edits):

  1. CHANGELOG.md said “Your runs, site suites and candidates move with it” and that going back lets 0.2.x find “your runs”. The app’s runs are in the repo’s runs/ folder and don’t move (Gate A ruling 1). Both lines now name site suites, candidates and gap-writer settings.
  2. TFP-280’s amendment said “add or update the marketplace”. It is corrected to remove and add again, as tested.
  3. TFP-281’s scope still listed “the secret switch-over (Decision 9)”, which Decision 9’s amendment removed. It is struck through, with an amendment.

Not checked here, and where they are checked: the full unit, self-test and regression suites, and npm run check:visible-name (it needs the built app and real Standard and Comprehensive runs). This session’s VM has no Chromium, and each unit file takes about 30 s to start here. A fresh Claude Code session on the owner’s machine that built none of Phase 48 runs them as part 2. Also not checked here: PR #23’s checks on d9a7853 (reported green).

For the owner’s ruling:

Gate B verification, part 2: the suites (a fresh Claude Code session on the owner’s machine that built none of Phase 48, 2026-11-11). It ran on e50cc6e (only docs changed since d9a7853), with a temporary LOCALAPPDATA and no data-folder setting. The real %LOCALAPPDATA%\TestForge was identical before and after (41 files), and nothing was committed.

Command First run Rerun, nothing changed
npm run test:unit 821 tests: 820 passed, 1 failed, 0 skipped (18 min 18 s), exit 1 The failing file alone (routes.test.ts): 3 of 3 passed, exit 0
npm run test:self “Timed out waiting 120000ms from config.webServer”, 0 tests ran, exit 1 5 of 5 passed, exit 0
npm run test:regression 73 passed, none skipped, flaky or failed, exit 0 —
npm run check:visible-name “no old name found”, exit 0. Title “Mr Onion | …”, og:site_name “Mr Onion”, JUnit <testsuites name="Mr Onion"> with counts equal to the reports’, the footer “Mr Onion 0.3.0 (e50cc6e)” —

The two first-run failures, read by the planning session:

Gate B ruling (Emil, 2026-11-11): passed, green on the reruns. Each first-run failure is logged as one data point with its cause. If either fails the same way again, it is treated as a real signal, not explained again. Next: the owner renames the repo (Decision 10), then the --no-ff merge and Acceptance Criteria 7’s post-merge checks.