Commits on May 2, 2026 v0.42.2: pin morph init --git-init to main A fresh GitHub-Actions runner that hasn't opted in to git 2.28+'s default-branch rename creates the repo on `master`, but morph's ref-mode contract treats `main` as canonical (it's what `morph checkout`, `morph branch`, `morph push`, and the merge breadcrumbs all assume). The mismatch surfaced as 20 spec failures (spec_checkout_branch, spec_clone_with_explicit_branch_*, the entire merge_* family) all reporting `pathspec 'main' did not match any file(s) known to git` because the very first commit landed on `master`. Pass `-b main` (anchored to morph_core::DEFAULT_BRANCH, now exported from the morph-core crate) so the initial branch matches morph's contract regardless of host config. The error message on failure also names the explicit invocation (`git init -b main <path>`) so a reader of the failure output can reproduce it without guessing.…