The release job feeds packages.arasaka.software itself; YoloCICD is gone

.gitea/scripts/packages.sh signs the rpm with the org secret PACKAGES_SIGNING_KEY,
publishes the deb and rpm into a new snapshot of the repository, signs its metadata and
rewrites SHA256SUMS.txt, on the nuvola runner. Tested against a copy of the live
repository with Debian 13 apt and Fedora 44 dnf.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KizzWs2WQPWN2qgE7G6r8B

README.md

@@ -50,7 +50,7 @@ Linux (deb, rpm), Windows, macOS and Android. Builds are published as releases o
 On Linux the deb and the rpm add the Arasaka package repository, packages.arasaka.software, when they are installed,
 so later versions arrive through the package manager. The rpm is signed with the repository's key; on openSUSE,
 import it first with `sudo rpm --import https://packages.arasaka.software/arasaka.asc`. The script the packages run
-is `packaging/arasaka-repository.sh`, generated by YoloCICD (`yolo repo kit`); it never calls the package manager,
+is `packaging/arasaka-repository.sh`; it never calls the package manager,
 leaves files you edited alone, and removes the repository only when no Arasaka package is left (purge or erase).
 
 ## Privacy