fix(ci): repair unparseable permissions scalar (1 workflow file(s))

[hyperpolymath]

permissions: read-all followed by an indented actions: read is a YAML
parse error. The workflow never starts, so it emits no check run — a
required context silently never reports, and this repository currently looks
greener than a repaired one.

read-all already grants actions: read, so removing the stray line is a
semantic no-op. Each file was verified with a real YAML parser: it fails
yq before the change and parses after it. Every diff is exactly one deleted line.

Files changed: workflow-linter.yml

Measured estate-wide: 42 such files across 28 repositories on main, all
carrying the identical stray key. Zero overlap with the TokenPermissions sweep.

🤖 Generated with Claude Code

https://claude.ai/code/session_0178nN4Nm3neFRy5K9StZKnB

[coderabbitai]

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: f75b7444-592d-4682-8d9b-1df99acfa985

📥 Commits

Reviewing files that changed from the base of the PR and between d6cbbb2 and 1f89dfd.

📒 Files selected for processing (1)

• .github/workflows/workflow-linter.yml

💤 Files with no reviewable changes (1)

• .github/workflows/workflow-linter.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. (27)

• GitHub Check: scan / rust-secrets
• GitHub Check: scan / shell-secrets
• GitHub Check: governance / Debt ratchet
• GitHub Check: governance / Code quality + docs
• GitHub Check: governance / Exemption ratchet
• GitHub Check: governance / Trusted-base reduction policy
• GitHub Check: governance / Licence consistency
• GitHub Check: scan / gitleaks
• GitHub Check: governance / Language / package anti-pattern policy
• GitHub Check: governance / Actions lockfile verify
• GitHub Check: governance / Well-Known (RFC 9116 + RSR)
• GitHub Check: governance / Check Workflow Staleness
• GitHub Check: governance / Workflow security linter
• GitHub Check: governance / Guix packaging policy (Nix retired)
• GitHub Check: governance / Security policy checks
• GitHub Check: governance / Live Actions policy (credentialed advisory)
• GitHub Check: governance / Allowlist Preflight
• GitHub Check: lint-workflows
• GitHub Check: scan / Hypatia Neurosymbolic Analysis
• GitHub Check: analyze (actions, none)
• GitHub Check: Empty-linter (invisible characters)
• GitHub Check: Validate A2ML manifests
• GitHub Check: Groove manifest check
• GitHub Check: Detect Project Configuration
• GitHub Check: Validate K9 contracts
• GitHub Check: submit-nuget
• GitHub Check: lint-workflows

---

📝 Summary

Summary by CodeRabbit

• Chores
  • Updated automated workflow permissions to use read-only access across available scopes.
  • Standardised how workflow actions inherit permissions, improving consistency without changing application functionality.
  • No user-facing features or behaviour have changed.

Walkthrough

The workflow linter changes its top-level permissions from explicit actions: read access to read-all.

Changes

Workflow permissions

Layer / File(s)	Summary
Update workflow permission scope .github/workflows/workflow-linter.yml	The workflow replaces the explicit actions: read permission with permissions: read-all.

Priority: ⬇️ Low

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

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 1f89d

The workflow permission cleanup has no identified merge-blocking risk.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the CI fix for the unparseable permissions scalar. It is specific to the main change, despite the minor file-count wording.
Description check	✅ Passed	The description directly explains the YAML parsing error, the removed line, the semantic effect, 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 gate
Read-only permissions now set the state
The actions scope follows the rule
The linter runs with access kept cool
One small change makes the file clear}

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

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE