Document verified vacuum compatibility and fix report routing - #92
Merged
Merged
Conversation
Lash-L
marked this pull request as ready for review
September 18, 2026 18:29
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.
Successful onboarding reports were missing from the tested-vacuum list, and the reporting links led to a disabled Discussions category. This consolidates the verified results into the docs and provides a working compatibility issue form.
Includes the compatibility additions proposed by Jezza34000 in #75, frazierjason in #82, and alwarnecke in #89, plus the S7 Pro Ultra report in #65 and S8+ confirmation in #66. The compatibility-only PRs #75, #82, and #89 can be closed as superseded after this merges; the broader documentation proposals in #65 and #66 still need their own disposition.
Closes #46
Closes #49
Closes #52
Closes #56
Closes #57
Closes #60
Closes #61
Closes #64
Closes #70
Closes #78
Closes #79
Closes #90
Also references #3, #47, #48, #67, and #83. Their remaining troubleshooting or device-support work is not resolved by this documentation update.