chore(ci): cap artifact retention at 7 days - account storage quota hit 2026-07-30

[Jesssullivan]

Summary

• On 2026-07-30 the Jesssullivan account hit its GitHub Actions artifact-storage quota: QA lanes across the estate died on CreateArtifact until a manual sweep deleted 1073 old artifacts (~7.5 GB). This repo was the second-largest holder (~1.6 GB).
• actions/upload-artifact steps without retention-days sit at the account default (90 days) and accumulate; this caps them at 7 days.

11 steps capped at retention-days: 7:

• fork-release.yml - macOS dmg, remote daemon assets
• release.yml - dry-run bundle
• nightly.yml - branch nightly bundle
• test-e2e.yml - test recording
• release-linux.yml - deb, tarball, debian-baseline deb, fedora rpm, rocky rpm
• release-qcow2.yml - qcow2 images

Nothing durable is lost: every release binary here is an inter-job transfer artifact that the downstream release job downloads and attaches to the GitHub Release in the same run (gh release upload); the durable copy lives on the Release. Test lanes already carried 7-day caps (test-ssh-proxy, test-distro, test-socket, test-gpu, test-cjk, distro validation logs).

Testing

• YAML validated for every touched workflow; retention key placed to match the existing release-linux.yml convention.
• Workflow metadata only - no runtime behavior change beyond artifact expiry.

Demo Video

• n/a (CI metadata change)

Checklist

• I requested bot reviews after my latest commit