Iter 39 — captures the 8 concrete lessons the SOTA /loop sprint learned
the hard way (cross-branch checkout incidents in iter 17-19, silent
absorption of foreign-branch Cargo.toml work in iter 18 → revert in
ca2059b07, fuzz-target stub gap in iter 11 → CI fail discovered in
iter 38). Future /loop or /loop-worker runs against THIS repo should
read these before kicking off a long autonomous sprint.
Key recommendations:
1. git branch --show-current at the start of every iter
2. git diff --cached before every commit after a branch switch
3. Document sibling-region ownership in this file
4. Extract pure helpers before committing inline mutations
(sync_snapshot, apply_sync_packet, fleet_role_counts patterns)
5. Cross-language wire-format pin in BOTH languages at the SAME iter
6. Helper tests > integration tests when state is heavy
7. Add fuzz stubs in the same commit as the firmware symbol they
mirror (iter 38 caught c6_sync_espnow_is_valid this way)
8. Reserve irreversible checkpoints (tag, release, PR ready) for
iters with surplus confidence from prior CI evidence
Co-Authored-By: claude-flow <ruv@ruv.net>
Iter 22 — defensive ultra-opt after iter 17-19 burned ~30 minutes
recovering from cross-branch checkouts. Reference card so the next
collaborator (or the next /loop) doesn't have to re-derive the layout
from git log.
Captures:
* Branch ownership table (who owns adr-110-esp32c6 vs
feat/adr-115-ha-mqtt-matter, what each carries, what to NOT merge)
* File-level region map for the two shared files
(Cargo.toml + sensing-server/src/main.rs) — the regions are
DISJOINT so merges should be clean line-merge with no conflicts
* Quick verification commands for either branch
* Recovery procedure pointer to iter 18 commit 2997165bc message
Verification baseline pinned in the doc: full v2 cargo workspace test
suite at 1437 tests, 0 failures (iter 22 measurement). Anyone running
that locally and seeing the same number knows the branch is sane.
Co-Authored-By: claude-flow <ruv@ruv.net>
ruv