alex/flybrain
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

Document recovery and run its regressions in infra gate

Browse source
This commit is contained in:
acamilo 2026-09-26 01:15:44 +00:00
parent 432991cbc5
commit dccc52ae1c
2 changed files with 10 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/loop-review.md
View file

@ -8,7 +8,9 @@ the project."
1. The release watchdog (`infra/bin/fly-watchdog` check 10) flags a suspected loop: few distinct
macros, a short sequence repeating, no growth in places explored. It exports
`fly_loop_suspected` and writes `/run/fly/wd/loop.json`. It never acts.
`fly_loop_suspected` and writes `/run/fly/wd/loop.json`. It never acts. The separate
`fly-loop-recover.timer` can restart only flysim after two fresh suspected probes;
see `infra/docs/loop-recovery.md`. This does not replace checkpoint-based review.
2. The coordinator session (Fable) checks that marker on a schedule. On a flag it pulls the
live checkpoint read-only (`pct pull`, into `.local/checkpoints/`, never committed), and
spawns a review agent with the trap brief: reproduce from the checkpoint with the real

7
infra/tests/lint.sh
View file

@ -1483,6 +1483,13 @@ else
echo " mention is genuinely legitimate, add it to infra/tests/de-pii-allow.txt with a reason." >&2
fi
echo "--- loop recovery tests ---"
if python3 -m unittest discover -s "$REPO_ROOT/infra/tests" -p 'test_loop_recover.py' >/dev/null 2>&1; then
pass "loop recovery: fresh probes, cooldown, and router refusal"
else
fail "loop recovery tests failed; run python3 -m unittest discover -s infra/tests -p test_loop_recover.py -v"
fi
echo "==="
if [ "$FAILED" -eq 0 ]; then
echo "lint.sh: ALL CHECKS PASSED"