## After landing — offer to update the preview review link

Skip this section entirely unless BOTH hold: (1) the changes were landed on
a branch other than the default (option (a), or (b) on a non-default
branch), and (2) the project has a review link configured (the project's
`primary_origin` is set — visible via `get_project`).

The review proxy has a preview variant —
`review.pinappai.com/p/<slug>~preview/` — that serves the project's
`preview_origin` so reviewers can see the changes you just applied BEFORE
they ship to production. Pins and decisions made there still record
against the canonical site, so nothing forks.

1. **Find the preview deploy URL for the branch you just landed on:**
   - If your run (or the user) deployed the branch and the deploy output
     printed a URL (e.g. `wrangler deploy` → `*.workers.dev`, Pages/
     Netlify/Vercel CLI output), use that.
   - If the host generates predictable branch URLs (e.g. Cloudflare Pages
     `https://<branch>.<project>.pages.dev`), derive it and SAY you
     derived it.
   - Otherwise ask: "Is there a preview deploy of this branch? Paste its
     URL and I'll wire it to the preview review link."
2. **Confirm before writing** — one line: "Set the preview review link to
   <url>? Reviewers will then see this round at
   review.pinappai.com/p/<slug>~preview/ (y/N)". A wrong origin sends
   reviewers to the wrong content, so never set it silently.
3. On yes: `update_project({project: "<slug>", preview_origin: "<url>"})`
   and report the preview review link back. On no / no deploy: skip —
   this is an optional convenience, not a required step.