mirror of
https://github.com/prosolis/gogobee.git
synced 2026-09-14 02:41:09 +00:00
The one-shot that seeded news_realm_firsts filtered on `abandoned = 0`, and `abandoned` does not mean anybody gave up: abandonZoneRunByID exists to retire a run whose boss is already dead when the expedition travels onward, which is how 30 of prod's 32 boss kills are stored. So the ledger holds 6 zones where the run history knows 9, and it dates every row to the minute the job ran rather than to the clear. The ledger is what claimRealmFirst tiers live dispatches against, so each missed zone is a spurious PRIORITY "realm first" waiting to fire the next time somebody clears it, months late. Fix the shared query, and add a re-seed (not a re-run) under its own job name: it writes the ledger, backdated to the real earliest clear, and emits nothing at all. It runs regardless of the news switches, because a ledger that is right only while emission is on mis-tiers the first dispatch after somebody flips it. Kept in place afterwards as an ordinary bootstrap for fresh deploys. Claude-Session: https://claude.ai/code/session_012bxpQQJDjC1mTtLN3VVtBQ