From 916d43c9b99c32485b8c8777bea007ec4a53fcab Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sun, 12 Jul 2026 10:55:36 +0100 Subject: [PATCH] docs(agents): clarify Testbox cleanup syntax (#105268) --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index 61444bf7091..a27c6b72d5b 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -132,6 +132,7 @@ Skills own workflows; root owns hard policy and routing. - Use `$openclaw-testing` for test/CI choice and `$crabbox` for remote/full/E2E proof. - At task start, if code changes, tests, builds, typechecks, lint fan-out, Docker, packaging, E2E, or live proof are likely, classify source trust and immediately pre-warm the safe Crabbox backend in a background command session. Trusted maintainer code defaults to Blacksmith Testbox; untrusted contributor/fork code uses secretless fork CI or sanitized direct AWS Crabbox under the rule above. Continue inspection/editing while it hydrates; sync the current checkout for every run, reuse the lease, then stop it before handoff. - Warm Testbox from the task checkout; lease ownership is checkout-path scoped. +- Testbox cleanup: `blacksmith testbox stop --id `; id is not positional. - PR review artifacts: keep template enum values; put evidence detail in summaries. - Crabbox request means real scenario proof: install/update/call/repro user path; not just copy tests and run them remotely. - Visual proof: use Crabbox, set up like a user, then screenshot-verify. No harness/bypass/shortcut unless explicitly asked.