playbooks(repo-sweep): add an Override block to the hygiene catalog's coupling entry

[kyle-sexton]

The coupling entry in skills/repo-sweep/catalogs/hygiene.md runs coupling:reduce with no #### Override. That skill hardcodes its own branch and PR steps. Phase E says to work on a short-lived branch created from the default branch, and phase G opens a pull request. Both conflict with repo-sweep's one-branch, one-commit model, and guard.sh would stop the step with exit 10 if the skill followed them.

In the melodic-software/.github sweep (melodic-software/.github#153), the agent avoided this only by stating its own instruction to stay on the branch. batch-simplify and tidy handle the same situation with an Override block.

Proposed Override text:

Stay on the current branch. Do not create a branch or a pull request, and do not commit per reduction; leave all changes uncommitted, repo-sweep makes the step commit. Record route-lane findings in the ledger; file tracker items only when the user approves.

A tracking issue against the coupling plugin could make the branch and PR steps optional; this Override would then point to it.

🤖 Generated with Claude Code

[kyle-sexton]

This was generated by AI during triage.

Agent Brief

Type: Bug
Summary: repo-sweep hygiene catalog's coupling entry gets an Override block.

Current behavior:
The coupling entry has no Override; coupling:reduce creates branches, PRs and per-reduction commits, which conflict with repo-sweep's one-branch/one-commit model (the sweep guard exits 10).

Desired behavior:
Add an Override: stay on the sweep branch, no branch or PR, no per-reduction commits, leave changes uncommitted for the step commit, ledger route-lane findings, file tracker items only with approval. Follow the batch-simplify entry's Override as precedent.

Acceptance criteria:

• catalog.sh --override coupling prints the new text.