Trouble getting artifact URLs

I was hoping to get the publish of system.txz working for arch and freebsd to unique urls. This way I could scale out to arm64 builds and other versions like 15.0, other distros, etc. I then wanted to make a deploy.sh script that could be used with something like curl to setup /System on an existing install, or live ISO bootstrap. I was thinking it could detect the system and install runtime requirements. So maybe we could split out have and requirements-build, and requirements-runtime. Then have the distro specific names under each so the script just does the thing. I am struggling which I have before with cirrus to get the exact publish URLs that work. I may have messed up the packaging or publish workflow parts.

Once this was all sorted I was going to update README to prioritize deploy and usage, then move the manual builds stuff down to the bottom. Then extend gershwin-documentation to cover the same things more or less with more in depth examples perhaps.

Start by tracing the existing packaging and publish workflow for system.txz, focusing on the artifact URLs for arch and FreeBSD. Define how deploy.sh should obtain artifacts, detect systems, and separate build from runtime requirements, then update README and gershwin-documentation with deploy and usage guidance.

Written by the indexing model from the issue text.