What Several permission checks were added that deny certain actions outright instead of prompting, specifically in situations (like Cowork sessions) where there is no "consent surface" — no user available to respond to an approval prompt:
- Uploading a local file as an artifact asset is now denied before even building the approval prompt, when there's no read rule for the path, the path looks suspicious or outside the allowed area, and the session has no consent surface.
- A similar early denial was added to another artifact-related action when a consent-surface-dependent value is missing and the session is in the same no-prompt (Cowork) state.
- Two new deny-response builders reject local file reads that fall outside a Cowork session's connected folders, or that can't be examined, explaining that no one can answer the approval card in that session.
Why Without these guards, an action needing approval could stall indefinitely in a session with no user present to approve it. Denying up front instead gives a clear, immediate result rather than a silent hang.