Skip to content

fix(ci): move the Hypatia pin from be98f74 to the template's 6693f9a - #38

Merged
hyperpolymath merged 1 commit into
mainfrom
claude/hypatia-pin-6693f9a
Nov 15, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
claude/hypatia-pin-6693f9a

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

What

All six be98f74 Hypatia pin sites move to 6693f9a, the pin rsr-template-repo main uses at the same sites:

  • hypatia-scan.yml (HYPATIA_SHA)
  • fork-governance.yml and verdict-grid-publish.yml (--hypatia-ref)
  • .machine_readable/policies/hypatia-rule-order.json (scanner.commit)
  • docs/HYPATIA-RULE-ORDER.adoc
  • tests/workflows/verdict_grid_test.sh

The dogfood-gate.yml checkout stays at 51539ab, as in the template. That commit already contains the fix.

Why

Hypatia Neurosymbolic Analysis fails on #37 with a segmentation fault: run 43705667451, hypatia-cli.sh scan, exit 139.

be98f74 predates hypatia#1062 (37b8d01). The BEAM compiler miscompiles Hypatia.Rules.PinSites.walk/4: an in-place binary append on a string that is still referenced makes the VM crash in garbage collection. #1062 turns that optimisation off for that module. 6693f9a contains 37b8d01.

This run crashed on OTP 27.3.4.19, so the OTP 27 pin in hypatia-scan.yml does not avoid the crash. #1062 had recorded OTP 27 as unaffected.

The crash comes from main's pins, so the fix belongs on main. #37 picks it up once main is merged into it.

Evidence

  • git merge-base --is-ancestor 37b8d01 6693f9a: true.
  • scripts/check-hypatia-rule-order.sh passes: 7 layers, 8 concerns, 8 clashes, 2 modules.
  • scripts/check-workflow-edges.sh passes: all workflow edges resolve.
  • tests/workflows/verdict_grid_test.sh: PASS: verdict grid lane suite (197 checks).

Not done

  • Other drift from the template in these files is left out to keep this to one topic: the upload-sarif pin, FLEET_REF, a guard on fork-governance.yml line 327, and doc wording.
  • The template itself still splits its Hypatia pins (6693f9a in four places, 51539ab in dogfood-gate.yml). That belongs in rsr-template-repo.

Generated by Claude Code

