TEST ROOMCODES 110 UI Case

TEST-ROOMCODES-110 - Invalid and expired room-code recovery

Linked specification for the matching authoritative QBrain TEST record. Persistence is reported by receipt.json. Current implementation evidence is in implementation-receipt.json; the original documentation-only snapshot is retained under archive/design-20261027/.

Field	Specification
Objective	Verify Invalid and expired room-code recovery.
QBrain reference/scope	TEST-ROOMCODES-110; Word Pairs / PROD-WORDPAIRS; workspace <home>/github/WordGame/.mcpServer/wordpairs; layer layer-1
Source revision	Original designs at 435be05abac5310172cfb9a9290c9d7ea0d1cbde; exact dirty prose/decision hashes in sources.json. New UI-DEC decisions derive from the operator instruction to fill gaps.
Source links	decisions.md; word_association_game_requirements.md
Frame/element identifiers	GAP-FLOW-ROOMCODES, GAP-TRANS-ROOMCODES-01, GAP-TRANS-ROOMCODES-02; exact SVG anchors are listed in coverage.md
FR/TR → specific AC references	TR-ROOM-CODES-010#TR-10-C01
Priority	high
Platform/viewport	Phone Chromium/Android and Safari/iPhone where applicable; project matrix320x568,390x844,844x390;1280px at400%zoom and200%text enlargement. OS-native installation is a separate physical-device dependency.
Preconditions/roles	Alice is at room-code entry; valid active and closed-code fixtures exist.
Test data	Invalid eight-character Crockford code, closed room code,10 invalid attempts in one minute and a valid generated code.
Synchronization	Await the explicit observable conditions and source-defined deadlines below; no fixed sleeps. Harness timeouts do not create a product response-time SLA.
Cleanup	Close case-owned contexts and reset only isolated fixture accounts, rooms or content, including after failure. Preserve shared catalog and real profile data.
Automation readiness	Automated isolated browser integration and supporting application/SQL checks executed; operational boundaries remain separate.
Basis	Specified by cited designs/QBrain; new gap behavior is specified by UI-DEC-01..08. Synthetic fixture identities/data are test configurations.
Execution	Executed applicable UI-DEC variants in Chromium with real React and isolated HTTP/application/domain fixtures; real disposable PostgreSQL covers persistence/audit. See execution receipt. This is the documented recovery variant, not a claim that every historical compound obligation was rerun.

Ordered actions and observable results

Step	Action / condition	Observable expected result
1	Submit invalid/closed codes, then correct to the valid active code.	A safe error permits correction without leaking another active code; the valid code reaches the intended room.
2	Exceed the documented invalid-attempt window and attempt another code.	Further invalid attempts are rate-limited until the window allows retry; no unauthorized membership or false success occurs.

Scenario

Feature: Invalid and expired room-code recovery
  Scenario: TEST-ROOMCODES-110 design verification
    Given Alice is at room-code entry; valid active and closed-code fixtures exist.
    And the fixture data is Invalid eight-character Crockford code, closed room code,10 invalid attempts in one minute and a valid generated code.
    When Submit invalid/closed codes, then correct to the valid active code.
    Then A safe error permits correction without leaking another active code; the valid code reaches the intended room.
    When Exceed the documented invalid-attempt window and attempt another code.
    Then Further invalid attempts are rate-limited until the window allows retry; no unauthorized membership or false success occurs.

Boundaries

Existing requirement, newly explicit UI scenario; no change to historical evidence or status.

Criterion references identify intended verification. Non-UI transaction, distribution, release/deployment and native OS guarantees retain separate technical/operational tests; this document is not a claim that a compound criterion passed.

Implementation evidence

Implementation snapshot and tiered results, hashed source inventory, and raw execution logs bind this case to the current tested implementation. Browser journeys use actual pages and real application/domain services behind isolated HTTP/persistence/time ports. They do not establish physical screen-reader behavior, native phone install, real OIDC, deployed availability or real private-push2..25UI delivery. Reflow at400% is the documented320CSS-pixel equivalent, not a physical browser-zoom certification.