track-land

Read installed project.json for STATE and primary language, then STATE's config/1.json. Use the project language for user-facing reports and new documents unless explicitly overridden; default to English. Preserve protocol keys, identifiers, commands and source quotations.

Request kind land through the durable agenda; do not manually push the target branch from a model session. The runtime checks the candidate and goal revision, creates an isolated integration checkout, verifies the combined tree, and publishes that exact merge with a compare-and-swap on the old base. Both base and candidate must be ancestors of the merged commit; rewriting history is forbidden.

If a response is lost, inspect remote ancestry and effect receipts before retrying. Integration conflicts return scoped work. Confirmed landing automatically schedules track-triage. Completion follows a current cleared triage receipt; starting the landing worker is not landing evidence. GitHub issue closure occurs only after triage, so PR descriptions use a related-issue reference rather than automatic closing keywords.