Skip to content

Qualify browser gates, CI e2e, lifecycle UX, and perf baselines - #7

Merged
devteapot merged 7 commits into
mainfrom
feature/browser-gate-qualification
Aug 7, 2026
Merged

Qualify browser gates, CI e2e, lifecycle UX, and perf baselines#7
devteapot merged 7 commits into
mainfrom
feature/browser-gate-qualification

Conversation

@devteapot

Copy link
Copy Markdown
Owner

Summary

  • Browser release gates: Wasm size measurement/enforcement, observe/__ofPerf, reconnect soak (isolated + under match-perf load), WebGPU evidence docs.
  • CI: dedicated local SpacetimeDB match-e2e smoke job.
  • Match lifecycle V1: victory/defeat overlay + Esc leave; Vercel leave best-effort deletes provisioned match DBs.
  • match-perf calls start_match after full lobby claims (fixes stall after interactive lobby cutover).
  • Recorded playtest128 + validation192/128 dilation baselines vs architecture budgets; production create/join/reconnect/leave smoke on of.carlid.dev.
  • Cluster-control playtest checklist + desk-review results.

Test plan

  • CI verify + match-e2e green on this PR
  • Spot-check docs/browser-gates.md / docs/performance.md baselines
  • After merge+deploy: create/leave lobby and confirm match DB cleanup via API cleanup field
  • Optional: re-run ./scripts/run-reconnect-soak.sh --fresh --cycles 20

Add Wasm download measurement, reconnect soak harness, F4/__ofPerf observability,
and deploy-time bundle enforcement so browser release evidence can be recorded
against documented budgets.
Run the two-identity harness against a fresh local SpacetimeDB database so integration regressions are caught before deployment.
Show an actionable victory result and reclaim provisioned match databases once their final lobby member leaves, without making cleanup availability block departure.
Capture the six V1 interaction risks and record the current desk-review evidence until a clean two-player session can validate player understanding.
Differentiate provisioning from the in-game match lobby and preserve the remaining concurrent-load reconnect qualification gap in the implementation guide.
Interactive lobby cutover stopped auto-starting on the final seat join, so the
load harness now starts the match from player 1 once every seat is claimed.
Close the concurrent reconnect gate, document match-perf dilation against
architecture budgets, and capture the of.carlid.dev create/join/reconnect/leave
smoke plus soak script token overrides.
@devteapot
devteapot merged commit 1808b26 into main Aug 7, 2026
1 of 2 checks passed
devteapot added a commit that referenced this pull request Aug 7, 2026
* Fix rustfmt failures blocking CI verify.

* Fix observe test args and e2e attack snapshot race.

* Align frame-spike test with cooldown and harden e2e waits.

* Fix clippy truncating cast and useless conversion.

* Gate AppExit writer to native for wasm victory leave.

* Cfg-gate AppExit import for wasm victory leave.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant