chore(protect-mcp): pin protect-mcp@0.5.5 and @veritasacta/verify@0.3.0

[tomjwxf]

Follow-up to the pinning suggestion @wshobson raised on #494. Replaces every npx protect-mcp@latest in executed paths with npx protect-mcp@0.5.5, and every npx @veritasacta/verify in the test runner with npx @veritasacta/verify@0.3.0. The tamper-detection test can no longer be silently flipped by an upstream npm publish.

What this changes

File	Pins applied
plugins/protect-mcp/hooks/hooks.json	2 × protect-mcp@latest → protect-mcp@0.5.5 (PreToolUse + PostToolUse)
plugins/protect-mcp/test/run-tests.sh	6 × protect-mcp@latest → protect-mcp@0.5.5, 3 × @veritasacta/verify → @veritasacta/verify@0.3.0

Header comment at the top of run-tests.sh updated to mention the pinned @veritasacta/verify version so the dependency is visible without reading the full script.

What this deliberately does NOT change

• README.md and skills/protect-mcp-setup/SKILL.md — the npx protect-mcp@latest references there are documentation of the pattern a user should use in their own project, and "latest" is genuinely the right advice for a downstream consumer. The test infrastructure is the only executed path where pinning affects reproducibility.
• marketplace.json — not touched at all, so no conflict with feat: add review-agent-governance plugin (second inhabitant of governance category) #495 or feat: add signed-audit-trails teaching plugin (third governance-category skill) #496.
• review-agent-governance and signed-audit-trails plugins — still in review. I will file a follow-up to pin those once they land.

How bumps work

When protect-mcp ships a new version with a breaking change, the bump is a two-file sed:

perl -i -pe 's/protect-mcp\@0\.5\.5/protect-mcp\@0.6.0/g' \
  plugins/protect-mcp/hooks/hooks.json \
  plugins/protect-mcp/test/run-tests.sh
./plugins/protect-mcp/test/run-tests.sh   # confirm tamper test still passes

Deliberate bumps from here on, not automatic.

Verification

• python3 -m json.tool hooks.json passes
• bash -n run-tests.sh passes syntax check
• No other files touched; clean 2-file diff
• npm view protect-mcp version confirmed 0.5.5 is current stable
• npm view @veritasacta/verify version confirmed 0.3.0 is current stable

Why this closes the loop from #494

On #494 you said: "run-tests.sh uses npx protect-mcp@latest, so an upstream release could silently turn the tamper-detection guard green or red without any repo change. Pinning to a specific protect-mcp@x.y.z (and bumping deliberately) would make the guard fully reproducible. Not blocking — happy to land as-is."

This is exactly that pin. The tamper-detection guard is now reproducible at protect-mcp@0.5.5 + @veritasacta/verify@0.3.0, and future changes to those packages require a deliberate bump here.

Out of scope (follow-ups after this and #495/#496)

• Pin the same versions in review-agent-governance and signed-audit-trails once they land.
• Add a note to the README pointing at this commit as the "how to update pinned versions" reference.

Thanks for the suggestion; small but real tightening of the test contract.