A broken-glass deploy skips manual approval

The emergency path works, but cleanup logic later tears down the wrong environment state. The service still works through the primary path, but one dependency only fails when the old component is finally drained away. The primary component still serves traffic, yet the retirement exercise exposes a latent dependency on what is being removed. The main path still works until the exercise finally removes the legacy dependency it had quietly relied on. Normal traffic stayed clean until the exercise finally removed a legacy path that the service still relied on indirectly. Normal traffic remained healthy until the exercise finally removed a legacy dependency the service still depended on indirectly. Normal traffic stayed clean until the exercise finally removed a legacy dependency the service still relied on indirectly.