provide permissions for 3-channel checks when called from deployment

[MusicalNinjaDad]

No description provided.

[sourcery-ai]

Hey - I've left some high level feedback:

• If only the called rust-stability.yml workflow needs these permissions, consider defining them in that reusable workflow under on.workflow_call.permissions instead of at the caller, so all callers share consistent permission requirements.
• Double-check whether issues: write is strictly required for the quality-check job; if only read or no issues access is needed, reduce the permission scope accordingly to follow least-privilege principles.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- If only the called `rust-stability.yml` workflow needs these permissions, consider defining them in that reusable workflow under `on.workflow_call.permissions` instead of at the caller, so all callers share consistent permission requirements.
- Double-check whether `issues: write` is strictly required for the `quality-check` job; if only read or no issues access is needed, reduce the permission scope accordingly to follow least-privilege principles.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}