fix(scanner): reject unsupported AI security claims

[Param-10]

Summary

• reject unresolved action-version freshness claims for immutable full-SHA references
• distinguish npm stage publish from direct npm publish using parsed command arguments
• require unqualified reviewer approval before accepting AI-only findings
• reject remediations that weaken action pinning, bypass staged approval, introduce duplicate YAML keys, or add deterministic findings
• add a deterministic high-severity rule for direct npm publication with a long-lived repository token

Root cause

AI-only findings were accepted when the reviewer marked their evidence valid even if the final remediation recommendation was reject. Polaris also lacked semantic guards for staged npm publishing and external version-freshness claims.

Verification

• original backend suite: 42/42 passed
• reliability suite: 29/29 passed
• exact release-workflow regression: 0 accepted findings
• Python compilation and diff checks passed

Security outcome

The false fixes can no longer become applicable: Polaris rejects full-SHA-to-tag downgrades and staged-to-direct publishing changes before commit.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
polaris	Ready	Preview, Comment	Jun 24, 2026 1:40am