The Hypatia scan crashes with a segmentation fault (exit 139) at
be98f74 (bactrian#37, run 43705667451). be98f74 predates hypatia#1062
(37b8d01), which stops a BEAM miscompile of
Hypatia.Rules.PinSites.walk/4 that crashes the VM in garbage
collection. This run crashed on OTP 27.3.4.19, so the OTP 27 pin in
hypatia-scan.yml does not avoid it.

All six be98f74 sites move to 6693f9a, the pin rsr-template-repo main
uses at the same sites. 6693f9a contains 37b8d01. The dogfood-gate
checkout stays at 51539ab, as in the template.

Checks: scripts/check-hypatia-rule-order.sh, scripts/check-workflow-edges.sh,
tests/workflows/verdict_grid_test.sh (197 checks) all pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136P7ZkGCWGEyedTtdEHAPT
@coderabbitai

coderabbitai Bot commented Nov 15, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 54 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

Commits

Reviewing files that changed from the base of the PR and between 4bd48e8 and 9bad47d.

Files selected for processing: 6

  • .github/workflows/fork-governance.yml
  • .github/workflows/hypatia-scan.yml
  • .github/workflows/verdict-grid-publish.yml
  • .machine_readable/policies/hypatia-rule-order.json
  • docs/HYPATIA-RULE-ORDER.adoc
  • tests/workflows/verdict_grid_test.sh

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

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 15, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-15T10:56:38.175937Z 9bad47d PR opened
🔒 Security Review ✅ Completed 2026-11-15T10:58:38.707856Z 9bad47d PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@sonarqubecloud

Copy link
Copy Markdown

@github-actions

github-actions Bot commented Nov 15, 2026 •

Copy link
Copy Markdown

Hypatia grid green

🟢 clean · commit 9bad47d3df0d · run 43706769631 · scope: this change (6 file(s))

Advisory: 11 row(s), worst 🔴 high (0 critical, 9 high in grid scope) — reported, never grading the change.

Unique graded findings across gating and advisory rows: 22 (22 reporter observations; 21 without sufficient identity to corroborate). Row counts remain per reporter; unique totals do not change gating.
Raw Hypatia alert-derived observations: 39 (code-scanning, Dependabot and secret-scanning; some may also be in SARIF; not an extra total).

Reporter Gate Status Critical High Medium Minor Since previous revision
Hypatia scan gating 🟢 clean 0 0 0 0 — same commit (no revision comparison)
panic-attack assail advisory 🟢 clean 0 0 0 0 — same commit (no revision comparison)
pons asinorum advisory 🟢 clean 0 0 0 0 — same commit (no revision comparison)
echidnabot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
rhodibot (RSR compliance) advisory 🟢 clean 0 0 0 0 — same commit (no revision comparison)
panicbot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
sustainabot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
glambot (presentation quality) advisory 🔵 minor 0 0 0 6 — same commit (no revision comparison)
seambot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
finishingbot (release readiness) advisory 🔴 high 0 9 7 0 — same commit (no revision comparison)
cipherbot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
accessibilitybot advisory ⚪ not applicable 0 0 0 0 — same commit (no revision comparison)
Hypatia scan: 4 finding(s)
  • 4 further finding(s) in files this change does not touch: reported, not graded (0 critical, 0 high).
panic-attack assail: 18 finding(s)
  • 18 further finding(s) in files this change does not touch: reported, not graded (0 critical, 0 high).
pons asinorum: 9 finding(s)
  • 9 further finding(s) in files this change does not touch: reported, not graded (0 critical, 0 high).
echidnabot: not_applicable — template default: enrol once the repository carries proofs and an ECHIDNA engine is configured
  • ⚪ not applicable: template default: enrol once the repository carries proofs and an ECHIDNA engine is configured
rhodibot (RSR compliance): 11 finding(s)
  • 11 further finding(s) in files this change does not touch: reported, not graded (0 critical, 10 high).
panicbot: not_applicable — panic-attack is already graded by the verdict grid's own panic-attack row, from static-analysis-gate.yml evidence; enrolling panicbot would report one scanner twice and give two rows that can disagree
  • ⚪ not applicable: panic-attack is already graded by the verdict grid's own panic-attack row, from static-analysis-gate.yml evidence; enrolling panicbot would report one scanner twice and give two rows that can disagree
sustainabot: not_applicable — reserved fleet slot; no adapter exists (gitbot-fleet bots/sustainabot/README.adoc)
  • ⚪ not applicable: reserved fleet slot; no adapter exists (gitbot-fleet bots/sustainabot/README.adoc)
glambot (presentation quality): 88 finding(s)
  • info GS-001 — Install git-seo for comprehensive SEO analysis: https://github.com/hyperpolymath/git-seo
  • info MACH-007 — ECOSYSTEM.scm not found in .machine_readable/ directory.
  • info MACH-007 — META.scm not found in .machine_readable/ directory.
  • info MACH-007 — STATE.scm not found in .machine_readable/ directory.
  • info MACH-005 — No robots.txt found. Consider adding one for crawler control.
  • info VIS-005 — docs/HYPATIA-RULE-ORDER.adoc:2 — Line 94 characters exceeds max length of 80.
  • 82 further finding(s) in files this change does not touch: reported, not graded (0 critical, 2 high).
seambot: not_applicable — template default: enrol once a seam register exists at spec/seams/seam-register.json
  • ⚪ not applicable: template default: enrol once a seam register exists at spec/seams/seam-register.json
finishingbot (release readiness): 177 finding(s)
  • high V1-DOC-ROADMAP.adoc — Required file ROADMAP.adoc not found (Project roadmap).
  • high TOOL-001 — .tool-versions file not found for asdf/mise version management.
  • high SCM-001-NEUROSYM.scm — Required SCM file NEUROSYM.scm not found (Neurosymbolic AI documentation).
  • high SCM-001-AGENTIC.scm — Required SCM file AGENTIC.scm not found (Agentic AI integration documentation).
  • high SCM-001-PLAYBOOK.scm — Required SCM file PLAYBOOK.scm not found (Operational playbooks and procedures).
  • high SCM-001-ECOSYSTEM.scm — Required SCM file ECOSYSTEM.scm not found (Project's place in the ecosystem).
  • high SCM-001-META.scm — Required SCM file META.scm not found (Meta-level information and architectural decisions).
  • high SCM-001-STATE.scm — Required SCM file STATE.scm not found (Project state and progress tracking).
  • high PH-100 — Found 127 placeholders, exceeds maximum allowed (0)
  • medium V1-COM-CONTRIBUTING.md — CONTRIBUTING.md file not found (Contribution guidelines).
  • medium V1-COM-CODE_OF_CONDUCT.md — CODE_OF_CONDUCT.md file not found (Code of conduct).
  • medium V1-SEC-001 — SECURITY.md not found for responsible disclosure.
  • medium TEST-001 — Could not determine if this is a Rust or Deno project.
  • medium REL-004 — No SECURITY.md file found
  • medium CLM-006 — docs/HYPATIA-RULE-ORDER.adoc — Documentation references non-existent file: static-analysis-gate.yml
  • medium CLM-006 — docs/HYPATIA-RULE-ORDER.adoc — Documentation references non-existent file: hypatia-scan.yml
  • 161 further finding(s) in files this change does not touch: reported, not graded (0 critical, 4 high).
cipherbot: not_applicable — template default: enrol once the repository implements cryptography
  • ⚪ not applicable: template default: enrol once the repository implements cryptography
accessibilitybot: not_applicable — template default: enrol once the repository serves HTML
  • ⚪ not applicable: template default: enrol once the repository serves HTML

Scope: static findings reported by each row's tool at the named commit. The table grades only findings in files this change touches, so the colour answers "does this change introduce anything?", not "what does the whole repository still carry?". Standing findings are counted in each accordion and in report.json; the baseline filter remains the place where acknowledged debt is recorded. The lane state is the worst GATING row; advisory rows are listed and counted but never set it. Purple, red, yellow and blue grade the worst GRADED finding present; orange is evidence missing, malformed or a scanner that did not run; grey is an explicit scope exclusion with its reason. No row is a security certification. report.json, badge.json and the raw findings are in the verdict-grid artifact on the linked run.

@hyperpolymath
hyperpolymath merged commit 09754a9 into main Nov 15, 2026
44 checks passed
@hyperpolymath
hyperpolymath deleted the claude/hypatia-pin-6693f9a branch November 15, 2026 11:22
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.

3 participants