dev-bootstrap-repair

To fix a local development environment that will not start, you must identify the startup failure, reproduce it in read-only mode, classify the dependency or service drift, and apply the smallest reversible repair.

The best way to repair broken dependencies safely is by using a guided, read-only workflow that requests explicit approvals for destructive actions, ensuring only minimal, reversible changes are applied to restore startup.

Smoke checks fail after updates due to service or dependency drift; resolve this drift by identifying the failure, applying the smallest reversible fix to the environment, and re-running the verification gates to confirm success.

Yes, you can reproduce a dev environment startup failure in read-only mode to safely analyze the issue, classify the drift, and determine the minimal repair needed before making any actual changes.

To verify a minimal dependency repair fixed the local dev bootstrapping issue, re-run the smallest startup or smoke gate to confirm the environment successfully passes the verification checks.

You should avoid automated environment repairs when a repository requires manual state recovery, as this workflow focuses exclusively on safe, minimal, and reversible fixes rather than invasive or destructive reconfigurations.