git-workflow — branch-per-change, R10-gated auto-landing

Every change to an charly-project repo follows ONE landing discipline. The R10 pass is the sole gate: nothing is committed, pushed, merged, or tagged on unverified state, and once R10 passes the landing is automatic — no per-change manual "push" step. This skill is the mechanics; CLAUDE.md "Post-Execution Policies" carries the mandate, /charly-internals:cutover-policy the one-phase rule, /charly-build:migrate the schema-version/tag coupling.

Non-negotiable invariants