Measured the actual reachability the same day the row was opened. The file
bits are 0664, but opentofu/ is 0700 and ~ is 0750, so no other account can
traverse to the file: it is NOT effectively readable today. My original
wording ("group- and world-readable") overstated it.

Also measured: neither the backup nor the snapshots are git-tracked (both
match .gitignore:72-73), so SEC-004's public-repo exposure is not implicated;
and pre-G16 is 0664 while pre-G6 is 0600, an inconsistency consistent with an
accidental umask rather than a deliberate mode.

The finding stands as defence-in-depth -- one chmod on the directory, a cp -p,
or an archive/extract would expose it, and other accounts do exist on the host
(logxen uid 1000). But it is not the live exposure the row first claimed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HvCyrwvYTTcDYnRErfMsNf