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: 6b7e7aa7-7d57-41fa-83c5-290bb0857fe1

📥 Commits

Reviewing files that changed from the base of the PR and between 5882b4f and bac788b.

📒 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. (2)

• GitHub Check: scan / Hypatia Neurosymbolic Analysis
• GitHub Check: analyze (actions, none)

---

📝 Summary

Summary by CodeRabbit

• Chores
  • Updated workflow permissions by removing the workflow-level read access for actions.

Walkthrough

The workflow removes the explicit actions: read entry from the top-level permissions: read-all declaration.

Changes

Workflow permissions

Layer / File(s)	Summary
Remove explicit actions permission .github/workflows/workflow-linter.yml	The top-level permissions block no longer declares actions: read.

Priority: ⬇️ Low

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

Change: Bug fix

Merge Risk: ⚪ Minimal · up to bac78

The workflow permission configuration has no identified remaining merge risk.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: fixing an unparseable permissions declaration in CI. The file-count suffix is unnecessary but does not reduce clarity.
Description check	✅ Passed	The description directly explains the YAML parse error, the workflow impact, the semantic no-op, and the verification performed. It is directly 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.

---

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
The actions scope is now resigned
Read-all remains in place
With one less entry to trace
The linting path stays neat and fine}

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