ci(secret-scan): rename caller job key secret-scan -> scan (D243)

[hyperpolymath]

What

Rename the secret-scanner caller job key secret-scan → scan in .github/workflows/secret-scanner.yml, so the check context becomes scan / gitleaks — the context the estate Secret-Scan-Floor ruleset (D243/D244) requires. One-line change; reusable pin, triggers and permissions unchanged. actionlint output is identical before and after.

Commit created via GraphQL createCommitOnBranch (GitHub-signed, signature valid: true).

🤖 Generated with Claude Code

https://claude.ai/code/session_0136eszqrQ53Kj7aBH1D4rXK

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

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: 1e4ceb80-6e88-4535-9a2f-5d1565069ff6

📥 Commits

Reviewing files that changed from the base of the PR and between 1fe3a70 and 1c5a572.

📒 Files selected for processing (1)

• .github/workflows/secret-scanner.yml

Included review availability: This review used your included allowance. 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. (4)

• GitHub Check: semgrep-cloud-platform/scan
• GitHub Check: scan / rust-secrets
• GitHub Check: scan / gitleaks
• GitHub Check: Analyze (actions)

🔇 Additional comments (1)

.github/workflows/secret-scanner.yml (1)

18-18: LGTM!

---

📝 Summary

Summary by CodeRabbit

• Chores
  • Updated an internal automation workflow label. This is an administrative change and does not alter the app’s features or behaviour for end users.

Walkthrough

The secret scanner workflow job ID changes from secret-scan to scan. Its reusable workflow and inherited secrets configuration remain unchanged.

Changes

Secret scanner workflow

Layer / File(s)	Summary
Rename workflow job .github/workflows/secret-scanner.yml	The job ID changes from secret-scan to scan. The reusable workflow and inherited secrets configuration remain unchanged.

Priority: ⬇️ Low

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

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 1c5a5

The renamed workflow produces the intended scan / gitleaks check, with no broken internal dependencies; no actionable merge-blocking risk remains.

Architecture Summary

Architecture risk: 🔵 Low · up to 1c5a5

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

• observed — Modified behavior in .github/workflows/secret-scanner.yml: The job ID changed from secret-scan to scan.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the CI job-key rename from secret-scan to scan. It matches the main change.
Description check	✅ Passed	The description explains the job-key rename, the required check context, and the unchanged workflow settings. It is related 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.

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

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

_{A rabbit checks the scanner's name,
One short new label joins the game.
The workflow keeps its former task,
No other changes hide beneath the mask.
I nibble clover, pleased to see,
The scan now wears its name as scan.}

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