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…
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…
Implemented in a250c29.
- New
app/internal/ai_health.py: a per-tier degradation registry (transcription,correlation_cheap,correlation_smart,extraction).classify(text)is now the…
The failure mode appears to have inverted. In the 2026-08-19 dump there is no over-splitting at all — every one of the 6 incidents has exactly one new call. What there is instead is heavy…
Measured against the 2026-08-19 dump: the 40km radius is not the main cause. Geocode success is 6.8%, and 17 of 26 location strings never geocode at all — because the strings themselves are…
Fixed in e6aab75.
Every fallback is gone rather than replaced with a better default:
icecast/entrypoint.shrefuses to start if either password is empty and prints how to generate one. This…