[Jammy2211]

Why

Every action button opened a prefilled GitHub issue that still had to be submitted there: two taps, and the second one left the dashboard.

What

• A 🔑 chip under the header takes a fine-grained token once (Issues read/write on this repo), kept in that browser's local storage. With it, a tap creates the same issue from the page through the GitHub API: title, body and label are read back out of the link the button already carries, so the workflows behind it see no difference, and the links stay the fallback without a token.
• The row disappears at once and stays hidden across reloads until the board's own re-render no longer carries it (or a day passes, which means the action failed and it comes back).
• 📥/📑 open an inline notes box first; the notes replace the placeholder line in the issue body. A failed call leaves the row and says why in a toast. Tapping the chip again signs out.
• README paragraph on setting it up.

Checks

• python -m pytest tests/ -q: 181 passed (the self-contained-page test now allows exactly one fetch, to api.github.com, and judges markup with the script stripped).
• Rendered page script parses under Node.
• Driven in headless Chromium against a stubbed API: setup, one-tap add hides the row and posts the labelled issue, intake with notes lands in the body, hidden rows survive a reload, a 403 leaves the row with an error toast, sign-out restores plain links.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Rhn9qWAjP54dP27dyEibG2

---

Generated by Claude Code