chore(release): Pascal opens the AUR account for ncly-bin #448

This issue is the card COR-105-T1, owned by Pascal.

Problem

The release can publish ncly-bin to the AUR only through an AUR account that holds the public half of the release key. The secret AUR_SSH_KEY holds the private half of the key nicely-release-aur since 2026-10-06. Its public half is not on om1, and nobody can compare a secret with a fingerprint. The AUR idea before #442 said that registration was closed. Nobody could check the registration page on 2026-11-03, because a bot challenge blocked it.

Goal

Pascal's AUR account holds the public half of a new release key, and AUR_SSH_KEY holds its private half. Pascal does this step, because the account publishes under his name.

Steps

1. Create an account at https://aur.archlinux.org/register.
2. Ask an agent on om1 to make a new key pair named nicely-release-aur-2026. The agent records the fingerprint of the public half in this issue.
3. Keep the private half in your password manager.

CAUTION: Keep the private half before the secret changes. If you lose it, nobody can check the key that the release uses.

4. Approve the agent's replacement of the secret AUR_SSH_KEY. The agent sets the secret from the same file, with gh secret set AUR_SSH_KEY -R pascalandy/nicely.
5. In "My Account" on the AUR, paste the public half in "SSH Public Key".
6. Tell the agent that the account is ready. The agent then sets COR-105-T1 to done in a pull request.

Examples

• Success: from om1, ssh -i <private half> aur@aur.archlinux.org help answers with the list of AUR commands, and the AUR account shows the recorded fingerprint.
• Failure: the same command answers "Permission denied".

Check

• The ssh command of the success example answers.
• The fingerprint on the AUR account is equal to the fingerprint in this issue.
• gh secret list -R pascalandy/nicely shows the date of the replacement for AUR_SSH_KEY.
• COR-105-T1 is done, and the state of COR-105 starts with Active.

by Opus-5.5 via Claude Code