mirror of
https://github.com/tiennm99/vngeoguessr.git
synced 2026-10-11 03:13:56 +00:00
tiennm99
c9a35dca9a
Reconcile every doc with the shipped code. All six described a flat five-city model, and features.md, tech-stack.md, game-flow.md and project-structure.md still documented the dart-throw over /images?bbox= that the prebuilt panorama indexes replaced. project-overview.md gains a Coverage note that classifies absent coverage into its three causes -- not yet added, no street imagery, missing from the boundary -- because a note that only says "partial" teaches maintainers to ignore real gaps. Cu Chi is named as the one instance of the third, which is the only one that is a defect. A context hook had been denying access to src/app/debug/coverage/page.js, so this also lands the two items earlier phases recorded as undeliverable: the api/debug/city-coverage -> region-coverage rename, and the page's migration from a flat city list to RegionSelect. With its last caller gone, game.js drops CITIES, cities, cityNames, cityCenters and cityBboxes; getCityIndex, indexedCities and fetchCityPanorama take names that match what they now take. Selecting a district with no boundary returned a 400 and left the previous region's panorama count and outline on screen beside the error, so Ho Chi Minh's 184,938 read as Cu Chi's. The error path now clears everything derived from the previous region, and a null boundary removes the outline rather than skipping the redraw. Two plan-time claims did not survive contact with the code and the docs follow the code: VN scores like any other node rather than being a zero-scoring exploration mode, and the fan-out credits two levels when a panorama falls outside every district outline.