push-branchlisted

## Quick Reference Rules: `GIT-01` (no trunk commits/push) Before: - [ ] Current branch matches `head` and is not `base` - [ ] Git state not unsafe per `${CLAUDE_PLUGIN_ROOT}/governance/definitions.md` (Unsafe Git State) After: - [ ] Working branch is on its remote — push SUCCEEDED, or the skill returned `blocked` (exit 1) - [ ] Final action is a Bash tool call (exit 0 = pushed/routing emitted, exit 1 = blocked) Push the current working branch to its remote. This skill does NOT create a pull request — its sole job is to place remediation commits on the remote so an in-flight review loop can resume against the updated branch. Contract: **the push succeeds or the skill returns `blocked`.** There is no warn-and-continue path. In the post-PR `push_remediation` flow a failed push means the review loop would resume against the UNCHANGED remote and could repeat the same finding forever (no `gh pr create` fallback exists here, unlike `hivemind:open-plan-pr`). Any push failure — auth, read-only, protected branch, hook policy, `[remote rejected]`, or a non-fast-forward that force-with-lease cannot resolve — is therefore a terminal `blocked` (exit 1), never a warning. Follow `${CLAUDE_PLUGIN_ROOT}/governance/workflow.md`. ## Required Inputs The orchestrator resolves and passes these. The skill does not resolve them on its own. - `base`: resolved trunk branch — used only as a guard (current branch must not equal it). - `head`: working branch (current branch). - `push_remote`: op