pre-push hook's committed-violation language overclaims: diff-scoped findings cannot see a clean committed violation outside --only

VENUS-476/84ecf29 remediation left this disclosed in .gitpush-pre.sh's own comments (lines 454-457: 'A violation in a CLEAN committed file is not seen here at all... prepush_scope's clean-against-HEAD branch is unreachable from here') but the hook/prepush_scope still emits language elsewhere implying a committed violation is caught (the DEFERRED-vs-PASSED framing from VENUS-476's own commit body). Actual mechanism: findings are built only from staged+unstaged+untracked diffs (git diff --cached + git diff + git ls-files --others), never from committed-but-clean content. A violation already landed in a file outside the current --only scope with no dirty hunk is therefore undetectable by this hook at push time, full stop - not merely DEFERRED (which implies a future pass will catch it), since nothing re-scans it unless that file gets a dirty edit later. Remedy per pmmaster 2026-10-06: narrow the CLAIM in the hook's/prepush_scope's own text to say this precisely, do NOT add a whole-tree committed-content scan (mars already does whole-tree greps separately, measured; venus's design is intentionally diff-scoped and that stays). Venus-only - mars does not share this gap.