verify-and-land
Verify, then land
The gap this closes: a fix is committed, the user opens "the app", the fix is not
there — so they conclude it did not work. Usually it did. They were looking at a
different build: the copy in /Applications that Spotlight, the Dock and
Launchpad all open, or a DerivedData product from another branch. Nothing rebuilds
when the branch changes, because nothing ever does. Measured on one real project: the
installed copy was a month older than the branch build, and four other stale build
products were registered besides.
So this skill never asks the user to open the app. It builds the branch they are standing on, launches that exact bundle, proves on screen which one is running, and only then asks whether the fix is there. A yes leads into landing; a no keeps the branch open and says what to look at next.
Invoke with: /superpowers-gstack:verify-and-land