/root/Routes-api was not a repository. Work had been done directly here
and existed nowhere else, so deploying from git would have silently
reverted it -- which nearly happened with the Valhalla road-backend
probe. Now the box tracks origin/main, and any drift shows up in
git status instead of being invisible until something breaks.
Runtime state is untracked rather than committed. ml_data holds the live
FAISS delivery-history index and bandit state, and the .pkl files hold
live rider state; all are written by the running container. Tracking
them meant git status was 93 lines of noise that would bury a real source
change, and a stray `git checkout .` would have rolled learned behaviour
back to a months-old commit. They stay on disk, they just leave the index.
Also drops __pycache__ and three stray files (Untitled (2), input,
output) that were committed by accident and no longer exist here.
.env stays tracked but is marked skip-worktree: it is per-environment, so
it would otherwise read as modified forever.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
/root/Routes-api on 31.97.228.132 is not a git repository. Work had been
done directly on the box and existed nowhere else -- a single rm -rf from
being lost, and impossible to review or roll back.
Deploying the previous HEAD over it would have silently reverted all of
this. Most visibly the Valhalla road-backend probe in main.py, whose own
comment explains why it exists: road sequencing degrades to aerial
silently by design, so an unreachable backend stays invisible, "which is
exactly how the expired Google key went unnoticed". Overwriting it would
have reintroduced precisely the failure it was written to catch, and the
service would have kept answering 200 throughout.
The server had also moved from Google Maps to Valhalla for road distance
(VALHALLA_URL, road_backend_status, +190 lines in route_optimizer),
extended docker-compose from 44 to 95 lines, and changed rider fetching,
health, dynamic config and the cache layer.
Only 10 files differ in substance. The other 27 that appeared to differ
were CRLF-vs-LF noise -- the server writes CRLF -- and are normalised to
LF here rather than committed as spurious whole-file rewrites.
Committed as-is, before any change of mine, so the diff that follows is
reviewable against what is actually running.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
