Playbook 07: the new test failed on its first two runs, not three

00-META/process/07-feature-branches.md

@@ -146,7 +146,7 @@ never into the running one, unless it blocks the running one.
    It says which round it is in ("round 1 of at most 3").
 3. **The report goes to the same fixing agents** that wrote the code, continued by their ids, so they fix
    with the context they already hold. Each answers the reviewer: what it changed, per finding, or why not.
-4. **Every new integration test is read against the code it drives before the first push.** It has never run: fixing agents only compile it, and its first run is the merge check, so each fault it hides costs a whole check. The reviewer traces each step of each new integration test through the code (fixtures against the manifest rules, what the store keeps and reads back, who holds a seat), and says which steps it could not trace. On 2026-10-17 a new test failed on its first three runs, a fixture and two faults of the change that reading it found only after a failed check.
+4. **Every new integration test is read against the code it drives before the first push.** It has never run: fixing agents only compile it, and its first run is the merge check, so each fault it hides costs a whole check. The reviewer traces each step of each new integration test through the code (fixtures against the manifest rules, what the store keeps and reads back, who holds a seat), and says which steps it could not trace. On 2026-10-17 a new test failed on its first two runs, on a fixture and then on a fault of the change; reading it against the code after the first failure found another fault, which would have failed a run too.
 5. **The reviewer reads the answers and the new commits**, and approves or reports again (step 6 says what a round
    may ask). After round 3 the lead stops and brings the operator what is left, with a recommendation.
 6. **A finding outside the issues' done-when is never a change asked, in any round.** More hardening, a