Repository navigation
docs: remove duplicated pinned microphone privacy fragment - #2464
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.
Addresses OBSERVABILITY-8 from REVIEW.md. Removes the repeated six-line pinned-microphone privacy fragment while retaining the fuller field list, fallback details and forwarding explanation immediately above it. No telemetry, payload or privacy policy changes.
Independent full diff and owning forwarding-policy review against origin/main 8a38235: GREEN. This extracts only the corresponding factual cleanup from broad pending #2336; that PR remains untouched.
Exact head 163d506: bash check.sh recorded six static PASS, one guarded full-fast exit 3 (overall FAIL), and the metadata-only preflight step skipped by the canonical runner. Standalone preflight passed. Source receipt was clean and stable and archived before verify-change.sh, which selected no app checks. No logger, audio, telemetry, account or native execution was needed or performed. Full fast and exact-head hosted validation remain pending.