chore(rules): sync to canonical rule set + OP-fork desloppify install

[OriginalGary]

Summary

Syncs this repo to the canonical Claude Code rule set established in ~/.claude/rules/ plus the OP-fork desloppify install command.

What changed

• .claude/rules/: 13 always-loaded rules synced from canonical (advocacy-domain, context-repo, cost-optimization, desloppify, external-contribution-safety, git-identity, parallelization, pipeline-nevers, research-methodology, seven-concerns, tooling-reference, user-profile, voice). Path-scoped rules (security/privacy/testing/emotional-safety/accessibility/geo-seo) now live in ~/.claude/rules/ globally with paths: frontmatter and are no longer duplicated per-repo.
• .claude/rules/desloppify.md: replaced upstream PyPI install with OP fork install (pip install "git+https://github.com/Open-Paws/desloppify.git#egg=desloppify[full]") per pipeline-nevers hard rule.
• .claude/agents/: removed pre-pipeline builder/planner/scout stubs. Canonical 11-agent set lives in ~/.claude/agents/.
• .claude/skills/: removed local stub set. Canonical 26-skill set lives in ~/.claude/skills/.
• .gitignore: appended .claude/agent-memory/ and .claude/worktrees/ per tooling-reference.md requirement.
• .coderabbit.yaml: replaced 441-byte stub with classified template per repo taxonomy (where applicable).

Why

Multi-repo drift identified during the 2026-04-25 audit session — 27 of 29 repos with .claude/rules/desloppify.md had the upstream PyPI install (hard-rule violation per ~/.claude/rules/pipeline-nevers.md). Per-repo agent and skill stubs intercepted canonical dispatches with stale content.

Generated as part of the canonical-rules-sync drive. No code or behavior changes — agent/AI configuration only.

[coderabbitai]

Warning

Rate limit exceeded

@OpenGaryBot has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 51 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 5 minutes and 51 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 4be1f7b0-a176-4896-82e8-cfd0084d5797

📥 Commits

Reviewing files that changed from the base of the PR and between 3903a1a and f808059.

📒 Files selected for processing (25)

• .claude/rules/accessibility.md
• .claude/rules/context-repo.md
• .claude/rules/desloppify.md
• .claude/rules/emotional-safety.md
• .claude/rules/external-contribution-safety.md
• .claude/rules/geo-seo.md
• .claude/rules/git-identity.md
• .claude/rules/parallelization.md
• .claude/rules/pipeline-nevers.md
• .claude/rules/privacy.md
• .claude/rules/research-methodology.md
• .claude/rules/security.md
• .claude/rules/seven-concerns.md
• .claude/rules/testing.md
• .claude/rules/tooling-reference.md
• .claude/rules/user-profile.md
• .claude/rules/voice.md
• .claude/skills/advocacy-code-review/SKILL.md
• .claude/skills/advocacy-testing-strategy/SKILL.md
• .claude/skills/geo-seo-audit/SKILL.md
• .claude/skills/git-workflow/SKILL.md
• .claude/skills/plan-first-development/SKILL.md
• .claude/skills/requirements-interview/SKILL.md
• .claude/skills/security-audit/SKILL.md
• .gitignore

✨ Finishing Touches

• 🛠️ fix NAV violations: Commit on current branch
• 🛠️ fix NAV violations: Create PR

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[OriginalGary]

Quality Gate failure on this PR is a pre-existing CI bug, not caused by the rule sync.

Root cause: the desloppify.yml workflow extracts objective (mechanical-only) score, which artificially fails when ESLint or another mechanical tool cannot run on the runner. The actual blended strict_score for this repo is ~70.9 (= 25% mechanical 49.3% + 75% subjective 78.2%) and passes the ≥70 threshold.

Fix in flight: template patched in Open-Paws/context handbook/ci-templates/desloppify.yml to use strict_score from desloppify status --json instead of grep on scan output. Will propagate via the standard CI-template sync once that PR merges.

Request: Sam, please apply override:allow-score-drop label with this comment as justification, per ~/.claude/rules/pipeline-nevers.md Emergency Overrides. Numeric delta: nominal 0 (strict score did not actually regress; gate misreads the field).

[OriginalGary]

Closing: this PR propagated ~/.claude/rules/user-profile.md (contains personal info) and other private config files to a public repo. Will reopen with a sanitized version that excludes user-profile.md and any other private-only rules.