Skip to content

ci(hypatia): standardise the wrapper caller id to the canonical hypatia - #93

Merged
hyperpolymath merged 1 commit into
mainfrom
fix/hypatia-caller-id
Sep 20, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
fix/hypatia-caller-id

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

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 (docs/audits/audit-hypatia-pin-orphan-2026-05-27.adoc), 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, its inputs and its secrets are byte-for-byte unchanged.

Audit-first, requirement-aware: this is --fix output from scripts/propagate-hypatia-caller-id.sh in hyperpolymath/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.

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

Copy link
Copy Markdown

@coderabbitai

coderabbitai Bot commented Sep 20, 2026

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: e6d075ae-cb94-4058-9022-ff11fdcd6ef5

📥 Commits

Reviewing files that changed from the base of the PR and between bd0f119 and 5d9cfda.

📒 Files selected for processing (1)
  • .github/workflows/hypatia-scan.yml

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. (14)
  • GitHub Check: scan / gitleaks
  • GitHub Check: scan / shell-secrets
  • GitHub Check: scan / rust-secrets
  • GitHub Check: hypatia / Hypatia Neurosymbolic Analysis
  • GitHub Check: governance / Workflow security linter
  • GitHub Check: governance / Trusted-base reduction policy
  • GitHub Check: governance / Language / package anti-pattern policy
  • GitHub Check: governance / Licence consistency
  • GitHub Check: governance / Security policy checks
  • GitHub Check: governance / Code quality + docs
  • GitHub Check: governance / Check Workflow Staleness
  • GitHub Check: governance / Guix primary / Nix fallback policy
  • GitHub Check: governance / Well-Known (RFC 9116 + RSR)
  • GitHub Check: rust-ci / Detect Cargo.toml
🔇 Additional comments (1)
.github/workflows/hypatia-scan.yml (1)

22-22: LGTM!


📝 Summary

Summary by CodeRabbit

  • Chores
    • Updated the name of the security scanning workflow job.

Walkthrough

The GitHub Actions workflow job is renamed from scan to hypatia. Its reusable workflow, permissions, triggers, and configuration remain unchanged.

Changes

Workflow job rename

Layer / File(s) Summary
Rename the workflow job
.github/workflows/hypatia-scan.yml
The job name changes from scan to hypatia. Existing workflow settings remain unchanged.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Bug fix

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description explains the change and its rationale, but it does not follow the repository template. It omits the required Summary, Changes, RSR Quality Checklist, Testing, and Screenshots sections,… Add the repository template sections. List the change under Changes, complete every applicable RSR Quality Checklist item, and document testing under Testing. State that Screenshots are not applicable, if no screenshots or terminal output a…
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the CI change and states that the wrapper caller ID is standardised to the canonical hypatia value.
Docstring Coverage ✅ Passed 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 ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Description check

Explanation

The description explains the change and its rationale, but it does not follow the repository template. It omits the required Summary, Changes, RSR Quality Checklist, Testing, and Screenshots sections, including the required checklist confirmations.

Resolution

Add the repository template sections. List the change under Changes, complete every applicable RSR Quality Checklist item, and document testing under Testing. State that Screenshots are not applicable, if no screenshots or terminal output are available.

  • Fix all pre-merge checks with AI

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

A rabbit checks the workflow lane
The job now bears a newer name
Triggers stay still
Permissions will
Hypatia hops through the chain

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

@hyperpolymath
hyperpolymath merged commit a1877c9 into main Sep 20, 2026
15 of 17 checks passed
@hyperpolymath
hyperpolymath deleted the fix/hypatia-caller-id branch September 20, 2026 23:19
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