optimize

# Optimize Five mode names share one authority: reversible local writes to the resolved target, never push, tag, publish, deploy, or mutate a remote. Full and `extremely-optimize` intentionally select the same measured-floor campaign route, rather than separate procedures; the retired name remains an explicit compatibility mode value. That route runs an isolated five-lens search with an integrated 1.05x gate and an atomic commit. Quick mode runs a single measure-identify-fix-verify loop with a noise-aware keep/revert and a CI guard for the obvious-bottleneck case. `fastopt` mode reports suspected-hot-path hypotheses without mutating code. `fastopt-extreme` mode reports estimated hot paths and complexity-neutral cold-path simplifications while refusing complexity theater. ## Contract | Field | Bound contract | |---|---| | Trigger | The user asks to optimize code, make a path faster, make this as fast as possible, reduce allocations, fix a performance regression, profile and optimize a path, symbol, or diff, or a performance requirement, slowness report, Core Web Vitals miss, or profiling evidence identifies a bottleneck; asks for a measured-floor campaign, hypothesis-only suspected-hot-path analysis, or estimated hot/cold analysis that refuses complexity theater; or says "extremely optimize" or "grill every inefficiency". | | Authority | Full and `extremely-optimize` modes write only the exact VCS-tracked source-target set shown before mutation plus `.outline/optimize/<targ...