ln-813-runtime-optimizer

Runtime performance issues in a codebase are optimized by loading audit findings, prioritizing fixes across modules, and applying surgical changes verified through a keep/discard loop with tests and lint checks.

Fixing blocking IO and sync sleep performance issues requires a prioritized fix loop that applies targeted surgical optimizations to hot-paths, followed by automated test and lint validation to ensure correctness.

The keep/discard verification loop works by applying targeted code fixes, running deterministic automated tests and linting, and retaining only the changes that pass validation while discarding the rest.

The runtime optimizer enforces pre-flight checks and uses isolated worktrees to apply changes, ensuring that surgical fixes are validated independently before any modifications are merged into the main codebase.

The runtime optimization workflow is a phase-driven process covering pre-flight checks, loading audit findings, iterating through targeted fixes with test verification, and generating a final structured report of applied changes.

Yes, the optimizer specifically targets blocking IO, sync sleep, excessive allocations, and hot-path optimizations by iterating through surgical fixes and enforcing deterministic verification through tests and lint.