You'll notice
Useful4 Signal2
Always-allow options only appear if their rule validates, and fall back to one-time allow otherwise.
What's wrong with this entry?
Anonymous. No account, no email.
What
Bash, skill, workflow, file-edit, web-domain and plan-mode consent prompts no longer build their permission rules when you click. Each option now carries a pre-checked list of permission updates, and accepting just replays that list. If the rule cannot be validated locally the option does not appear at all, and an accept with a missing or invalid entry degrades to a plain one-time allow.
Details
- Suggestions arriving from the backend as arrays are run through a length-capped, trap-safe validator before they can become an option.
- The prompt gained a
yes-apply-suggestionschoice; callers thread through persist, suggestion and veto state. - Permission-mode changes are asserted when the option is built, logging
setModeRow: schema rejected a designed setMode updateon rejection. - Old inline builders were deleted, including the skill exact/prefix rule builder and the file-edit
.claudefolder scope branch.
Evidence
yes-apply-suggestions, setModeRow: schema rejected a designed setMode update
Strings lifted out of the shipped bundle, so the claim above can be checked against them.