Phase 9: application services and admin completion

Implements PLAN.md Phase 9. internal/appservice reads registration files
(appservice.config_files), matches namespaces the way Synapse does
(anchored at the start), and delivers events to each service as
transactions read from the roomserver's event stream at a cursor kept in
appservice_state. A transaction in flight is recorded, so after a restart
it is resent under the same ID; failures back off from 2s to 5m, and a
successful ping cuts the backoff short.

In the Client-Server API an as_token acts as the service's sender or, with
?user_id=, as any existing user in its namespace. Services register and
log in their users with m.login.application_service; exclusive user and
alias namespaces are refused to everybody else with M_EXCLUSIVE. Unknown
aliases and users in a namespace are asked of the service first. The
ping endpoint reports M_URL_NOT_SET, M_BAD_STATUS, M_CONNECTION_FAILED
and M_CONNECTION_TIMEOUT. Services' own requests, and their users' when
rate_limited is false, skip the rate limiter.

Users can change their password (POST /account/password) and deactivate
their account (POST /account/deactivate), both behind the password.
Deactivation revokes tokens, deletes devices, optionally erases the
profile and leaves every room through a new userapi.AccountObserver.

The admin API is complete: user detail, the admin flag, deactivation and
reactivation, password resets, devices, media quotas
(media.max_user_storage_bytes plus per-user overrides), registration
tokens with use limits and expiry (registration.require_token), server
notices (internal/servernotices, server_notices.*), an editor for the
federation allow/deny lists persisted in server_settings, a delivery view
of the application services, and an audit log of every change.

Migration 0011 adds the registration token, server notice room, media
quota, audit log and appservice cursor tables. Policy lists are now
returned sorted. The Complement entrypoint loads the registrations
Complement mounts in /complement/appservice.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

server/test/complement/README.md

@@ -44,8 +44,14 @@ The switch reaches the container through `COMPLEMENT_SHARE_ENV_PREFIX`:
 as `WARP_FEDERATION_ENABLED`.
 
 The federation set leaves out partial-state joins (MSC3706,
-`TestPartialStateJoin*`), which Warp does not implement, and anything that
-needs application services (Phase 9).
+`TestPartialStateJoin*`), which Warp does not implement.
+
+Application services arrived in Phase 9. Complement writes the
+registration file of each service a blueprint asks for into
+`/complement/appservice`, and `entrypoint.sh` hands every file there to
+`WARP_APPSERVICE_CONFIG_FILES`. The tests that use them, and the Phase 9
+account tests (password change, deactivation), are not in either set yet.
+They join once a run has shown which pass.
 
 ## The test set
 

server/test/complement/entrypoint.sh

@@ -59,6 +59,21 @@ if [ -f "$CA_DIR/ca.crt" ] && [ -f "$CA_DIR/ca.key" ]; then
 	export WARP_FEDERATION_TLS_CA_FILE="$CA_DIR/ca.crt"
 fi
 
+# Application services. Complement writes the registration file of every
+# service a blueprint asks for into /complement/appservice; Warp reads
+# them at startup like any other registration file.
+AS_DIR=/complement/appservice
+if [ -d "$AS_DIR" ]; then
+	files=""
+	for f in "$AS_DIR"/*.yaml; do
+		[ -f "$f" ] || continue
+		files="${files:+$files,}$f"
+	done
+	if [ -n "$files" ]; then
+		export WARP_APPSERVICE_CONFIG_FILES="$files"
+	fi
+fi
+
 # Complement captures the container's output, so text at debug level is the
 # most useful thing to have when a test fails.
 export WARP_LOG_LEVEL="${WARP_LOG_LEVEL:-debug}"