traceable-git-submitlisted

# Traceable Git Submit Keep checkpoints reviewable and Git submission phases explicit. ## Intent Gate Identify one active phase before Git inspection. Route selection never grants action authority. Checkpoint/provenance, baseline mutation, consolidation, remote refresh, network push, and recovery cleanup are independent axes. A combined commit, tag, and push of an already-prepared plugin release selects the hardened phase; this never authorizes the commit, tag, or push. Ordinary named-remote non-force staging, commits, and pushes without a tag or another listed phase stay host-native; submit, publish, or push alone is insufficient. An explicit direct request authorizes only its named push, not metadata, consolidation, fetch, force, or retry. Resolve predictable push conflicts before commit. Ask once only when active checkpoint history obscures the outcome; never reconfirm an unchanged envelope. ## Load Only The Active Phase - Explicit baseline metadata or workflow audit: read `references/safe-git-values-and-metadata.md` and `references/baseline-and-preflight.md`. - Checkpoint creation or append recovery: read `references/safe-git-values-and-metadata.md`, `references/baseline-and-preflight.md`, `references/checkpoint-provenance.md`, and `references/checkpoint-execution.md`. - Explicit simple named-remote, one-branch, non-force direct submission, or a specialized stale-tracking request that states the verified live remote tip is an ancestor of the final co