feat(loop): gate target precedence + ecosystem-neutral gate docs

[mabry1985]

Follow-up to the auto gate resolver (#73): make the model first-class for complex-CI, non-node repos.

The insight

The pre-PR gate is the coder's fast slice of CI — lint + typecheck + unit tests — not a full-CI replica. A complex CI's heavy jobs (cross-platform matrix, integration, docker publish, release, deploy) stay CI-only: they run once on the PR as the human's merge gate, and anything the local slice misses returns to the coder via the CI-bounce. You never replicate heavy CI in a worktree.

Changes

• gate target resolves first (before ci/check/verify), for both package.json scripts and Makefile/justfile targets — so a repo whose ci is the whole heavy suite points coders at a dedicated fast gate, and auto won't grab the heavy one.
• Ecosystem-neutral docs: node → pnpm run <it>; Python/Rust/Go → make/just <it>. Worked example — protoAgent: 9 workflows, but only checks.yml (ruff + pytest) is pull_request-gating and coder-relevant; desktop-build/docker-publish/release/marketing-deploy are push/tag/dispatch and never a coder gate. Its slice is make gate = ruff check . && pytest -q -m "not integration".

2 new resolver tests (gate beats ci in package.json and Makefile). Full suite green.

🤖 Generated with Claude Code

[protoquinn]

👀 Quinn is reviewing — verdict (PASS / WARN / FAIL) + findings to follow.

[protoquinn]

QA Audit — PR #74 | feat(loop): gate target precedence + ecosystem-neutral gate docs

VERDICT: WARN (CI pending — comment only; auto-approve-on-green once CI settles)

---

CI Status

• test: ⏳ queued

Diff Review

• 3 files, +135/-19 — mostly docs (README, loop.py docstring) + a single-line logic change: _GATE_TARGET_NAMES = ("gate", "ci", "check", "verify") replaces inline tuples in both the package.json and Makefile/justfile resolver paths.
• Two new tests: test_resolve_gate_auto_prefers_gate_over_ci_script and test_resolve_gate_auto_makefile_gate_beats_ci.

Observations

• CLAWPATCH: structural pass across 18 features — zero findings. No correctness, concurrency, data-loss, or contract issues detected.
• The _GATE_TARGET_NAMES tuple extraction is clean — DRYs the two resolver paths and makes the gate-first precedence explicit in one place. No risk of the two paths drifting.
• Docs are thorough and ecosystem-neutral (Python/Rust/Go examples with Makefile/justfile, not just Node).
• LOW: the warning message in the gateless fallback case (log.warning(...)) mentions gate/ci/check for scripts and gate/ci for Makefile — slightly asymmetric vs the actual tuple ("gate", "ci", "check", "verify") which is used for both paths. Not a bug, just a docs-log surface misalignment. The warning string is fine because Makefile targets won't practically be named check or verify, but the log string doesn't reflect the actual code's behavior. Cosmetic.

---

⚠️ CI (test) is still queued. Per the approve-on-green policy, this review promotes to APPROVED automatically once every check settles terminal-green — no re-review needed.

— Quinn, QA Engineer

[protoquinn]

Submitted COMMENT review on #74.

[protoquinn]

CI terminal-green, no blockers on prior review — auto-approving on green (#748).

[protoquinn]

✅ CI went terminal-green with no blockers on the prior review — promoting it to APPROVED per the approve-on-green policy (#748).