Summary

Kiro has zero references in CI workflows. S-tier tools must be tested on every merge. Add explicit Kiro coverage to the CI pipeline.

What's needed

• Add Kiro fixture tests to CI test matrix
• Include Kiro real-world repo validation in CI
• Add Kiro rule parity check (rules.json vs VALIDATION-RULES.md)
• Ensure Kiro regressions block merges (S-tier = "test always")

Acceptance criteria

• Kiro tests run in CI on every PR
• Kiro real-world repo validation included
• Kiro rule parity enforced
• CI failures on Kiro regressions block merge