Post-launch cleanup: review-queue lanes, bots, snooze, mobile

[jarstelfox]

Post-launch cleanup for the v2 board.

The rewrite has been in prod for a while, and living in it day to day turned up a batch of rough edges. Almost none of these are new features. They are places where the board was technically working but doing the wrong thing for how we actually review. Grouped by the problem each one solves, since the diff already shows the how.

The board was hiding work it exists to surface

• Starved PRs got buried. With a repo priority set, the Starving section pulled starved PRs out of the queue into a capped fold. A high-volume repo (ops) filling that fold pushed a starved PR from a quieter repo (ifixit) behind "show more," and because it had been removed from its own repo block, it never came back. The fairness backstop was doing the opposite of its job. Starving and code regions are non-exclusive highlights now: the card stays in the queue and the section is a copy, the same relationship a claimed PR and "Recently updated" already have with their lanes.
• Recently updated was an activity feed, not a review surface. It listed anything that moved since you last cleared, including PRs you had already stamped and bumps from over a week ago. That pulls against the whole point of the board (what is my move, not what happened). It is bounded now: recent, and only work you might still review.

Bot activity was leaking into human-review signals

Bots author a lot of our PRs and claude[bot] reviews most of them, so the board reading that activity as human work is a steady low-grade wrongness.

• A bot's comment or review read as "changes requested" or a re-review you owed, and once auto-unsnooze landed it would wake a PR you had snoozed. Bot activity stays out of the nudge and the snooze now. The server sends a human-only comment count, since the client can't tell a bot's comment from a human's in a bare comment_count.
• Hiding bots also stripped them from the CI lens and Ready-to-merge, where you still want a bot's red build and its one-press-from-done PR. Hiding now empties the queue and the bot fold but keeps CI and Ready, and a saved filter, author:, or is:bot brings a named bot back.
• Our own machine accounts (ifixit-systems, Copilot) carry no [bot] suffix, so nothing recognized them as bots. They are in the config now.

Small things that only real use surfaces

• The snooze tooltip already promised "until it changes," but comments and reviews arrive on a path that never moves updated_at, so they never woke a snooze. They do now.
• On a phone, tapping a PR title both opened the PR and, a beat later, popped its hover preview on the board you had left. The hover-arm skips touch now (mouse and pen keep it).
• The "shipped while you were away" toast threw the titles away and showed a bare count; it names the PRs now, and it plus the notifications stopped truncating.
• Ten to fifteen pinned filters wrapped the whole filter bar and shoved the controls around. They got their own scrollable row.

QA

• tsc, 446 vitest, vite build; 61 backend tests after build:shared; root eslint ./ reports 0 errors.
• Reviewed by a Fable-model pass over the full git diff master...HEAD; every finding addressed.
• Not yet eyeballed on a real device (the in-session browser renderer was wedged). The mobile popover and the bot behaviors are the ones to poke.

Deploy notes

• No DB changes.
• human_comment_count is an additive wire field; an older client ignores it and the snooze falls back to comment_count.
• Prod and dev config.js both need ifixit-systems + Copilot in their bots list. Both are done (see the deploy comment below).

🤖 Generated with Claude Code

[jarstelfox]

Deploy record (2026-07-25) 🤖

Deployed straight from this branch to both instances; this PR is the review trail. No DB changes.

	instance	image	status
dev	pulldasher-dev.cominor.com	pulldasher-dev:10249968	live
prod	pulldasher.cominor.com	pulldasher:latest (built from 1024996)	live, 598 open pulls loaded

Both config.js files got ifixit-systems + Copilot added to bots. Smoke on both: / 302, /api/v1/me 401, no errors in the logs.

Rollback (seconds, nothing to unwind):

# prod
docker rm -f pulldasher && docker run -d --name pulldasher --restart=always \
  --publish 8090:8090 --env-file ~/pulldasher-prod/.env.db pulldasher:pre-1024996-20260725
# dev
docker rm -f pulldasher-dev && docker run -d --name pulldasher-dev --restart=always \
  --publish 51515:8090 --env-file ~/pulldasher/.env.db pulldasher-dev:ac72d931

Note

Both deploy checkouts (~/pulldasher-prod, ~/pulldasher) are pinned to this branch right now instead of master. Merging this restores them to master-tracking on the next routine deploy.