fix(ci): give the Security Status aggregator its own workflow file

[hyperpolymath]

What

Adds one step to the security-status job in .github/workflows/security-policy.yml: a sparse checkout of that workflow file, with persist-credentials: false.

Why

The orphan-job self-check (#850) parses .github/workflows/security-policy.yml, but the job had no checkout. So the step fails on every run:

awk: fatal: cannot open file `.github/workflows/security-policy.yml' for reading: No such file or directory
##[error]Process completed with exit code 2.

That leaves the aggregator red for the wrong reason, and the verdict step after it is skipped. The aggregator never actually consults its eight scans. This happens on main (5173ca7, 2bc2103, fd7db07) and on every PR.

Checks

• actions/checkout@v7.0.1 is already listed in actions.lock for this workflow, so the lock is unchanged.
• Ran the self-check script locally against the edited file. It reports 9 jobs, with all 8 non-aggregators named in needs:, and prints "ok".
• The new step parses with yq, and the job list is unchanged.

What to expect on this PR

Once the self-check passes, the verdict step will run. It will still report Security Status as failed on main's tree, correctly, because rust-audit and rust-deny fail on main. #929 fixes both, with lock bumps and a current-schema deny.toml. On #929's head every scan job is already green, so this change plus #929 should turn Security Status green. The same step is ported into #929.

---

Generated by Claude Code

[hyperpolymath]

Expected reds on this PR. None of them come from this change, which adds a single checkout step to security-status. All are already red on main at fd7db07.

• Governance, Hypatia scan and secret-scanner jobs die at Set up job with invalid lockfile pin for actions/checkout@3d3c42e…. main still calls the old standards pins. ci: repin standards callers to 75bd599, whose own lock GitHub accepts #929 repins them.
• Rust Dependency Audit, Rust License & Ban Check, abi-codegen-drift: red on main. ci: repin standards callers to 75bd599, whose own lock GitHub accepts #929 carries the lock bumps and a current-schema deny.toml. The Idris 2 cache key was already fixed in fix(ci): key the Idris 2 cache on the Chez Scheme version #930.
• E2E — Elixir Scanner Pipeline, Integration Tests: red on main since chore(deps): bump the actions group across 1 directory with 7 updates #926, because main's actions-lock parser rejects this repo's v0.0.3 lockfile. fix(actions-lock): accept lockfile v0.0.3 (github.com dependencies) #928 fixes that, and ci: repin standards callers to 75bd599, whose own lock GitHub accepts #929 carries it. This PR changes no Elixir code.
• Security Status will now get past its self-check and reach the verdict step. The verdict will still fail on this tree, correctly, because rust-audit and rust-deny fail here.

I'm not copying #929's repin into this PR. That would turn this one-step fix into a duplicate of #929, along with its baseline gate. Instead, this commit is already ported into #929 as 5c27a59. On #929's head every scan job feeding Security Status passes, so that is where the fix shows green.

Either merge order works:

• If ci: repin standards callers to 75bd599, whose own lock GitHub accepts #929 merges first, merging main here leaves this PR a no-op, and it can be closed.
• If this PR merges first, ci: repin standards callers to 75bd599, whose own lock GitHub accepts #929's copy no-ops.

---

Generated by Claude Code

[coderabbitai]

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 23 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

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 93f03156-d95a-4cc1-9780-f90ff8d80aa9

📥 Commits

Reviewing files that changed from the base of the PR and between fd7db07 and 71a1af9.

📒 Files selected for processing: 1

• .github/workflows/security-policy.yml

• 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

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

[chatgpt-codex-connector]

Codex Review Summary

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

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-19T16:56:51.091641Z	71a1af9	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.

[coderabbitai]

Add Carrot credits or activate Agent usage billing to use Autofix