A relaunched merge-gate run has land_work but no message to turn on: the raising run's poll consumes the approval DECISION. The host writes the instance's landHolders entries into session.json as landing, and the runner takes one fixed-template turn per entry before its receive loop. Row 149's chief-of-staff message stays as the fallback; a second land gets decision-consumed. Co-Authored-By: Claude Opus 5.5 <[email protected]>