dan-claude-bot a5b48d5b2c fix(close-root): DenyUsers judged fail-closed — patterns and USER@HOST flag ... All three reviewers, same substance, and they were right that it was lockout-adjacent: the literal grep passed a candidate whom a DenyUsers PATTERN really denies ('DenyUsers dan*' vs admin 'dan'), and the door closed on a false proof. The judgment now lives in the lib as a pure deny_verdict: a literal hit flags, and so does ANY pattern or host-qualified token — a token the check cannot prove irrelevant counts as a hit, never as a pass. The asymmetry with AllowUsers is now the same direction on both sides: every error closes toward repair, never toward a welded-shut door. Also (claude-bot): the -C probe resolves Match blocks against a synthetic addr=127.0.0.1, so Match Address is out of the local proof's scope — named in --help, the README, and the gate's comment, so the separate-session advisory reads as load-bearing, not ceremony. Regressions ride the sourced lib: wildcard (the review's dan* case), '?', USER@HOST, literal hit, irrelevant-literals pass, plus a grep guard that the shipped gate consults deny_verdict. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-18 17:02:48 +00:00
..
runner-config.sh	bootstrap: infer the tailnet tag from the pre-auth key, verify the granted tag	2026-07-17 15:27:09 +00:00
users-config.sh	fix(close-root): DenyUsers judged fail-closed — patterns and USER@HOST flag	2026-07-18 17:02:48 +00:00