Repository navigation
0.3.2: gate screener clear behind --allow-destructive, pin HEY main 9dfe00f, README consistency test + badges - #13
Merged
Conversation
…ain 9dfe00f, README consistency test and badges (0.3.2)
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.
Finishes the remaining 0.3.2 work before publishing (version stays 0.3.2; its CHANGELOG entry is updated).
1.
screener clearneeds an explicit opt-inOn HEY main,
screener clearmoves everything waiting in the Screener to Trash (every sender) with no confirmation. It now goes through the same gate as--allow-send/--allow-secret:DESTRUCTIVE_COMMANDSinsrc/policy.js. Without--allow-destructive(orHEY_AXI_ALLOW_DESTRUCTIVE=1) it is refused with exit 2 anderror: destructive command blocked. HEY isn't run. The refusal says what the command would do and suggestsscreener listplus per-senderscreener deny.--allow-destructiveis a hey-axi switch: it is never forwarded to HEY, and=falseis refused.--help, the skill and the README explain the flag. There's a CHANGELOG line and an upgrade note.test/destructive-gate.test.jscovers this with the fake HEY.2. HEY coverage reference: 8bf9310 → 9dfe00f (2026-10-06)
src/manifest.jsonwas regenerated withnpm run manifest:mainfrom basecamp/hey-cli at 9dfe00f (#545). Commands and flags are identical to 8bf9310; only the version and commit metadata changed.hey thread update --name, not yet approved here), 0e4feac (#542, TUI only) and 73938bb (#546, CI only). Against current main, the drift check reports exactly one surface change,+ command thread update (flags: --name), so theupstream driftjob is expected to fail until that command is adopted.4. README consistency test and badges
test/readme.test.jschecks the README's command count against the manifest and router. It also checks the HEY version, commit link, short sha and date against the manifest andcoverageLabel, and checks the badges.npm testandnpm run skill:checkpass locally.