Verify write-guard hook still fires under '--dangerously-skip-permissions' (CC v2.1.126)

[itsdestin]

Surfaced by /release v1.2.2 → next review (review-cc-changes agent).

CC v2.1.126 CHANGELOG:

`--dangerously-skip-permissions` now bypasses prompts for writes to `.claude/`, `.git/`, `.vscode/`, shell config files, and other previously-protected paths (catastrophic removal commands still prompt as a safety net).

YouCoded's bundled `youcoded-core/hooks/write-guard.sh` (PreToolUse) protects exactly these areas (`~/.claude/` settings.json, memory files, etc.) for cross-session concurrency safety. The hook layer should be upstream of CC's prompt logic so it should still fire regardless of the flag — but this needs verification, since this is an area YouCoded directly couples to.

What to do

1. Set up two active YouCoded sessions (or one session + a concurrent terminal claude).
2. In session A, run `claude --dangerously-skip-permissions` (or set the flag in session config) and trigger a write to `~/.claude/CLAUDE.md` (or any file in the write-guard's tracked list).
3. While session A's write is in flight, have session B also attempt to write the same file.
4. Confirm that session B's write is blocked by `write-guard.sh` (PreToolUse hook output should show "WRITE BLOCKED" message).

If the hook is bypassed too — write-guard's same-machine concurrency guarantee is broken under that flag, which is a v1.2.2 → v1.2.3 regression class.