docs: drop workspace-path assumption from plugin docs and skills

[JacobPEvans]

Summary

Follow-up to #330. That PR swapped hardcoded ~/git/... references for ${GIT_HOME_PUBLIC}/<repo>/.... Reviewer pushback: skill docs and convention rules shouldn't bake any local workspace path into prose at all — describe what to do, not where files live.

What changed (10 files)

• .claude/rules/worktree-conventions.md: convention table shows relative paths (<repo>/main/, <repo>/{branch-name}/). Operational sync line drops cd, frames as "from the main worktree".
• git-standards/skills/git-workflow-standards/SKILL.md: layout diagram + table use relative paths. Create/Remove commands use ../ from the main worktree.
• git-workflows/skills/sync-main: "find and sync main" describes the worktree role; drops cd.
• git-workflows/skills/troubleshoot-worktree: git worktree add ../<branch> (relative).
• github-workflows/skills/rebase-pr: "from the main worktree" framing.
• github-workflows/skills/refresh-repo: drop the ${GIT_HOME}/CLAUDE.md citation; drop the ${GIT_HOME_PUBLIC}/<repo>/<default>/ path-resolution rule in favor of git worktree list --porcelain matching on branch refs/heads/<default>; --sweep glob description loosened.
• infra-orchestration/orchestrate-infra: "locate each target repo's main worktree" instead of a path glob.
• infra-orchestration/sync-inventory: "from the X main worktree" framing; repo list shows names only.
• infra-orchestration/test-e2e: same.
• codeql-resolver/README.md: examples annotate the worktree, drop cd.

Why this PR exists separately from #330

The user merged #330 quickly after open; the further-cleanup amend (this PR's content) didn't have time to apply pre-merge. Splitting into a follow-up keeps history clean rather than force-pushing already-merged content.

Related

• docs: use ${GIT_HOME_PUBLIC} path var across plugin docs and skills #330 — the initial path-variable sweep this builds on
• Sibling follow-up PR in JacobPEvans/ai-assistant-instructions#658 applying the same lens
• The ${GIT_HOME} / ${GIT_HOME_PUBLIC} nix-home sessionVariables stay — this PR just stops referencing them in docs where they're not load-bearing

Assisted-by: Claude noreply@anthropic.com

[gemini-code-assist]

Code Review

This pull request updates various documentation and skill files to remove absolute paths referencing ${GIT_HOME_PUBLIC} and replace them with relative paths or context-aware instructions, aligning the documentation with a more flexible workspace layout. The feedback suggests removing a redundant git switch main command when syncing from the main worktree, as the main branch is already checked out in that directory.