ci(hypatia): standardise the wrapper caller id to the canonical hypatia - #14
Merged
Merged
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.
Contributor
|
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. (23)
🔇 Additional comments (1)
📝 SummarySummary by CodeRabbit
WalkthroughThe GitHub Actions job that runs the Hypatia security scan is renamed from ChangesHypatia workflow
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Bug fix 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 lane Comment |
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.