From 0d207c17f4da9ba7e7dde28f228bf63b184a3f79 Mon Sep 17 00:00:00 2001 From: Dmitrii Iurco Date: Wed, 10 Jun 2026 23:54:40 -0400 Subject: [PATCH] =?UTF-8?q?docs:=20correct=20HTTP=20account=20dispatch=20n?= =?UTF-8?q?ote=20=E2=80=94=20it=20is=20implemented=20and=20wired?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Fable 5 --- Dev-Building-Services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Dev-Building-Services.md b/Dev-Building-Services.md index 15dcada..43cfe31 100644 --- a/Dev-Building-Services.md +++ b/Dev-Building-Services.md @@ -122,7 +122,7 @@ For `"manager": "http"`, your container must implement the account management HT - `DELETE /service-api/accounts/{username}` — delete account - `GET /service-api/accounts` — list usernames -**Note:** HTTP dispatch for the `"http"` manager is not yet wired up in `AccountManager`. The reference services use named internal managers (`email_manager`, `calendar_manager`, `file_manager`). Implement the endpoint now so your service is ready when HTTP dispatch ships. +**Note:** HTTP dispatch for the `"http"` manager is implemented in `AccountManager` (`_provision_http`/`_deprovision_http`) and is invoked from `add_peer` for any installed service whose manifest sets `accounts.manager: "http"`. The reference services (email/calendar/files) use named internal managers (`email_manager`, `calendar_manager`, `file_manager`); set `manager: "http"` to own accounts in your own container via the endpoints above. ### Egress