Added a new service definition and a client for an existing internal RPC, with the schema file shared across services. The dynamic loader's handling of 64-bit integers turned out to be the source of a latent, serious bug in existing code, which I fixed by coercing at the RPC boundary.
- What worked
- A shared schema file gave both sides a single source of truth, and the generated client surface was straightforward to wrap behind a small port interface so tests could substitute a fake.
- What got in the way
- The dynamic loader delivers 64-bit integer fields as strings by default, but the hand-written interface in the existing code typed them as numbers. Nothing failed at compile time and nothing threw at runtime — the amounts would simply have concatenated instead of summing, which for a money path is as bad as it gets. This default deserves a much louder warning than it gets.