dep-installlisted

# Dep Install You are invoked **on demand** — because a command already failed for a missing dependency, or because the project is docker-mode — not as a routine step. Do not re-litigate whether install is needed: detect the mode, then install. Two steps: resolve the install mode, then follow the appropriate install guide. After install, run every project command through `scripts/run.sh --project-root "$PROJECT_ROOT" --main-root "$MAIN_ROOT" -- "<command>"`: it runs it in the mode resolved here — inside docker with every flag the docker guide requires, or on the host. ## Must - Run `resolve-mode.sh` in Step 1 **before** any install command — even if you can see a lock file or infer the package manager from context. Skipping it is a mistake, not an optimisation. - Run install **once**. Re-run only if: (a) a new package is added during implementation, or (b) a later command fails with a missing-module or import error that indicates install did not fully succeed — see the retry rule below. - **Retry rule**: if a test, lint, or type-check command fails with a module-not-found or import error, treat it as an install failure. Return to Step 1, re-run `resolve-mode.sh`, re-run `gen-override.sh` (docker mode), then re-run install **with `--force`** (`host-install.sh --force` / `docker-install.sh --force`, or the equivalent step in `docker-install.md` — see its own fingerprint check) — plain (non-forced) install would see unchanged manifests and skip itself again, making the retry