sasa/battleship
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add the always-available recovery menu and child-safe confirmations

Browse Source
This commit is contained in:
sasa
2026-08-30 23:28:47 +03:00
parent a68023e684
commit d5eb26d330
6 changed files with 143 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PLANS.md
+13 -2
View File
@@ -1661,7 +1661,7 @@ When all criteria pass, set Milestone 021 to `DONE`, append its execution record
## Milestone 022 — Add the always-available recovery menu and child-safe confirmations
**Status:** `READY`
**Status:** `DONE`
**Depends on:** Milestone 021
### Objective
@@ -1757,11 +1757,22 @@ Add tests covering at least:
When all criteria pass, set Milestone 022 to `DONE`, append its execution record, and change Milestone 023 from `BLOCKED` to `READY`. Do not start Milestone 023 in the same task unless explicitly requested.
### Execution record
- Date: 2026-08-30
- Board model and revision: ESP32-C6FH4 QFN32, revision v0.2.
- Toolchain and library versions: PlatformIO Core 6.1.19; `espressif32` 7.0.1; ESP-IDF 6.0.1; `esp_littlefs` 1.20.4.
- Result: PASS, pending physical-device layout confirmation.
- Evidence: Added a 44-pixel lifebuoy-labelled recovery control outside the gameplay surfaces. It is hidden at registration and visible in lobby, game, result, reconnecting, and error states with an active session. Its modal has focus containment, Escape/close restoration, role-gated full reset, separate icon/text scopes, and cancellation as the initial confirmation focus. Leave and profile reset require a second explicit confirmation; full reset requires a two-second pointer hold with visible progress, while keyboard activation supplies the accessible equivalent. Successful leave preserves the name; profile/full reset clears all `battleship.*` browser data, selection, cached state/statistics, effects, timers, polling, and socket retry state before showing registration. Offline profile reset is explicitly local-only and warns about the retained server seat.
- Measurements: `node --test test/web/test_target_interaction.js test/web/test_ship_sprite.js test/web/test_recovery_ui.js` passed 15/15, including recovery visibility, role gate, scope clearing, hold/cancel, keyboard, and Escape assertions. `make -C test/host run` passed all ten host suites. `node --check data/app.js`, `git diff --check`, `pio run -e esp32-c6-devkitm-1 -t buildfs`, and `pio run -e esp32-c6-devkitm-1` passed. Browser assets are 43,011 B / 10,622 B gzip JavaScript, 23,570 B / 5,589 B gzip CSS, and 4,466 B / 1,633 B gzip SVG. The LittleFS image is the fixed 2,031,616-B partition image. Firmware remains 39,604 / 327,680 B RAM (12.1%) and 1,020,806 / 2,097,152 B flash (48.7%).
- Issues or deviations: No attached browser backend is available for live phone/tablet screenshots, and no firmware/filesystem upload or physical recovery exercise was performed.
- Next action: Milestone 023 is READY. Do not start it unless explicitly requested.
---
## Milestone 023 — Verify multi-client reset recovery and document the emergency workflow
**Status:** `BLOCKED`
**Status:** `READY`
**Depends on:** Milestone 022
### Objective