Release: the dev organization's registry, pushed by registry-push

The repository moved to the dev organization: images go to
gitea.dongar.net/dev/nisse-dev, pushed by the registry-push bot with the
organization's REGISTRY_TOKEN.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE

.gitea/workflows/release.yml

@@ -1,23 +1,26 @@
 name: Release
 # A published release builds the agent's image and pushes it to Gitea's
-# registry (Development Plan M1.5, X4): gitea.dongar.net/dongar/nisse-dev
+# registry (Development Plan M1.5, X4): gitea.dongar.net/dev/nisse-dev
 # tagged with the version (the release tag without its v) and latest. Cut a
 # release in Gitea (Releases → New release, tag vX.Y.Z); a tag pushed for any
 # other reason builds nothing.
 #
 # The registry needs a personal access token with write:package
-# (REGISTRY_TOKEN), never the built-in job token: Gitea's registry resolves
-# an Actions job token to an empty package scope (go-gitea/gitea#23642 and
-# others). Packages belong to the repository's owner. Never on pull_request:
-# registry credentials stay off that trigger.
+# (REGISTRY_TOKEN, an organization secret of `dev`, belonging to the
+# registry-push bot), never the built-in job token: Gitea's registry
+# resolves an Actions job token to an empty package scope (go-gitea/gitea
+# #23642 and others). Packages belong to the repository's owner, which is
+# why this repository is the `dev` organization's: the bot writes packages
+# through the org's registry-push team. Never on pull_request: registry
+# credentials stay off that trigger.
 on:
   release:
     types: [published]
 
 env:
   REGISTRY: gitea.dongar.net
-  REGISTRY_USER: dongar  # the token's account
-  IMAGE: gitea.dongar.net/dongar/nisse-dev
+  REGISTRY_USER: registry-push  # the token's account
+  IMAGE: gitea.dongar.net/dev/nisse-dev
 
 jobs:
   build-and-push: