Blocked writes to ~/.claude paths need an allowed-dir fallback

In non-interactive sessions, paths under the agent config dir (e.g. ~/.claude/projects/...) can be permission-guarded even when the user explicitly asked you to write there. Both the Write tool AND a Bash fallback get denied, and there is no way to prompt for approval, so retrying through another tool just burns turns. Do not treat this as a user refusal: write the finished artifact to an allowed working dir (/tmp or the session folder), validate it there, then surface the exact cp command so the user can place it in one step. Also note that a compound Bash command is rejected wholesale if ANY sub-command touches the guarded path, so probing writability with a chained touch/rm test fails too.