ci: add ci-ok aggregate gate

[AngeloAvv]

Summary

Adds an aggregate ci-ok job as the last job of the Pipeline workflow (default.yml).

• ci-ok depends on: analyze, test, build
• It runs with if: always() and fails if any required job failed, was cancelled or was skipped.
• Tag-only / deploy jobs (publish) are intentionally excluded, since they are skipped on regular pushes and PRs.

Why

ci-ok gives a single, stable status check name. It can be used as the only required check in branch protection and for native auto-merge, instead of listing every matrix job individually (which breaks whenever the matrix changes).

No other changes to the workflows.

Summary by CodeRabbit

• Chores
  • Added a CI status check that fails when analysis, tests, or builds fail, are cancelled, or are skipped.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 06a116dd-64c7-41b9-bbb9-405d16020b3d

---

📥 Commits

Reviewing files that changed from the base of the PR and between d2e147e and b5ebb5f.

---

📒 Files selected for processing (1)

• .github/workflows/default.yml

---

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

---

📝 Walkthrough

Walkthrough

The default workflow adds an always-run ci-ok job. It checks the results of analyze, test, and build and exits with status 1 if any job fails, is cancelled, or is skipped. The publish job retains its workflow reference.

Changes

CI workflow

Layer / File(s)	Summary
CI result gate .github/workflows/default.yml	The workflow adds an always-run ci-ok job that checks analyze, test, and build. It exits with status 1 if any of those jobs fails, is cancelled, or is skipped. The publish job continues to reference .github/workflows/publish.yml.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

---

Merge Risk: ⚪ Minimal · up to b5ebb

The workflow provides a ci-ok check on pull requests and pushes and fails it when a required job reports failure, cancellation, or skip. No merge-blocking defect is established; select ci-ok in branch protection if it should be required for merges.

Pre-merge checks | 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the addition of the ci-ok aggregate CI gate, which is the main change in the pull request.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

---

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}