docs: web comments say what the app does, not how it came to be (#6277)

Rewrites the web app's comments to rule 32. Task, milestone, rule and
spec ids are gone; regression stories are restated as the trap they
guard (public auth routes, the menu's stopPropagation, universal loads
under adapter-static, metric deltas with their margin). Flutter and
Tauri mentions now name the Android app or a native shell, operator
quotes and dates are dropped, and one library's counts no longer
appear outside test fixtures. Verified with a TypeScript-scanner token
comparison (template literals and regex literals re-scanned): only
comment text changed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

web/src/lib/serverEvents.svelte.ts

@@ -2,17 +2,17 @@ import { queryClient } from '#lib/query/client.js';
 import { qk } from '#lib/api/queries.js';
 import { user } from '#lib/auth/store.svelte.js';
 
-// Inbound server events over SSE (#968). The web client's OUTBOUND half
-// (play events) lives in player/events.svelte.ts; this is the inbound
-// listener it never had. Today it reacts to `playlist.system_rebuilt` — the
+// Inbound server events over SSE. The web client's OUTBOUND half (play
+// events) lives in player/events.svelte.ts; this is the inbound listener.
+// It reacts to `playlist.system_rebuilt` — the
 // daily 03:00 rebuild or a manual refresh — by invalidating the home +
 // system-playlist query caches so a tab left open across the rebuild stops
-// serving yesterday's snapshot (the stale-browse-view bug). Active playback
+// serving yesterday's snapshot. Active playback
 // self-heals separately on the failure path (store.handleLoadFailure); we
 // deliberately do NOT yank a playing queue here — that would interrupt a
 // mid-song listen to restart the new mix at track 0.
 
-// Monotonic rebuild counter (#980). Bumped on every playlist.system_rebuilt.
+// Monotonic rebuild counter. Bumped on every playlist.system_rebuilt.
 // An open system-playlist DETAIL page can't be invalidated in place (its id
 // rotates on rebuild — a refetch would 404), so instead it watches this
 // counter and offers a "this mix was refreshed → Refresh" affordance that
@@ -32,7 +32,7 @@ function onSystemRebuilt(): void {
   queryClient.invalidateQueries({ queryKey: qk.systemPlaylistsStatus() });
 }
 
-// A new notification for this user (M489). The frame carries no content — it
+// A new notification for this user. The frame carries no content — it
 // is a nudge — so the inbox and badge refetch rather than trusting a payload.
 function onNotificationCreated(): void {
   queryClient.invalidateQueries({ queryKey: ['notifications'] });