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

docs/Development-Plan.md

@@ -281,8 +281,8 @@ accepted once a tag's image passes the e2e suite.
   mounted at `/etc/nisse-dev/nisse-dev.yaml`, secrets as environment variables,
   keys mounted read-only. Its `test` stage carries the tests over the installed
   package, for `scripts/e2e.sh --image REF`. CI builds both on every PR;
-  `release.yml` pushes `gitea.dongar.net/dongar/nisse-dev:<tag>` and `:latest`
-  (`REGISTRY_TOKEN`).
+  `release.yml` pushes `gitea.dongar.net/dev/nisse-dev:<version>` and `:latest`
+  on a published release (`REGISTRY_TOKEN`, the `dev` organization's).
 - The live bring-up's switch to the image waits for the next live test (it needs
   its own test repository too); `bringup.sh plan` shows what it will run.