docs(#38): record node-stability test result (Steam's virtual isn't usable)#141
Merged
Conversation
On-Deck disappearance-correlation test (2026-07-25): powered a DS4 off; its physical node AND its Steam 28de virtual both vanished in the dead window. On reconnect the virtual returned at the same eventN — but having vanished, it's a new instance that merely reclaimed the freed minor. Steam destroys its virtual when the physical pad dies, so a bwrap bind to it is dead on reconnect, same as raw-binding (#62). Matching numbers are a trap; stability = continuous existence. Closes the 'why not just bind Steam's virtual' question empirically: a virtual we hold open ourselves (evsieve) — or relaunch — is required, not reinvention. Refs #38, #112. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UZuoMpX28CbtGJbigVTv5H
This was referenced Jul 25, 2026
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
1 participant
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.
Banks the one empirical result from today's Deck session into the design doc (§3.1).
Test: powered a DS4 off; its physical node and its Steam
28devirtual both vanished in the dead window. On reconnect the virtual came back at the same eventN — but having vanished, it's a new instance that reclaimed the freed minor number.Conclusion: Steam destroys its virtual when the pad dies, so binding it is dead on reconnect (same failure as raw-binding, #62). A virtual we hold open ourselves (evsieve) — or relaunch — is genuinely required, not a redundant reinvention. Closes the 'why not just use Steam's virtual' question with hardware evidence.
🤖 Generated with Claude Code