repo-bootstraplisted

# Repo Bootstrap Take a repository from a URL to a verified working local install. The value here is not running `pip install` - the user could do that. The value is reading what the project actually says it needs, comparing that honestly against what is already on the machine, and closing the gap without leaving a trail of half-installed tooling behind. ## Phase 0: Pick a mode Before touching anything, establish how much autonomy you have. Ask once, up front: - **Auto** - install missing prerequisites and the project without stopping, report at the end. Good for well-known repos and low-stakes tooling. - **Guided** - investigate everything, present a plan with exactly what will be installed and what it will change, then wait for approval before executing. Default to **Guided** if the user does not say. Always use Guided regardless of preference when any of these are true, and say why: - The install requires admin/elevated rights or modifies system PATH beyond a package manager's normal behavior - The repo wants a global runtime version change (a different Python or Node as system default) - Setup touches credentials, cloud accounts, or anything requiring an API key - The repo has fewer than ~50 stars, no releases, or looks unmaintained - unfamiliar code deserves a human read of the plan - The repo is itself an installer, bootstrapper, or agent-configuration tool (see Phase 3), since installing it means running its installer too ## Phase 1: Read the repo before decidin