Keep changes focused on the execution protocol, runners, compiler profiles, language SDKs, or conformance coverage. Challenge-specific educational content and workloads belong in the challenges repository.
Before opening a pull request:
gofmt -w .
go test ./...
go vet ./...
sh scripts/check-repository-hygiene.shProtocol and SDK changes must document compatibility effects and add conformance coverage for every affected language. Do not commit participant submissions, hidden evaluations, credentials, local build products, generated reports, model transcripts, or orchestration prompts.