From 6416da2cc579a4729ca3ff6020bff030d80cd887 Mon Sep 17 00:00:00 2001
From: hatayama <booqle@gmail.com>
Date: Tue, 20 Oct 2026 00:46:13 +0900
Subject: [PATCH 1/2] revert: hide compile-check again until its place beside
 compile is settled

ADR 0018 showed the command in --help, uloop list, completion, the
README and skill installs once its miss-side gaps were closed. Those
gaps stay closed, but when an agent should run the offline check
instead of uloop compile is still open, and the next release would
advertise a command whose use is not explained yet. So the command
goes back to routable-but-unlisted, as it was before #3364; nothing
in what it detects changes.

- Hidden: true on the native command entry. Tests pin that
  compile-check stays routable but is left out of listing, completion
  and the unknown-command suggestions; the hidden-probe test no longer
  assumes it is the only hidden entry.
- internal: true on the skill, so skill installs leave it out again.
  The generated .claude and .agents copies are removed, and the
  command's --help no longer points at a skill that is not installed.
- README entries removed, the glossary notes the hidden state, and
  ADR 0018 carries an amendment saying this is not its reversal
  condition and how the amendment is undone.
- Shared release inputs stamped for the common module change.
---
 .agents/skills/uloop-compile-check/SKILL.md   | 123 ------------------
 .../references/full-compiles.md               |  85 ------------
 .claude/skills/uloop-compile-check/SKILL.md   | 123 ------------------
 .../references/full-compiles.md               |  85 ------------
 .../CliOnlyTools~/CompileCheck/Skill/SKILL.md |   1 +
 README.md                                     |   6 +-
 README_ja.md                                  |   6 +-
 cli/common/clicore/command_errors_test.go     |   2 +-
 cli/common/clicore/command_registry.go        |   5 +-
 cli/common/clicore/command_registry_test.go   |  26 +++-
 cli/common/tooldocs/skill_guidance.go         |   7 +-
 cli/common/tooldocs/skill_guidance_test.go    |  10 +-
 .../internal/dispatcher/compile_check_test.go |   7 +-
 .../internal/dispatcher/help_test.go          |  12 +-
 cli/dispatcher/shared-inputs-stamp.json       |   2 +-
 .../internal/projectrunner/list_names_test.go |   4 +-
 cli/project-runner/shared-inputs-stamp.json   |   2 +-
 ...e-check-is-its-own-command-and-is-shown.md |   9 ++
 docs/glossary.md                              |   4 +-
 19 files changed, 61 insertions(+), 458 deletions(-)
 delete mode 100644 .agents/skills/uloop-compile-check/SKILL.md
 delete mode 100644 .agents/skills/uloop-compile-check/references/full-compiles.md
 delete mode 100644 .claude/skills/uloop-compile-check/SKILL.md
 delete mode 100644 .claude/skills/uloop-compile-check/references/full-compiles.md

