"Land & Deploy report" recap says "Shipped" — terminology is inconsistent and "land" isn't standard

In the chat excerpt below, the "LAND & DEPLOY REPORT" ends with a recap that says "Shipped...":

```
● All 4 jobs succeeded (test, build-and-push, deploy-production, smoke-test). The in-CI
smoke-test already hit https://XXXXXX post-deploy per your project's Deploy
Configuration, so the site is verified healthy.

Skipping the gstack canary — this change is to a local dev-sync script that doesn't
run in production, so hitting the site gives zero signal about the fix. The real
verification is running ./dev.sh --sync on your machine; CI + smoke-test already
covered prod health.

LAND & DEPLOY REPORT
════════════════════
PR: #XXX — fix(scripts): skip self-referential CREATE TABLE LIKE
in loadFromRemoteDb
Branch: fix/load-remote-db-self-like → master
Merged: 2026-04-22 (squash, branch deleted)
Merge SHA: XXXXXXX

CI (pre-merge): ✓ test, ✓ GitGuardian
Deploy workflow: ✓ test, ✓ build-and-push, ✓ deploy-production, ✓ smoke-test
Canary: skipped (dev script, zero prod surface)

Reviews addressed:
Copilot (nit): SOURCE_DB constant extracted (XXXXXXX)
Codex (P1): existence check replaces target==source guard (XXXXX)

VERDICT: DEPLOYED AND VERIFIED (via in-CI smoke-test)

The fix is live. To confirm end-to-end, run ./dev.sh --sync locally — it should
finish cleanly without the MySQL 1066 error.

✻ Worked for 17m 7s

※ recap: Shipped a fix for the `./dev.sh --sync` MySQL 1066 error via PR #XXX, which
is now merged and deployed to prod with CI smoke-test green. Next: run `./dev.sh
--sync` locally to confirm it finishes cleanly. (disable recaps in /config)
```

The skill clearly just ran land-and-deploy. Shipping happened earlier. But the recap says "Shipped." When I come back to this terminal hours later and read "shipped," I think I still need to run land-and-deploy — but I already did.

The inverse happens after `/ship`: the recap says "Next: merge it" when it really means "run `/land-and-deploy`."

Summary:
- Run `/ship` → recap says "next: merge" when it means land-and-deploy
- Run `/land-and-deploy` → recap says "shipped" when it means land-and-deploy

My guess: the model's training has very little concept of "land and deploy," but it knows "ship" and "merge," so it biases toward the familiar terms. Tellingly, the LAND & DEPLOY REPORT itself uses "merge" 4 times and never says "land" or "landed."

This is a signal we probably shouldn't use "land and deploy." ChatGPT calls "land" a niche term — used mainly at Google/Meta to mean merging into main, non-standard elsewhere where people say "merge" or "commit."

**Recommendation:** rename to `/merge-and-deploy`. The "land" term is problematic.