[hyperpolymath]

Summary

hyperpolymath/proven-cicd is being retired. Its commits were merged into hyperpolymath/proven-cicd-and-workflows (proven-cicd-and-workflows#95). This PR moves the 4 suite calls to the new repository before the owner deletes the old one.

All 4 move from proven-cicd@03e858b to proven-cicd-and-workflows@1fd5e63 (the merge of proven-cicd-and-workflows#94). They stay on one commit, because the proof-runner control exercises the action at the same commit as the estate caller. 03e858b is an ancestor of 1fd5e63.

Call	Change at the new commit
proof-runner-control.yml (2 steps)	proof-runner-check is unchanged.
secret-scanner.yml	The caller check also admits the new repository name. This call needs that.
main-estate-audit.yml	Gate actions are called under the new name at the same commits. New optional zig-ffi-paths input (default empty). The Zig adapter gate is pinned at 3c2d402. This repository tracks no Zig source.

docs/ESTATE-AUDIT.adoc gets a dated section for the move. The earlier run receipts in that file are not rewritten: they are records of the old pin.

actions.lock is not changed: it records no entry for these calls.

Test plan

• Secret Scanner: scan / gitleaks, rust-secrets, shell-secrets pass at the new pin.
• Estate audit: the 5 component jobs run and pass.
• Proof-runner control: the valid fixture passes and the ill-typed fixture fails as required.

---

Generated by Claude Code

[coderabbitai]

Caution

Review failed

The pull request is closed.

Summary

Summary by CodeRabbit

• Chores

  • Updated the automated estate audit, proof-runner and secret-scanning checks to use the consolidated workflow suite. Existing proof-runner test cases and their failure-handling behaviour remain unchanged.
  • The estate audit now supports an optional Zig-related path input.

• Documentation

  • Updated the audit guide with the workflow transition and current check details, including a note that this repository does not track Zig source.

Three workflow callers now reference the successor repository at a new commit. The audit documentation records the migration and describes related caller and audit configuration updates.

Changes: Workflow caller migration

Layer / File(s)	Summary
Update workflow callers and migration record .github/workflows/main-estate-audit.yml, .github/workflows/secret-scanner.yml, .github/workflows/proof-runner-control.yml, docs/ESTATE-AUDIT.adoc	The three workflow callers now reference hyperpolymath/proven-cicd-and-workflows at commit 1fd5e6371a50f0fc3687206a5adca0cdf7b39aa6. The documentation records the migration and describes associated checks and audit configuration.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Possibly related PRs

• hyperpolymath/residual-evidence-types#27: Updates the same three callers that this PR moves to the successor repository.
• hyperpolymath/residual-evidence-types#25: Updates the estate-audit caller and documents its pin, which this PR changes to the successor repository.
• hyperpolymath/residual-evidence-types#24: Introduces the estate-audit workflow pin and documentation that this PR updates.

Merge Risk: Minimal · up to f9c86

No merge-blocking issue was identified. Normal CI checks should still run.

- [ ] Autofix · 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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[chatgpt-codex-connector]

Codex Review Summary: ❌ Failed

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

Review	Status	Commit	Review trigger
📝 Code Review	❌ Failed 2026-11-10T20:02:13.354738Z We couldn’t complete this review. Comment @codex review to try again.	f9c8660	Draft marked ready

ℹ️ 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.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.