Add zero-content plugin feedback - #1
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
experience=unknowngood / mixed / badbefore any experience signal existsWhy
The previous implementation minimized and sanitized diagnostic data, but it still handled data derived from Sessions, runtime errors and stable installation identity. The new privacy parameter requires a stronger capability boundary: the health and experience paths must never read logs or content at all.
Operational health and subjective experience are now separate. The Host supplies health; only the user can supply an experience verdict. Network sharing remains a separate explicit action and is described as a zero-content payload rather than anonymous transport.
Compatibility and migration
0.3.00.1.0-rc.6Validation
pnpm test:all