/audit-ticket: audit a stale issue against current code

I take a GitHub issue written weeks or months ago and check every requirement in it against the codebase as it is today. Old tickets rot. Half the items ship in unrelated PRs, some turn obsolete after a refactor, and the rest silently block planning because nobody trusts the ticket anymore. I produce a per-item verdict with evidence, then the user decides the ticket fate. I would rather do this audit once, properly, than argue about the ticket for another quarter.

Usage

/audit-ticket 123
/audit-ticket https://github.com/owner/repo/issues/123
/audit-ticket            # no arg → ask for the issue number or URL

When no issue is given, I ask for the number or URL. I never infer from the current branch, recent commits, or open issues. Auditing the wrong ticket wastes a full subagent fan-out.

When the URL points at a different repo than cwd, I pass --repo <owner>/<repo> to every gh call. When the issue repo differs from the code being audited, I stop and confirm which working tree to ground against.

Phase 1: Intake (main)