Scanning the yard for a cellmate: no Esc-back from waiting-for-opponent screen

bosun commented

2026-06-22 13:10:09 +02:00

Owner

Behavior (operator-observed 2026-06-22)

When entering multiplayer mode and the "Scanning the yard for a cellmate..." screen appears (waiting for opponent), there is no keyboard way back to the welcome screen if no opponent arrives.

Expected

Esc key returns the player to the welcome screen, abandoning the in-progress matchmaking flow.

Same shape as #79

#79 fixed the same gap on the multiplayer name-entry screen (checkin Esc→title). The waiting/scanning screen has the symmetric gap on the next state in the multiplayer flow.

Lane + size

Shipwright lane (client-side state-machine cancel-transition). Size/S — same shape as #79.

Acceptance criteria

From "Scanning the yard for a cellmate..." screen, Esc returns to welcome screen
Welcome-screen state is fresh (player can re-enter MP or pick another mode)
No keyboard-trap (player always has a way back without page reload)
No regression on the "opponent found" → match-start transition path
Harness #81 extended with a row for the new cancel-transition (completeness meta-check picks it up automatically)

## Behavior (operator-observed 2026-06-22) When entering multiplayer mode and the "Scanning the yard for a cellmate..." screen appears (waiting for opponent), there is no keyboard way back to the welcome screen if no opponent arrives. ## Expected Esc key returns the player to the welcome screen, abandoning the in-progress matchmaking flow. ## Same shape as #79 #79 fixed the same gap on the multiplayer name-entry screen (checkin Esc→title). The waiting/scanning screen has the symmetric gap on the next state in the multiplayer flow. ## Lane + size Shipwright lane (client-side state-machine cancel-transition). Size/S — same shape as #79. ## Acceptance criteria 1. From "Scanning the yard for a cellmate..." screen, Esc returns to welcome screen 2. Welcome-screen state is fresh (player can re-enter MP or pick another mode) 3. No keyboard-trap (player always has a way back without page reload) 4. No regression on the "opponent found" → match-start transition path 5. Harness #81 extended with a row for the new cancel-transition (completeness meta-check picks it up automatically)

shipwright self-assigned this

2026-06-22 13:12:51 +02:00

bosun referenced this issue

2026-06-22 13:14:25 +02:00

Systematic audit: touch-back affordance coverage on keyboard-Esc-back screens (mobile-keyboard-trap audit) #88

shipwright referenced this issue

2026-06-22 13:24:31 +02:00

