crates/agnix-cli/tests/kiro_ci_gate.rs:173

• This Kiro-only VALIDATION-RULES.md parity check appears redundant with rule_parity.rs::test_rules_json_matches_validation_rules_md() which already enforces that all rules.json IDs are present in VALIDATION-RULES.md and runs under cargo test --workspace. Unless CI is intentionally skipping the global parity test, consider removing this duplicate to reduce maintenance burden.

fn kiro_rules_still_documented_in_validation_rules() {
    let rules_path = workspace_root().join("knowledge-base/rules.json");
    let rules_content = fs::read_to_string(&rules_path)
        .unwrap_or_else(|e| panic!("Failed to read {}: {}", rules_path.display(), e));
    let index: RulesIndex = serde_json::from_str(&rules_content)

.github/workflows/ci.yml:40

• ci.yml currently only runs fmt/clippy/tests + the Kiro gate, but .github/workflows/README.md documents ci.yml as including “coverage” and “build” as well. If this workflow is intended to replace the shared ci-rust.yml, consider restoring the missing checks (or updating the workflows README to match the new behavior) so CI expectations stay accurate.

      - name: Test
        run: cargo test --workspace

      - name: Kiro S-tier Gate
        run: cargo test -p agnix-cli --test kiro_ci_gate -- --include-ignored

crates/agnix-cli/tests/kiro_ci_gate.rs:133

• This has_non_cc_rule assertion is redundant/misleading: any KIRO-* / KR-SK-* diagnostic already satisfies “non-CC”, and you assert those separately. Consider removing this assertion, tightening it to check for a non-Kiro prefix, or rewording the message to reflect what’s actually being validated.

    assert!(
        has_non_cc_rule,
        "With --target kiro, non-CC rules should still run"
    );

crates/agnix-cli/tests/kiro_ci_gate.rs:155

• This README Kiro-row check largely duplicates docs_website_parity.rs::readme_supported_tools_kiro_row_matches_current_rules_surface() (which also validates the rule count derived from rules.json). Consider reusing/factoring the existing parity assertion (or dropping this one) to avoid having two near-identical checks that can drift independently.

    let kiro_row = readme
        .lines()
        .find(|line| line.starts_with("| [Kiro](https://kiro.dev) |"))
        .expect("README.md Supported Tools table must include a Kiro row");