2 Commits

Include renames

Author	SHA1	Message	Date
thepraandClaude Opus 5.5	3827d903a3	House rules: numbers through one formatter, no made-up server errors, and the rules fail the build ... - Every number shown on a page goes through NumbersExtensions: counts, percentages, the nerd readouts and the values written into a style. - A failure the client builds itself (offline, timeout, retries run out, an answer it can't read) is a 400 that names its kind; only a server's own 5XX passes through. - Login, sign-up, recovery and password confirmations leave autocomplete to the browser, so it can offer the saved login. - The Daisy components start with empty lists and attributes, and a decorative image still renders alt="". - Arasaka.HouseRules.Analyzers checks all of this in every build, together with PrivaPub.ClientModels. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W4YtEJrgxG12Pc39Fai8Bd	2026-11-10 01:26:39 +01:00
thepraandClaude Opus 5.5	ab17959ed4	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	2026-10-18 09:50:46 +02:00