dotfiles/common/claude/memory/-home-connor-projects-news/news-triage-v02-gotchas.md

name, description, metadata

name	description	metadata
news-triage-v02-gotchas	Operational traps in the running news_triage v0.2 container - config reload scope, permanently-unhealthy healthcheck, dead ntfy buttons	type project

Traps in the still-running connor_news-backend_1 (built from the news_triage source tree, which is no longer on disk — it was not carried into ~/projects on 2026-10-02; the running container is all that is left), each of which costs a debugging cycle to rediscover:

• SIGHUP does not reload sources. watch_sighup swaps the config, and per-cycle reads pick up [topics], [notify], [clustering] and [llm]. But spawn_source_loop takes an owned Source and the source list is enumerated once at startup in build_runtime, so adding, removing, or disabling a feed needs sudo podman restart, not a HUP.
• The container reports unhealthy forever and is fine. The compose healthcheck is CMD curl -f localhost:3000/healthz and the runtime image ships no curl.
• ntfy feedback buttons have never worked. NEWS_API_BASE_URL is unset, so they are dropped at boot with a single WARN. ntfy executes those actions from the phone, so it needs a publicly reachable URL. Deliberately left unfixed — /api/feedback has no auth, and with no data import into the rewrite the labels have no carry-over value.
• The bypass lane ignores relevance entirely (gate.rs:302): it fires priority-5 push on source_count >= 2 OR p99 importance, skipping quiet hours, the token bucket, and the blocklist. bypass_ceiling_per_day is the only brake on it.

Config is bind-mounted, so per the usual rule an edit needs sudo podman restart — podman-compose up -d does nothing when only the mounted file changed.

Related: news-rewrite-status