mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-10-19 05:26:47 +00:00
Maurice
eebe9a52e1
create_place learned stop_type when the column arrived; the three tools that could change a place did not. Over MCP the kind was therefore writable exactly once and never afterwards: a place saved as fuel fell out of every stop count, wore the wrong disc for good, and could only be put right through the REST API. update_place and bulk_update_places take it nullable, which is how the service already reads "turn this back into an ordinary place" (an explicit null rather than COALESCE). create_and_assign_place takes it the way create_place does. The description also named four kinds where the enum holds six, so the model had no way to reach restaurant or sights.