Non-required Woodpecker check reliability sweep — dry-run validation

Issue #4471. This is a one-time offline validation of scripts/ci/check_wp_non_required_reliability.py's flagging logic against the historical queue-docker-smoke/detect-changes incident (pipelines 5096 and 5102, both failure, per docs/incidents/2026-08-10-queue-docker-smoke-ci-commit-before-unset.md), run against a fixture reconstructed from that incident doc rather than a live WP API call (no WOODPECKER_API_TOKEN available in this dev environment). The weekly WP cron (.woodpecker/wp-non-required-reliability- sweep.yaml) will write a real report to this directory once enabled and run against live pipeline history — see scripts/ci/tests/test_check_wp_non_required_reliability.py for the automated regression coverage of this same fixture shape.

Required-workflow set used: {ci-pr, pii-scan} (confirmed live via gh api repos/raxx-app/TradeMasterAPI/branches/main/protection on 2026-09-08 — queue-docker-smoke is not in required_status_checks. contexts, confirming it is in-scope for this sweep).

--min-runs set to 2 for this reconstruction (the incident doc only records 2 confirmed failing pipeline numbers, 5096/5102) instead of the script's production default of 5 — see the test suite's test_padded_to_five_runs_all_failing_is_flagged for proof the same logic flags the sustained pattern at the production default once it accumulates to 5+ runs (the real defect was latent since the step was authored, i.e. far more than 5 runs in practice).

Weekly non-required Woodpecker check reliability sweep

Generated: 2026-08-10T00:00:00Z UTC Lookback window: 7 days Flag threshold: failure rate > 80% over >= 2 runs

Scope: .woodpecker/*.yaml workflows NOT in branch protection's required_status_checks.contexts (those already have merge-time visibility). See #4471.

Flagged (sustained failure, candidate for fix or removal)

All non-required checks observed