migrate-repo

name	migrate-repo
description	Migrate a repo from docs/history.md + docs/todo.md to GitHub Issues with canary gates.
user-invocable	true

Always run --dry-run first.

Irreversibility hard rule

• gh issue create consumes monotonically increasing global issue numbers; they can never be reused, freed, or reassigned. Every canary stage is irreversible.
• Each stage MUST run as its own process: never chain stages, never pipe yes into the orchestrator, never run two stages in one command.
• AskUserQuestion is the only gate between stages — never invoke orchestrate.sh inside a pipeline that supplies stdin.

Pre-flight

• gh auth status — confirm project scope is active.
• AGENTS_CONFIG_DIR must be set.
• Step 1 label setup is delegated to bin/github-issues/bootstrap-labels.sh.

Procedure

MR-1. Get the migration target path from the user.

• Never infer REPO_PATH from a path mentioned only as documentation / reference / context — accept only the path the user explicitly designates as the target.
• Resolve REPO_PATH to an absolute path, then AskUserQuestion: "Migration target = <abs path> — correct? (confirm this is NOT the agents repo itself)"
  • "Yes, proceed with this path" → MR-2
  • "No, re-enter the correct path" → re-collect , repeat MR-1