#272 qa: a guided tour of the new UX - put seven fresh improvements through their paces (no code required)

[Anonymous]

Originally created by: fu351

A wave of UX improvements just landed (#252, [#261], [#265], [#266], [#267], [#268]), and every one of them changes something CI fundamentally cannot verify: whether colors read on a real terminal, whether a screen reader actually announces the approval queue, whether a prompt feels clear at the moment it interrupts you. That takes a human on a real machine - and fresh eyes are strictly better here than the eyes that built it.

So this issue is deliberately shaped as a tour: by the end you'll have installed Doberman, watched it make PASS/AUTH/BLOCK decisions, approved a challenge from the dashboard, and seen most of the product's surface. No code required - your deliverable is a comment with the checklist results and anything that felt wrong along the way. "Felt wrong" reports are as valuable as hard failures; UX bugs rarely throw exceptions.

Setup

Follow the README quickstart (pip install doberman-core, then doberman setup in a scratch repo). doberman demo generates decisions to look at; doberman dash starts the local dashboard (needs pip install "doberman-core[dash]").

The checklist

Verdict rendering (#252)

• [ ] In a real terminal, doberman log / doberman status / doberman review show BLOCK bright-red bold, AUTH yellow bold, PASS green - and the TUI's verdict column matches.
• [ ] doberman log | cat (piped) and NO_COLOR=1 doberman log print plain text with column alignment identical to the colored view.

Setup wizard (#266)

• [ ] Mistype the mode at the prompt (e.g. blanced): it warns and re-asks instead of exiting and losing your answers.
• [ ] Each advanced-tuning dimension shows a one-line plain-English description above its prompt.

Session summary rename (#267)

• [ ] doberman session-summary prints the panel, and the old doberman dashboard still works identically (it is a permanent alias - existing installs depend on it).

Challenge deadlines (#265)

• [ ] Trigger an AUTH challenge: the terminal prompt (and the GUI dialog, if it appears) states when it auto-denies if unanswered.
• [ ] Let one expire, then run doberman status: it reports a challenge was auto-denied in the last 24h.

Dashboard (#261, [#268])

• [ ] With your OS in light mode, the PASS/AUTH/BLOCK badges are clearly readable - not pale green/amber on white.
• [ ] The browser tab title shows a pending count, e.g. (1) Doberman Dashboard, when an approval is waiting.
• [ ] Approve takes two clicks: first click turns the button into "Confirm approve", second click within 3 seconds resolves it. Deny stays single-click.
• [ ] The pending card shows its expiry time and has no thick amber stripe down its left edge.
• [ ] Bonus, if you have a screen reader (Narrator/NVDA/VoiceOver): a newly arriving pending approval is announced, and the TOTP field announces its name ("TOTP code").

How to report

Comment with the checklist (pass/fail/couldn't-test) plus your OS, terminal, and browser. Partial runs are genuinely useful - check what you can, skip what you can't. Anything broken or confusing gets its own issue; link it here. Questions welcome on this thread.