v0.5.0 — Secure feedback reporting loop
v0.5.0 — Secure feedback reporting loop
This release adds a local-first feedback path for evidenced agy-worker defects and concrete improvement requests.
Highlights
- local
bug,improvement, and private-onlysecurityfeedback drafts - exact preview digest plus a separate matching public-safety digest before any public submission
- fixed public destination and in-memory exact-body submission
- metadata-only
feedback-triage.shwith 100-record, 64 KiB, one-page, and 20-second bounds - weekly/manual read-only feedback watcher with no issue mutations or agent ingestion
- prompt-injection, spam/burst, lookalike-target, overflow, signal, process-group, and bytecode regressions
Security and privacy boundary
The periodic watcher does not request titles, bodies, comments, labels, or usernames. Only canonical issue numbers/URLs, timestamps, and bounded aggregate flags are emitted. Explicit security reports remain on GitHub's private vulnerability route. Keyword matching is an additional deny barrier, not proof that a draft is safe to publish.
Verification
- 27 offline suites: 2,964 passed / 0 failed
- reporting: 47 / 47
- feedback triage: 26 / 26
- package/CI policy: 365 / 365
- RTK: 154 / 154
- exact merge-SHA push CI and GitHub Pages: successful
- independent security and instruction audits: accepted
The release does not automatically submit, label, comment on, or close GitHub issues, and it does not dispatch agents from issue content.