[eniac111]

The SUSE step of the deploy wizard used a plain zypper addrepo. Such a repository has no gpgkey= line, so zypper looks for the key at rpm/repodata/repomd.xml.key, which the server never published. The metadata signature then failed with "signed with an unknown key" and the installation stopped before the package, while every later line of the pasted script failed on its own.

• SUSE: write /etc/zypp/repos.d/bor.repo with a gpgkey= line (gpgcheck=0 for unsigned development builds). Packages are accepted by the checksum in the signed metadata, the same as dnf's repo_gpgcheck=1.
• assemble-agent-repo.sh: also publish the public key as rpm/repodata/repomd.xml.key, so a plain zypper addrepo works as well.
• The generated script is one command: its lines are joined with "&& ", so a paste runs as a unit and a failing step stops it. Repository files are written with printf, one line per continuation line, and the explanations moved from comment lines to notes under the code block.
• The enrollment token goes to bor-agent --token-file on stdin, so nothing is left on disk when a later step fails.
• The docs and the static /agent/ page use the same form; troubleshooting documents the zypper symptom.