gdo in the vel's own stack, and portal v0.5.2

The mailer moves in. Portal decides what to send and publishes it on
this NATS; gdo is what hands it to a mail server, and it belongs here
rather than shared, so the vel's mail leaves on the vel's own terms. It
has no mail server of its own and relays through the host's - on kasse,
Klingenberg Bygg's postfix - which is the one thing this stack borrows
and the one line that changes if the vel ever gets a host of its own.

Also:

- portal v0.5.2, four releases on from the v0.3.36 this pinned.
- The Kanidm setup makes the onboarding service account and its token.
  The vel's desks invite neighbours, and portal needs a token to do it;
  without one every invite fails closed. It goes in
  idm_people_on_boarding, which may create a person and issue a first
  credential reset and nothing else, plus idm_people_pii_read so an
  invite finds someone who already has an account instead of making
  them a second one.
- The deploy workflow runs. It was pointed at a `tomtervel` runner
  label that has never existed, so every push queued and did nothing.
  It now runs on kasse's host runner, which is not root and may run one
  argumentless script that pulls this repo and brings the stack up.
- The hosts default to vel.klingenbergbygg.no and
  id.vel.klingenbergbygg.no, which is where this actually runs. Both
  already resolve to kasse.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

kanidm-setup.sh

@@ -36,6 +36,36 @@ $K system oauth2 update-claim-map-join $C groups array
 
 secret=$($K system oauth2 show-basic-secret $C 2>/dev/null | tail -1)
 sed -i "s|^OAUTH2_CLIENT_SECRET=.*|OAUTH2_CLIENT_SECRET=$secret|" .env portal.env
+
+# Onboarding from a desk. A committee inviting a neighbour, and any
+# state whose `grants:` makes someone a member, both go through Kanidm
+# as this service account - not as a person, and not as an admin. It is
+# in idm_people_on_boarding, which may create people and issue a first
+# credential reset and nothing else, so the token cannot touch anyone's
+# existing credentials. idm_people_pii_read lets an invite find someone
+# who already has an account by their email, and add them to the group
+# instead of making a second account for the same person.
+#
+# The token is shown once, by Kanidm, at creation. Written straight into
+# the env files here and never printed.
+SA=portal-onboarding
+if ! $K service-account get $SA >/dev/null 2>&1; then
+  $K service-account create $SA "Portal onboarding" idm_admin
+  $K group add-members idm_people_on_boarding $SA
+  $K group add-members idm_people_pii_read $SA || true
+fi
+if ! grep -q '^KANIDM_API_TOKEN=.' portal.env 2>/dev/null; then
+  token=$($K service-account api-token generate $SA "portal" --rw 2>/dev/null | tail -1)
+  if [ -n "$token" ]; then
+    grep -q '^KANIDM_API_TOKEN=' portal.env \
+      && sed -i "s|^KANIDM_API_TOKEN=.*|KANIDM_API_TOKEN=$token|" portal.env \
+      || printf 'KANIDM_API_TOKEN=%s\n' "$token" >> portal.env
+    echo "onboarding token written to portal.env"
+  else
+    echo "warning: could not generate the onboarding token - invites will fail closed until it is set"
+  fi
+fi
+
 podman compose restart portal
 echo "client $C configured; portal restarted with its secret"
 echo