[starmorph]

The selected repository can have Issues disabled or an inaccessible base branch while setup proceeds through App creation and paid deployment. Both doctor checks previously missed the disabled-Issues case encountered during evaluation. General workspace access and model-key presence also prove less than full runtime capability.

Added npm run setup:preflight and a local-only Node check. Before any environment-group provisioning, setup:render now checks the pinned Node major, required values, selected workspace identity/access, App installation, Issues availability, repository archive status, and every configured base branch. A failure on any target prevents all group writes. Repository checks use scoped read-only installation tokens and validate external metadata with Zod. Doctor repeats Issues and configured-branch checks to catch drift.

The runbook places local checks in Phase 1, calls out Issues in repository selection, and describes the automatic pre-deployment gate. Quickstart and environment-group guidance explain the command and its limits. Preflight changes no repository settings, creates no Sandbox, and makes no model request. It explicitly leaves configured-model/Sandbox execution and provider spend caps unverified; the separately approved smoke test remains required.

This catches basic blockers before paid deployment and provides actionable remediation without silently changing external settings or creating billable probes.

Validation: npm run check passed — 27 files, 203 tests. Added 33 preflight tests plus three doctor regressions covering healthy/slash-branch access, disabled Issues, invalid/missing/inaccessible metadata and branches, rejected workspace access, required values, Node mismatch, blank branches, all-target gating, scoped tokens, no env-group writes after failures, and secret-safe output. The local-only CLI also passed without a .env or network requests. External dependencies are faked in tests.

Fixes #77.