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: cd3ba627-5c91-4e3c-8019-907acb0c77ee

📥 Commits

Reviewing files that changed from the base of the PR and between 1c29558 and cfb33ff.

📒 Files selected for processing (3)

• .github/workflows/governance.yml
• .github/workflows/hypatia-scan.yml
• .github/workflows/mirror.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. (11)

• GitHub Check: scan / shell-secrets
• GitHub Check: scan / gitleaks
• GitHub Check: scan / rust-secrets
• GitHub Check: hypatia / Hypatia Neurosymbolic Analysis
• GitHub Check: lint-workflows
• GitHub Check: analyze (actions, none)
• GitHub Check: Validate A2ML manifests
• GitHub Check: Groove manifest check
• GitHub Check: Validate K9 contracts
• GitHub Check: Empty-linter (invisible characters)
• GitHub Check: lint-workflows

🔇 Additional comments (3)

.github/workflows/governance.yml (1)

17-20: LGTM!

.github/workflows/hypatia-scan.yml (1)

20-23: LGTM!

.github/workflows/mirror.yml (1)

13-16: LGTM!

---

📝 Summary

Summary by CodeRabbit

• Bug Fixes
  • Corrected workflow permission declarations so governance, security scanning, and mirroring jobs apply their required access levels correctly.
  • Preserved existing read and write permission settings while improving workflow validation and execution reliability.

Walkthrough

The reusable workflow jobs now place their existing permissions blocks at job level. The permission values remain unchanged in all three workflow files.

Changes

Workflow permissions

Layer / File(s)	Summary
Correct job-level permissions .github/workflows/governance.yml, .github/workflows/hypatia-scan.yml, .github/workflows/mirror.yml	The three reusable workflow jobs move permissions to the job level. The values remain actions: read, contents: read, and security-events: write.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 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: fixing invalid CI workflow permissions indentation. It is concise and specific.
Description check	✅ Passed	The description accurately explains the invalid YAML indentation, the affected permissions blocks, 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 checks the workflow line
Permissions sit in place and shine
Three jobs now read the file just right
Security events gain their write
The YAML rests, neat and light}

_{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