Hookline for Python and Go: SDK parity across three languages

Until this release the TypeScript SDK was the reference and the others trailed by a few weeks. Starting with 2.0, all three SDKs ship from the same spec on the same day, with the same method names and the same error types.

What parity means in practice

Send, verify, replay and the local dev server work identically. Signature verification uses the same constant-time comparison in every language. The conformance suite runs 300 shared test cases against each SDK before a release is tagged.

Upgrading

There are no breaking changes for TypeScript. Python users should note that verify() now raises instead of returning false, and Go users get a context-aware client. The migration guide in the docs covers both in a few lines.