v0.19.45

Gate-self floor unification

Gate-self (changes to the gate's own code/config) is now the ordinary hard-floor category gate_self - not a separate un-skippable tier. The bespoke gself: coverage hash and its PASS-only release are retired; gate-self changes inherit the full floor lattice (audit_coding PASS, SYNTH_CONFIRM, free confirm_floor, lineage-verified recommendations_applied, accept_risk_no_review), while judgment/path skips and an uncovered recent_pass still never release them. This eliminates the gate-self commit deadlock (review -> findings -> apply -> re-fire -> no admissible release).

• False-floor prevention: collision-prone gate basenames (hooks.json, integrity.py, cacert.pem, platforms.yaml, ...) floor only in repos that demonstrably contain the gate product (repo-identity sentinel); distinctive names and .git/hooks/ stay global. No path matches that didn't match before.
• Zero-changed-line file ops still review: a pure rename / mode-only / binary change to a gate file tags a synthetic path-derived floor hunk.
• Comment-only edits to non-core gate files stay review-free; gate-core always reviews.
• Stale (pre-0.19.45) hooks fail OPEN on gate-self against the new server - never a deadlock.

Published with npm provenance via the tag-path workflow.