Skip to content

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

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.
@coderabbitai

coderabbitai Bot commented Sep 20, 2026 •

Copy link
Copy Markdown
Contributor

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: 5db4d1e0-ea7a-4120-ac24-2f0a06c8aeed

📥 Commits

Reviewing files that changed from the base of the PR and between 7003b64 and d802fbe.

📒 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. (10)
  • GitHub Check: hypatia / Hypatia Neurosymbolic Analysis
  • GitHub Check: scan / rust-secrets
  • GitHub Check: scan / shell-secrets
  • GitHub Check: scan / gitleaks
  • GitHub Check: lint-workflows
  • GitHub Check: Validate A2ML manifests
  • GitHub Check: Groove manifest check
  • GitHub Check: Empty-linter (invisible characters)
  • GitHub Check: Validate K9 contracts
  • GitHub Check: analyze (actions, none)
🔇 Additional comments (1)
.github/workflows/hypatia-scan.yml (1)

18-18: LGTM!


📝 Summary

Summary by CodeRabbit

  • Chores
    • Renamed the GitHub Actions job identifier for improved workflow clarity.

Walkthrough

The GitHub Actions job identifier changes from scan to hypatia. The reusable workflow and configuration remain unchanged.

Changes

Hypatia workflow

Layer / File(s) Summary
Rename the workflow job
.github/workflows/hypatia-scan.yml
The job identifier changes from scan to hypatia.

Priority: ⬇️ Low

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

Change: Bug fix

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: renaming the Hypatia wrapper caller job ID to the canonical hypatia.
Description check ✅ Passed The description directly explains the job ID rename, the resulting check context, and the unchanged workflow contents. It is relevant to the changeset.
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.

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 watched the workflow run
The job name changed beneath the sun
From scan to hypatia, neat and bright
The workflow keeps its former flight
One small rename, the path stays clear

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

@sonarqubecloud

Copy link
Copy Markdown

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