@avi2dg/checks 0.70.0 → 0.72.0

package/CHANGELOG.md

@@ -2,6 +2,22 @@
 
 Every release of `@avi2dg/checks`, newest first, written by the release from its conventional commits.
 
+## 0.72.0
+
+Released 2026-11-07.
+
+### Features
+
+- **checks-setup:** write root AGENTS.md and CLAUDE.md when absent [#60](https://github.com/avi2d/checks/pull/60)
+
+## 0.71.0
+
+Released 2026-11-07.
+
+### Features
+
+- rename night run to whole-tree run [#59](https://github.com/avi2d/checks/pull/59)
+
 ## 0.70.0
 
 Released 2026-11-07.

package/docs/bins.md

@@ -9,7 +9,7 @@ The kit ships one bin per check, each named `checks-` and called from a package
 ## What runs
 
 `checks-lint` runs each of these gates that applies to the repository, and names every one that fails.
-A gate reads either the working tree or the range `checks-lint` resolves, or the whole tree at the head under `checks-lint --night`.
+A gate reads either the working tree or the range `checks-lint` resolves, or the whole tree at the head under `checks-lint --whole-tree`.
 It scopes tree gates to the change unless `--full` forces the full run, and `--desk` runs the fast tree gates.
 The table groups the gates by vector, the part of a repository each one judges.
 
@@ -37,9 +37,9 @@ The table groups the gates by vector, the part of a repository each one judges.
 
 <!-- end generated gates -->
 
-Four of these gates run only at night.
+Four of these gates run only on the whole-tree run.
 They are `checks-lint-coverage`, `checks-quarantine-clock`, `checks-repetition` and `checks-suppressions-ratchet`.
-The night-run workflow runs them with `checks-lint --night`, which hands each range gate `--whole-tree HEAD`, so the four judge the whole tree with no base.
+A whole-tree-run workflow the repository writes runs them with `checks-lint --whole-tree`, which hands each range gate `--whole-tree HEAD`, so the four judge the whole tree with no base.
 
 These bins run on their own:
 
@@ -50,8 +50,8 @@ These bins run on their own:
 - [`checks-mutation-baseline`](gates/checks-mutation-baseline.md) restores the newest mutation baseline from `main`, saves it on a self-hosted runner's disk in place of an artifact, and deletes superseded baselines after a `main` run.
 - [`checks-mutation-scope`](gates/checks-mutation-scope.md) turns a branch's diff into the files its mutation runs mutate.
 - [`checks-subsumed-tests`](gates/checks-subsumed-tests.md) lists each test another test subsumes in a mutation run.
-- [`checks-night-run`](gates/checks-night-run.md) opens or comments on one GitHub issue per finding of a night run on `main`, each file whose mutation score fell, each failing test, each failed nightly gate, and each missing mutation report.
-  It closes the issue of a test, a gate or a missing mutation report that a later night no longer reports, and it comments on a mutation issue it no longer reports without closing it, but only when a previous night exists and every requested mutation report is present.
+- [`checks-whole-tree-run`](gates/checks-whole-tree-run.md) opens or comments on one GitHub issue per finding of a whole-tree run on `main`, each file whose mutation score fell, each failing test, each failed whole-tree gate, and each missing mutation report.
+  It closes the issue of a test, a gate or a missing mutation report that a later run no longer reports, and it comments on a mutation issue it no longer reports without closing it, but only when a previous run exists and every requested mutation report is present.
 - [`checks-changelog`](gates/checks-changelog.md) writes the pending release into `CHANGELOG.md` from the conventional commits since the last release.
 - [`checks-release-notes`](gates/checks-release-notes.md) writes one `CHANGELOG.md` section to a file for a GitHub release.
 - [`checks-release-report`](gates/checks-release-report.md) tells whether the history holds unreleased features or fixes since the last tag.
@@ -65,7 +65,7 @@ These bins run on their own:
 - [`checks-commit-title`](gates/checks-commit-title.md) lints the pull request title in one step of the `ci` job.
 - [`checks-pr-text`](gates/checks-pr-text.md) scans the title, body and comments of a pull request in a public repository for a secret or a term of the private pack.
 - [`checks-docs-only`](gates/checks-docs-only.md) tells whether a change touches only top-level Markdown and Markdown under `docs/`, so a docs-only change skips the full run.
-- [`checks-setup`](gates/checks-setup.md) writes the kit config, the CI workflow, the night-run workflow and the doc templates into a new repository.
+- [`checks-setup`](gates/checks-setup.md) writes the kit config, the CI workflow and the doc templates into a new repository.
 
 `checks-lint` has [its own page](gates/checks-lint.md), which says which range it resolves.
 oxlint runs through its own tool, as [Native settings](configs/native-settings.md) says.

package/docs/configs/native-settings.md

@@ -93,7 +93,7 @@ export default defineConfig({ baseline: "widely", tokens: false });
 
 The size rules are oxlint's own rules at `error`, which every `oxlint.config.ts` built with `defineConfig` sets over the whole tree, so `bun run lint` fails on any file over them.
 A repository records its existing violations with `oxlint --suppress-all`, which writes them to `oxlint-suppressions.json`.
-`checks-suppressions-ratchet` refuses every count that file still holds when the night run scans the whole tree.
+`checks-suppressions-ratchet` refuses every count that file still holds when the whole-tree run scans the whole tree.
 `SOURCE_LIMITS` holds the limits for sources and `TEST_LIMITS` the limits for tests:
 
 <!-- generated size-limits: bun run build writes it from SOURCE_LIMITS, TEST_LIMITS, SOURCES and TESTS in src/quality/presets/oxlint.ts and scripts/doc-blocks.ts -->

package/docs/design.md

@@ -130,7 +130,7 @@ The gates run one at a time and pass their output straight through, so each repo
 `checks-lint` picks the gates that apply from the tracked files for the full run, and a repository cannot select gates.
 A scoped run selects a subset by changed paths, and the desk run selects the fast tree gates.
 A TypeScript gate applies as soon as the repository tracks TypeScript source, and `checks-lint-coverage` and `checks-graphwalk` also apply on tracked Astro source.
-`checks-lint-coverage` and `checks-repetition` run only at night.
+`checks-lint-coverage` and `checks-repetition` run only on the whole-tree run.
 
 dependency-cruiser runs inside the `checks-graphwalk` gate rather than as a script each repository adds to `lint`, so the full run keeps it.
 A repository with no config of its own is cruised against the kit's defaults, since every rule has one.
@@ -167,7 +167,7 @@ A stylesheet already over 400 lines fails until it is split, whatever the suppre
 `checks-repetition` runs jscpd at both ends of the range with the head's `.jscpd.json`, so the same `path` and `ignore` globs pick the files at both ends.
 It compares each file's count of repeated lines, and does not use jscpd's `--baseline-from-ref`.
 That flag reports a repeated block as new once its text changes, so a change that shortens an existing repeated block would fail.
-At night `checks-lint --night` runs both ratchets over the whole tree with no base, so every suppression count and every repeated line still present fails until it is removed.
+On the whole-tree run `checks-lint --whole-tree` runs both ratchets over the whole tree with no base, so every suppression count and every repeated line still present fails until it is removed.
 
 ## checks-test runs the suite itself
 

package/docs/gates/checks-browser.md

@@ -157,7 +157,7 @@ So are a `motion` check with no state whose `reducedMotion` is `reduce`, a `keyb
 
 A viewport `{ "preset": "anchor" }` stands for the anchor set of screen sizes, and `{ "preset": "full" }` for the full set.
 The full set holds the anchors and eleven more sizes.
-A product runs the anchor set on every pull request and the full set at night.
+A product runs the anchor set on every pull request and the full set on a run started by hand.
 Each size in a set is a viewport named for its device and its size, with `device` set, and each phone also sets `touch`.
 A preset sits beside a product's own viewports.
 A name both declare is refused as declared twice, and so is a size that two listed presets both hold.
@@ -231,7 +231,7 @@ A host resolves it as `@avi2dg/checks/browser-checks.json`.
 
 <!-- end generated starter -->
 
-For the night run, a product keeps a second declaration in a directory of its own.
+For a run started by hand, a product keeps a second declaration in a directory of its own.
 Its `site` is a path from that directory, such as `../dist`, and its viewports are `{ "preset": "full" }`.
 It runs `checks-browser <directory>` on that directory.
 

package/docs/gates/checks-ci-wiring.md

@@ -32,16 +32,6 @@ A workflow without a `name` answers to its path from the repository root.
 A local reusable `uses` must name a file under `.github/workflows/` that the repository holds.
 Each `needs` entry names a job in the same workflow, so every one must match a job id in that file.
 Each refusal names the file, the line and the missing workflow or job.
-It requires a run step that invokes `checks-lint --night` in a repository that tracks TypeScript, so the four nightly gates run on the night run.
-A call counts directly, through `bunx`, or through `bun` or `bun run` with the bin's path or its source file.
-The call carries only `--night`, since any other argument stops the night run before it runs a gate.
-A call through a `package.json` script counts, as `bun run <script>` where the named script runs the night step with the arguments the step passes.
-A call through a local reusable workflow counts only through a job that uses the file that runs the night step.
-A call through a repository shell script counts, as a path inside the repository whose file runs the night step.
-A shell wrapper forwards its arguments through a standalone `"$@"`, so `exec checks-lint --night "$@"` counts with no arguments passed.
-Shell control flow inside scripts is not evaluated: a night call after `false &&`, in an `if` branch, in a loop body or after `exit 0` counts all the same.
-A call inside a function body counts whether or not the workflow calls the function.
-A step or job with `if: false` or `continue-on-error: true` never counts, nor does a job that waits on one that never runs.
 
 ### Runners
 
@@ -120,7 +110,7 @@ Each refusal names the workflow file, the line of its `schedule` trigger and wha
 
 ### Schedules
 
-It refuses every other workflow that triggers on `schedule`, since a test, mutation, flake, browser or night run starts only by hand, with `gh workflow run`.
+It refuses every other workflow that triggers on `schedule`, since a test, mutation, flake, browser or whole-tree run starts only by hand, with `gh workflow run`.
 The one schedule it keeps is a weekly advisory scan in a public repository.
 A workflow scans advisories when a run step calls `checks-advisories`, the same ways a release call counts, and every other run step is a `bun install`.
 A weekly scan has one `cron` entry with one minute, one hour and one weekday, and `*` for the day of the month and the month.
@@ -141,7 +131,6 @@ Each refusal names the workflow file, the job and the limit.
 
 The bin reads `.github/workflows/*.yml`, `*.yaml`, the `scripts`, `private` and `checks` runners in `package.json` and the shell scripts those steps and scripts run from the working tree.
 It reads each shell script that a shell script it reads runs, until none is left.
-It lists the `*.ts` and `*.tsx` files `git ls-files` tracks to decide whether the night run applies.
 It reads each file a setup-bun step names for its version.
 It reads `.bun-version` for each step that uses the shared setup action.
 It reads the fleet pin from the kit's own `.bun-version`.
@@ -158,7 +147,7 @@ It takes no arguments.
 | Code | Result |
 | --- | --- |
 | 0 | Every required command has a reachable step. |
-| 1 | A required command is missing or blocked, a job runs on the wrong runner, a workflow names a missing workflow or job, a bun setup step drifts from the fleet bun version, a workflow that releases runs on a schedule outside a public npm package or more than once a day, a workflow other than a weekly public advisory scan runs on a schedule, a job can run for more than 60 minutes, or a repository that tracks TypeScript never runs `checks-lint --night`. |
+| 1 | A required command is missing or blocked, a job runs on the wrong runner, a workflow names a missing workflow or job, a bun setup step drifts from the fleet bun version, a workflow that releases runs on a schedule outside a public npm package or more than once a day, a workflow other than a weekly public advisory scan runs on a schedule, or a job can run for more than 60 minutes. |
 | 2 | A workflow or `package.json` cannot be decoded, or the kit's own `.bun-version` is missing, unreadable or blank. |
 
 ## Sample output
@@ -171,14 +160,6 @@ ci-wiring: 1 of 6 gate(s) do not run on pull requests to main:
     no run step invokes it
 ```
 
-A missing night step produces a report like this:
-
-```
-ci-wiring: 1 gate(s) never run on the night run:
-  checks-lint --night
-    no run step invokes it
-```
-
 A mutation job that names `CI_RUNS_ON` in `runs-on` produces a report like this:
 
 ```
@@ -205,7 +186,7 @@ A scheduled test run and a daily advisory scan produce a report like this:
 ```
 ci-wiring: 2 workflow(s) run on a schedule:
   .github/workflows/advisories.yml line 3: the advisory scan runs more than once a week; keep one cron at a minute, an hour and a weekday, such as "15 5 * * 1"
-  .github/workflows/night-run.yml line 4: drop the schedule, so it runs only when someone starts it with gh workflow run
+  .github/workflows/whole-tree-run.yml line 4: drop the schedule, so it runs only when someone starts it with gh workflow run
 ```
 
 A job that sets no timeout produces a report like this:

package/docs/gates/checks-frontend-syntax.md

@@ -54,14 +54,14 @@ The builder changes four of the shared config's rules:
 - In an `.html` or `.astro` file, `declaration-block-single-line-max-declarations` is off, since a `style` attribute is one line.
 
 The comment rule refuses every comment but a sourcemap `/*# */` one, which stylelint passes to keep the map.
-CSS repetition is not a family of this gate: a repository adds `"css"` to `format` in `.jscpd.json`, and [checks-repetition](checks-repetition.md) then fails at night on every repeated line a stylesheet still holds.
+CSS repetition is not a family of this gate: a repository adds `"css"` to `format` in `.jscpd.json`, and [checks-repetition](checks-repetition.md) then fails on the whole-tree run on every repeated line a stylesheet still holds.
 A stylesheet's length is not a family of this gate either, and [checks-css-size](checks-css-size.md) fails one that holds more than 400 lines.
 
 ### What no comment turns off
 
 It sets stylelint's `ignoreDisables`, so a `stylelint-disable` comment silences nothing in either run, and [checks-comment-gate](checks-comment-gate.md) refuses one on the line that adds it.
 A repository adopts a family over existing problems by counting them in `stylelint-suppressions.json` with `--suppress`.
-stylelint lets a file and rule through while its problems stay within the count, and the nightly [checks-suppressions-ratchet](checks-suppressions-ratchet.md) fails on every count still present until it is removed.
+stylelint lets a file and rule through while its problems stay within the count, and [checks-suppressions-ratchet](checks-suppressions-ratchet.md) fails on every count still present on the whole-tree run until it is removed.
 `--suppress` counts only what the repository run reports, and a file that does not parse still fails in the kit run.
 
 ### Files

package/docs/gates/checks-lint-coverage.md

@@ -53,7 +53,7 @@ lint-coverage: the program tsconfig.json builds holds the ts-reset rules is-arra
 
 ## When it runs
 
-`checks-lint --night` runs it nightly when the repository tracks a `.ts`, `.tsx` or `.astro` file.
+`checks-lint --whole-tree` runs it on every whole-tree run when the repository tracks a `.ts`, `.tsx` or `.astro` file.
 No pull request run selects it.
 
 ## Related topics

package/docs/gates/checks-lint.md

@@ -9,7 +9,7 @@ audience: consumers
 ## What it checks
 
 It runs the gates under [What runs](../bins.md#what-runs), each in its own process.
-With `--night` it runs the four nightly gates instead.
+With `--whole-tree` it runs the four whole-tree gates instead.
 It scopes the run to the gates the change reaches, and the full run stays the fallback.
 Applicability below selects the full run, and a scoped or desk run selects a subset.
 A Markdown change runs the range gates plus `checks-copy`.
@@ -32,7 +32,7 @@ A local run with `GITHUB_BASE_REF` set starts at that branch on `origin` instead
 A clone with no remote tracking refs checks `HEAD` alone.
 On a pull request the range ends at the event's head commit and starts at its merge base with the event's base branch.
 Tree gates read the working tree rather than the range.
-With `--night` the range gates read the whole tree at `HEAD` instead of a range.
+With `--whole-tree` the range gates read the whole tree at `HEAD` instead of a range.
 
 ## Arguments
 
@@ -40,13 +40,13 @@ With `--night` the range gates read the whole tree at `HEAD` instead of a range.
 checks-lint
 checks-lint [--full | --desk]
 checks-lint [--full | --desk] <base-ref> <head-ref>
-checks-lint --night
+checks-lint --whole-tree
 ```
 
 With two arguments, the base and head override range discovery.
 `--full` forces the unscoped run.
 `--desk` runs the fast tree gates.
-With `--night`, it takes no other arguments and runs the four nightly gates over the whole tree.
+With `--whole-tree`, it takes no other arguments and runs the four whole-tree gates over the whole tree.
 
 ## Exit codes
 
@@ -73,7 +73,7 @@ A repository runs it from `bun run lint` in a pull request workflow that fetches
 It leaves out the TypeScript gates while the repository tracks no TypeScript file, except that `checks-lint-coverage` and `checks-graphwalk` run when it tracks an `.astro` file.
 It never runs `checks-browser`, which a product runs after it builds its site.
 A pull request run scopes the gates to the change.
-A repository runs the four nightly gates from its night-run workflow with `checks-lint --night` over the whole tree.
+A repository that adds a whole-tree-run workflow runs the four whole-tree gates from it with `checks-lint --whole-tree` over the whole tree.
 
 ## Related topics
 

package/docs/gates/checks-mutation-compare.md

@@ -69,7 +69,7 @@ mutation-compare: REGRESSION (1 mutant(s))
 
 Only a CI step the repository writes runs it.
 A person starts that step by hand on a branch, and no pull request triggers it or waits for it.
-[checks-night-run](checks-night-run.md) judges the mutation score of `main` each night and opens an issue for each file whose score fell.
+[checks-whole-tree-run](checks-whole-tree-run.md) judges the mutation score of `main` on each whole-tree run and opens an issue for each file whose score fell.
 A repository runs it with `--advisory`, so the comparison stays advisory.
 Its lines land only in the CI log.
 A full sweep runs in CI and never on a laptop.
@@ -145,5 +145,5 @@ The job never reads `CI_RUNS_ON`, so an override that moves a repository's other
 
 - [checks-mutation](checks-mutation.md)
 - [checks-mutation-scope](checks-mutation-scope.md)
-- [checks-night-run](checks-night-run.md)
+- [checks-whole-tree-run](checks-whole-tree-run.md)
 - [checks-test-layout](checks-test-layout.md)

package/docs/gates/checks-quarantine-clock.md

@@ -30,7 +30,7 @@ checks-quarantine-clock --whole-tree <head-ref>
 
 With two arguments it judges the head, and the base must resolve but changes nothing.
 With one it judges that commit, including a repository's first commit.
-With `--whole-tree` it judges the named head, which is the form `checks-lint --night` runs.
+With `--whole-tree` it judges the named head, which is the form `checks-lint --whole-tree` runs.
 
 ## Exit codes
 
@@ -49,7 +49,7 @@ quarantine-clock: 1 test(s) in tests/quarantine/ is past 30 days; fix each and m
 
 ## When it runs
 
-`checks-lint --night` runs it nightly in every repository, as [checks-lint](checks-lint.md) says.
+`checks-lint --whole-tree` runs it on every whole-tree run in every repository, as [checks-lint](checks-lint.md) says.
 A repository with no test file under `tests/quarantine/` passes with nothing checked.
 
 ## Related topics

package/docs/gates/checks-repetition.md

@@ -12,7 +12,7 @@ The gate runs jscpd at 50 tokens and 5 lines against the base and head revisions
 It compares repeated lines for each file, so a decrease in another file never offsets a rise.
 It follows an edited rename back to the original file.
 A file that repeats lines without a rise is advisory.
-At night `checks-lint --night` scans the head alone with no base, so every file that repeats lines at the head fails until the repetition is removed, and no file is advisory.
+On the whole-tree run `checks-lint --whole-tree` scans the head alone with no base, so every file that repeats lines at the head fails until the repetition is removed, and no file is advisory.
 A block two bins need goes into a module both import, as `rangeFromArgs` and `checkoutFiles` in `src/core/git.ts` show.
 
 ## What it reads
@@ -38,7 +38,7 @@ checks-repetition <ref>
 checks-repetition --whole-tree <head-ref>
 ```
 
-With `--whole-tree` it scans the named head alone, which is the form `checks-lint --night` runs.
+With `--whole-tree` it scans the named head alone, which is the form `checks-lint --whole-tree` runs.
 
 ## Exit codes
 
@@ -58,7 +58,7 @@ repetition: 1 file(s) .jscpd.json holds repeat lines at the head, at 50 tokens a
 
 ## When it runs
 
-`checks-lint --night` runs it nightly when the repository tracks a `.ts` or `.tsx` file.
+`checks-lint --whole-tree` runs it on every whole-tree run when the repository tracks a `.ts` or `.tsx` file.
 When the head holds no `.jscpd.json`, the gate reports that no file was measured.
 
 ## Related topics

package/docs/gates/checks-setup.md

@@ -4,7 +4,7 @@ audience: consumers
 ---
 # checks-setup
 
-`checks-setup` writes the kit config, the CI workflow, the night-run workflow and the doc templates into a repository that does not hold them yet.
+`checks-setup` writes the kit config, the CI workflow and the doc templates into a repository that does not hold them yet.
 
 ## What it checks
 
@@ -30,10 +30,8 @@ A newer push to the same pull request cancels the run in progress.
 A `--private` run pins each job to `${{ vars.CI_RUNS_ON || 'ubuntu-latest' }}`.
 Setting the `CI_RUNS_ON` variable to a self-hosted runner label then lands the jobs there.
 A public run pins each job to `ubuntu-latest`.
-It writes `.github/workflows/night-run.yml`, which installs with `bun install --frozen-lockfile` and then runs `bunx checks-lint --night`.
-It runs on manual dispatch alone.
-Its job uses the same runner choice as the CI workflow.
 It copies each kit template under `dist/templates/` into `templates/`, so a new doc file starts from a copy there.
+It copies `dist/templates/agents.md` to `AGENTS.md` and `dist/templates/claude.md` to `CLAUDE.md` when the root lacks them, and keeps either file it finds.
 It names every file it wrote and every file it kept.
 It tells the owner to declare the repository owners in `package.json` `author` or `contributors` before the first commit.
 
@@ -72,6 +70,8 @@ checks-setup: set the CI_RUNS_ON variable to a self-hosted runner label so the n
 
 A repository owner runs it once in a new repository, before the first install.
 Declare the repository owners in `package.json` `author` or `contributors` before the first commit.
+Fill `AGENTS.md` with what an agent cannot infer from the code before the first commit.
+`checks-docs` fails on the unfilled placeholder entry until it is filled.
 Running it again with the same kit version changes nothing.
 A later kit release arrives through [Upgrade the kit](../how-to/upgrade-the-kit.md).
 

package/docs/gates/checks-suppressions-ratchet.md

@@ -11,7 +11,7 @@ audience: consumers
 oxlint accepts whatever `oxlint --suppress-all` writes to `oxlint-suppressions.json`, so raising a count to let a new site through passes the lint.
 stylelint accepts `stylelint-suppressions.json` the same way, and writes it in the same shape, a count per rule per file.
 The ratchet fails naming the suppressions file, the file and the rule of each count that rose or appeared.
-At night `checks-lint --night` compares the head against the empty tree, so every count still present is reported until it is removed.
+On the whole-tree run `checks-lint --whole-tree` compares the head against the empty tree, so every count still present is reported until it is removed.
 A count that fell and an entry that went both pass.
 
 ## What it reads
@@ -29,7 +29,7 @@ checks-suppressions-ratchet --whole-tree <head-ref>
 
 With two arguments it reads the base where the head branched off, at their merge-base, so a count the base branch lowered since does not read as a rise at the head.
 With one it compares that commit with its parent, or with the empty tree for a repository's first commit.
-With `--whole-tree` it compares the named head with the empty tree, which is the form `checks-lint --night` runs.
+With `--whole-tree` it compares the named head with the empty tree, which is the form `checks-lint --whole-tree` runs.
 
 ## Exit codes
 
@@ -49,7 +49,7 @@ suppressions-ratchet: 2 count(s) rose or appeared; fix the site instead of suppr
 
 ## When it runs
 
-`checks-lint --night` runs it nightly in every repository, as [checks-lint](checks-lint.md) says.
+`checks-lint --whole-tree` runs it on every whole-tree run in every repository, as [checks-lint](checks-lint.md) says.
 A repository with neither file passes.
 
 ## Related topics

package/docs/gates/checks-test.md

@@ -147,10 +147,10 @@ A timings option waits for Bun to honour timings under random order.
 ## Arguments
 
 The default command takes no arguments except `--parallel=<workers>`, as [Parallel runs](#parallel-runs) says, `--full` and `--junit=<file>`.
-`--full` runs the full suite outside CI, so a night run covers what a local run skips.
+`--full` runs the full suite outside CI, so a run started by hand covers what a local run skips.
 A `package.json` script never takes `--full`, as [checks-test-layout](checks-test-layout.md) says of `scripts.test`.
 Its named tier options are `--tier=live`, `--tier=pixel`, `--tier=unit` and `--tier=e2e`, and a tier run takes `--parallel=<workers>` too, but not `--full`.
-`--junit=<file>` keeps the JUnit report Bun wrote at `<file>`, whether the tests passed or failed, so a night run hands it to [checks-night-run](checks-night-run.md).
+`--junit=<file>` keeps the JUnit report Bun wrote at `<file>`, whether the tests passed or failed, so a whole-tree run hands it to [checks-whole-tree-run](checks-whole-tree-run.md).
 A `package.json` script never takes `--junit`, as [checks-test-layout](checks-test-layout.md) says of `scripts.test`.
 Each option appears at most once.
 It refuses test filters because every test excluded by a filter would look skipped.
@@ -186,4 +186,4 @@ A repository that tracks no TypeScript source does not need it, as [checks-test-
 - [checks-test-layout](checks-test-layout.md)
 - [checks-flake](checks-flake.md)
 - [checks-quarantine-clock](checks-quarantine-clock.md)
-- [checks-night-run](checks-night-run.md)
+- [checks-whole-tree-run](checks-whole-tree-run.md)