Rebuild repository experience around local qualification - #10
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.
What changed
Why
The public repository mixed duplicated documentation, broken or inconsistent navigation, obsolete Pages checks, and a website that could not truthfully perform installed-device qualification. This change restores one canonical source for generated surfaces and separates GitHub documentation from the local hardware-facing console.
User and contributor impact
Visitors get a concise README and task-based documentation entry points. Contributors get repository-wide Markdown link and anchor validation plus generated folder ownership pages. Installed users get a local-only console that reads the actual bridge state without cloud inventory or direct browser HID access.
Verification
188a1feNo release, tag, package publication, hardware-writing authorization, or product-readiness claim is included.