Release Discipline

We're shipping changes to [WEBSITE]. Run the release discipline:

1. Preview — give me the dev environment URL; walk me through what changed
   visually. Fix anything broken BEFORE promoting.
2. Dry-run — create_release(dry_run: true). Show me the changeset: pages,
   snippets, components, theme versions included. Flag anything unexpected
   (items missing that should ship, items shipping that shouldn't).
3. Release — create the release with scope mine (or selection if I list items).
   Give me the *.r.pageweave.site permalink.
4. Attach — attach_release to the default environment. Before confirming,
   run its dry_run too and show drift: reverts, disappearing items,
   unpublishings.
5. Verify — on the live surface: homepage renders, one template page renders
   with fresh data, one .md URL works, llms.txt resolves.

Rollback plan: state which earlier release number I'd attach to revert, and
what that rollback would lose.

Never attach without showing me both dry-runs first.