A live URL is not the handoff.

GoLive is an early-alpha agent skill and command-line tool for deploying an app through the user's own provider accounts. Its current README lists tested routes for hosting, databases, custom-domain DNS, transactional email, test-mode payments, Supabase authentication, and teardown. The project also labels unbuilt and untested routes instead of hiding them behind a broad launch claim.

The useful idea is not one command that owns the whole release. GoLive divides the job into detection, a plan, explicit confirmation, application, verification, drift checks, handoff, and teardown. The plan carries an identity. A changed release, configuration schema, or approved step content invalidates that identity before a write.

The control is still local to the tool. The trust document says an agent can pass the approval flags. It does not record a human signature or second factor. Existing provider logins can also write outside GoLive. A plan gate is useful, but it is not an account-wide policy.

GoLive's recovery guide separates a production re-point from teardown. A re-point works only for an earlier deployment that the tool recorded. The current guide says Netlify supports that path. Vercel does not expose the needed production read and re-point through this implementation, so the dashboard remains the correction route.

Other changes have different inverses. The tool can re-apply declared DNS records. It cannot restore old database data because it keeps no backup. Teardown removes only resources it can prove it created. Supabase and Neon projects, a Resend sending domain, adopted resources, and unreadable provider state can remain as manual handoffs.

This is why a single ROLLBACK=YES field is weak. Recovery must be recorded per resource. The handoff should say what the tool can reverse, what it can remove, what it can only inspect, and what the next owner must do by hand.