Keep map theme state aligned
This commit is contained in:
@@ -9365,7 +9365,7 @@ Boundaries:
|
||||
Validation so far:
|
||||
- Backend compile and frontend typecheck passed.
|
||||
- Source-catalog plus governed-refresh focused suite passed: 20 tests.
|
||||
- Full `scripts/run_readiness_check.sh` passed: 780 backend tests, 110
|
||||
- Full `scripts/run_readiness_check.sh` passed: 781 backend tests, 110
|
||||
documented route contracts, one Alembic head, frontend typecheck/build and
|
||||
all packaged smoke checks.
|
||||
- Live Tower staging completed all 112 municipality/theme partitions for
|
||||
@@ -9379,6 +9379,10 @@ Validation so far:
|
||||
- Live browser validation exposed and fixed additive theme ranking where two
|
||||
extra old water features could outweigh a newer observation date. Ranking is
|
||||
now priority, observation date, import date, then feature-count tie-breaker.
|
||||
- Post-deploy browser validation also exposed a stale map-theme remount state:
|
||||
returning from Status to Map could retain the Water legend while the viewport
|
||||
query and zoom guidance reverted to Buildings. Map state now initializes from
|
||||
the selected persisted dataset so all four signals remain aligned.
|
||||
|
||||
Next:
|
||||
- Run the full release gate, deploy to Tower, execute a live read-only plan and
|
||||
|
||||
Reference in New Issue
Block a user