diff --git a/.agents/skills/uloop-compile-check/SKILL.md b/.agents/skills/uloop-compile-check/SKILL.md
deleted file mode 100644
index c86024e23a..0000000000
--- a/.agents/skills/uloop-compile-check/SKILL.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-name: uloop-compile-check
-description: "Compile C# with the Unity-bundled Roslyn compiler without launching or contacting the Unity Editor; reports errors and warnings only."
----
-
-# uloop compile-check
-
-Compile the project's C# offline, without starting Unity or sending anything to a running Editor.
-It replays the response files Unity wrote during its last build with
-the C# compiler bundled in the Editor install; the output lands in `Library/uloop/compile-check/`
-and is never loaded by Unity.
-
-## When to use
-
-- You want to know whether the code compiles, without starting the Editor or waiting for an import
-  and a domain reload, and the result need not be live in the Editor yet.
-
-## When not to use
-
-- You want the change reflected in the Editor (play mode, tests, a tool call): run `uloop compile`.
-- You just added or removed an `.asmdef`, added a reference to one, or changed scripting defines:
-  run `uloop compile` once first; the response files describe the previous build only, so the run
-  is refused with `COMPILE_CHECK_UNITY_BUILD_REQUIRED`.
-- The project has no `Library` yet (a fresh clone, or an Editor that has never opened it): there is
-  no build to replay, so the run is refused with the same code. Let Unity build once, with
-  `uloop launch` or headless (`<Unity executable> -batchmode -nographics -quit -projectPath <dir>`).
-  After that one build, compile-check works without the Editor until an `.asmdef` or build-setting
-  change makes it ask for another (see Limitations).
-
-## Usage
-
-```bash
-uloop compile-check
-uloop compile-check --all --project-path /path/to/project
-```
-
-By default it compiles the assemblies whose sources changed since the last Unity build, plus every
-assembly that references one of them. Independent assemblies compile at the same time (`--jobs`
-caps how many; `--jobs 1` is sequential). An assembly whose inputs are exactly as the previous run
-read them is not compiled again: its recorded diagnostics are reported, errors included. `--all`
-compiles every assembly from scratch, the way out if a reused result ever looks wrong.
-
-Once compile-check has compiled a large assembly in full without errors, an edit that keeps every
-declaration is checked on its changed files only, in a few seconds, and the assembly is listed in
-`FastCheckedAssemblies`. Compiled in full instead (`FastPathFallbacks` says why when the check was
-tried): the first run after a Unity build; a run that adds, removes or renames a `.cs` file, or
-changes more than 30 files; an edit that changes a declaration (a `using` directive counts); the
-first run after a full compile that had errors; and an assembly compiled only because one it
-references changed, which records no baseline. A change to the public surface also compiles the
-dependents that can see it: those that write a changed name, or all of them when no name carries the
-change; `SurfaceChecks` says which and why. Details and times: `references/full-compiles.md`.
-
-Full compiles run the project's analyzers with the response file's flags, `-warnaserror` included.
-The changed-files check skips the assembly-wide rules in `FastChecks[].UncheckedCodes`, so run once
-with `--full` before finishing: it compiles in full what differs from its last full compile and
-reuses the rest; right after a run that compiled in full it takes about a second. When warnings are
-errors, such a rule (CS0414, for example) can fail that run only. A run that stops on declaration
-errors (an unknown type, say) reports neither body errors nor analyzer diagnostics: fix them and run
-again.
-
-## Parameters
-
-| Parameter | Type | Description |
-|-----------|------|-------------|
-| `--all` | flag | Compile every assembly instead of only the changed ones and their dependents |
-| `--full` | flag | Compile changed assemblies in full instead of checking only their changed files |
-| `--editor-version <version>` | string | Use this Unity Editor version's compiler instead of ProjectVersion.txt |
-| `--jobs <N>` | number | Compile up to N assemblies at once (default: half the CPUs, at least 1; `1` compiles sequentially) |
-| `--max-depth <N>` | number | Search depth when locating the project (default: 3, -1 for unlimited) |
-| `--project-path <path>` | string | Target another Unity project instead of the current directory |
-
-## Output
-
-A JSON payload; an empty list means the case did not occur in this run:
-
-- `Success`: whether the compile produced no errors
-- `ErrorCount`, `WarningCount`: totals across every compiled and reused assembly
-- `Errors`, `Warnings`: each with `Message`, `Code`, `File`, `Line`, `Column`, `Assembly`
-- `CompiledAssemblies`: compiled by this run, in dependency order
-- `ReusedAssemblies`: reported from the previous run's result, without compiling
-- `BlockedAssemblies`: not compiled because an assembly they reference has errors, as in Unity's
-  build; fix those and run again
-- `FastCheckedAssemblies`: checked on their changed files only
-- `FastChecks`: per fast-checked assembly, `ChangedFiles`, `UncheckedCodes` (rules only `--full` runs),
-  `GeneratorsNotRerun`, and `Reused` (the same edit's previous check, reported again)
-- `FastPathFallbacks`: `Assembly` and `Reason` for each assembly compiled in full instead
-- `FastPathBaselineNotes`: `Assembly` and `Reason` for each successful full compile that left no
-  baseline for the next check
-- `SurfaceChecks`: per assembly others reference that this run compiled, replayed or fast-checked
-  without errors: `Kept`, or the `ChangedNames` a dependent must write to be affected (`Unnamed`
-  says why no name tells the change), and the compiled `Dependents` it reached, each with the
-  `Name` that selected it
-- `SkippedAssemblies`: how many were left out because nothing they can see changed
-- `ResponseFileSet`, `ProjectRoot`: the Bee build the run replayed and the resolved project root
-- `Message`: one-line summary
-- `NextActions`: the next step (fix and rerun, `--full` for the skipped rules, or `uloop compile` to
-  make the result live); empty when nothing changed
-
-The process exits 1 when `ErrorCount` is greater than zero, and when the command itself fails, such
-as with `COMPILE_CHECK_UNITY_BUILD_REQUIRED`; then no payload is printed and the error, with its
-`ErrorCode`, goes to stderr. One compile-check runs per project at a time; a second waits up to
-five minutes, then fails with `COMPILE_CHECK_PROJECT_BUSY`. Run it once more rather than retrying in
-a loop.
-
-## Limitations
-
-- It replays the last Unity build's response files. A new or deleted `.asmdef`, a changed `.asmdef`
-  reference, an `.asmdef` that stopped building for the Editor, or a newly required precompiled
-  reference stops the run and asks for `uloop compile`.
-- Build settings are compared against a record the first run after a Unity build writes: a
-  removed scripting define, a changed `csc.rsp`, `defineConstraints`, `versionDefines`,
-  `packages-lock.json` or `manifest.json` stops the run, and a scripting define the last build lacks
-  stops it when `ProjectSettings.asset` was saved after that build. A change made before that first
-  run (other than an added define) is not seen, so run `uloop compile` after one. Under a Unity 6
-  build profile that overrides Player Settings or carries its own defines, only the global
-  ProjectSettings defines are compared.
-- A reference removed from an `.asmdef` stops the run too; the four references Unity adds on its own
-  are allowed, and a reference that matches no `.asmdef` in the project is not judged.
-- A new `.cs` file outside every `.asmdef` goes to `Assembly-CSharp` or a sibling by Unity's path
-  rules (`Editor` folders, `Assets/Plugins`); if the last build did not produce that assembly, the run
-  stops and asks for `uloop compile`. A new script in a package folder without an `.asmdef` is not seen.
-- A generator that reads a referenced assembly is not rerun for a change in that assembly; run
-  `uloop compile` after one.
diff --git a/.agents/skills/uloop-compile-check/references/full-compiles.md b/.agents/skills/uloop-compile-check/references/full-compiles.md
deleted file mode 100644
index a671cf125c..0000000000
--- a/.agents/skills/uloop-compile-check/references/full-compiles.md
+++ /dev/null
@@ -1,85 +0,0 @@
-# When compile-check compiles in full
-
-Read this when a run took longer than you expected, when an assembly shows up in
-`FastPathFallbacks`, or when you want to know what the next edit will cost.
-
-The changed-files check applies to assemblies with at least 300 sources, once compile-check has
-compiled that assembly in full without errors and kept a baseline, and at most 30 of its files
-changed. Smaller assemblies are always compiled in full.
-
-## What an edit costs
-
-| Edit | What runs | Typical time |
-|------|-----------|--------------|
-| A body-only edit of up to 30 files in a large assembly with a baseline | Changed-files check | A few seconds |
-| A body-only edit of more than 30 files | Full compile (`FastPathFallbacks`: too many changed files) | As for a full compile |
-| A new, deleted or renamed `.cs` file | Full compile of the assembly | About Unity's compile of it, without the import and the domain reload |
-| A declaration change (a member, a signature, a `using` directive) | Full compile, plus the dependents that can see the change | The assembly, then its dependents |
-| The first run after a Unity build | Full compile of every changed assembly | As for a full compile |
-| The first run after a full compile that had errors | Full compile (no baseline was recorded) | As for a full compile |
-| An assembly compiled only because a reference changed | Full compile now, and again on its next body-only edit (it records no baseline) | As for a full compile |
-| `--full` | In full: whatever differs from its last full compile - the assemblies fast-checked since, the dependents their rebuilt reference assemblies reach, and anything edited since the last run; the rest reused | As for a full compile of those; about a second right after a run that compiled in full |
-| `--all` | Every assembly | The whole build |
-
-## Dependents
-
-When an assembly compiles in full, its public surface (its reference assembly) is compared with the
-one from the last Unity build, not with the previous compile-check run; a surface that differs from
-Unity's keeps compiling its dependents until Unity builds again. Only the dependents that write a
-name the change touches are compiled; adding a member counts the type's name among the changed
-names. A change a dependent can feel without writing any name is unnamed and compiles every
-dependent: a new base type or interface, an operator, an added abstract member, a member C# binds by
-pattern (`GetEnumerator`, `Deconstruct` and the like), among others. The output's `SurfaceChecks`
-lists, per assembly that others reference, the verdict, the changed names or the unnamed reason, and
-the compiled dependents the change reached, with the name that selected each.
-
-An assembly starts once every assembly it references that this run also compiles has finished. An
-assembly selected for its own sources, or a dependent already known to need compiling, starts
-sooner: as soon as every assembly it references that was selected for its own sources has finished.
-The dependents it references that are still compiling are assumed to keep Unity's public surface;
-when one of them turns out to have changed it, the assembly is compiled again after they finish, at
-most twice per run. A dependent whose recorded result may still apply once those finish waits for
-them instead.
-
-## Baselines and `no baseline` reasons
-
-A full compile that succeeds records the baseline the next changed-files check is made against. When
-there is none, `FastPathFallbacks[].Reason` says why:
-
-- `no baseline: no full compile of this assembly is on record`: no full compile has run yet, or an
-  input changed while it ran (`FastPathBaselineNotes` of that run says which).
-- `no baseline: the last full compile (at <time>) had errors; the first full compile without errors
-  records one`: a failed full compile drops the baseline an earlier one left.
-- `no baseline: the last full compile (at <time>) did not record one`: `FastPathBaselineNotes` of
-  that run says why, or the assembly was compiled only because a reference changed.
-- `no baseline: it was recorded by another version of compile-check`: the baseline was written by a
-  different compile-check build.
-
-`<time>` is when that full compile finished, in UTC; it can be from an earlier session or from
-before a Unity build in between.
-
-In every case the next full compile that succeeds records one, and body-only edits after it are
-fast-checked.
-
-A run with `--all` records baselines too. Under `--all`, a reference whose rebuilt API differs from
-Unity's build is read from this check's output; when a later run leaves that reference out and so
-reads Unity's build again, the first body edit of an assembly referencing it is compiled in full,
-with `inputs other than source contents changed: references` as the reason.
-
-## Runs that stop on declaration errors
-
-A run whose assembly has declaration errors, such as an unknown type or an ambiguous name, reports
-those errors only: the errors inside method bodies, the warnings of that stage (which `-warnaserror`
-would turn into errors) and the analyzer diagnostics are not reported until the declaration errors
-are fixed. Such a run is also faster than a full compile. Fix the declaration errors and run again.
-
-## Analyzers
-
-A full compile uses the response file as Unity wrote it, its `-analyzer:` entries and flags such as
-`-warnaserror` included; compile-check adds only the output folder for generated files. The
-changed-files check skips the rules listed in `FastChecks[].UncheckedCodes`: those of CS0067,
-CS0169, CS0414 and CS0649 that the project does not suppress, and the rules of analyzers that look
-at the whole compilation. Run once with `--full` before finishing to cover them. That run compiles
-in full whatever differs from its last full compile - the assemblies fast-checked since, the
-dependents their rebuilt reference assemblies reach, and anything edited since the last run - and
-reuses the rest; right after a run that compiled in full it takes about a second.
diff --git a/.claude/skills/uloop-compile-check/SKILL.md b/.claude/skills/uloop-compile-check/SKILL.md
deleted file mode 100644
index c86024e23a..0000000000
--- a/.claude/skills/uloop-compile-check/SKILL.md
+++ /dev/null
@@ -1,123 +0,0 @@
----
-name: uloop-compile-check
-description: "Compile C# with the Unity-bundled Roslyn compiler without launching or contacting the Unity Editor; reports errors and warnings only."
----
-
-# uloop compile-check
-
-Compile the project's C# offline, without starting Unity or sending anything to a running Editor.
-It replays the response files Unity wrote during its last build with
-the C# compiler bundled in the Editor install; the output lands in `Library/uloop/compile-check/`
-and is never loaded by Unity.
-
-## When to use
-
-- You want to know whether the code compiles, without starting the Editor or waiting for an import
-  and a domain reload, and the result need not be live in the Editor yet.
-
-## When not to use
-
-- You want the change reflected in the Editor (play mode, tests, a tool call): run `uloop compile`.
-- You just added or removed an `.asmdef`, added a reference to one, or changed scripting defines:
-  run `uloop compile` once first; the response files describe the previous build only, so the run
-  is refused with `COMPILE_CHECK_UNITY_BUILD_REQUIRED`.
-- The project has no `Library` yet (a fresh clone, or an Editor that has never opened it): there is
-  no build to replay, so the run is refused with the same code. Let Unity build once, with
-  `uloop launch` or headless (`<Unity executable> -batchmode -nographics -quit -projectPath <dir>`).
-  After that one build, compile-check works without the Editor until an `.asmdef` or build-setting
-  change makes it ask for another (see Limitations).
-
-## Usage
-
-```bash
-uloop compile-check
-uloop compile-check --all --project-path /path/to/project
-```
-
-By default it compiles the assemblies whose sources changed since the last Unity build, plus every
-assembly that references one of them. Independent assemblies compile at the same time (`--jobs`
-caps how many; `--jobs 1` is sequential). An assembly whose inputs are exactly as the previous run
-read them is not compiled again: its recorded diagnostics are reported, errors included. `--all`
-compiles every assembly from scratch, the way out if a reused result ever looks wrong.
-
-Once compile-check has compiled a large assembly in full without errors, an edit that keeps every
-declaration is checked on its changed files only, in a few seconds, and the assembly is listed in
-`FastCheckedAssemblies`. Compiled in full instead (`FastPathFallbacks` says why when the check was
-tried): the first run after a Unity build; a run that adds, removes or renames a `.cs` file, or
-changes more than 30 files; an edit that changes a declaration (a `using` directive counts); the
-first run after a full compile that had errors; and an assembly compiled only because one it
-references changed, which records no baseline. A change to the public surface also compiles the
-dependents that can see it: those that write a changed name, or all of them when no name carries the
-change; `SurfaceChecks` says which and why. Details and times: `references/full-compiles.md`.
-
-Full compiles run the project's analyzers with the response file's flags, `-warnaserror` included.
-The changed-files check skips the assembly-wide rules in `FastChecks[].UncheckedCodes`, so run once
-with `--full` before finishing: it compiles in full what differs from its last full compile and
-reuses the rest; right after a run that compiled in full it takes about a second. When warnings are
-errors, such a rule (CS0414, for example) can fail that run only. A run that stops on declaration
-errors (an unknown type, say) reports neither body errors nor analyzer diagnostics: fix them and run
-again.
-
-## Parameters
-
-| Parameter | Type | Description |
-|-----------|------|-------------|
-| `--all` | flag | Compile every assembly instead of only the changed ones and their dependents |
-| `--full` | flag | Compile changed assemblies in full instead of checking only their changed files |
-| `--editor-version <version>` | string | Use this Unity Editor version's compiler instead of ProjectVersion.txt |
-| `--jobs <N>` | number | Compile up to N assemblies at once (default: half the CPUs, at least 1; `1` compiles sequentially) |
-| `--max-depth <N>` | number | Search depth when locating the project (default: 3, -1 for unlimited) |
-| `--project-path <path>` | string | Target another Unity project instead of the current directory |
-
-## Output
-
-A JSON payload; an empty list means the case did not occur in this run:
-
-- `Success`: whether the compile produced no errors
-- `ErrorCount`, `WarningCount`: totals across every compiled and reused assembly
-- `Errors`, `Warnings`: each with `Message`, `Code`, `File`, `Line`, `Column`, `Assembly`
-- `CompiledAssemblies`: compiled by this run, in dependency order
-- `ReusedAssemblies`: reported from the previous run's result, without compiling
-- `BlockedAssemblies`: not compiled because an assembly they reference has errors, as in Unity's
-  build; fix those and run again
-- `FastCheckedAssemblies`: checked on their changed files only
-- `FastChecks`: per fast-checked assembly, `ChangedFiles`, `UncheckedCodes` (rules only `--full` runs),
-  `GeneratorsNotRerun`, and `Reused` (the same edit's previous check, reported again)
-- `FastPathFallbacks`: `Assembly` and `Reason` for each assembly compiled in full instead
-- `FastPathBaselineNotes`: `Assembly` and `Reason` for each successful full compile that left no
-  baseline for the next check
-- `SurfaceChecks`: per assembly others reference that this run compiled, replayed or fast-checked
-  without errors: `Kept`, or the `ChangedNames` a dependent must write to be affected (`Unnamed`
-  says why no name tells the change), and the compiled `Dependents` it reached, each with the
-  `Name` that selected it
-- `SkippedAssemblies`: how many were left out because nothing they can see changed
-- `ResponseFileSet`, `ProjectRoot`: the Bee build the run replayed and the resolved project root
-- `Message`: one-line summary
-- `NextActions`: the next step (fix and rerun, `--full` for the skipped rules, or `uloop compile` to
-  make the result live); empty when nothing changed
-
-The process exits 1 when `ErrorCount` is greater than zero, and when the command itself fails, such
-as with `COMPILE_CHECK_UNITY_BUILD_REQUIRED`; then no payload is printed and the error, with its
-`ErrorCode`, goes to stderr. One compile-check runs per project at a time; a second waits up to
-five minutes, then fails with `COMPILE_CHECK_PROJECT_BUSY`. Run it once more rather than retrying in
-a loop.
-
-## Limitations
-
-- It replays the last Unity build's response files. A new or deleted `.asmdef`, a changed `.asmdef`
-  reference, an `.asmdef` that stopped building for the Editor, or a newly required precompiled
-  reference stops the run and asks for `uloop compile`.
-- Build settings are compared against a record the first run after a Unity build writes: a
-  removed scripting define, a changed `csc.rsp`, `defineConstraints`, `versionDefines`,
-  `packages-lock.json` or `manifest.json` stops the run, and a scripting define the last build lacks
-  stops it when `ProjectSettings.asset` was saved after that build. A change made before that first
-  run (other than an added define) is not seen, so run `uloop compile` after one. Under a Unity 6
-  build profile that overrides Player Settings or carries its own defines, only the global
-  ProjectSettings defines are compared.
-- A reference removed from an `.asmdef` stops the run too; the four references Unity adds on its own
-  are allowed, and a reference that matches no `.asmdef` in the project is not judged.
-- A new `.cs` file outside every `.asmdef` goes to `Assembly-CSharp` or a sibling by Unity's path
-  rules (`Editor` folders, `Assets/Plugins`); if the last build did not produce that assembly, the run
-  stops and asks for `uloop compile`. A new script in a package folder without an `.asmdef` is not seen.
-- A generator that reads a referenced assembly is not rerun for a change in that assembly; run
-  `uloop compile` after one.
diff --git a/.claude/skills/uloop-compile-check/references/full-compiles.md b/.claude/skills/uloop-compile-check/references/full-compiles.md
deleted file mode 100644
index a671cf125c..0000000000
--- a/.claude/skills/uloop-compile-check/references/full-compiles.md
+++ /dev/null
@@ -1,85 +0,0 @@
-# When compile-check compiles in full
-
-Read this when a run took longer than you expected, when an assembly shows up in
-`FastPathFallbacks`, or when you want to know what the next edit will cost.
-
-The changed-files check applies to assemblies with at least 300 sources, once compile-check has
-compiled that assembly in full without errors and kept a baseline, and at most 30 of its files
-changed. Smaller assemblies are always compiled in full.
-
-## What an edit costs
-
-| Edit | What runs | Typical time |
-|------|-----------|--------------|
-| A body-only edit of up to 30 files in a large assembly with a baseline | Changed-files check | A few seconds |
-| A body-only edit of more than 30 files | Full compile (`FastPathFallbacks`: too many changed files) | As for a full compile |
-| A new, deleted or renamed `.cs` file | Full compile of the assembly | About Unity's compile of it, without the import and the domain reload |
-| A declaration change (a member, a signature, a `using` directive) | Full compile, plus the dependents that can see the change | The assembly, then its dependents |
-| The first run after a Unity build | Full compile of every changed assembly | As for a full compile |
-| The first run after a full compile that had errors | Full compile (no baseline was recorded) | As for a full compile |
-| An assembly compiled only because a reference changed | Full compile now, and again on its next body-only edit (it records no baseline) | As for a full compile |
-| `--full` | In full: whatever differs from its last full compile - the assemblies fast-checked since, the dependents their rebuilt reference assemblies reach, and anything edited since the last run; the rest reused | As for a full compile of those; about a second right after a run that compiled in full |
-| `--all` | Every assembly | The whole build |
-
-## Dependents
-
-When an assembly compiles in full, its public surface (its reference assembly) is compared with the
-one from the last Unity build, not with the previous compile-check run; a surface that differs from
-Unity's keeps compiling its dependents until Unity builds again. Only the dependents that write a
-name the change touches are compiled; adding a member counts the type's name among the changed
-names. A change a dependent can feel without writing any name is unnamed and compiles every
-dependent: a new base type or interface, an operator, an added abstract member, a member C# binds by
-pattern (`GetEnumerator`, `Deconstruct` and the like), among others. The output's `SurfaceChecks`
-lists, per assembly that others reference, the verdict, the changed names or the unnamed reason, and
-the compiled dependents the change reached, with the name that selected each.
-
-An assembly starts once every assembly it references that this run also compiles has finished. An
-assembly selected for its own sources, or a dependent already known to need compiling, starts
-sooner: as soon as every assembly it references that was selected for its own sources has finished.
-The dependents it references that are still compiling are assumed to keep Unity's public surface;
-when one of them turns out to have changed it, the assembly is compiled again after they finish, at
-most twice per run. A dependent whose recorded result may still apply once those finish waits for
-them instead.
-
-## Baselines and `no baseline` reasons
-
-A full compile that succeeds records the baseline the next changed-files check is made against. When
-there is none, `FastPathFallbacks[].Reason` says why:
-
-- `no baseline: no full compile of this assembly is on record`: no full compile has run yet, or an
-  input changed while it ran (`FastPathBaselineNotes` of that run says which).
-- `no baseline: the last full compile (at <time>) had errors; the first full compile without errors
-  records one`: a failed full compile drops the baseline an earlier one left.
-- `no baseline: the last full compile (at <time>) did not record one`: `FastPathBaselineNotes` of
-  that run says why, or the assembly was compiled only because a reference changed.
-- `no baseline: it was recorded by another version of compile-check`: the baseline was written by a
-  different compile-check build.
-
-`<time>` is when that full compile finished, in UTC; it can be from an earlier session or from
-before a Unity build in between.
-
-In every case the next full compile that succeeds records one, and body-only edits after it are
-fast-checked.
-
-A run with `--all` records baselines too. Under `--all`, a reference whose rebuilt API differs from
-Unity's build is read from this check's output; when a later run leaves that reference out and so
-reads Unity's build again, the first body edit of an assembly referencing it is compiled in full,
-with `inputs other than source contents changed: references` as the reason.
-
-## Runs that stop on declaration errors
-
-A run whose assembly has declaration errors, such as an unknown type or an ambiguous name, reports
-those errors only: the errors inside method bodies, the warnings of that stage (which `-warnaserror`
-would turn into errors) and the analyzer diagnostics are not reported until the declaration errors
-are fixed. Such a run is also faster than a full compile. Fix the declaration errors and run again.
-
-## Analyzers
-
-A full compile uses the response file as Unity wrote it, its `-analyzer:` entries and flags such as
-`-warnaserror` included; compile-check adds only the output folder for generated files. The
-changed-files check skips the rules listed in `FastChecks[].UncheckedCodes`: those of CS0067,
-CS0169, CS0414 and CS0649 that the project does not suppress, and the rules of analyzers that look
-at the whole compilation. Run once with `--full` before finishing to cover them. That run compiles
-in full whatever differs from its last full compile - the assemblies fast-checked since, the
-dependents their rebuilt reference assemblies reach, and anything edited since the last run - and
-reuses the rest; right after a run that compiled in full it takes about a second.
diff --git a/Packages/src/Editor/CliOnlyTools~/CompileCheck/Skill/SKILL.md b/Packages/src/Editor/CliOnlyTools~/CompileCheck/Skill/SKILL.md
index c86024e23a..5314200a91 100644
--- a/Packages/src/Editor/CliOnlyTools~/CompileCheck/Skill/SKILL.md
+++ b/Packages/src/Editor/CliOnlyTools~/CompileCheck/Skill/SKILL.md
@@ -1,6 +1,7 @@
 ---
 name: uloop-compile-check
 description: "Compile C# with the Unity-bundled Roslyn compiler without launching or contacting the Unity Editor; reports errors and warnings only."
+internal: true
 ---
 
 # uloop compile-check
diff --git a/README.md b/README.md
index 6c21167817..e80a7d609e 100644
--- a/README.md
+++ b/README.md
@@ -184,14 +184,13 @@ That's it! After installing Skills, LLM tools can automatically handle instructi
 
 
 <details>
-<summary>All 23 Bundled Skills</summary>
+<summary>All 22 Bundled Skills</summary>
 
 - `/uloop-launch` - Launch Unity with correct version
 - `/uloop-status` - Check whether Unity can take a command now
 - `/uloop-cancel` - Cancel the command Unity is running now, when BUSY keeps rejecting commands
 - `/uloop-compile` - Execute compilation
 - `/uloop-verify-project` - Check .meta files, GUIDs, conflict markers, and the package manifest without Unity
-- `/uloop-compile-check` - Check that C# compiles without launching or contacting Unity
 - `/uloop-get-logs` - Get console logs
 - `/uloop-run-tests` - Run tests
 - `/uloop-hot-reload` - Apply method-body changes to running code instantly, without recompiling
@@ -233,9 +232,6 @@ uloop launch -r
 # Check .meta files, GUIDs, and conflict markers without Unity
 uloop verify-project
 
-# Check that C# compiles without launching or contacting Unity (replays the last Unity build)
-uloop compile-check
-
 # Execute compilation
 uloop compile
 
diff --git a/README_ja.md b/README_ja.md
index 5c7f203cb5..acb2d652a2 100644
--- a/README_ja.md
+++ b/README_ja.md
@@ -184,14 +184,13 @@ V2 のプロジェクトの Settings ウィンドウで **Update CLI** や **Dow
 
 
 <details>
-<summary>バンドルされている全23個のSkills一覧</summary>
+<summary>バンドルされている全22個のSkills一覧</summary>
 
 - `/uloop-launch` - 正しいバージョンでUnityを起動
 - `/uloop-status` - Unityが今コマンドを受け付けられるかを確認
 - `/uloop-cancel` - BUSYでコマンドが拒否され続けるときに、Unityが実行中のコマンドをキャンセル
 - `/uloop-compile` - コンパイルの実行
 - `/uloop-verify-project` - Unityを起動せずに.metaファイル・GUID・コンフリクトマーカー・パッケージmanifestを検査
-- `/uloop-compile-check` - Unityを起動・接続せずにC#がコンパイルできるかを確認
 - `/uloop-get-logs` - Consoleログの取得
 - `/uloop-run-tests` - テストの実行
 - `/uloop-hot-reload` - メソッド本体の変更を再コンパイルなしで実行中のコードへ即時適用
@@ -233,9 +232,6 @@ uloop launch -r
 # Unityを起動せずに.metaファイル・GUID・コンフリクトマーカーを検査
 uloop verify-project
 
-# Unityを起動・接続せずにC#がコンパイルできるかを確認（最後のUnityビルドを再生する）
-uloop compile-check
-
 # コンパイルを実行
 uloop compile
 
diff --git a/cli/common/clicore/command_errors_test.go b/cli/common/clicore/command_errors_test.go
index b0a5f971d3..1f107b1786 100644
--- a/cli/common/clicore/command_errors_test.go
+++ b/cli/common/clicore/command_errors_test.go
@@ -9,7 +9,7 @@ import (
 func TestAvailableCommandNamesIncludesBuiltIns(t *testing.T) {
 	// Verifies unknown-command suggestions include visible built-in CLI commands before cached tools.
 	names := availableCommandNames(ToolsCache{})
-	expectedBuiltIns := []string{"launch", "compile-check", "verify-project", "list", "sync", "focus-window", "await-pause-point", "pause-point-status", "set-code-optimization", "status", "cancel", "skills", "package", "install", "update", "uninstall"}
+	expectedBuiltIns := []string{"launch", "verify-project", "list", "sync", "focus-window", "await-pause-point", "pause-point-status", "set-code-optimization", "status", "cancel", "skills", "package", "install", "update", "uninstall"}
 	for index, expected := range expectedBuiltIns {
 		if names[index] != expected {
 			t.Fatalf("built-in command mismatch: %#v", names)
diff --git a/cli/common/clicore/command_registry.go b/cli/common/clicore/command_registry.go
index c0f4eaef87..db60371701 100644
--- a/cli/common/clicore/command_registry.go
+++ b/cli/common/clicore/command_registry.go
@@ -25,7 +25,6 @@ type NativeCommandEntry struct {
 	Description string
 	Owner       CommandOwner
 	// Hidden keeps a command routable while leaving it out of help, `list --names`, and completion.
-	// No command sets it today; it stays for the next command that must run before it is advertised.
 	Hidden bool
 }
 
@@ -38,7 +37,9 @@ const (
 
 var NativeCommands = []NativeCommandEntry{
 	{Name: LaunchCommandName, Description: "Open this Unity project with the matching Editor version", Owner: DispatcherOwned},
-	{Name: CompileCheckCommandName, Description: "Compile changed assemblies with the Editor's bundled C# compiler without launching Unity", Owner: DispatcherOwned},
+	// Why compile-check is hidden: its place beside `uloop compile` is not settled, so it stays
+	// runnable for development while nothing user-facing advertises it (ADR 0018, amendment).
+	{Name: CompileCheckCommandName, Description: "Compile changed assemblies with the Editor's bundled C# compiler without launching Unity", Owner: DispatcherOwned, Hidden: true},
 	{Name: VerifyProjectCommandName, Description: "Check .meta files, GUIDs, merge conflict markers, and Packages/manifest.json without Unity", Owner: DispatcherOwned},
 	{Name: "list", Description: "Show Unity tools currently exposed by the Editor", Owner: RunnerOwned},
 	{Name: "sync", Description: "Refresh .uloop/tools.json from the running Editor", Owner: RunnerOwned},
diff --git a/cli/common/clicore/command_registry_test.go b/cli/common/clicore/command_registry_test.go
index 16c29b7af2..481203c6f6 100644
--- a/cli/common/clicore/command_registry_test.go
+++ b/cli/common/clicore/command_registry_test.go
@@ -118,6 +118,7 @@ func TestPausePointStatusNativeCommandDescription(t *testing.T) {
 func TestVisibleNativeCommandsLeaveOutAHiddenEntry(t *testing.T) {
 	original := NativeCommands
 	t.Cleanup(func() { NativeCommands = original })
+	visibleBefore := len(VisibleNativeCommands())
 	const probe = "hidden-probe"
 	NativeCommands = append(append([]NativeCommandEntry{}, original...),
 		NativeCommandEntry{Name: probe, Owner: DispatcherOwned, Hidden: true})
@@ -135,7 +136,28 @@ func TestVisibleNativeCommandsLeaveOutAHiddenEntry(t *testing.T) {
 			t.Fatalf("%s must not be offered as a completion: %#v", probe, NativeCommandNamesForCompletion())
 		}
 	}
-	if len(VisibleNativeCommands()) != len(original) {
-		t.Fatalf("only %s should be hidden: %#v", probe, VisibleNativeCommands())
+	if len(VisibleNativeCommands()) != visibleBefore {
+		t.Fatalf("adding the hidden %s must not change the listed commands: %#v", probe, VisibleNativeCommands())
+	}
+}
+
+// Verifies compile-check is registered as a hidden dispatcher-owned command: routable by name but
+// left out of the listed commands and of completion while its place beside `uloop compile` is open.
+func TestCompileCheckIsRoutableButNotListed(t *testing.T) {
+	if !IsDispatcherOwnedCommandName(CompileCheckCommandName) {
+		t.Fatalf("%s must stay registered as a dispatcher-owned command", CompileCheckCommandName)
+	}
+	for _, entry := range VisibleNativeCommands() {
+		if entry.Name == CompileCheckCommandName {
+			t.Fatalf("%s must not be listed: %#v", CompileCheckCommandName, VisibleNativeCommands())
+		}
+	}
+	for _, name := range NativeCommandNamesForCompletion() {
+		if name == CompileCheckCommandName {
+			t.Fatalf("%s must not be offered as a completion: %#v", CompileCheckCommandName, NativeCommandNamesForCompletion())
+		}
+	}
+	if len(VisibleNativeCommands()) != len(NativeCommands)-1 {
+		t.Fatalf("only %s should be hidden: %#v", CompileCheckCommandName, VisibleNativeCommands())
 	}
 }
diff --git a/cli/common/tooldocs/skill_guidance.go b/cli/common/tooldocs/skill_guidance.go
index 952cd77161..d568e86830 100644
--- a/cli/common/tooldocs/skill_guidance.go
+++ b/cli/common/tooldocs/skill_guidance.go
@@ -24,10 +24,9 @@ var commandSkillNames = map[string]string{
 	"simulate-mouse-ui":    "uloop-simulate-mouse-ui",
 	"hot-reload":           "uloop-hot-reload",
 
-	"launch":        "uloop-launch",
-	"status":        "uloop-status",
-	"cancel":        "uloop-cancel",
-	"compile-check": "uloop-compile-check",
+	"launch": "uloop-launch",
+	"status": "uloop-status",
+	"cancel": "uloop-cancel",
 
 	// One skill covers the four pause-point commands and the three watch commands: watch
 	// expressions are documented by the pause-point skill's references/watch-expressions.md.
diff --git a/cli/common/tooldocs/skill_guidance_test.go b/cli/common/tooldocs/skill_guidance_test.go
index 396f91e7d1..4af00bb2be 100644
--- a/cli/common/tooldocs/skill_guidance_test.go
+++ b/cli/common/tooldocs/skill_guidance_test.go
@@ -19,12 +19,12 @@ func TestSkillGuidanceLineNamesTheMatchingSkill(t *testing.T) {
 	}
 }
 
-// Verifies the CLI-only compile-check command points at its own skill, which it did not while the
-// command was hidden.
-func TestSkillGuidanceLineNamesTheCompileCheckSkill(t *testing.T) {
+// Verifies the hidden compile-check command gets no skill guidance line: its skill is internal and
+// not installed, so pointing at it would send the reader to a skill that does not exist.
+func TestSkillGuidanceLineLeavesOutTheHiddenCompileCheckCommand(t *testing.T) {
 	line, ok := SkillGuidanceLine("compile-check")
-	if !ok || !strings.Contains(line, "uloop-compile-check") {
-		t.Errorf("guidance line = %q (ok %v), want it to name uloop-compile-check", line, ok)
+	if ok {
+		t.Errorf("guidance line = %q, want none while compile-check is hidden", line)
 	}
 }
 
diff --git a/cli/dispatcher/internal/dispatcher/compile_check_test.go b/cli/dispatcher/internal/dispatcher/compile_check_test.go
index 5d8b5893ed..0f47ebfa9a 100644
--- a/cli/dispatcher/internal/dispatcher/compile_check_test.go
+++ b/cli/dispatcher/internal/dispatcher/compile_check_test.go
@@ -108,8 +108,7 @@ func TestTryHandleCompileCheckRequestIgnoresAnotherCommand(t *testing.T) {
 	}
 }
 
-// Verifies that --help documents the command without compiling anything and closes with the line
-// that sends agents to its skill.
+// Verifies that --help documents the command without compiling anything.
 func TestTryHandleCompileCheckRequestPrintsHelp(t *testing.T) {
 	stdout := bytes.Buffer{}
 	stderr := bytes.Buffer{}
@@ -118,9 +117,7 @@ func TestTryHandleCompileCheckRequestPrintsHelp(t *testing.T) {
 	if !handled || exitCode != 0 {
 		t.Fatalf("expected help to be handled, got handled=%v exitCode=%d", handled, exitCode)
 	}
-	for _, expected := range []string{
-		"uloop compile-check", "--all", "without contacting the Unity Editor", "Load the uloop-compile-check skill",
-	} {
+	for _, expected := range []string{"uloop compile-check", "--all", "without contacting the Unity Editor"} {
 		if !strings.Contains(stdout.String(), expected) {
 			t.Fatalf("expected the help to mention %q, got %q", expected, stdout.String())
 		}
diff --git a/cli/dispatcher/internal/dispatcher/help_test.go b/cli/dispatcher/internal/dispatcher/help_test.go
index b89c53f595..c376dda704 100644
--- a/cli/dispatcher/internal/dispatcher/help_test.go
+++ b/cli/dispatcher/internal/dispatcher/help_test.go
@@ -24,7 +24,6 @@ func TestPrintDispatcherHelpListsNativeCommandsAndLiveToolGuidance(t *testing.T)
 		"Dispatcher. Finds the Unity project, then dispatches live Unity tool commands.",
 		"Native commands:",
 		"  launch",
-		"  compile-check",
 		"  verify-project",
 		"  focus-window",
 		"  list",
@@ -46,9 +45,8 @@ func TestPrintDispatcherHelpListsNativeCommandsAndLiveToolGuidance(t *testing.T)
 		}
 	}
 	for _, unexpected := range []string{
-		// Why the trailing space: compile-check is listed now, and this element must still catch a
-		// baked-in Unity compile.
-		"  compile ",
+		// Why compile-check is here: it is a hidden native command, still routable but never listed.
+		"  compile",
 		"  get-logs",
 		"  run-tests",
 		"uloop --list-commands",
@@ -70,7 +68,6 @@ func TestPrintProjectLocalHelpListsNativeCommandsAndLiveToolGuidance(t *testing.
 	for _, expected := range []string{
 		"Native commands:",
 		"  launch",
-		"  compile-check",
 		"  verify-project",
 		"  focus-window",
 		"  list",
@@ -89,9 +86,8 @@ func TestPrintProjectLocalHelpListsNativeCommandsAndLiveToolGuidance(t *testing.
 		}
 	}
 	for _, unexpected := range []string{
-		// Why the trailing space: compile-check is listed now, and this element must still catch a
-		// baked-in Unity compile.
-		"  compile ",
+		// Why compile-check is here: it is a hidden native command, still routable but never listed.
+		"  compile",
 		"  get-logs",
 		"  run-tests",
 		"uloop --list-commands",
diff --git a/cli/dispatcher/shared-inputs-stamp.json b/cli/dispatcher/shared-inputs-stamp.json
index 55ce117b68..6ae2067704 100644
--- a/cli/dispatcher/shared-inputs-stamp.json
+++ b/cli/dispatcher/shared-inputs-stamp.json
@@ -1,4 +1,4 @@
 {
   "schemaVersion": 1,
-  "sharedInputsHash": "0118207a2e77e3ffe7996c21b7d259adf0b9ae83"
+  "sharedInputsHash": "68c6e7a635c04380cec52756124655d0cfb389a5"
 }
diff --git a/cli/project-runner/internal/projectrunner/list_names_test.go b/cli/project-runner/internal/projectrunner/list_names_test.go
index bf698441d7..1161f38f8c 100644
--- a/cli/project-runner/internal/projectrunner/list_names_test.go
+++ b/cli/project-runner/internal/projectrunner/list_names_test.go
@@ -44,7 +44,7 @@ func TestRunResolvedProjectCommandListNamesWritesNativeAndLiveToolNames(t *testi
 		t.Fatalf("list --names failed: code=%d stdout=%s stderr=%s", code, stdout.String(), stderr.String())
 	}
 
-	const expected = "launch\ncompile-check\nverify-project\nlist\nsync\nfocus-window\nawait-pause-point\npause-point-status\nset-code-optimization\nstatus\ncancel\nskills\npackage\ninstall\nupdate\nuninstall\nversion\nenable-watch\nclear-watch\nget-watch-values\n"
+	const expected = "launch\nverify-project\nlist\nsync\nfocus-window\nawait-pause-point\npause-point-status\nset-code-optimization\nstatus\ncancel\nskills\npackage\ninstall\nupdate\nuninstall\nversion\nenable-watch\nclear-watch\nget-watch-values\n"
 	if stdout.String() != expected {
 		t.Fatalf("list --names output mismatch:\n got:\n%s\nwant:\n%s", stdout.String(), expected)
 	}
@@ -58,7 +58,7 @@ func TestRunResolvedProjectCommandListNamesWritesNativeAndLiveToolNames(t *testi
 // Verifies list accepts repeated names selectors but rejects value assignment and positional
 // arguments with the complete stable INVALID_ARGUMENT envelope.
 func TestRunListOptionBoundaries(t *testing.T) {
-	const namesOutput = "launch\ncompile-check\nverify-project\nlist\nsync\nfocus-window\nawait-pause-point\npause-point-status\nset-code-optimization\nstatus\ncancel\nskills\npackage\ninstall\nupdate\nuninstall\nversion\n"
+	const namesOutput = "launch\nverify-project\nlist\nsync\nfocus-window\nawait-pause-point\npause-point-status\nset-code-optimization\nstatus\ncancel\nskills\npackage\ninstall\nupdate\nuninstall\nversion\n"
 	const namesAssignmentError = "{\n" +
 		"  \"Success\": false,\n" +
 		"  \"Error\": {\n" +
diff --git a/cli/project-runner/shared-inputs-stamp.json b/cli/project-runner/shared-inputs-stamp.json
index 6431b2fdac..7b5c4f9f33 100644
--- a/cli/project-runner/shared-inputs-stamp.json
+++ b/cli/project-runner/shared-inputs-stamp.json
@@ -1,4 +1,4 @@
 {
   "schemaVersion": 1,
-  "sharedInputsHash": "f5915ed784da3b23d15d4047fa8ab9834995e1c6"
+  "sharedInputsHash": "f7fa407b8e7a8d761115abddac7aa879f428301d"
 }
diff --git a/docs/adr/0018-compile-check-is-its-own-command-and-is-shown.md b/docs/adr/0018-compile-check-is-its-own-command-and-is-shown.md
index d4e015c385..fa5b9d706a 100644
--- a/docs/adr/0018-compile-check-is-its-own-command-and-is-shown.md
+++ b/docs/adr/0018-compile-check-is-its-own-command-and-is-shown.md
@@ -102,3 +102,12 @@ These are documented and not detected; after any of them, run `uloop compile`:
 - Running the check offline before `uloop compile` - returning its errors without touching Unity -
   is decided in a separate ADR, once the detection above has gone through one tester round without
   a miss.
+
+Amended 2026-10-20: the command is hidden again - `Hidden: true` on its native command entry and
+`internal: true` in its skill - so it stays routable by name but is left out of `--help`,
+`uloop list`, shell completion, the README and skill installs. This is not the reversal condition
+under "Revisit When": no tester round reported an error `uloop compile` does not report or a
+refusal it does not clear, and everything this record says the check detects stays in place. It is
+hidden because its place beside `uloop compile` - which edits an agent should check offline and
+when it should compile in the Editor instead - is not settled; the amendment is reversed by
+removing the two markers and restoring the README entries once that is decided.
diff --git a/docs/glossary.md b/docs/glossary.md
index 08c471adb3..97e2794389 100644
--- a/docs/glossary.md
+++ b/docs/glossary.md
@@ -192,7 +192,9 @@ The dispatcher-owned native command `compile-check`. It compiles the project's C
 replaying the response files of the last Unity build through the C# compiler bundled with the
 Editor install. It never launches or contacts the Editor, and nothing it produces is loaded by
 Unity. When the project moved in a way the last build cannot describe, it refuses with
-`COMPILE_CHECK_UNITY_BUILD_REQUIRED` rather than guess. See `docs/compile-check.md` and
+`COMPILE_CHECK_UNITY_BUILD_REQUIRED` rather than guess. It is a hidden command: routable by
+name, but left out of `--help`, `uloop list`, shell completion and skill installs until its place
+beside `uloop compile` is settled. See `docs/compile-check.md` and
 `docs/adr/0018-compile-check-is-its-own-command-and-is-shown.md`.
 
 ### Hot reload

From aedcb095d7fbf7337df5cbf1cc9afdba75b43d74 Mon Sep 17 00:00:00 2001
From: hatayama <booqle@gmail.com>
Date: Tue, 20 Oct 2026 01:00:32 +0900
Subject: [PATCH 2/2] Restore the hidden-command paragraph in the compile-check
 reference doc

The glossary and the repository instructions send readers to this file,
and its opening still said the command is shown since ADR 0018. State
the hidden state and the reason here too, so the three documents agree.
---
 docs/compile-check.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/docs/compile-check.md b/docs/compile-check.md
index b9a01a67b6..fe97803039 100644
--- a/docs/compile-check.md
+++ b/docs/compile-check.md
@@ -4,8 +4,11 @@
 without contacting a running one. It is a dispatcher-owned command: it needs no IPC connection and
 no project runner.
 
-Shown since ADR 0018 (`docs/adr/0018-compile-check-is-its-own-command-and-is-shown.md`); what it
-detects and what stays undetected is listed under Limitations.
+The command is hidden: it stays runnable, but help, `uloop list --names`, completion, and the
+installed skills do not list it, and its skill is marked `internal: true` so `uloop skills install`
+skips it. It is hidden because its place beside `uloop compile` is not settled, not because of a
+detection gap: what it detects and what stays undetected is listed under Limitations, and the
+decision history is in `docs/adr/0018-compile-check-is-its-own-command-and-is-shown.md`.
 
 It is not a replacement for `uloop compile`. Nothing it produces is loaded by Unity, so use it only
 when you want to know whether the code compiles — not when you need the result to be live in the