Changelog

This release ships the away-email digest — a batched notification email that collects questions, mentions, comments, assignments, handoff completions, agent failures, and due/overdue cards into one email per person, with quiet hours, presence-aware delivery, and crash-safe deduplication. It also introduces a continuous QA system that runs visual regression and review checks in disposable Docker workers, with evidence attached to issue cards. Smaller improvements include agents waking on new comments, a layout fix for agent rows at large text sizes, and a range of internal reliability fixes.

New

• Get a single digest email covering everything that happened while you were awayA new "while you were away" email batches questions, mentions, comments, assignments, handoff completions, agent failures, and due/overdue cards into one digest per person. Delivery respects a 10-minute collection window, quiet hours, and your presence — and an atomic claim/lease transaction ensures a crash, restart, or two containers racing the same database can never send the same digest twice. 184ea4a 4bd631d 600a148 a68b68c 834c885 5f31ef3 9aca613 850b982 f4bc9d4 35a6f60 fdf4443 c6b1f00 4e6fe38
• Away email is now available to all users, not just ownersThe owner-only allowlist has been removed from the deploy configuration, so every user on a workspace can receive the away digest. 4e6fe38
• Agents assigned to a card now wake when a new comment is publishedPublishing a comment on a card that has an assigned agent now triggers the agent to resume, so it can respond to the new input without waiting for a manual nudge. a7674b6

Improved

• "Your turn" label renamed to "Yours" in the email and attention popoverThe attention popover and away-email digest now use "Yours" with a shared • count separator, consistent across both surfaces. 9aca613

Fixed

• Agent rows wrap correctly at large text sizes instead of hiding content off-screenAt 200% text size on a 390 px viewport, the agent row now wraps to a second line so the name, hover actions, and Connect button all remain visible and reachable. The layout is unchanged at 100%. 27b90d2

This release introduces a QA run tracking system integrated with Overdew, including the full scaffolding for disposable QA runs — lifecycle management, coverage, fixtures, review, and a worker/client architecture — along with a Docker configuration fix to keep temporary QA files out of production images.

New

• Disposable QA runs are now tracked in OverdewA full QA run system has been added under scripts/qa/, covering lifecycle management (lifecycle.ts), coverage tracking (coverage.ts), fixture handling (fixture.ts), review (review.ts), and a worker/client architecture (worker.ts, client.ts). Runs are registered and tracked in Overdew via overdew.ts, and the corresponding API surface is exposed through src/qa_api.ts and src/qa_protocol.ts. a569231

This release ships card tagging and filtered search — cards can now be tagged and the palette filters by those tags. The card toolbar is used for tag selection, and inline tags are restored to the card view. Dependency updates round out the release.

New

• Tag cards and filter search results by tagCards can now be tagged, and the command palette filters results based on those tags. Tag selection is available directly from the card toolbar, and inline tags are displayed within the card view. 2d8e586 cc8c32c 6a396af

This release fixes a stale-page bug where leaving a board tab open and returning to it would show outdated content instead of today's board. It also reduces the frequency of scheduled backup cleanup checks.

Fixed

• Returning to a long-open board tab now shows today's board, not a stale snapshotHTML pages were served without Cache-Control headers, so browsers reloading a discarded tab would silently serve the stored copy — showing the old background and cards with no indication anything was wrong. Pages now carry private, no-cache, must-revalidate and Vary: Cookie, so the browser always revalidates with the server before displaying them. Additionally, tabs restored from the back/forward cache now trigger a resync via the pageshow persisted event rather than relying on the EventSource reconnect, which was neither guaranteed nor ordered. 6055789