Kotlin Code Review

Lead with findings ordered by severity. A review is not a style summary.

Evidence workflow

1. Read the change, surrounding contracts, call sites, build configuration, and relevant tests.
2. Reproduce or statically trace each suspected defect.
3. Check nullability and platform types, equality/hash behavior, exceptions, ABI, serialization, coroutine cancellation, resource ownership, and dependency scopes.
4. Verify tests would fail for plausible defects and exercise production paths.
5. Report each finding with location, trigger, impact, and smallest credible remedy.

Severity

• Critical: data loss, exploitable security defect, broad outage, or irreversible incompatibility.
• High: common-path wrong result, deadlock/leak, broken public contract, or migration parity failure.
• Medium: bounded correctness, resilience, performance, or maintainability risk.
• Low: concrete improvement with limited operational impact.