Use the server's renamed registry capability, urn:inbuxa:jmap:registry

inbuxa-server renames the identifiers that carried the upstream name (its
SPEC.md §2.4). Upstream's capability for the registry (x:) objects is now
urn:inbuxa:jmap:registry, beside the fork's own urn:inbuxa:jmap, which is
unchanged. There's no alias, so this lands with the server change and
deploys with it. The mock advertises the new name too. No user-visible
strings change.

web/src/jmap/client.ts

@@ -20,7 +20,7 @@ export const CAP = {
 } as const;
 
 /** Stalwart's own capability, which carries its `x:` registry methods. */
-export const STALWART_CAP = "urn:stalwart:jmap";
+export const STALWART_CAP = "urn:inbuxa:jmap:registry";
 
 /** INBUXA's own capability (contract C-1), on the signed-in account. */
 export const INBUXA_CAP = "urn:inbuxa:jmap";
@@ -155,7 +155,7 @@ export class JmapClient {
    * Whether the server carries a capability at all, wherever it chose to
    * advertise it.
    *
-   * Stalwart hands `urn:stalwart:jmap` out per-account rather than putting it
+   * Stalwart hands `urn:inbuxa:jmap:registry` out per-account rather than putting it
    * in the session-level `capabilities`, so `hasCapability` alone reports every
    * real 0.16 server as though it were older. Look in all three places.
    */

web/src/views/admin/__tests__/account-sheet.test.tsx

@@ -15,7 +15,7 @@ const HELPDESK = ["sysAccountGet", "sysAccountQuery", "sysAccountUpdate"];
 
 function signIn(permissions: string[], username = "[email protected]") {
   useSession.setState({
-    session: { capabilities: {}, accounts: {}, primaryAccounts: { "urn:stalwart:jmap": "self" }, username, ihasmail: { permissions } } as unknown as JmapSession,
+    session: { capabilities: {}, accounts: {}, primaryAccounts: { "urn:inbuxa:jmap:registry": "self" }, username, ihasmail: { permissions } } as unknown as JmapSession,
   });
 }