#265 feat(auth): state the auto-deny deadline on every challenge channel

[Anonymous]

Originally created by: fu351

Slice

• UX fix wave / UX.3 - challenge deadline visibility (2026-08-05 audit + critique P1)

What this PR does

An unanswered AUTH challenge auto-denies - 120s at the GUI dialog, 1200s for the whole challenge - but no channel ever said so; a human who stepped away learned about it only by digging in doberman log. Every channel now states its own deadline via one shared render.deadline_note helper: the TTY prompt appends [auto-denies in 20m if unanswered], the GUI dialog carries a body line with its 2-minute window, and doberman status reports warning: N challenge(s) auto-denied in the last 24h - see doberman log (derived from existing redacted log rows via the shared TIMEOUT_METHOD constant; no new state).

Tests added (run in CI)

• tests/unit/test_prompter_deadline.py - TTY prompt and GUI dialog text both state the deadline; helper output is ASCII.
• tests/unit/test_cli_status.py - status counts a seeded timeout row inside 24h, ignores older rows, prints nothing when N=0.

Security checklist

• [x] Fails closed on error / uncertainty (timeout still denies; unparseable ts rows are skipped, never counted wrong)
• [x] No secret, full file, or unredacted prompt logged or committed
• [x] Any guardrail/learning change is raise-only (presentation-only; deadlines unchanged)
• [x] Every BLOCK/AUTH carries reason codes + a human explanation (unchanged)

Edge cases covered / Deviations from plan / Risks introduced

• Channel-specific honesty: TTY shows the 20m challenge window, GUI shows its own 2m dialog window.
• The 24h scan is bounded (limit=200) and tolerant of naive/corrupt timestamps (skipped, not crashed).

[Anonymous]

Ticket changed by: fu351

• status: open --> closed