Use monotonic integer IDs for ID.random by default

[JamieScanlon]

Summary

• Change ID.random to allocate monotonic JSON integer ids (.number) instead of UUID strings.
• Keep the previous UUID behavior available as ID.randomUUID.
• Integer ids remain JSON-RPC 2.0 valid and work with servers that only accept numeric id values.

Motivation

Apple's xcrun mcpbridge (Xcode) never responds to JSON-RPC requests whose id is a string, null, or float — it only answers integer ids. With the current UUID-string default, clients built on this SDK hang forever on initialize when talking to mcpbridge, while ad-hoc clients that use integer ids work.

String/UUID ids are legal per JSON-RPC 2.0; mcpbridge is non-compliant. Defaulting to integers preserves legality and maximizes real-world server compatibility.

Test plan

• Unit: ID.random yields unique .number values; encoding produces a bare JSON number
• Unit: ID.randomUUID still yields UUID strings
• Unit: string/number Codable round-trips unchanged
• Manual (macOS + Xcode): connect client to xcrun mcpbridge; initialize completes; tools/list returns tools

Made with Cursor