language-performance-safety

Validate runtime performance and safety changes by requiring explicit measurement contracts with profiling, stress evidence, and bounded growth surfaces before approving hot path modifications.

To prevent GC and allocation regressions, you need profiling traces, allocation logs, and system-level benchmarks to justify optimizations and document correct cleanup invariants.

Enforce bounded resource limits by mandating explicit ceilings for queues, collections, batches, retry accumulators, caches, and fan-out to avoid OOM and denial-of-service patterns in concurrency primitives.

Async cancellation requires safety validation covering event-loop and scheduler interaction, blocking work, and unsafe/FFI boundaries to ensure correct cleanup and documented invariants.

You should not optimize native interop or unsafe FFI boundaries without stress evidence, as validating runtime safety changes requires bounded growth surfaces and clearly documented invariants to prevent regressions.