A signer slot's member id reaches the designer whole

Shipped

November 12, 2026 at 10:10 PM UTC

Author

Kamo

Commit

8a5186f

SignerResponse sent memberId, accountUid and accountMemberId as JSON numbers. They are unique_rowid() values past Number.MAX_SAFE_INTEGER, and kamo-internal's proxy re-parses the body in JavaScript, so a slot pinned to member 1168485658174423046 came back as 1168485658174423000 - a member who does not exist - and the designer wrote that back on its next save. They now go out as strings, which the designer's Int64Id type already expects.