FIRST GATE: bash scripts/first-gate-run.sh git merge-base --is-ancestor @@TIP@@ origin/main

THE FIRST MILE COMES FIRST: run the FIRST GATE on the untouched base (it is RED: the green work is not on main yet), write and push the proof file alone as your first commit, then start the work below.

WHY THIS LANE EXISTS. Rendered by the reconciler's green-unlanded leg (ops/fleet-watchdog/reconcile.sh, check_green_unlanded) on @@DATE@@: lane @@ORIG_TASK@@ (run @@RUN_ID@@) exited with its LANE-RESULT saying its work is green and its landing NOT LANDED, its landing died on ONE named gate leg, and its branch @@BRANCH@@ on origin is still at the tip its LANE-RESULT names. A green exit never waits for a hand to read it (docs/derived-rules.md, "Running a gate or a wait"; docs/postmortems/2026-10-14-a-landing-leg-read-a-built-binary-as-the-merge-state-and-an-unlanded-green-exit-had-no-payer.md). Queued through scripts/debt-queue.sh --charter-file as row @@TASK_ROW@@; it runs on @@NODE@@, the lane's own landing node.

THE EXIT, read at render time:
- task: @@ORIG_TASK@@
- branch: @@BRANCH@@ at tip @@TIP@@
- red leg: @@LEG@@
- its log line: @@LEG_LINE@@
- LANE-RESULT: @@LANE_RESULT@@
- report: @@REPORT@@

WHAT SHIPS. The work is already green; this lane LANDS it and changes nothing else:
1. Fetch @@BRANCH@@ and confirm origin still holds it at @@TIP@@, and that its work is not already on main under another landing (`git cherry origin/main @@TIP@@` prints no `+` line when every commit is already there: then the row is done, say so and stop). If the branch moved, or its work is red when you read it, STOP and say so: red work is the coordinator's resume decision, never a hand-landing.
2. Rebase the branch onto origin/main (in your worktree, with your own lane branch reset to @@TIP@@ first), resolving only mechanical conflicts; a conflict in the work's own logic is a STOP.
3. Re-run the one red leg (@@LEG@@) on the rebased tree under a slot and name why it is green now, or why it is still red (a leg red for the node's environment, not the work, is a finding to name, never a leg to skip).
4. Run the gate round under a slot and land with scripts/land.sh: one LAND: line, verified with git ls-remote.

DoD:
1. `git merge-base --is-ancestor @@TIP@@ origin/main` passes or the rebased equivalent of every commit of @@BRANCH@@ is on main, the LAND: line pasted.
2. The red leg's re-run output pasted verbatim, with the cause named.
3. `bash scripts/lane-finish.sh` green; land with scripts/land.sh; the turn ends at the LAND line.

Will NOT do: change the work's code beyond the rebase, land red work, or skip a red leg.

BUDGET: 240 min (the landing through scripts/land.sh included; the turn ends at the LAND line, not at the push). No sudo. Report incrementally, LANE-RESULT last.
