fix: match required check terminal conclusions

[coygeek]

Summary

• Treat SUCCESS, SKIPPED, and NEUTRAL as passing terminal required-check states.
• Treat STARTUP_FAILURE as a terminal failed required-check state.
• Add regression coverage for skipped, neutral, and startup failure conclusions.

Validation

• PYTHONPATH=src python3 -m pytest tests/test_cli.py -q
• PYTHONPATH=src python3 -m pytest -q
• PYTHONPATH=src python3 -m ruff check .
• autoreview --mode local --engine droid: clean, no accepted/actionable findings

Closes #16

[mberman84]

The required-check conclusion mapping is sound, but this submitted head is blocked on current main: it conflicts in tests/test_cli.py, and GitHub CI has not run (action_required). Please rebase onto current main, preserve the newer exact-commit/integration coverage, and reconcile this reducer with #22 so PASSED_CHECK_STATES survives the identity aggregation. Re-request review on the updated head.

[mberman84]

This replacement test conflicts with the newer tests on current main. Please rebase and preserve both sets of coverage. While resolving the shared reducer with #22, make sure SKIPPED and NEUTRAL remain passing for every retained check identity.

[coygeek]

Addressed the review feedback in the updated head. Rebased onto current main, preserved the newer check coverage, and kept the required-check reducer aligned with GitHub semantics for success/skipped/neutral passing states and startup failure as terminal failure.

Verification: PYTHONPATH=src uv run --with pytest --with ruff python -m pytest tests/test_cli.py -q and uv run --with ruff ruff check src tests both pass.

[mberman84]

Re-reviewed on current main after the requested reconciliation. Full suite: 219 passed, 3 skipped, 202 subtests; Ruff and package build pass; structured autoreview reports no actionable findings.