repo-init-scanlisted

# Repo Init Scan Use this thin orchestrator when the repository needs full init or scaffold repair. ## Entry Contract - Default path: invoke `repo-init-gate` first, then load this skill only when the gate reports `needs_init`, `version_mismatch`, or `invalid_sentinel`. - If this skill is called directly without gate context, it may do one shallow read of the target root `best-copilot.md` and return early when the sentinel already matches. - Explicit reinitialize/repair requests may bypass the gate. - Stage order: `repo-init-official` first, then `repo-init-manual-fallback`. ## Boundary - This skill is fail-closed. Do not continue to substantive planning or implementation until required scaffolds are verified and `best-copilot.md` has been rewritten for version `0.5.1`. - Loading this skill is not execution. In Claude Code, `Skill(best-copilot:repo-init-scan) Successfully loaded` is only a preload trace. A valid `INIT_SCAN` requires running the stages below, creating or repairing target-local files when needed, checking them on disk, and returning the init summary. - Do not dispatch specialist agents, run broad code search, or produce architecture/implementation plans while `required_artifacts_verified` is not `yes`. ## Stage Split - `repo-init-official` owns `/init` or `copilot init`, plus normalization of official output into `.github/instructions/project.instructions.md`. - `repo-init-manual-fallback` owns bounded manual scanning, scaffold bootstrap, artifact verific