docs: align README telemetry line (no telemetry shipped)#186
Merged
Conversation
README line 223 ("No telemetry or analytics by default — opt-in only, error
stacks only") implied an opt-in error reporter exists, contradicting line 256
("zero telemetry") and PRIVACY_POLICY.md ("No analytics, telemetry, or
tracking of any kind"). Verified: no telemetry is implemented — the only
"telemetry" token in src/ is a comment at platform.js:150. Reworded to
"nothing is collected, not even opt-in error reports" so all three surfaces
agree. (docs/TELEMETRY_DESIGN.md remains an unshipped design exploration.)
heznpc
added a commit
that referenced
this pull request
Jun 9, 2026
… to #192 (#194) Wraps up the shadow-DOM migration: - header-controls.js: document why the header language selector / dark toggle stay in the light DOM by design — they are blend-in components that deliberately borrow Skilljar's own `headerheight align-vertical` classes to sit like native header items. Shadow-isolating them would sever exactly the styles they borrow and force hand-replicating the host header's metrics (brittle against Skilljar changes, no observed leak there). Overlay components with their own visual identity (FAB, sidebar, TOC) are the ones that live in #skillbridge-root. - CHANGELOG [Unreleased]: add the entries merged since the last batch — FAB icon collapse (#182, #183), reset-button host-blue leak (#185), "Claude(Claude)" gloss self-duplication (#187), chip alignment (#191), shadow-root isolation (#188–#190, #192), README telemetry wording (#186), capture:store → @starter-series/shotkit (#192). No behavior change (comment + changelog only).
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
1 participant
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.
README line 223 read "No telemetry or analytics by default — opt-in only, error stacks only", implying an opt-in error reporter exists. That contradicts:
Verified: no telemetry is implemented — the only
telemetrytoken acrosssrc/lib,src/content,src/background.js,src/popupis a comment atplatform.js:150("…round-trips through JSON for logs / telemetry").docs/TELEMETRY_DESIGN.mdis an unshipped design exploration.Fix: reworded 223 to "No telemetry or analytics — nothing is collected, not even opt-in error reports" so README ↔ README ↔ PRIVACY all agree.
(README:330 "Translation quality analytics and community review" is a roadmap item about translation-quality review, a different sense of "analytics" — left as-is.)
🤖 Generated with Claude Code