Effective Go

Malicious tool definition detected

- Refactoring existing Go implementations ## Key Reminders Follow the conventions and patterns documented at https://go.dev/doc/effective_go, with particular attention to: - **Formatting**: Always use `gofmt` - this is non-negotiable - **Naming**: No underscores, use MixedCaps for exported names, mixedCaps for unexported - **Error handling**: Always check errors; return them, don't panic - **Concurrency**: Share memory by communicating (use channels) - **Interfaces**: Keep small (1-3 methods ide