live.forgetOne server call purges every trace of a user across the framework - push
registry and sessions, presence rosters, rate-limit buckets, idempotency
cached results, dead-letter entries, aggregate k-anonymity cohorts - and
resolves only after the durable store confirms. The result is a per-surface
audit: { ok, at, rowsAffected, surfaces }. This demo
erases you (the server uses ctx.user.id, never
a wire-supplied id).
You are Spunky Noodle (ec8b4bbb) - the identity that gets erased below.
Writes three entries to an app-owned Redis log keyed by your user id and caches an idempotent RPC result keyed by you. Your presence entry and push registration already exist just from having this tab open.
The app can only count its own storage. Framework-internal surfaces are
not enumerable from app code - the authoritative audit is the surfaces
map live.forget returns in step 3.