Checkouts whose origin was renamed are rejected as a different repository #116

Status: Reported by agent sessions during the rollout. The mechanism was checked by reading the code; the failure was not re-run on current main.

Part of epic: Epic: Onboarding other organizations and registry-free operation.

Summary

One rollout checkout still had the old repository name as origin; the skill refused it ("different repository") and the operator used a fresh clone.

Evidence

• Reported by one agent session (the website repository). Not reproduced; the resolver only follows renames recorded in the estate data.

Impact

Any post-rename checkout fails until the remote is edited.

Proposed fix

Reproduce first. If confirmed, follow GitHub's rename redirect with a read-only API call (logged) or accept --assume-repo OWNER/REPO.

Acceptance criteria

• A renamed-origin fixture is accepted with a log, or rejected with a message that names the fix.

Tasks

Each task below is a sub-issue.

Prior work

Prior work: open PR #20 (opt-in --allow-t3 and the Pick Your AI family), open #7 and PR #13 (variant J badges), merged PRs #14 to #19 (icon art-direction path, UTF-8 output, registry-free org health and label planning, Windows test portability, footer URL repair) and closed issues #8 to #12. Nothing here duplicates those; where an item is already handled it is linked, not refiled.

Fresh VM verification: not run. Findings were verified on a Windows host; hosted CI is separate evidence.