feat(events): the public calendar, event pages and participation history (Phase 14a)

The anonymous surface an event was always for: GET /public/events,
/public/events/:slug and /public/events/series/:slug, plus
GET /player/events/history, and the four screens over them.

Four org-lead decisions taken up front: split Phase 14 into 14a (website)
and 14b (the app); add a `listed` flag rather than letting `state` mean both
schedulable and announced; put the `events` capability string in the version
block rather than publishing core as a pseudo-module; and drop "venue" from
the spec rather than adding a field nothing had ever built.

`listed` is announcement, not permission. Publishing is what makes a
definition runnable, so without a separate flag a surprise event would have
to be advertised in order to be allowed to happen. It is a column, a switch
in Phase 13's editor, and three SQL predicates -- never a filter applied
after a read, which works exactly as well until the first caller that forgets.

The public shapes are a projection, and the projection is the security
boundary: nothing is spread, so a column added to event_runs next year does
not ride out through it. The spec, health, cleanup, claims, errors and
member_key are all absent by construction.

The six public event triggers gained `eventUrl` (version 1 -> 2), carrying
?run= because the page lives at the definition's slug while every trigger is
about one occurrence. notify.event-started gained the button, at seedVersion 2.

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

server/src/model/events/eventDefinitions.db.js

@@ -11,6 +11,9 @@ const hydrate = (row) =>
   row && {
     ...row,
     spec: parseJson(row.spec, null),
+    // TINYINT(1) arrives as 0/1. Every reader of this column asks a yes/no
+    // question, and the public model's filters compare against a boolean.
+    listed: Boolean(row.listed),
   }
 
 // `current_version` is joined rather than stored: the list screen shows "v3" and
@@ -60,8 +63,8 @@ const insert = async (d) => {
   const result = await query(
     `INSERT INTO event_definitions
        (title, slug, summary, body, image_url, owner_module, series_id, series_order,
-        concurrency_key, grace_seconds, timezone, spec, created_by, updated_by)
-     VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)`,
+        concurrency_key, grace_seconds, timezone, listed, spec, created_by, updated_by)
+     VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)`,
     [
       d.title,
       d.slug,
@@ -74,6 +77,7 @@ const insert = async (d) => {
       d.concurrency_key,
       d.grace_seconds,
       d.timezone,
+      d.listed ? 1 : 0,
       JSON.stringify(d.spec),
       d.created_by,
       d.created_by,
@@ -87,7 +91,7 @@ const update = (id, d) =>
     `UPDATE event_definitions
         SET title = ?, slug = ?, summary = ?, body = ?, image_url = ?, series_id = ?,
             series_order = ?, concurrency_key = ?, grace_seconds = ?, timezone = ?,
-            spec = ?, updated_by = ?
+            listed = ?, spec = ?, updated_by = ?
       WHERE id = ?`,
     [
       d.title,
@@ -100,6 +104,7 @@ const update = (id, d) =>
       d.concurrency_key,
       d.grace_seconds,
       d.timezone,
+      d.listed ? 1 : 0,
       JSON.stringify(d.spec),
       d.updated_by,
       id,
@@ -140,20 +145,51 @@ const markReady = (id, versionId, userId) =>
  * its arc exactly as a materialised run is, and a second query to learn the name
  * of a row this one already reached would be two round trips for a join.
  */
-const findSchedulable = async () => {
+const findSchedulable = async ({ listedOnly = false } = {}) => {
   const rows = await query(
-    `SELECT d.id, d.title, d.slug, d.timezone, d.grace_seconds, d.concurrency_key,
-            d.current_version_id, d.series_id, v.spec AS version_spec,
+    `SELECT d.id, d.title, d.slug, d.summary, d.image_url, d.timezone, d.grace_seconds,
+            d.concurrency_key, d.current_version_id, d.series_id, v.spec AS version_spec,
             s.name AS series_name, s.slug AS series_slug
        FROM event_definitions d
        JOIN event_versions v ON v.id = d.current_version_id
        LEFT JOIN event_series s ON s.id = d.series_id
-      WHERE d.state = 'ready'
+      WHERE d.state = 'ready'${listedOnly ? ' AND d.listed = 1' : ''}
       ORDER BY d.id`,
   )
   return rows.map((row) => ({ ...row, version_spec: parseJson(row.version_spec, null) }))
 }
 
+/**
+ * One definition by slug, for the PUBLIC event page (Phase 14a).
+ *
+ * `ready` and `listed` are both in the WHERE rather than checked by the caller,
+ * so an unlisted event answers exactly as a nonexistent one does — a 404 that
+ * cannot be told from "no such slug". A caller that filtered afterwards would
+ * be one forgotten early-return away from publishing a draft.
+ *
+ * An ARCHIVED definition is deliberately absent too. Archiving is what delete
+ * means on the admin screen, and a page that kept answering afterwards would
+ * make the only delete this feature has do nothing an operator could see.
+ */
+const getPublicBySlug = async (slug) => {
+  const [row] = await query(
+    `${SELECT_LIST} WHERE d.slug = ? AND d.state = 'ready' AND d.listed = 1`,
+    [slug],
+  )
+  return hydrate(row)
+}
+
+/** Every listed, ready definition in one series, in the arc's own order. */
+const listPublicBySeries = async (seriesId) => {
+  const rows = await query(
+    `${SELECT_LIST}
+      WHERE d.series_id = ? AND d.state = 'ready' AND d.listed = 1
+      ORDER BY d.series_order, d.id`,
+    [seriesId],
+  )
+  return rows.map(hydrate)
+}
+
 /**
  * Archive. Never a hard delete while runs reference it (§ API surface) — and the
  * schema would refuse one anyway, because `event_runs.version_id` RESTRICTs.
@@ -166,6 +202,8 @@ module.exports = {
   list,
   getById,
   getBySlug,
+  getPublicBySlug,
+  listPublicBySeries,
   slugTaken,
   findSchedulable,
   insert,