Ullrich Schäfer c16c140223 Drop the flagship BRouter service after cutover ... After PR #293 flipped BROUTER_URL to the dedicated host and Grafana + manual smoke tests confirmed clean routing (US route worked, request rate/latency/memory/logs all green), there's no reason to keep the in-tree flagship brouter container warm any longer. - Remove the `brouter:` service and its `./segments` bind mount from `infrastructure/docker-compose.yml`. - Remove `depends_on: brouter` from the planner service. - Tighten the BROUTER_URL and BROUTER_AUTH_TOKEN env wiring from `${…:-default}` to `${…:?message}` so a missing SOPS value fails the compose up loudly instead of silently pointing at the removed service (or missing auth). - Tick tasks 5.5, 7.5, 8.4, 9.3 in the OpenSpec change; 9.4 (archive) is the last remaining step once this merges. Post-merge operator step: `docker image prune -f` on the flagship to reclaim the brouter image. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-24 18:04:17 +02:00
..
changes	Drop the flagship BRouter service after cutover	2026-04-24 18:04:17 +02:00
specs	Prompt users with stale terms_version to re-accept	2026-04-19 08:06:16 +02:00