Ask the release gate which commitlore the plugin actually ran

[MongLong0214]

Closes #483. Found running RELEASE-GATE.md §4 against a fresh clone during the 0.7.0 release.

The gate passed while resolving to the wrong build

node dist/commitlore.mjs --version                            → 0.7.0
CLAUDE_PLUGIN_ROOT=$PWD sh scripts/commitlore-run.sh --version → 0.6.0

Both exit 0. The check asked whether something resolved, not whether the right thing did — and it has passed that way for two releases.

The resolution order stays

commitlore-run.sh tries commitlore on PATH before CLAUDE_PLUGIN_ROOT, deliberately: the installer's wrapper execs node itself, so it works where this script would otherwise have to find node, and on the hook hot path a missing node means no context at all.

What changes is the gate. It narrows PATH and compares the version.

Two cases, both halves pinned

nothing shadows it	entry point answers the repository's own version
a commitlore sits ahead on PATH	entry point answers that one

The second is not a bug being enshrined. It is the documented order, asserted so that changing it becomes a decision someone makes rather than a side effect of an unrelated edit.

Why this option and not the other two

#483 recorded three. This is the smallest and the only one that does not touch the hot path.

• Making the mismatch loud at runtime means running --version twice on every edit, to report a condition doctor's inject-version check already reports.
• Preferring CLAUDE_PLUGIN_ROOT reopens how ADR-0011's ship-dist-in-the-repo interacts with the installer's wrapper — a decision, not a patch.

Stated limits

The gate catches it at release time and doctor catches it for a user, but nothing tells a user who has never run doctor.

The narrowed PATH includes the interpreter's directory, so a machine whose node lives beside a commitlore wrapper still shadows the plugin and the check would pass for the wrong reason.

[github-actions]

CommitLore — record lint

Trailers: clean — 1 commit in origin/dev..7dab3e3376533712c8d9d806a656f84b98c8e4b7
Active constraints: 2 limits · 4 ruled-out · 3 warnings — from 3 records over 2 changed paths

Active constraints for the paths this PR touches

Limits (2)

• r-plugres483 7dab3e3 — the gate now catches the mismatch at release time, and doctor's inject-version check catches it for a user, but nothing tells a user who has never run doctor
• r-exit065 e545dee — any new command's exit codes must be drawn from SPEC §10, not invented locally

Ruled out (4)

• r-plugres483 7dab3e3 — preferring CLAUDE_PLUGIN_ROOT over PATH | it reopens how ADR-0011's ship-dist-in-the-repo interacts with the installer's wrapper, and the node-resolution advantage that motivated the current order would need re-examining rather than reversing
• r-plugres483 7dab3e3 — comparing versions inside the run script | it sits on the hot path of every edit and would spend a second process launch there to report a condition doctor already reports
• r-exit065 e545dee — leaving guard's inversion in place and only documenting it | guard and inject are the two commands wired into hooks and CI, so a script written against guard today is already trusting the number; a documented inversion is still an inversion, and it gets load-bearing the longer it sits. The surface is one boolean per command right now — cheaper to fix once than to explain forever.
• r-7a48c3 b85d847 — a CONFLICTED lifecycle state for divergent declarations | see above — it would block work on records that have a correct answer

Warnings (3)

• r-plugres483 7dab3e3 (claim) — the narrowed PATH in the gate includes the interpreter's directory, so a machine whose node lives beside a commitlore wrapper still shadows the plugin and the check will pass for the wrong reason
• r-exit065 e545dee (claim) — guard's swap is a breaking change for anything scripted against the old exit 2 for "matched" — see CHANGELOG Unreleased/Breaking
• r-7a48c3 b85d847 (claim) — these two changes were developed concurrently in one worktree and share a built dist/. Splitting them would leave one commit whose dist/ did not match its src/, so they land together and are described together

git log --follow accepts exactly one pathspec, so renames are not followed for 2 paths; query one path at a time to follow its rename chain

_{Trailer violations fail this check. Active constraints are informational — they are what the repository already decided, not a verdict on this PR.}