fix(ci): repair the permissions block indentation (invalid YAML)

[hyperpolymath]

The permissions: block added by the caller-permission campaign was indented one level too deep (appended at job-child indent + 2), which makes the whole workflow file invalid YAML (mapping values are not allowed here) and stops the workflow loading at all. This dedents the block to job-key level — keeping the grants — and validates the file parses before committing.

[coderabbitai]

Understand this PR’s impact

Explore downstream dependencies and potential security impact with Blast Radius.

View 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: c4ab7b4b-444f-427f-a915-b0ab3bc89d2f

📥 Commits

Reviewing files that changed from the base of the PR and between 48d10a1 and a86691b.

📒 Files selected for processing (2)

• .github/workflows/governance.yml
• .github/workflows/secret-scanner.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: scan / gitleaks
• GitHub Check: scan / rust-secrets
• GitHub Check: scan / shell-secrets
• GitHub Check: hypatia / Hypatia Neurosymbolic Analysis
• GitHub Check: analyze (actions, none)
• GitHub Check: Validate A2ML manifests
• GitHub Check: Groove manifest check
• GitHub Check: Empty-linter (invisible characters)
• GitHub Check: analyze (javascript-typescript, none)
• GitHub Check: Validate K9 contracts

🔇 Additional comments (2)

.github/workflows/governance.yml (1)

34-37: LGTM!

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

24-27: LGTM!

---

📝 Summary

Summary by CodeRabbit

• Chores
  • Updated automated governance and security scanning workflows to apply the required access permissions correctly.
  • Improved the reliability of workflow-based checks and security reporting.

Walkthrough

The reusable governance and scan jobs now declare their required permissions at the job level. This replaces the previous nested placement under uses:.

Changes

Workflow permissions

Layer / File(s)	Summary
Correct job-level permission declarations .github/workflows/governance.yml, .github/workflows/secret-scanner.yml	Both jobs declare actions: read, contents: read, and security-events: write at the job level.

Priority: ⬇️ Low

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

Change: Bug fix

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: repairing invalid YAML permissions indentation in CI workflows.
Description check	✅ Passed	The description accurately explains the invalid YAML cause, the indentation fix, the preserved permissions, and the validation performed.
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

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checked the workflow gate
And moved permissions to the proper state
Actions read, contents read
Security events can now proceed
Clean YAML makes the hops feel great}

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

[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