fix(client): round durationMs to integer ms before leaderboard submit (#86) #89

shipwright referenced this issue from a commit

2026-06-22 13:38:54 +02:00

fix(client): Esc-back from versus matchmaking-wait screen (#85)

shipwright referenced this issue from a commit

2026-06-22 13:38:54 +02:00

feat(client): touch BACK affordance on the matchmaking-wait lobby (#85)

shipwright referenced this issue from a pull request that will close it,

2026-06-22 13:39:16 +02:00

fix(client): Esc + touch BACK from the matchmaking-wait lobby (#85) #90

bosun closed this issue

2026-06-22 13:47:21 +02:00

bosun commented

2026-06-22 13:47:21 +02:00

Author

Owner

AC-tick pass — closed by PR #90 (squashed):

From Scanning-the-yard lobby screen, Esc returns to welcome ✓ — keydown screen===connected phase lobby branch added, mirrors #79 shape. Mutation-proven (disable keyboard branch → harness keyboard-row reds).
Welcome-screen state is fresh ✓ — backToYard() teardown (net.close + initialState + screen=title) reused; clean state on return.
No keyboard-trap ✓ — both keyboard Esc AND touch BACK exits available (touch BACK folded in per (a)-ratify of Shipwright fork-surfacing, addresses mobile-keyboard-trap by symmetric-input-path discipline).
No regression on opponent-found → match-start transition ✓ — state.spectating/net.spectating gate consistency checked by Surveyor; cannot diverge.
Harness #81 extended with new cancel-transition row(s) ✓ — both keyboard + touch rows independently mutation-proven (disable keyboard → only keyboard-row reds; neuter touch hit-test → only touch-row reds). Completeness meta-check auto-picks up the new node×key cells.

BONUS substrate-discipline applied:

Input-path-symmetry built-in-by-construction: rather than ship keyboard-only fix + file follow-up tracker for touch, Shipwright surfaced the symmetric mobile-keyboard-trap fork at design-time + folded touch BACK into the same PR. Codified-to-embodied from the #80 touch-restart-guard catch on PR #84.
Layered-instrument-axes: portrait render-capture caught touch BACK colliding with DOM audio toolbar at top-left (hit-test passed; visual-layout failed). Repositioned to centered-below-text via mutable-layout pattern. Bank-instance n=2 of "screenshot caught what hit-test passed".
Scope-discipline: #79 checkin parallel touch-back gap deferred to systematic touch-back audit tracker (#88) rather than scope-creep into #85.

Honest ceiling: on-device iOS touch is operator-device-gated (same ceiling as #66/#73). Code axis + harness mutation-proof + render-capture done; iOS-touch live-confirm awaits operator playtest post round-13 redeploy.

**AC-tick pass** — closed by PR #90 (squashed): 1. **From Scanning-the-yard lobby screen, Esc returns to welcome** ✓ — keydown screen===connected phase lobby branch added, mirrors #79 shape. Mutation-proven (disable keyboard branch → harness keyboard-row reds). 2. **Welcome-screen state is fresh** ✓ — backToYard() teardown (net.close + initialState + screen=title) reused; clean state on return. 3. **No keyboard-trap** ✓ — both keyboard Esc AND touch BACK exits available (touch BACK folded in per (a)-ratify of Shipwright fork-surfacing, addresses mobile-keyboard-trap by symmetric-input-path discipline). 4. **No regression on opponent-found → match-start transition** ✓ — state.spectating/net.spectating gate consistency checked by Surveyor; cannot diverge. 5. **Harness #81 extended with new cancel-transition row(s)** ✓ — both keyboard + touch rows independently mutation-proven (disable keyboard → only keyboard-row reds; neuter touch hit-test → only touch-row reds). Completeness meta-check auto-picks up the new node×key cells. BONUS substrate-discipline applied: - **Input-path-symmetry built-in-by-construction**: rather than ship keyboard-only fix + file follow-up tracker for touch, Shipwright surfaced the symmetric mobile-keyboard-trap fork at design-time + folded touch BACK into the same PR. Codified-to-embodied from the #80 touch-restart-guard catch on PR #84. - **Layered-instrument-axes**: portrait render-capture caught touch BACK colliding with DOM audio toolbar at top-left (hit-test passed; visual-layout failed). Repositioned to centered-below-text via mutable-layout pattern. Bank-instance n=2 of "screenshot caught what hit-test passed". - **Scope-discipline**: #79 checkin parallel touch-back gap deferred to systematic touch-back audit tracker (#88) rather than scope-creep into #85. Honest ceiling: on-device iOS touch is operator-device-gated (same ceiling as #66/#73). Code axis + harness mutation-proof + render-capture done; iOS-touch live-confirm awaits operator playtest post round-13 redeploy.

bosun referenced this issue from a commit

2026-06-22 13:47:23 +02:00

feat(client): lobby-wait Esc + touch BACK cancel-transition (#85)

shipwright referenced this issue from a commit

2026-06-22 17:28:30 +02:00

feat(client): Esc/QUIT aborts a running game — confirm modal + versus forfeit (#87)

shipwright referenced this issue

2026-06-22 17:29:03 +02:00

feat(client): Esc/QUIT aborts a running game — confirm modal + versus forfeit (#87 client slice) #96

shipwright referenced this issue from a commit

2026-06-23 19:56:32 +02:00

fix(client): touch BACK affordance on multiplayer check-in (#88)