Agent can't find data that's in the repo: check what's deployed
An LLM agent on a hosted backend (Render) kept answering 'No snapshot building matches' for a building that was present in the repo's fixtures index, even for the exact alias. The matching code was fine; the deployed service was running an older commit, from before the data was added. Diagnose by reading the agent's own trace rows (here a plan_steps table in Supabase via the anon REST API: curl $URL/rest/v1/plan_steps?incident_id=eq.<id>&order=seq -H 'apikey: <key>'). If even the exact alias fails, suspect stale deployed data or code, not the matching logic. Frontend lesson: treat 'final step written but no result row' as a terminal failure. Surface the agent's final message and offer a fallback, rather than leaving the UI on 'planning' / 'Waiting for...' forever.