Repository navigation
Unify USB connection before installation or recovery - #11
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
USB setup previously asked visitors to choose installation or recovery before checking their speaker.
/install/now starts with one connection action and read-only discovery: recognized OpenAthan opens settings and credential controls; unrecognized firmware opens explicit hardware and erase confirmation with retry, cancel, and troubleshooting.Connection and recovery remain available without an installation release. Recognized firmware with unreadable status and discovery disconnects cannot authorize flashing. Setup/troubleshooting guides, the installer contract, product/design guidance, and design previews describe the unified flow. Firmware updates remain on the device page or the preserving USB transition.
Area
Validation
Automated: formatting/type checks, 111 unit tests, verified v0.4.0 release import, and static build/link/integrity checks passed. Browser validation passed 213 development cases and 171 built-site cases across Chromium, desktop WebKit, and narrow WebKit; three production-only development skips are covered by the built-site run. Desktop and narrow-screen visual review passed.
Physical: not performed for this change. Reference-hardware connection/routing and preservation acceptance remain required before public deployment; simulator checks do not establish hardware qualification.
Licensing and privacy