Optimize Codebase With Senior Dev

Find the highest-leverage way to improve a named workflow without silently changing behavior. Use targeted scope for a known pain or finding. Use sweep scope only when the user explicitly asks for repository-wide optimization discovery.

Planning is mandatory. Implementation remains available only after the planning artifact validates and the user explicitly authorizes code changes. Prefer configuration and supported capabilities already present in the resolved stack over custom machinery, new dependencies, upgrades, or rewrites.

Non-Negotiables

1. Evidence selects the leverage point; documentation does not create one.
2. Preserve APIs, outputs, errors, side effects, persistence, security, release gates, and operational promises unless the user names an authorized change.
3. Establish a comparable baseline or bounded static evidence before researching an ecosystem solution.
4. Never rank candidates with ordinal arithmetic. Apply the deterministic promotion gates in references/optimization-rubric.md.
5. Sweep breadth is coverage-accounted and depth-bounded. Deferred work is visible and resumable.
6. Never implement from an unvalidated report or execute more than one candidate at a time.
7. Reconcile the requested workflow and success metric with tracing and baseline evidence, then obtain explicit confirmation before researching or selecting candidates.

Canonical Records