fix(git): correct three command claims the plugin got wrong, and give rebase an owner

Three statements were false against the git in use (2.39.5), each verified by
running it.

`git rebase --autosquash HEAD~N` without `-i` is a silent no-op: git prints
"Successfully rebased", the `fixup!` commit survives with the same SHA, and
rewrite-history.md presented that as the preferred flow with `-i` as an optional
review step. The agent reports the squash as done and the `fixup!` subject then
trips this repo's own commit-msg gate. `-i` is now the command, not the alternative.

"Fetch never modifies a local branch, so it is always safe to run" — new text on
this branch — is false: `git fetch origin main:probe` fast-forwarded the local
branch, and a `+` prefix force-updates it, losing commits. The claim is scoped to
the no-refspec form.

`git worktree add --orphan` does not exist before Git 2.42; on 2.39.5 it is
`error: unknown option 'orphan'`, exit 129. The same file gives a version floor for
`--recurse-submodules` three sections earlier. Floor added, with a fallback that
was tested before being documented.

git-workflow claimed "every request resolves to exactly one of these six" while
rebase, reset and stash were owned by no skill — `git reset` appeared nowhere in
the plugin, old tree or new — so "undo my last commit" routed nowhere. The claim is
gone, the router gains rows for all three, and the procedures now exist: plain
rebase with `--onto` and conflict handling, a reset mode table gated on `--hard`,
and stash save/pop/list/drop. `--hard` gets an always-loaded Gotcha, matching the
register the force-push refusal already sets.

Cherry-pick had three claimants pointing at git-history while git-commits owned the
flow, and the two copies were not equivalent — git-history's lacked the destination
check, the rtk prefix and `--abort`. Resolved to git-commits per #112; the weaker
duplicate is replaced by a hand-off.

git-commits' metadata.version was deleted rather than bumped in 14af50b, leaving two
house-contract documents citing a worked v0.1.2 to v0.1.3 transition against a file
declaring no version. Restored to 0.1.3.

Also: the divergent-pull explanation stated a `--ff-only` default that does not
exist (it is a hard error); `--remote` "requires" a configured branch where it uses
one; `git push origin --delete` moved to git-remotes, which owns the remote-side
gates; seven retired `git:<name>` source slugs; git-orchestrate quoted a
git-workflow sentence that no longer exists; git-submodules regains the indirect
trigger that made "add a dependency repo" routable; and commit atomicity is a common
gate rather than reachable only from the create flow.

Refs: #112, #113

plugins/git/skills/git-branches/README.md

@@ -20,7 +20,7 @@ Describe your branch task: create a feature/hotfix/release branch, switch, delet
 |------|---------|
 | `SKILL.md` | Skill instructions for agents |
 | `references/branch-patterns.md` | Loaded when a branch's base, name prefix, or merge rule depends on GitHub Flow vs. Gitflow |
-| `references/branch-operations.md` | Loaded when running a create/switch/delete/rename/track/list action, or resolving `get-intent` |
+| `references/branch-operations.md` | Loaded when running a create/switch/delete/rename/track/list/stash action, or resolving `get-intent` |
 | `references/merging.md` | Loaded when merging one branch into another or resolving merge conflicts |
 | `references/comparing-branches.md` | Loaded when comparing two branches or finding where they diverged |
 | `references/orchestrator-contract.md` | Loaded when `git-orchestrate` or another calling agent supplies a structured request rather than prose |
@@ -29,5 +29,6 @@ Describe your branch task: create a feature/hotfix/release branch, switch, delet
 ## Composition
 
 `git-orchestrate` calls this skill for the branch step of a multi-step workflow and parses its
-structured result. Cherry-pick and revert are `git-history`'s; commit authoring and rebase are
-`git-commits`'; branch operations against a Gitea-hosted remote are `gitea-branches`'.
+structured result. Revert is `git-history`'s; commit authoring, rebase, reset and cherry-pick are
+`git-commits`'; deleting a remote branch is `git-remotes`'; branch operations against a
+Gitea-hosted remote are `gitea-branches`'.

plugins/git/skills/git-branches/SKILL.md

@@ -33,7 +33,7 @@ The two patterns are not mixable, and the wrong merge rule silently damages hist
 
 | Action | Reference |
 |---|---|
