Prepare deck_neo for public launch - #1
Merged
Merged
Conversation
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
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
Why
The repository began as a functional code release, but it lacked the documentation, support boundaries, automation, and community files expected of a public project. Two existing paging tests also depended on timing or ordering that was not part of the product contract.
User impact
Visitors now get a clear explanation of what the Stream Deck integration does, what hardware and software it supports, how to install it, and where current Claude Code and Codex behavior differs. Contributors receive reproducible setup and reporting guidance. CI protects the supported Node 22 and 24 lines.
Validation
Notes
The CI badge will begin resolving after GitHub registers the new workflow on the default branch.