Stop security-reviewer from blocking on governing document type labels

[shinpr]

Summary

security-reviewer returned blocked when a governingDocuments entry used a type label other than design-doc or work-plan, even though every path was readable. The reviewer never uses the type value for anything, so this check only stopped reviews over a label.

The label is easy to get wrong. The build and implement recipes ask for a "typed governingDocuments list" but do not name the accepted values. document-reviewer also names the same documents differently (DesignDoc, UISpec). So a caller that has been calling document-reviewer all session can easily pass DesignDoc here.

This PR fixes it by removing the check, not by adding examples or aligning names across agents.

Changes

• Removed: the type check from the Step 1 input gate in security-reviewer.md. The gate now blocks only when governingDocuments is empty or a path is unreadable.
• Changed: the quality checklist item now checks that the paths are readable, not the type and path.

Also included: the patch version is bumped to 0.27.5, and the plugin copies are synced.

Verification

I ran security-reviewer with claude -p and --plugin-dir on a small fixture repository, once with the main definition and once with this branch.

Input	main	This branch
DesignDoc + UISpec labels, readable paths	blocked (invalid type)	pass after checking the Design Doc's requirements against the code
design-doc label, missing path	—	blocked (file does not exist)

claude plugin validate passes for the marketplace and all plugins.

🤖 Generated with Claude Code