Add confirmed category summaries - #2
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
Plugin authors need more direction than a bare good/bad signal, while users need assurance that their current task, conversation, logs, and error details cannot enter the feedback path. A closed category vocabulary provides useful product context without opening a free-text exfiltration channel.
User impact
Users now choose one of eight broad experience areas, review every readable field locally, and explicitly confirm the upload. The Agent can prepare a fixed-template preview but cannot publish it. Network transport metadata remains outside the payload guarantee and is documented honestly.
Validation
pnpm test:all0.1.0-rc.6package/install/Web boot/Client loader/remove E2E passed