fix(git): restore router coverage and commands the retrofit dropped

git-workflow calls itself a router but named two of the six domains it routes to;
the other four appeared nowhere in the file. All six are now named, with a
routing table in the always-loaded body.

git-submodules lost the foreach shell-variable semantics -- only the bare names
survived, though $sm_path and $displaypath differ solely by which directory you
are in. The table is back. Its relocated commands had also dropped the rtk git
prefix its own SKILL.md mandates; 24 of them are re-prefixed. The wider rtk
inconsistency across the plugin stays with #113.

Also restores git-commits' body and footers output fields, git-branches' tag/
branch detection commands, git-worktrees' git config --worktree, pc-run's
ambiguity fallback, git-remotes' git-history boundary, and git-history's pickaxe
triggers.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EJJrm5YmacbwMdzZpXcoti

plugins/git/.apm/skills/git-history/SKILL.md

@@ -2,10 +2,10 @@
 name: git-history
 
 description: >
-  Use when investigating git history — querying logs, tracing when a change
-  landed, bisecting the commit that broke something, or locating one to
-  revert or backport. Not authoring or rebasing commits -> `git-commits`.
-  Not history on a Gitea server -> `gitea-branches`.
+  Use when investigating git history — pickaxe (`-S`/`-G`) or `-L` line-range log
+  queries, tracing when a change landed, bisecting what broke something, or
+  locating a commit to revert or backport. Not authoring or rebasing commits ->
+  `git-commits`. Not a Gitea server's history -> `gitea-branches`.
 
 metadata:
   category: git