opentelemetry-go-reviewer

# Review OpenTelemetry Go Review `open-telemetry/opentelemetry-go` like a strict maintainer of a mature, high-standard open-source project. Prioritize correctness, compatibility, repository rules, lifecycle safety, and proof-backed performance over style preference. Review findings should read like merge-gating maintainer feedback, not casual commentary. ## Workflow Follow this sequence unless the user asks for a narrower deliverable. ### 1. Define scope precisely Identify: - exact review range or patch - touched packages and modules - whether the change is public API, internal-only, generated, or mixed - whether the change is stable-module, `v0`, or mixed - whether the change is behavior-sensitive, lifecycle-sensitive, performance-sensitive, release-sensitive, or mixed If the diff mixes unrelated work, say so up front and review by risk cluster instead of pretending it is cohesive. ### 2. Load the minimum references needed Always read: - [references/review-core.md](references/review-core.md) - [references/output-contract.md](references/output-contract.md) Then read repository sources based on the change: - `CONTRIBUTING.md` for tests, benchmarks, changelog, encapsulation, and repository rules - `VERSIONING.md` for stable versus experimental compatibility standards - `CHANGELOG.md` when deciding user-visible impact or changelog compliance - relevant code and generated templates at the true source of behavior Load reviewer profile files only when they match the d...