Places, and the fields we do not have

/places/search, /places/nearby and /places/{id} over the points of interest the geocoding corpus already carries. /geocode/nearby is unchanged. The plan asks for phone numbers and opening hours; we do not have them, so they are absent from the response rather than null.

• /places/search returns places, where /geocode/search returns whatever best matches and for Calgary that is the city
• /places/{id} is new capability rather than a rename: the geocoder had no by-id lookup, so a client that stored a result had no way to refresh it
• A malformed id is a 404, not a 400. From a caller's side that is the same answer, and distinguishing them would leak our storage type into the contract

AvailabilityAvailability was not re-checked against production for this record. Phone, hours, website, accessibility, and operator are absent from the corpus, not returned as null.