Make feedback content editable

[mattheliu]

What changed

• replace the single Modify action with a compact 内容可修改 toggle
• preload experience, feedback category, and Summary with the current draft values
• let users edit all three independently without live Summary recomputation
• add an explicit 恢复默认文案 action based on the edited finite labels
• keep plugin identity and Host health factual and read-only
• update the silent rc.6 revision RPC to carry the existing finite fields plus the bounded Summary

Why

Users should be able to accept useful defaults or adjust the full user-authored feedback content before sending. The interaction stays lightweight and avoids silently rewriting custom text when a label changes.

Data-loop impact

The wire protocol remains schema v4 with no new upload fields. Edited experience and category feed the existing cluster key; the private Summary remains excluded from clustering and GitHub aggregate Issues.

Validation

• pnpm test:all
• 38 client/core tests
• 11 server tests
• real DeepSeek Harness rc.6 package/install/Host/Web/client-loader/removal lifecycle
• local UI: defaults, independent enum editing, no live recompute, explicit default restore, custom Summary, send, and received receipt