adventure: tell a player what happened while they were away

The site could only reach somebody who was already looking at it. Push
existed and adventure used none of it, so the one communal event in the
game -- the Siege -- was invisible to anyone not sitting in Matrix, and a
player whose adventurer died found out whenever they next opened a tab.

Four opt-in categories, every one of them off until asked for: the Siege
(realm-wide, begins and ends), your expedition ending, your adventurer
wandering off, and a contract landing on you. Turning on news
notifications is not consent to be told about the game, so nothing here
enrolls anybody automatically.

No new wire. Every trigger is a dispatch already landing in
adventure_events, so this is Pete-side only and gogobee is untouched.

Two things it needed from storage. push_subscriptions now keeps the
Matrix localpart alongside the OIDC subject, because every ownership
join in the schema is keyed on the localpart and the sender runs on a
ticker with no session to read one from -- without it there is no way to
answer "whose adventurer is this". And the alerts carry their own
watermark, kept apart from the digest's: the two run on different clocks
and one column would let each consume the other's backlog.

The ownership join is re-read on every pass rather than trusted from the
subscription row, so an opt-out or a removal closes the channel at once.
It fails closed in both directions, and an unresolved owner can never
fall through to a broadcast -- a game alert naming somebody's adventurer,
delivered to the wrong phone, is a privacy leak dressed as a feature.

An existing subscription carries watermark 0, which read literally means
"has never been told anything" and would page every subscriber for the
whole history of the realm on the first tick after deploy. Those rows are
stamped to now and start from the next dispatch.

Verified against a running Pete with a real push service, real P-256
client keys and real encryption: the right person is notified, the wrong
one is not, a second pass is silent, and dropping the player from the
board takes the channel with it.

Claude-Session: https://claude.ai/code/session_012bxpQQJDjC1mTtLN3VVtBQ

internal/web/static/js/prefs.js

@@ -10,7 +10,13 @@
 (function () {
   // The localStorage keys we sync. The weather *cache* is deliberately excluded:
   // it's transient and per-device.
-  var SYNCED = ["pete.disabledSources.v1", "pete.weather.loc.v1", "pete-weather-off", "pete.sfx.off"];
+  // pete.advPush.v1 is read by the *server* — the adventure alert sender parses
+  // it out of the stored blob to decide who to notify — where every other key
+  // here is only ever read back by a feature script. If it stops syncing, the
+  // toggles keep working locally and no alert is ever sent, which is the kind of
+  // failure nobody reports.
+  var SYNCED = ["pete.disabledSources.v1", "pete.weather.loc.v1", "pete-weather-off", "pete.sfx.off",
+                "pete.advPush.v1"];
 
   var user = window.PETE_USER || null;
   var serverPrefs = window.PETE_PREFS || null;

internal/web/static/js/pwa.js

@@ -65,6 +65,68 @@
     });
   }
 
+  // ---- adventure alert categories -------------------------------------------
+  // Stored as a JSON string under a synced prefs key, because this is the one
+  // preference the *server* reads back: the alert sender parses the same blob to
+  // decide who to notify. Absent key means nothing enabled, on both sides.
+  var ADV_KEY = "pete.advPush.v1";
+
+  function advRead() {
+    try {
+      var raw = localStorage.getItem(ADV_KEY);
+      if (!raw) return {};
+      var v = JSON.parse(raw);
+      return v && typeof v === "object" ? v : {};
+    } catch (e) { return {}; }
+  }
+
+  function advWrite(set) {
+    try { localStorage.setItem(ADV_KEY, JSON.stringify(set)); } catch (e) {}
+    if (window.PetePrefs) window.PetePrefs.push();
+  }
+
+  // initAdvUI wires the category boxes. `on` is whether a push subscription
+  // currently exists — a category switch with no subscription behind it is wired
+  // to nothing, so the block stays hidden until there is one.
+  function initAdvUI(slot, on) {
+    var box = slot.querySelector("[data-adv-push]");
+    if (!box) return;
+    box.hidden = !on;
+    if (!on) return;
+
+    var note = box.querySelector("[data-adv-push-note]");
+    var inputs = box.querySelectorAll("[data-adv-cat]");
+    var set = advRead();
+
+    function paintNote() {
+      if (!note) return;
+      var n = 0;
+      for (var i = 0; i < inputs.length; i++) if (inputs[i].checked) n++;
+      note.textContent = n === 0
+        ? "Nothing selected. You'll only get the news digest."
+        : (n === 1 ? "1 alert type on." : n + " alert types on.");
+    }
+
+    for (var i = 0; i < inputs.length; i++) {
+      (function (el) {
+        el.checked = !!set[el.getAttribute("data-adv-cat")];
+        // This function re-runs every time the subscription state changes; bind
+        // the listener once or a toggle-off-toggle-on writes the pref twice.
+        if (!el.dataset.advBound) {
+          el.dataset.advBound = "1";
+          el.addEventListener("change", function () {
+            var cur = advRead();
+            var key = el.getAttribute("data-adv-cat");
+            if (el.checked) cur[key] = true; else delete cur[key];
+            advWrite(cur);
+            paintNote();
+          });
+        }
+      })(inputs[i]);
+    }
+    paintNote();
+  }
+
   // ---- settings-panel toggle ------------------------------------------------
   function initPushUI() {
     var slot = document.querySelector("[data-push-section]");
@@ -80,6 +142,7 @@
       btn.setAttribute("aria-pressed", on ? "true" : "false");
       btn.textContent = on ? "Notifications on" : "Turn on notifications";
       if (note && text != null) note.textContent = text;
+      initAdvUI(slot, on);
     }
 
     function refresh() {