refactor(git): normalize rtk-prefix usage, add metadata.version

Two bundled fixes across the same nine skills, since both touch the
same files.

Issue #113: skill prose used rtk git and bare git inconsistently for
the same operations, with no stated rule for which applied where.
Executable instructed commands (a dispatch-table "Run" cell, a fenced
code-block procedure, an imperative step) now consistently use rtk
git; illustrative or referential mentions -- naming a flag's behavior,
quoting a doc heading, warning against an anti-pattern -- stay bare
git. Documented in the new plugins/git/README.md, scoped to this
plugin only: gitea-* skills talk to the server over MCP tools and
carry no git/rtk mentions at all.

Also the git-plugin slice of #127: metadata.version added to the
eight skills that lacked it. git-commits already had one and is
untouched.

Fixes: #113
Fixes: #127
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EeH8SCbcrCAQrtymkNuhKP

plugins/git/.apm/skills/git-history/references/bisect.md

@@ -12,43 +12,43 @@ or line range to search the log for. Binary search reduces the trials from O(N)
 ## Manual flow
 
 ```bash
-git bisect start
-git bisect bad [HEAD]        # mark current (or specified) as broken
-git bisect good <commit>     # mark known-good baseline
+rtk git bisect start
+rtk git bisect bad [HEAD]        # mark current (or specified) as broken
+rtk git bisect good <commit>     # mark known-good baseline
 # Git checks out the midpoint; test it
-git bisect good              # test passes
-git bisect bad               # test fails
+rtk git bisect good              # test passes
+rtk git bisect bad               # test fails
 # Repeat until git reports "X is the first bad commit"
-git bisect reset             # return to the original HEAD
+rtk git bisect reset             # return to the original HEAD
 ```
 
 ## Automated
 
-With a test command available, use `git bisect run <cmd>`. Git reads the exit code: `0` good,
+With a test command available, use `rtk git bisect run <cmd>`. Git reads the exit code: `0` good,
 `1`–`124` bad, `125` skip (build broken), `126`–`127` POSIX shell errors, treated as bad, and
 `128` or above aborts the session outright rather than marking the commit bad.
 
 ## Untestable commits
 
-`git bisect skip` excludes a commit that cannot be built or tested without deciding good or bad
+`rtk git bisect skip` excludes a commit that cannot be built or tested without deciding good or bad
 for it. When the first bad commit is adjacent to a skipped range, bisect reports that it cannot
 pinpoint the culprit and lists the candidates — that is the precise answer the skip range allows,
 not a failure.
 
 ## Undoing a wrong good/bad call
 
-`git bisect log` prints the session's decision history. Save it, edit out the mistaken entry, and
+`rtk git bisect log` prints the session's decision history. Save it, edit out the mistaken entry, and
 resume from the corrected log rather than restarting the search:
 
 ```bash
-git bisect log > bisect.log
+rtk git bisect log > bisect.log
 # edit bisect.log, removing the wrong decision
-git bisect reset && git bisect replay bisect.log
+rtk git bisect reset && rtk git bisect replay bisect.log
 ```
 
 ## Narrowing and speeding up
 
-- `git bisect start HEAD v1.2 -- src/` restricts bisection to a path, cutting the trial count.
+- `rtk git bisect start HEAD v1.2 -- src/` restricts bisection to a path, cutting the trial count.
 - `--no-checkout` updates the `BISECT_HEAD` ref instead of checking out a working tree — useful
   for tests that do not need one, and automatic in bare repos.
 - `--first-parent` follows only first parents at merges, finding the integration commit that
@@ -56,12 +56,12 @@ git bisect reset && git bisect replay bisect.log
 
 ## Inspecting the remaining candidates
 
-`git bisect visualize` (alias `view`) opens the suspects in gitk, falling back to `git log` when
+`rtk git bisect visualize` (alias `view`) opens the suspects in gitk, falling back to `git log` when
 no graphical display is detected. Add `--stat` or `-p` for a diffstat or full patches.
 
 ## Hunting a non-bug property change
 
-`git bisect start --term-new <new> --term-old <old>` searches for any property change — a
+`rtk git bisect start --term-new <new> --term-old <old>` searches for any property change — a
 performance regression, say — instead of a bug. Use the custom terms in place of `good` and `bad`
 for the rest of the session.