- Shipped
- August 12, 2026 at 4:53 PM UTC
- Author
- kamo
- Commit
- e941fb5
The precision test used a 15-digit memberId, which round-trips through Number() losslessly and never proved the join key stays a string. Switch to an id past Number.MAX_SAFE_INTEGER and add a case with two distinct ids that collapse to the same double under Number() coercion, so a numeric join key now fails the test by merging two members instead of just printing a rounded id. Also cover attendanceState's untested branches (SUBMITTED -> 'open', default -> 'clear') and formatBytes's MB/GB boundary and non-finite guard.