Playbook 07: a fixing agent never runs an integration test locally (the operator, 2026-10-17)

2026-10-17 21:23:05 +02:00
parent d5ddd1e715
commit 610be93803
1 changed files with 4 additions and 1 deletions
@@ -115,7 +115,10 @@ never into the running one, unless it blocks the running one.
  message ("issue 805: landing in mesh-catalog"); reach the mesh only through the mesh MCP server, never ssh;
  never push, open, merge or close a pull request; never write to a store's database by hand, a schema change
  is a numbered migration and the consolidated schema; Go only unless the context file says otherwise; never
-  move another issue. Report back in under 150 words: commits, tests added and that they failed first, the
+  move another issue; **never run an integration test locally** (no `go test -tags integration`, no `merge-check.sh`,
+  no bus or store test run): compile them with `go vet -tags integration ./...` and leave the running to the
+  forge's merge check. On 2026-10-17 three fixing agents ran them anyway, one for minutes on end, because the
+  brief only said they wait for the check (the operator). Report back in under 150 words: commits, tests added and that they failed first, the
  check results, anything you stopped on.
 - **An agent that finds the code differs from its context file stops and reports** (file:line); the lead
  settles it, updates the context file, and continues the agent.