-| create, switch, delete, rename, track, list, get-intent | `references/branch-operations.md` |
+| create, switch, delete, rename, track, list, get-intent, stash | `references/branch-operations.md` |
 | merge a branch, resolve merge conflicts | `references/merging.md` |
 | compare two branches, find their divergence | `references/comparing-branches.md` |
 
@@ -51,7 +51,7 @@ These gates are passable. The `main`/`master` refusal in Gotchas is not.
 
 ## Step 4 — Set tracking
 
-When pushing a branch for the first time, always `git push -u origin <branch>`. Without an upstream, later pushes and pulls either fail or silently target the wrong remote branch, and the caller has no way to tell which happened.
+A new branch's first push must be `git push -u origin <branch>`. The push itself is `git-remotes`' — every remote-side gate lives there, which is why Step 2's remote-delete row hands off the same way — but the upstream requirement originates here, so carry it in the handoff. Without an upstream, later pushes and pulls either fail or silently target the wrong remote branch, and the caller has no way to tell which happened.
 
 ## Step 5 — Return a structured result
 

plugins/git/skills/git-branches/references/branch-operations.md

@@ -15,7 +15,9 @@ hatch.
 - **delete (local)** — `git branch -d <branch>` refuses when the branch holds unmerged commits,
   which is why it is the default. `git branch -D <branch>` forces the deletion and discards that
   work — only after the destructive-operation gates pass and `confirm: true` is set.
-- **delete (remote)** — `git push origin --delete <branch>`.
+- **delete (remote)** — not this skill's. Deleting a remote branch is a push, and every remote-side
+  gate lives in `git-remotes`; hand it there rather than running the push from here. Its
+  `references/push.md` carries the command and the refspec form.
 - **rename** — `git branch -m <old> <new>`.
 - **list** — `git branch` (local), `-a` (local plus remote-tracking), `-r` (remote-tracking only),
   `--merged` / `--no-merged` (filter by merge status into the current branch).
@@ -32,3 +34,23 @@ On `get-intent`, either parse the intent back out of the branch-name convention
 (`feature/<intent-slug>`) or return `{ "intent": null }` when the caller never persisted the
 create-time value. Never fabricate an intent: a downstream commit message built on a guessed
 intent is worse than one built on none.
+
+## Stashing work in progress
+
+A switch aborts rather than clobbering conflicting local changes (see Gotchas). Stash is the way
+past it: it shelves the working tree and index so the branch pointer can move.
+
+- **save** — `git stash push -m "<message>"`. Add `-u` to include untracked files; verified on Git
+  2.39.5, a plain `push` leaves them in place, and a plain `push` with *only* untracked changes
+  reports `No local changes to save` and stashes nothing. Bare `git stash` is `push` with no message.
+- **restore** — `git stash pop` applies the newest entry and deletes it. `git stash apply stash@{n}`
+  applies without deleting, for replaying one shelf onto more than one branch.
+- **list** — `git stash list`; `git stash show -p stash@{n}` prints that entry's diff.
+- **drop** — `git stash drop stash@{n}` deletes one entry. `git stash clear` deletes all of them
+  and nothing recovers them — confirm before running it.
+- **branch from a stash** — `git stash branch <branch> stash@{n}` creates a branch at the commit the
+  stash was taken from and pops it there. Use it when the stash no longer applies to the current tip.
+
+**A conflicting `pop` keeps the entry.** Verified on 2.39.5: it exits 1, writes conflict markers,
+prints "The stash entry is kept in case you need it again", and `git stash list` still shows it.
+Resolve, `git add`, then `git stash drop` the entry by hand — otherwise it silently accumulates.

plugins/git/skills/git-branches/references/merging.md

@@ -6,8 +6,8 @@ source_keys:
 
 # Merging one branch into another
 
-Scope is fast-forward and merge-commit mechanics plus conflict resolution. Rebase belongs to
-`git-commits`; cherry-pick and revert to `git-history`.
+Scope is fast-forward and merge-commit mechanics plus conflict resolution. Rebase and cherry-pick
+belong to `git-commits`; revert to `git-history`.
 
 - **Fast-forward** — `git merge <branch>` advances the pointer with no merge commit when the
   target has not diverged.