notes: acceptance tests never in the background -- first rule in rules.md
Build / Image RASPI (push) Canceled after 0s
Build / Image PC (push) Canceled after 0s
Build / Image MILKV (push) Canceled after 0s
Build / v4 tests (32- and 64-bit cells) (push) Canceled after 0s
Acceptance / Acceptance (pull_request) Successful in 36m12s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This commit is contained in:
Claude
2026-11-11 17:22:29 +00:00
parent a7be895c7f
commit 89dbed7c4e
+10
View File
@@ -1,5 +1,15 @@
# How to work in this repo
## READ FIRST — rules I have broken in front of Captain Bob (2026-11-11)
1. **NEVER run an acceptance test in the background. EVER.** (Bob: "You are NOT to run acceptance tests in
background EVER!") No `run_in_background`, no `&`, no detached loop, no "it might outlast the tool timeout".
One stage per foreground command, read its result, then the next. I broke this twice on 2026-11-11.
2. **Before doing anything, check it against CLAUDE.md, not just before the session.** Having read a rule is
not following it. I had summarised the foreground rule to Bob and broke it anyway.
3. Every log and every CSV is evidence and is committed — passing, failing, stopped.
4. Never create a branch, never stash, never fix unasked, never push without Bob saying push.
Source of authority: `.claude/CLAUDE.md` (wins), then the FABRIC record (`docs/fabric/`, FABRIC-3 living),
then `docs/v4.0.0/`, `docs/reference/ROADMAP.md`, `boards/BRINGUP.md`. Code wins over all documents.