fix(git): scope git-workflow's trigger to ambiguity rather than to its domains

git-workflow's description enumerated the six domains it exists to route away
from, so it competed for selection with the very skills it should be handing
off to. It now triggers on the case it actually serves: an interactive request
whose domain is not yet clear.

Also clears frontmatter drift across the plugin and removes duplicated guidance
in pc-run that had diverged from its reference.

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

@@ -9,21 +9,20 @@ description: >
   Not submodule pointers -> `git-submodules`.
 
 metadata:
-  category: git-workflow
+  category: git
   source_keys:
     - git-scm-remote-docs
     - git-scm-fetch-docs
     - git-scm-push-docs
     - git-scm-pull-docs
     - context7-git-htmldocs
-
 ---
 
 ## Gotchas
 
 - **`--force-with-lease` alone is not safe** — background processes (IDE plugins, cron jobs) running `git fetch` silently defeat the protection. Combine it with `--force-if-includes`, or pin the explicit `--force-with-lease=<ref>:<sha>` form.
 - **Prune does not touch tags by default** — `git fetch --prune` leaves orphaned tags behind. Use `--prune --prune-tags`, or set `fetch.pruneTags true`.
-- **Pull defaults shift between Git versions** — older ones default to merge, newer to `--ff-only`. Set `pull.ff only` explicitly rather than trusting the installed default.
+- **Set `pull.ff only` explicitly** — do not trust the installed default.
 
 ## Step 1 — Clear the force-push gate
 

plugins/git/.apm/skills/git-remotes/references/pull.md

@@ -23,6 +23,10 @@ A pull that diverges with no strategy configured fails, and that failure is the
 
 ## Config precedence
 
+The installed default varies by Git version — older versions merge on divergence, newer ones
+default to `--ff-only` — so an unset `pull.ff` means the same pull behaves differently on different
+machines. Set it explicitly.
+
 Highest wins:
 
 1. Command-line flag (`--ff-only` / `--rebase` / `--no-rebase`)