Catcrafts/Crafter.Debug
Watch
2
0
Fork
You've already forked Crafter.Debug
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: which app the client picks when other projects' apps run too

Browse source 
The consumer notes tell agents that commands pick their project's app
and how to reach another with -i, the README's discovery row says the
same, and the agent notes describe CRAFTER_DEBUG_PROJECT and how an app
is matched to its project.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Jorijn van der Graaf 2026-11-01 18:33:59 +01:00
commit 98e92c1976
Signed by: jorijnvdgraaf
GPG key ID: 2937E59CDCC1BCFB
3 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

1
AGENTS.template.md
View file

@ -128,6 +128,7 @@ A test's own output appears only when it fails. To see its PASS lines, run the b
- **A consumer's `#ifdef`'d `import Crafter.Debug;`** is harmless in its plain builds.
- **`project.cpp` regenerates `build/generated/<core variant>/Crafter.Debug.Core-BuildInfo.cpp`** when the sources or the client's path change. `crafter-build clean` removes it, and the next load writes it again.
- **The launcher is written by `Debug::Use` while crafter-build loads the consumer,** not by the build. A plain build keeps an existing launcher; a fresh plain build writes the stub.
- **The launcher tells the client its project** in `CRAFTER_DEBUG_PROJECT`, which becomes `Cli::Environment::project`. An app is the project's when its executable lies under that directory, as `-r` runs it from `<project>/bin/<variant>/`. With a project set, commands pick only the project's apps unless `-i` says otherwise, and `ls` exits 3 while none of them runs. A client started without the launcher has no project and picks the one app running, as before.
- **A consumer that depends on Crafter.Network itself** must name it exactly as `project.cpp` here does (same URL, no pin, same args). Otherwise the graph holds two Crafter.Network configurations, and crafter-build refuses with "module … built twice".
- **`debug.log`'s `last` of 0 means no backlog**, as `tail -n 0` does. A `TimelineQuery`'s `last` of 0 means all.
- **Answer before you raise a flag the main loop acts on.** The loop may end the Session at once. A reply given before the connections close is delivered; one given after is not. `quit` replies first, then sets `QuitRequested`.