Examples · Bug fix
Nine event types that updated the database but never the screen
Wired live-refresh for the missing subjects, and rewrote the guard's admission table so what's left out has a durable reason instead of "out of scope for this refactor."
- $11.93
- Cost, start to finish
- 48m
- Lead time, filed to merged
- 4
- Files changed in the merge
Measured from this task's real merge.
- Cost
- $11.93
- Turns
- 192
- Lead time
- 48m
- Merged
- Aug 7, 2026
- Diff
- 4 files · +351 -30
The SPA's realtime router maps each event type to the queries it should invalidate. Nine event types, covering members, invitations, integrations, plan limits, and workspace lifecycle, mapped to nothing, so a second viewer only saw the change after a manual navigation.
What was asked for
Nine of the SPA's realtime event subjects route to zero cache invalidations, so the Members, Repos, Secrets, Integrations and Plan screens never live-refresh — a second viewer sees stale data until they navigate away and back.
Filed by a developer, routed by capability (react).
What the herd did
- plan
- code
- review
- merge
- verify
- done
- plan
- Read the router's own coverage test to find every event type with no branch, and grouped the nine into the screens they actually affect.
- code
- Added a branch per subject group, invalidating the right query keys for members, integrations, plan status, and workspace lifecycle events.
- review
- Rewrote the coverage test's admission table so any event type still left unrouted needs a real, written reason instead of a blanket exemption.
- merge
- Four files: the router, its query-key import, and two test files covering the new branches.
- verify
- Confirmed the previously-silent event types now trigger the expected refetch on the affected screens.
- done
- $11.93 and 48 minutes, one of the cheaper fixes in this set.
What it changed
The merge touched 4 files (+351 −30). Among them:
app/src/realtime/eventRouting.tsapp/src/realtime/eventRouting.test.tsapp/src/realtime/eventRouting.coverage.test.tsapp/src/api/queryKeys.ts
What it cost
$11.93 in model spend, 192 agent turns, and 48m from filed to merged. See what a month of work like this would cost your own team on our cost calculator.
A live-updating screen is only as live as its worst-covered event type.
Got something like this to ship?
Tell us what you're building. We'll set your workspace up and you can file it today.