landlisted

# Land Merged is not shipped. Landing is everything between the merge commit and "verified in production": pipelines, migrations, deploys in the right order, and proof that the thing actually works where users are. This skill executes that sequence the way a careful release engineer would — from a written runbook, step by step, verifying each step before the next, and stopping loudly the moment reality disagrees. Two kinds of steps, always explicit: - **`[agent]`** — you execute and verify it directly (watch a pipeline, call a health endpoint, run a migration command you have access to). - **`[human]`** — production access the user holds and you don't (a psql session into a locked VPC, a cloud console action). You hand over the **exact** command or click-path, then wait for their confirmation. A human step is never assumed done, inferred done, or skipped. ## The runbook — `docs/landing.md` The landing sequence is project knowledge, not skill knowledge, so it lives in the repo where the team can review and version it. The skill reads `docs/landing.md`, which defines: ```markdown # Landing runbook ## Deploy order 1. {repo/service} — {how it deploys: CI on main / command} 2. … ## Migrations - How they're applied: {auto on deploy | command `…` | [human] manual psql against prod} - Where they live: {path} ## Health checks <!-- [agent] --> - {GET https://…/health → expect 200} - {command → expected output} ## Smoke checks <!-- the 2–3 flows tha