[Clare72]

The weekly bot commit read "FlyBase n/a": check_flybase_release.py returned early when every gene_id_map.tsv already matched the current FlyBase release, so checks/flybase_release_check.json was never written, and the workflow's commit title falls back to n/a.

• Maps current and the release is not yet recorded → record it (maps_current: true, no Chado query, no issue) and set changed=true, so the workflow commits it once per release.
• Release already recorded → nothing to do, as before.
• The newer-release path is unchanged; its record write now shares a _record helper. --dry-run writes nothing on either path.
• DESIGN: drop the inaccurate "created on the first FlyBase release check" note.

Tests: the old "same release does nothing" test is replaced by one that checks the release is recorded once (changed=true then changed=false), plus a dry-run test. 131 pass. A real --dry-run against flybase.org reports FB2026_03 current and writes nothing.

The next weekly run should commit checks/flybase_release_check.json for FB2026_03.

🤖 Generated with Claude Code