You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.236,
ImprovementsSection of the release
What
The approval prompt for an artifact database write now shows the local file the document comes from, and lists reasons the automatic permission classifier cannot approve it: a path whose spelling can name a different file, a path resolving outside the allowed read paths, and a hard-linked source.
Details
The prompt no longer promises session-wide coverage when the write is not one that can be covered for the session.
Evidence
the path\u2019s spelling can name a different file than it appears to \u2014 approval must come from the user, not the auto-permission classifier
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
