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

[hyperpolymath]

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

Description

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 📖 Documentation update
• 🎨 Code style/refactoring (no functional changes)
• ⚡ Performance improvement
• 🔒 Security fix
• 🧪 Test updates
• 🔧 Configuration/infrastructure changes

Related Issues

Closes #
Related to #

Changes Made

Testing

Test Environment

• Ruby version:
• Rails version:
• Database:
• Browser (if applicable):

Test Steps

Test Results

• All existing tests pass
• New tests added for new functionality
• Manual testing completed
• No regressions detected

Screenshots

Checklist

Code Quality

• My code follows the project's coding standards
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings or errors
• I have added SPDX license headers to all new files

Testing

• I have added tests that prove my fix/feature works
• New and existing unit tests pass locally
• I have tested on multiple browsers/devices (if applicable)

Documentation

• I have updated relevant documentation (README, CONTRIBUTING, etc.)
• I have updated CHANGELOG.md with notable changes
• I have added/updated code comments where necessary
• API documentation is updated (if applicable)

Security

• No security vulnerabilities introduced
• Sensitive data is properly handled
• Input validation is implemented
• No debugging code (console.log, binding.pry, etc.) left in

Database

• Database migrations are reversible
• Migrations tested on a copy of production data (if applicable)
• No destructive changes without confirmation

Performance

• No significant performance degradation
• Database queries are optimized (no N+1 queries)
• Large files/data handled efficiently

Additional Context

Reviewer Notes

---

By submitting this pull request, I confirm that:

• I have read and agree to the Code of Conduct
• I have read the Contributing Guidelines
• My contribution is original or properly attributed
• I agree to license my contribution under GPL-3.0-or-later

[coderabbitai]

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: cab2d31b-78ff-4df2-8369-50092570cb55

📥 Commits

Reviewing files that changed from the base of the PR and between 2972495 and f0b6538.

📒 Files selected for processing (1)

• .github/workflows/hypatia-scan.yml

 ________________________________________________
< Press W-A-S-D to move me around your codebase. >
 ------------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       / 　 づ

• Autopilot · 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.}