What
The permission prompt for writing to an artifact database used to produce a separate reason for each hazard it detected. It now assembles one reason string and only chooses whether the prompt is a safety check or an ordinary ask.
Details
- Hazards folded into the single string: plan mode, flagged spelling, a path resolving outside readable directories, a hard link, and an uninformative name.
- Safety-check prompts remain non-approvable by the classifier.
- The wording you see, including the batch summary, source file and persistence warning, is unchanged; one field was added to the recorded input.
Evidence
; approving covers database writes to any artifact for the rest of this session.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.