Make unsnooze better

What is worth reporting

The most valuable reports are the ones nobody else can reproduce from the outside. In rough order of usefulness:

• A limit banner unsnooze did not recognise. Agents change their wording without warning, and a banner that is not matched is a session that never gets recorded. unsnooze report captures the exact text — attach it and the adapter can be fixed in one release.
• A wake that did not happen. Say which agent, which multiplexer, and what unsnooze status showed at the time. If the reset time looked wrong, that detail matters most — a reset parsed as relative rather than absolute is a different bug from a missed wake.
• A wake that happened at the wrong moment. Too early usually means a misread reset; too late usually means the machine slept through it.
• Anything that typed into the wrong pane, which is treated as the most serious class of bug this tool can have.
• Ideas. A flag you keep wishing existed, an agent that is not supported yet, or a workflow that does not fit.

What the statuses mean

Every item on the board carries one:

• new — received, not yet triaged.
• planned — accepted and queued for a release.
• in-progress — being built now.
• shipped — released; the changelog records which version.
• declined — out of scope, with the reasoning given rather than silence.

Here, or a GitHub issue?

Use this board when you want to say something quickly and without an account — it is the lower-friction path, and it is read. Open a GitHub issue instead when you have logs, a stack trace, or a unsnooze report capture to attach, since files cannot be uploaded here. Anything touching the security boundary should follow SECURITY.md rather than either public channel.

Before reporting a wake that did not fire, it is worth running unsnooze doctor — it reports problems rather than a checklist, so a healthy install answers in one line. The troubleshooting guide covers the common causes.