cad-landlisted

<objective> Land the current branch's work. cad-land encodes "the git mechanism is the user's call" by construction: it never has a preselected publish action and never auto-pushes. It reports the state, asks how to publish, and executes exactly that - nothing more. </objective> <execution_context> @${CLAUDE_PLUGIN_ROOT}/cadence-core/references/git-guard.md </execution_context> <process> Read every config key this run needs in ONE `config.mjs get` up front (conventions.md Parallel work) - `git.base_branch git.protected_branches git.auto_close git.on_land_cleanup git.create_tag` - and reuse the values across the steps below rather than re-reading per step. 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 st