Block a user
Admin page redirects away before auth claims resolve, so /admin is unreachable on a cold load
/dashboard does not exist, so every post-login and guard redirect lands on a 404
Firestore rules and indexes are in source control but never deployed
Confirmed live in prod (drb.cusano.net, git_sha 861ea41, 2026-08-23 02:07 EDT) — both halves of this are still undeployed and now cause visible, misleading UI failures:
Indexes. `useIncidents…
models.py types incident location as coordinates, so PUT /incidents/{id} cannot set one
Pre-existing incidents keep an unverifiable map pin until a call links to them
Incident title is re-derived from the newest call, so incidents are named after their last event
Incident map pin and incident label disagree in 5 of 6 incidents
unit-continuity correlation path never writes corr_matched_units, so the debug view can't show why it matched
Correlation debug endpoint hides the LLM fields, so LLM activity cannot be audited
Deploy failed silently on 15 consecutive pushes — production ran 08-18 code until 08-20
CORS defaults to "*" while allow_credentials is True
Incident title is re-derived from the newest call, so incidents are named after their last event
Incident title is re-derived from the newest call, so incidents are named after their last event
Duplicate of server-26#26, filed twice in the same session by mistake — the exact failure CLAUDE.md warns about, since a split history is worse than no issue. Continue the discussion on #26; it…
Thin-call auto-attach has no fit check, merging unrelated events into one incident
Fixed in 33a247d; deployed (Gitea Actions 732 build + 733 deploy, both success, health check passed).
Three changes:
_is_thin_callnow rejects any call carrying tags, a location string, a…
Incident title is re-derived from the newest call, so incidents are named after their last event
Sweep retry budget can expire before the incident the orphan belongs to exists