Clarify permissions requirements for actions/upload-artifact@v6

[Copilot]

Addressed review question about whether actions/upload-artifact@v6 requires actions: write permission in the workflow configuration.

Resolution

No code changes required. The automated review comment suggesting to add actions: write permission was incorrect:

• actions/upload-artifact@v4+ uses a new backend API that does not require the actions permission scope
• The GITHUB_TOKEN is automatically provided to actions even with restrictive permissions
• Current configuration is correct: permissions: {} at workflow level with contents: read at job level

The workflow in .github/workflows/compile.yml follows security best practices with least-privilege permissions and will function correctly as-is.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}