Problem
CI outcomes are consumed ad hoc in maintenance automation and can misclassify no checks states as pass.

Why now
Cross-repo reliability workflows require deterministic check-state categorization.

Current behavior is insufficient
Raw check rollups are heterogeneous and not normalized for automation consumers.

Expected behavior
Introduce a machine-readable classifier command/script that maps check rollups to normalized states.

Acceptance criteria

• Deterministic JSON output schema.
• Correct mapping for failed, pending, no checks, policy-blocked.
• Explicit handling for gh pr checks returning no checks reported.

Validation

• Unit/fixture tests for all states.
• Verification against at least one real PR in each category when available.

Codepaths

• libs/cli
• scripts
• Makefile