Record cooperative map verification

This commit is contained in:
SimpleTest 2026-08-25 20:38:39 +03:00
parent 85039b76ef
commit 3238a9feb3

View File

@ -3495,3 +3495,32 @@ promoted.
- These checks were read-only. They did not install or update the phone app,
change Play Console, deploy production, modify the frozen hackathon test,
change shared Caddy, or push the public Git remote.
# 2026-08-25 cooperative mobile-map gesture verification
- Commit `85039b7` enables MapLibre cooperative gestures on both embedded map
constructors. On the connected physical Android phone, a one-finger vertical
swipe beginning inside the development landing-page map scrolled the page
without moving the map. A one-finger map-pan attempt left the camera in place
and displayed the localized Ukrainian instruction to use two fingers. This
verifies the visible touch contract on the current phone; it is not an
assertion about every Android browser or assistive input method.
- The development origin served compiled asset
`app-2955e63e547b68ff131cd82f72ead392.js`; the fetched asset contained both
cooperative map options and the localized interaction text. The focused
browser-asset suite passed all 19 tests, including the source-contract test
that covers every embedded MapLibre constructor.
- The local Kind rolling verifier was corrected to validate the stable
readiness contract directly inside each replacement web pod instead of
expecting an undocumented node field from `/healthz/ready`. The complete
rerun retained evidence under
`output/resilience/cooperative-map-verifier-20260825/`: 218 sampled readiness
requests had zero failures, both replacement web pods returned
`{"status":"ready"}`, all four application pods were replaced and ready with
zero restarts, and the selected database table counts were identical before
and after the rollout.
- The live local development cluster ended at web and worker deployment
revision 40 with 2/2 ready replicas for each role. Both the local NodePort and
`https://whoneedhelp.imalto.site/healthz/ready` returned the exact ready
payload after verification. Production, the frozen hackathon test, shared
Caddy, and the public Git remote were not changed or pushed.