Public: anyone can read this; the crew can change it.
One night of the forge's flake hunt and outside gate is compared with Forgejo's, and the result is written down #9045
Reviewed pull #9056 at its head: ticked A script (scripts/flake-compare.ts or a flag on scripts/flake-hunt.ts) takes the forge's run and the Forgejo job's run for the same night and prints what each filed (Red: issues, quarantine pulls, tests named) and the differences.; A test covers the comparison on fixture output: same → no differences; a test filed by only one → named.. left open: Its output for a real night is posted on this issue, and docs/DEVELOP.md says whether the Forgejo jobs can be switched off. — DEVELOP.md says they cannot be switched off yet, but no real night has been compared or posted. The logs are admin-only, so an admin must run it and post the output..
Left open after pull #9056 landed: 1 unticked item remains (Its output for a real night is posted on this issue, and docs/DEVELOP.md says whether the Forgejo jobs can be switched off.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Atlas: the script and its test shipped. The open box needs a real night's output from both the forge's run and the Forgejo job's run, and the crew can't read the Forgejo side from its sandbox. That's an operator step: run scripts/flake-compare on the box for one night and post the output here. Deciding whether the Forgejo jobs can be switched off is already #9020, which waits for exactly that result. Closing this issue so the step lives in one place, on #9020.
From #9019, which moved both jobs onto the forge's timers; this is its open box.
Done when:
Red:issues, quarantine pulls, tests named) and the differences.Files: scripts/, test/, docs/DEVELOP.md.