cad-land

<execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/references/git-guard.md </execution_context>

1. Report git state. Current branch; the base = $ARGUMENTS, else git.base_branch, else the first git.protected_branches entry that exists here (references/git-guard.md's fallback); commits ahead of base; unpushed commits; uncommitted/untracked changes; and the remote host detected from the origin URL (gitlab -> MR, github -> PR, any other host where tea holds a login -> Forgejo/Gitea PR via tea, else local only). Show this plainly before doing anything.

   Then the tracker, in the same report. Run it here, before any publish ask, on both step-3 arms:

node "${CLAUDE_PLUGIN_ROOT}/cadence-core/bin/issue-check.mjs" check --dir <root> --base <base>

Branch on action alone. On report: say in ONE sentence which issues this branch's commits reference and which of them are still open ("your branch references #42 and #47; #42 is still open"), naming a not-found number as not found and an unresolved one unresolved, never closed or not found. Print the open list ONLY when referenced is empty - it is the fallback, never the headline, because a bare list is what a reader skims past. On skip: print reason verbatim as ONE line and carry on - never block, never retry, never ask, and never list an issue the seam did not read. On off - git.issue_check: false, decided before any forge CLI runs - say NOTHING about the tracker: not the reason, not that it was skipped. The off switch is off, so this paragraph produces no output at all.

This report never writes: landing closes no issue, and closing one stays an explicit ask you make at publish time.

1. Uncommitted changes. If the tree is dirty, do NOT auto-commit. Ask (ask-user seam): commit them first (then continue), leave them out of this land, or stop. If HEAD is a protected branch, the protected-branch guard (references/git-guard.md) applies to any commit here.

2. Publish - branch on git.auto_close.

   First the deferred queue, on BOTH arms and ahead of the branch below. A gate resolved deferred ran its reviewer and let the run continue, so the finding stops the LAND. Ask what is still queued:

node "${CLAUDE_PLUGIN_ROOT}/cadence-core/bin/planning.mjs" deferred list

On ANY entry in members, STOP the land here: no publish ask, no seam call, no merge, no tag, neither arm. Print each member's trigger, discriminator and finding count with the path its bodies are in, then point the reader at ${CLAUDE_PLUGIN_ROOT}/cadence-core/references/triage-gate.md, whose deferred arm says how to clear one - triage the member's findings and record the rulings with planning.mjs adjudication for the same trigger, discriminator and round, which supersedes it. A non-empty unreadable arrives as ok:false and refuses exactly as a member does: the queue could not be PROVEN empty, and this gate never reports "nothing deferred" about input it could not read, the disposition land-cleanup.mjs gate already takes for a findings payload it could not parse.

It is NOT land-cleanup.mjs gate and must not be folded into it: that gate halts only when git.auto_close is true and reads only risk_surface survivors, so a default-configured project would publish straight over a deferred plan, diff or phase_diff finding.