Repository navigation
feat(alpha): complete proof-of-play readiness program - #6
Merged
Merged
Conversation
ovasylenko
force-pushed
the
feat/alpha-readiness-program
branch
from
August 24, 2026 20:10
a86c305 to
3514063
Compare
Zendevve
added a commit
that referenced
this pull request
Aug 25, 2026
The pnpm format:check step in CI failed after the proof-of-match merge because the repo had 45 files with formatting drift accumulated since the last prettier pass. Most of the drift landed in the alpha readiness PR (#6) — new ADRs, alpha scripts, the Tauri runtime layer, the client matchCoordinator, usePlayableMatch, etc. — and was not run through prettier before commit. This commit is mechanical: `pnpm format` with no manual edits, applied to exactly the 45 files prettier flags. No semantic changes; no Rust files touched. Verified locally: - pnpm format:check -> exit 0 - pnpm typecheck -> exit 0 - pnpm test -> 20/20 tests pass - pnpm build -> exit 0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Verification
Capability boundary
A successful OpenCade UDP probe is not presented as proof that RetroArch gameplay occurred. Native launch is enabled only for a verified same-LAN host candidate. Authenticated relay and reflexive UDP results remain readiness evidence until OpenCade has a real bridge for RetroArch native TCP traffic.
Physical two-Windows RetroArch gameplay remains the external evidence gate because emulator binaries, cores, BIOS files, and ROMs are user supplied and intentionally absent from CI.