04ec6693b3
All checks were successful
CI / skinny-install (aco) (push) Successful in 51s
CI / skinny-install (api) (push) Successful in 30s
CI / skinny-install (bcda) (push) Successful in 24s
CI / skinny-install (bib) (push) Successful in 25s
CI / skinny-install (bls) (push) Successful in 20s
CI / skinny-install (ccw) (push) Successful in 34s
CI / skinny-install (cli) (push) Successful in 27s
CI / skinny-install (cms) (push) Successful in 24s
CI / skinny-install (conf) (push) Successful in 25s
CI / skinny-install (pfs) (push) Successful in 25s
CI / skinny-install (rex) (push) Successful in 25s
CI / lint-test (push) Successful in 6m4s
Infra CI / notebooks (push) Successful in 7s
Infra CI / zotero (push) Successful in 7s
Infra CI / docs (push) Successful in 37s
Infra CI / api (push) Successful in 6s
Infra CI / mc (push) Successful in 7s
Deploy / build-scan-report (push) Successful in 4m0s
Add backend-agnostic CI failure reporter (api.diag.ci) and wire `if: failure()` steps into every job across all generated workflows. - src/api/diag/ci.py: CLI tool that files Gitea issues with workflow, job, run, commit context — works with Gitea Actions, GitHub Actions, and Woodpecker (takes args, not env-specific) - dev/scripts/backends/gitea.py: _failure_step() added to all 6 workflows (11 jobs total) - dev/scripts/backends/github.py: same _failure_step() pattern for GitHub Actions backend - .gitea/workflows/pkg-supply-chain.yml: manual failure step added (stale generated file) - 6 new tests, 12,061 total passing Now ANY step failure in ANY CI workflow on ANY backend will auto-create a Gitea issue with the workflow name, job, run number, and commit SHA.