R9 Web Push in decePub: one subscription per persona, each with its own token and registration

Settings gets "Notifications on this device" (PushEditor): personas, alerts in four groups, policy, a test
notification, after a one-time notice of what the push service learns. Each persona ticked gets its own service
worker registration (push-worker.js at push/{slot}/), so its own endpoint and keys, subscribed with its own token
(IHttpService's *As); nothing PrivaPub stores ties two personas together and the worker never reads the payload's
token. PushService follows the tokens (re-subscribing after a renewal), reconciles at every session start, turns
off before sign-out and drops deleted or suspended personas. A click opens that persona's notifications; the app
badge counts the unread ones. Exchanges now ask for the push scope.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WpVCoDeM1qUTRp4fXQdfof

Components/Settings/AccountEditor.razor

@@ -148,6 +148,7 @@
 @code {
 	[Inject] AuthService AuthService { get; set; }
 	[Inject] ConfirmService Confirm { get; set; }
+	[Inject] PushService Push { get; set; }
 
 	/// <summary>The login as PrivaPub describes it; null until read, or when it couldn't be (the email block stays empty).</summary>
 	ViewAccount account;
@@ -294,6 +295,8 @@
 			return;
 		}
 
+		// PrivaPub ended every Web Push subscription with the tokens: this browser forgets its own
+		await Push.Forget();
 		await CascadingState.SignOut();
 		Navigation.NavigateTo("login");
 	}
@@ -309,6 +312,8 @@
 			return;
 		}
 
+		// the personas' Web Push subscriptions went with them: this browser forgets its own, asking no persona gone
+		await Push.Forget();
 		await CascadingState.SignOut();
 		Navigation.NavigateTo("login");
 	}