feat(validation): enforce label-to-score-band consistency

[peterexcel494-oss]

Summary

Extends scripts/validate-fixtures.mjs to enforce the documented score bands for each destination label, as specified in CONTRIBUTING.md. Before this change the validator confirmed scores were integers in 0–100 but never checked whether a score matched the band for its label — a fixture could be labelled clean with a malicious-range score and CI would not catch it.

Changes

scripts/validate-fixtures.mjs

• Export SCORE_BANDS constant mapping each label to its { min, max } band: clean → 0–25, suspicious → 40–70, malicious → 75–100
• Export scoreMatchesBand(label, score) — returns true when score falls within the expected band for the given label
• Export bandRangeLabel(label) — returns a human-readable range string (e.g. "0–25") for use in error messages
• Band-check loop produces actionable errors naming the fixture ID, actual score, and expected range; intentional gaps (26–39 and 71–74) are preserved

scripts/validate-fixtures.test.mjs (new file)

78 tests using Node's built-in node:test runner covering:

• SCORE_BANDS shape and values for all three labels
• bandRangeLabel output and unknown input handling
• scoreMatchesBand boundary values (min and max of each band)
• Values just inside and just outside each boundary
• All gap values (26–39 and 71–74) rejected by every label
• Cross-label mismatch scenarios (the core issue Enforce label-to-score-band consistency in fixture validation #62 case)
• Invalid/unknown label inputs

package.json

• Added "test": "node --test scripts/validate-fixtures.test.mjs" script

Acceptance Criteria

• Valid existing fixtures pass (npm run validate exits 0)
• Mismatched label/score bands fail with an actionable error message
• Boundary values follow CONTRIBUTING.md (clean 0–25, suspicious 40–70, malicious 75–100)
• Error output identifies the fixture ID and expected range
• Automated tests cover valid and invalid boundaries (78 tests, all passing)

Testing

npm test          # 78 tests — all pass
npm run validate  # Fixture validation passed: 12 destinations, 12 scores

Cross-Repository Impact

None. Fixture values in destinations.json and scores.json are unchanged.

Closes #62

[knytcomics-ui]

please one test failing