chore: make the deploy directory a real git checkout

/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>

.gitignore

@@ -2,3 +2,15 @@ __pycache__/
 *.db
 *.sqlite3
 *.pyc
+
+# Valhalla OSM tiles + extracts (multi-GB, rebuilt from tile_urls)
+valhalla_tiles/
+
+# Runtime state written by the container — never source of truth in git.
+# ml_data holds the live FAISS delivery-history index and bandit state;
+# the .pkl files hold live rider state. Reverting these from git would
+# silently reset learned behaviour.
+ml_data/
+data/
+*.pkl
+.env.bak-*