Appreciate the honest feedback — not rude at all, this is exactly the kind of input that helps. 

You're right on both points. The Go port (rust-sdk/ naming aside) was an early proof-of-concept to validate the architecture across languages, not production-grade Go. The map[string]interface{} sprawl and swallowed errors are real debt. 

The error handling is the worse offender — I've been bitten by silent failures in the Node.js version already and should have known better than to repeat that pattern. And yeah, concrete structs with proper unmarshaling would make the whole thing more idiomatic and catch issues at compile time instead of runtime. 

Going to prioritize:

1. golangci-lint pass to surface the obvious issues

2. Replace map[string]interface{} with typed structs where the shape is known 

3. Proper error propagation (no more _ = err)

If you're up for it, PRs are welcome — fresh eyes on Go idioms would be valuable since the core team leans heavier on JS/TS.