Crafter.Debug/tooling
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Jorijn van der Graaf 2a954b7f1f
docs(tooling): tell consumers' agents how to code with Crafter.Debug
The consumer notes only said how to drive a running app. They now also
say how to add to what an agent can reach: where the hook points and
registrations go, gating pause and step, registering commands,
watches, samples and checks, and the rules that keep that code right
(handlers run on the app's thread and must not block; Async for
results that take frames; call the app's own code paths instead of
re-implementing them, the lesson from 3DForts' drifting verbs; Group
for per-object state; which types travel).

All of it stays in tooling/AGENTS.consumer.md, which every build
merges through the unconditional pragma. Notes beside the root
project.cpp would only come with debug builds, when the library is in
the graph, and would then duplicate these; AGENTS.template.md now says
so.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 02:16:05 +01:00
..
interfaces feat(tooling): wire consumers in through Debug::Use and a launcher 2026-11-01 01:18:07 +01:00
AGENTS.consumer.md docs(tooling): tell consumers' agents how to code with Crafter.Debug 2026-11-01 02:16:05 +01:00
project.cpp feat(tooling): wire consumers in through Debug::Use and a launcher 2026-11-01 01:18:07 +01:00