You'll notice
Useful3 Signal3
Publishing skips the permission prompt when the bytes match an edit you already approved.
What's wrong with this entry?
Anonymous. No account, no email.
What
Publishing an artifact no longer prompts for permission when the bytes being published exactly match a staged automatic edit you already approved. The permission check returns an allow instead of asking.
Details
- Requires the SHA-256 of the pending source to equal the recorded hash on the staged auto-reaction edit, plus a decision reason of either "other" or a safety check the classifier can approve.
- An additional check on the tool and its input also gates this path; when any part fails, the normal ask flow runs unchanged.
- Allowed publishes log an analytics event marking the publish as tool-allowed.
Evidence
b("artifact_comments_autoreact", { edit_publish_tool_allowed: !0 })
Strings lifted out of the shipped bundle, so the claim above can be checked against them.