git:20260928.7b48077 to git:20261001.52de599

1 added, 1 removed. Audit A to A.

---

name: track-land

description: Integrate an authorized, verified and independently reviewed TODO Flow candidate using the runtime landing boundary.

---

# 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.

- Consume the existing exact-head verification and independent review. Do not add blanket preflight or post-landing test runs, duplicate reviews, or exploratory resource audits. The configured combined-tree verification remains required; distinguish it from optional checks instead of bypassing its evidence boundary. After confirmed landing and required triage, report delivery and any already-known deferred resources, then stop within the user's scope.

+ Consume the existing exact-head verification and independent review. Do not add blanket preflight or post-landing test runs, duplicate reviews, or exploratory resource audits. The configured combined-tree verification remains required; distinguish it from optional checks instead of bypassing its evidence boundary. After confirmed landing and required triage, finish cleanup of this run before reporting run completion. Recoverable cleanup deferrals remain part of the authorized work; resolve them and retry. If user changes or reused sessions genuinely block safe removal, report code delivery separately and the run as incomplete.

Keep automatic cleanup enabled through the landing boundary, including temporary approval drivers and recovery scripts. Disable it only when the user explicitly requests retaining the resources, and report that scoped exception. Do not substitute a promise to clean later for cleanup. Code landing does not establish resource removal: use cleanup receipts and the relevant Git/Orca inventory to report removed resources or concrete deferrals, without weakening ownership or user-data protections.

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.