cw-land

Verified work still has to land without stepping on other writers, losing contributor credit, or merging past a gate that has not actually passed. This stage is about the boundary between "it works" and "it is in main", and about which of those steps you are allowed to take.

Stage 5 of the loop: cw-orient → cw-slice → cw-gates → cw-dogfood → land → cw-handoff.

When to use

• The change is verified and needs to become a commit on main.
• You are landing someone else's PR, harvesting a contributor's work, or resolving a conflict caused by main moving.
• You are about to merge something behind a required gate.

Workflow

1. Land on the canonical checkout's main. AGENTS.md owns this: no maintainer PR branches, worktrees, nested clones or integration lanes. Several agents share the checkout, so partition by file, check git status before staging, stage only your paths (never git add -A), and retry a commit that fails on index.lock. Push verified main directly. A push is not a CI request: hosted CI runs once, at the final release step (docs/RELEASE_CHECKLIST.md), and routine slice commits carry [skip ci]. PRs are for contributors.

2. Commit narrow and build-green. One coherent change per commit; the tree builds at every commit. Put the real verification in the message, actual pass/fail counts, not "tests pass".