fix(org-migration): fail on a bad baseline path, and route the runbook to the transfer steps

[twistedmelonman]

What happened

Following docs/runbooks/org-migration-rename.md straight through — D → E → F,
no steps skipped — produces 31 lines of missing snapshot at Part F. Nothing is
actually wrong: the repos have not been transferred yet, and the baseline path in
the runbook does not exist. Neither condition announced itself.

Three fixes

verify.sh never validated the baseline dir. It guards the after-dir
carefully, but a wrong baseline path was not an error — every repo just missed
its baseline file, and the comparison loop reported missing snapshot for the
entire move list. That reads as catastrophic drift rather than as one typo. It
now fails on the path and names it, and treats an existing-but-empty baseline dir
as the same class of mistake.

Part F cited the wrong path — docs/data/org-migration/baseline vs. the
actual dated docs/data/org-migration/2026-09-04-baseline.

The runbook never mentions the transfer. Parts A–E cover design Step 2 only,
but Part F verifies a transfer that no part of the document performs — Steps 3
and 4 live in docs/superpowers/specs/2026-09-03-org-migration-design.md and
were never linked. A stop block before Part F now carries the transfer commands
and the pointer, so the runbook stops reading as a complete start-to-finish
procedure.

Part G also gains a note that a shell opened before the rename holds a stale
sourced gh wrapper, which fails closed trying to switch to smartwatermelon;
exec bash -l clears it. which gh / hash -t gh reveal it, command -v does
not. This bit on ASIAGO during the live run.

Tests

Two cases in test-verify.sh, both confirmed failing against the unpatched
script before the fix — the failure output reproduces the missing snapshot
noise exactly. Full suite green, shellcheck clean at -S info.

Not a defect

An earlier read of this suggested .github was missing from the baseline (30
files vs. 31 move-list entries). It is not: the snapshot is .github.json, a
dotfile, invisible to a *.json glob. The tooling iterates the move list rather
than globbing, so it was always handled correctly. No change needed.

https://claude.ai/code/session_01P7jGdvXTTzxwxjpf34qUbM

[claude]

Validation improvements for baseline directory handling.

The new baseline checks in verify.sh (lines 37–49) prevent silent failures when the baseline path is wrong or empty. Tests (Cases 10–11) properly verify the new error messages. Documentation updates clarify the dated baseline convention and execution order. No regressions introduced.

VERDICT: PASS