ci(hypatia): standardise the wrapper caller id to the canonical hypatia - #84
Conversation
…tia` The check a reusable-caller job publishes is `<caller job id> / <inner job display name>`. The estate's canonical required context is `hypatia / Hypatia Neurosymbolic Analysis`, so the caller job must be named `hypatia`. This wrapper named it `scan` and so published `scan / Hypatia Neurosymbolic Analysis` — two names for one gate, and any requirement written against one is unsatisfiable in a repository that publishes the other (the defect class of hyperpolymath/tropical-types#17). Rename only: the job body, its pin, inputs and secrets are byte-for-byte unchanged. Audit-first, requirement-aware sweep — hyperpolymath/standards scripts/propagate-hypatia-caller-id.sh.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (27)
🔇 Additional comments (1)
📝 SummarySummary by CodeRabbit
WalkthroughThe GitHub Actions job in ChangesHypatia workflow
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Bug fix 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkExplanation The description explains the purpose, scope, rationale, and validation context, but it does not follow the repository template. It omits the required Summary, Changes, RSR Quality Checklist, Testing, and Screenshots sections.
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. A rabbit checks the workflow bright Comment |
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
1 participant
The check a reusable-caller job publishes is
<caller job id> / <inner job display name>. The estate's canonical required context ishypatia / Hypatia Neurosymbolic Analysis(docs/audits/audit-hypatia-pin-orphan-2026-05-27.adoc), so the caller job must be namedhypatia. This wrapper named itscan, and so publishedscan / Hypatia Neurosymbolic Analysis— two names for one gate, and any requirement written against one is unsatisfiable in a repository that publishes the other (the defect class of hyperpolymath/tropical-types#17).Rename only — the job body, its pin, its inputs and its secrets are byte-for-byte unchanged.
Audit-first, requirement-aware: this is
--fixoutput fromscripts/propagate-hypatia-caller-id.shinhyperpolymath/standards(the script stages; it never commits or pushes). The repository's active branch rulesets were read before the rename — no rule here names the old prefixed context, so the published name and every requirement stay in agreement.