repo-init-manual-fallbacklisted

# Repo Init Manual Fallback Use this stage inside `repo-init-scan` whenever scaffold verification, bounded repair, or `best-copilot.md` rewrite is still needed. After official init succeeds, this stage still owns the final scaffold verification barrier and sentinel rewrite. ## Boundary - This stage is fail-closed. Do not continue to requirements analysis, planning, dependency/framework changes, security rewrites, or implementation until the required files have been created or a `BLOCKED` result has been returned. - Reading package/build files is allowed only as bounded evidence for creating `.github/instructions/project.instructions.md`. - Write persistent state into the target repository, never into the plugin installation/cache directory. - Loading this skill or the bootstrap skills is not enough. Success requires actual create/repair operations in the target repository followed by path and content checks on disk. - If `target-instructions-bootstrap`, `target-memory-bootstrap`, or `target-spec-bootstrap` cannot be invoked mechanically, read their `SKILL.md` templates and perform the documented create-only repair inline. Do not skip a missing scaffold because skill invocation was unavailable. ## Required First-Use Artifacts Before `next_task_ready: yes`, verify these paths in the target repository: - `.github/instructions/project.instructions.md` - `.github/instructions/must.instructions.md` - `.github/instructions/skills-index.instructions.md` - `CLAUDE.md` when the a