M5: Realtime claims #38

New issue

Closed

opened 2026-07-05 19:20:53 +01:00 by TimCane · 0 comments

TimCane commented

2026-07-05 19:20:53 +01:00

(Migrated from github.com)

Goal

The live claim screen: hub gestures with throttle, snapshot broadcast on every mutation, and a version-guarded client cache across two browsers.

Scope

Hub gestures + per-connection throttle, snapshot broadcast on every mutation, Claim screen, join prompt, version-guarded client cache.

References

Acceptance criteria (docs/14)

A1 Two browsers: claim visible on the other in < 1s
A2 Shared item with shares 2:1 shows exact largest-remainder amounts on both
A3 Concurrency integration test (100 parallel SetShares) consistent
A4 Kill/restore network on one client: pill reconnects, snapshot heals
A5 Refresh mid-session resumes identity from localStorage without rejoining

Notes

Backend hub methods + broadcast precede meaningful FE testing; useParticipantToken + useSession precede the Claim screen and join prompt.

Sub-tasks are tracked as sub-issues below.

## Goal The live claim screen: hub gestures with throttle, snapshot broadcast on every mutation, and a version-guarded client cache across two browsers. ## Scope Hub gestures + per-connection throttle, snapshot broadcast on every mutation, Claim screen, join prompt, version-guarded client cache. ## References - [docs/14-build-order.md#m5---realtime-claims](https://github.com/TimCane/bill-splitter/blob/main/docs/14-build-order.md#m5---realtime-claims) - [docs/05-realtime-contract.md](https://github.com/TimCane/bill-splitter/blob/main/docs/05-realtime-contract.md) - [docs/08-frontend-design.md](https://github.com/TimCane/bill-splitter/blob/main/docs/08-frontend-design.md) - [docs/09-ux-flows.md](https://github.com/TimCane/bill-splitter/blob/main/docs/09-ux-flows.md) - [docs/11-testing-strategy.md](https://github.com/TimCane/bill-splitter/blob/main/docs/11-testing-strategy.md) ## Acceptance criteria (docs/14) - [ ] A1 Two browsers: claim visible on the other in < 1s - [ ] A2 Shared item with shares 2:1 shows exact largest-remainder amounts on both - [ ] A3 Concurrency integration test (100 parallel `SetShares`) consistent - [ ] A4 Kill/restore network on one client: pill reconnects, snapshot heals - [ ] A5 Refresh mid-session resumes identity from localStorage without rejoining ## Notes Backend hub methods + broadcast precede meaningful FE testing; useParticipantToken + useSession precede the Claim screen and join prompt. Sub-tasks are tracked as sub-issues below.