# 01 — Route Session lifecycle Status: ready-for-agent ## What to build Add the narrowest end-to-end Route Session lifecycle that can be used by distributed inference routes: create a session, bind it to a selected Inference Route, expose status, and close it cleanly. This slice does not need real model cache yet; it proves stable session identity across the control plane and activation plane. ## Acceptance criteria - [ ] A request can create a Route Session with a stable `session_id`, `route_id`, model preset, backend id, and route membership. - [ ] Every downstream activation request carries the same session identity and fails clearly if the session or route id does not match. - [ ] Session status reports phase, route nodes, model preset, backend id, created time, and last activity time. - [ ] Closing a session releases all registered per-session state. - [ ] Tests cover create, status, close, stale-session rejection, and wrong-route rejection. ## Blocked by None - can start immediately.