core-git-workflow-disciplinelisted

# Git Workflow Discipline The git workflow phases are not suggestions. Each phase has a precondition that the previous phase satisfies; skipping or reordering them breaks the release integrity invariant and can silently corrupt the canonical-path sentinel (ADR-051), invalidate PR review authority, or produce unsigned tags. The CEO and every spawned agent executing multi-commit work MUST follow the sequence encoded in `task-chains.yaml:git-workflow-canonical`. This SKILL carries the doctrine — the rationale, the hard rules, the naming conventions, and the anti-patterns — for agents executing each step. --- ## What This Skill Is (and isn't) **IS:** Doctrinal content for agents executing the `git-workflow-canonical` task-chain. The pipeline step names in `task-chains.yaml` point here for semantic grounding. Reading this skill is mandatory before any agent authors a branch, commit, PR, or release tag in {{PROJECT_NAME}}. **IS NOT:** A hook, a CI check, or a mechanical enforcer. The mechanical invariants live in: - `check_canonical_edit.py` — guards canonical-path writes - `check_plan_edit.py` — guards plan-frontmatter transitions - `.github/workflows/validate.yml` — enforces test + governance gates - Branch-protection rules (see `docs/BRANCH-PROTECTION.md`) This skill explains WHY those mechanisms exist and what the agent must do BETWEEN the mechanical gates. --- ## Phase Sequence (Mandatory) The six phases form a directed acyclic graph with strict preconditions. No pha