Skip to content

ci(hypatia): standardise the wrapper caller id to the canonical `hypa… - #147

Merged
hyperpolymath merged 2 commits into
mainfrom
fix/hypatia-caller-id
Sep 27, 2026
Merged

hyperpolymath merged 2 commits into
mainfrom
fix/hypatia-caller-id

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

…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.

Summary

Closes #

Type of change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (would change existing behaviour)
  • 🕳️ Soundness fix (fixes a checker/proof false-negative)
  • 📖 Documentation
  • 🧹 Refactor / tech debt (behaviour-preserving)
  • ⚡ Performance
  • 🔧 Build / CI / tooling

How has this been verified?

Checklist

  • My commits are signed (git commit -S).
  • I ran the project's own checks/tests locally and they pass.
  • New files carry the correct SPDX-License-Identifier (code/config MPL-2.0,
    prose CC-BY-SA-4.0); I did not relicense existing files.
  • Docs are updated, and no public claim now overstates what the code does.
  • I have not introduced a soundness hole (or I have flagged where I might have).

Notes for reviewers

…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.
@hyperpolymath
hyperpolymath merged commit 4c03813 into main Sep 27, 2026
0 of 2 checks passed
@coderabbitai

coderabbitai Bot commented Sep 27, 2026

Copy link
Copy Markdown
Contributor

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: d8d48c08-a3e8-41b8-8c9e-f2622116b591

📥 Commits

Reviewing files that changed from the base of the PR and between ae5c7b5 and b547f7e.

📒 Files selected for processing (1)
  • .github/workflows/hypatia-scan.yml
 _______________________________________________________
< Cancel my subscriptions ... I'm tired of your issues. >
 -------------------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       /   づ

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

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

@hyperpolymath
hyperpolymath deleted the fix/hypatia-caller-id branch September 27, 2026 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant