Two ordering conflicts introduced by earlier fixes in this PR.
- Restoring the work branch before construction left gh stack add unable
to run, since it must run from the parent. The managed arm now plans
from the restored work branch and checks the parent out again to attach
- A fork parent materialized from refs/pull/<n>/head has no
remote-tracking branch, so construction's fetch-and-verify step could
not be satisfied. It now accepts Topology's verified local branch
Declined a third finding: the standalone arm was reported as having no
branch-only path and as having dropped the refs/pull fetch. The
branch-only clause is present, and the fetch is in gh-stack-cli.md,
which Topology points at by design of the earlier consolidation.
Trevin Chow
d254fa6846