Align kernel spec Release tags to satisfy spec entanglement check

[Copilot]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Spec Entanglement Mismatch Check failed because SPECS/kernel/kernel.spec was at Release: 2 while its entangled kernel spec set remained at Release: 1.
This change synchronizes release metadata across that entangled group so the workflow’s epoch/version/release consistency check passes.

Change Log

• Root cause alignment
  • Updated Release from 1%{?dist} to 2%{?dist} in all specs in the kernel entanglement set checked by toolkit/scripts/check_entangled_specs.py.
• Files updated
  • SPECS/kernel/kernel.spec
  • SPECS/kernel-64k/kernel-64k.spec
  • SPECS/kernel/kernel-uki.spec
  • SPECS/kernel-headers/kernel-headers.spec
  • SPECS-SIGNED/kernel-signed/kernel-signed.spec
  • SPECS-SIGNED/kernel-64k-signed/kernel-64k-signed.spec
  • SPECS-SIGNED/kernel-uki-signed/kernel-uki-signed.spec
• Representative change

-Release:        1%{?dist}
+Release:        2%{?dist}

Does this affect the toolchain?

NO

Associated issues

• N/A

Links to CVEs

• N/A

Test Methodology

• N/A

[dethoma]

Closing — the fix from commit 875a8eb has been cherry-picked into #17362
(commit 6f147b7) which is the primary PR for disabling CONFIG_RDS on
aarch64. Thanks Copilot for catching the entangled-specs release
mismatch — that's exactly the kind of cross-spec coupling that's easy
to miss when only one kernel-family spec is touched.

No further action needed on this PR.