[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_387":388,"_389":390},"routes/_app.x.$handle.$name",{"_118":117,"_34":65,"_126":108,"_29":127,"_13":14,"_128":-5,"_11":129,"_130":131,"_132":133,"_134":135,"_136":137,"_22":-5,"_138":-5,"_139":-5,"_140":27,"_141":142,"_143":47,"_144":-5,"_145":-5,"_146":147},"routes/_app.x.$handle.$name.branch.$branch.version.$version.diff",{"_11":12,"_13":14,"_15":16,"_17":-5,"_18":-5},"project",{"_63":64,"_34":65,"_40":66,"_67":-5,"_68":27,"_69":70,"_71":70,"_72":73,"_74":-5,"_18":75,"_76":-5,"_77":27,"_78":-5,"_79":-5,"_80":81,"_82":83,"_84":85,"_86":87,"_88":89,"_90":-5,"_91":92,"_93":92,"_94":95,"_96":95,"_97":95,"_98":92,"_99":92,"_100":101,"_102":103,"_104":105,"_106":27},"version",128,"changes",[19,20,21],"aiChatInfo","userId",{"_22":55,"_24":56,"_26":47,"_28":27,"_29":57,"_31":57},{"_22":45,"_24":46,"_26":47,"_28":27,"_29":48,"_31":48},{"_22":23,"_24":25,"_26":27,"_28":27,"_29":30,"_31":30},"file",{"_32":33,"_34":30,"_35":36,"_37":39,"_40":41,"_42":14,"_43":44,"_26":27},"previous",{"_32":33,"_34":30,"_35":36,"_37":38},"deleted",false,"deletedHere","path","main.ts","latestPath","fileId","f0eeffb8-9a93-11f1-9bb6-1607ee4eb77e","name","fileType","http","content","// sports-today — val.town HTTP val (plusjade/sports-today, file main.ts)\n//\n// Live at: https://plusjade--f0eeffb89a9311f19bb61607ee4eb77e.web.val.run/\n//\n// That URL is derived from this file's val.town file id, NOT its path — so\n// this file must only ever be updated in place. Deleting and recreating\n// main.ts (or renaming it) mints a new id and a new URL, silently pointing\n// the iOS widget at a dead endpoint while the new one returns a healthy\n// 200. Verify `links.endpoint` still ends in f0eeffb8… after any deploy.\n//\n// Deploy process, and which files under lib/ and render/ ship alongside\n// this one: docs/valtown-brief.md.\n//\n// ---- module map ----\n//\n// lib/catalog.ts the static tables (sports, channels, teams)\n// lib/text.ts lib/color.ts lib/dates.ts domain-free pure helpers\n// lib/channels.ts lib/teams.ts lib/games.ts lib/params.ts\n// pure application logic over those tables\n// lib/config.ts pure: stored-config + per-request facts -> the query\n// string /config/resolve redirects to\n// lib/sleeper.ts lib/configStore.ts lib/push.ts the only outbound\n// I/O (Sleeper, this val's own std/sqlite state, and\n// APNs silent push, respectively)\n// render/theme.ts the palette\n// render/layout.ts render/metrics.ts the png fit math: how much fits in\n// the canvas, and how wide a string will draw\n// render/json.ts render/html.ts render targets (pure + a wrapper)\n// render/configHtml.ts pure: the helper's config-picker HTML\n// render/png-tree.ts pure: slate -> satori element tree\n// render/png.ts impure: wasm, fonts, satori, resvg\n//\n// Everything except lib/sleeper.ts, lib/configStore.ts, lib/push.ts and\n// render/png.ts is pure and covered by tests/ under bin/ci; those four do\n// real I/O (Sleeper, this val's own sqlite storage, APNs, and wasm/font\n// loading, respectively) and are covered by hitting the endpoint instead.\n//\n// ---- erasable TypeScript, and the one rule that bites ----\n//\n// bin/ci runs the tests under `node --experimental-strip-types`, which\n// deletes type syntax without understanding it. Keep every file to erasable\n// TypeScript (type annotations and type aliases only — no enums, namespaces\n// or parameter properties), and **import every type with the `type`\n// modifier**: `import { type Game, transformScores }`. A plain\n// `import { Game }` survives stripping as a runtime import and dies with\n// \"does not provide an export named 'Game'\" — including when the module\n// also exports real values. Deno is more forgiving, so this fails in CI\n// rather than on the val. (This file itself is never imported by a test —\n// there's no main.test.ts — so its `npm:hono` import never reaches the\n// strip-types runner. Don't let that change: if a test ever imports\n// main.ts, that specifier breaks bin/ci.)\n//\n// ---- / — the stateless data route (unchanged) ----\n//\n// Usage:\n// ?day=today|tomorrow|next (default: next; anything else is dropped into\n// `effective.rejected` on json and falls back to\n// next, same drift-echo as sports[]/teams[]/tz.\n// Alpha-stage relaxation (2026-08-26): every value\n// scans the same 3-day window — in parallel, one\n// /scores call per date, never serial — and\n// returns the earliest date in it with a\n// qualifying game. `today`/`tomorrow` only move\n// where the window starts (today = the client's\n// local today, tomorrow = +1 day; `next` starts at\n// the same place `today` does, so the two are\n// functionally identical); they no longer mean an\n// exact single date. A live-right-now favorite\n// still wins outright whenever it falls in the\n// window. No date in the window qualifies -> the\n// same empty-slate render a quiet day always had.\n// See docs/widget-next-up-plan.md for why this is\n// bounded rather than a real schedule lookup.)\n// ?format=html|json|png (default: html)\n// ?w=&h= (png only, ignored by json — default 329x155, an\n// iOS \"medium\" widget-ish size)\n// ?sports[]=nfl|wnba|mlb|nba (repeated; default: all four)\n// ?teams[]=sparks|fever|dodgers|... (repeated; see TEAMS in lib/catalog.ts)\n// ?tz=-25200 (seconds east of GMT, e.g. iOS's\n// TimeZone.current.secondsFromGMT();\n// default: Pacific's live offset. What\n// `day` resolves against and what game\n// times render in — see lib/dates.ts)\n// ?hideCompleted=1 (format=json only; omits items whose\n// status is final instead of leaving\n// them in the list captioned END —\n// the intraday-vs-day-granularity\n// personalization, lib/config.ts's\n// Personalization.intradayFilter.\n// Never set by hand: /config/resolve\n// derives it from the stored config\n// and bakes it into the redirect.)\n//\n// teams[] wins: any valid team switches to team mode, where sports[] is\n// ignored and the fetch list is derived from the selected teams. Unknown\n// values are dropped, never fatal — a 4xx renders as a broken image in\n// WidgetKit — and echoed back in `effective` (json) plus a \"! ignored:\" line\n// on the png, so a typo in the iOS repo is visible instead of silent.\n//\n// format=json is the SwiftUI widget's real data contract (schemaVersion 2,\n// mirrors the Codable types at Shared/WidgetPayload.swift in the iOS repo,\n// dateDecodingStrategy = .secondsSince1970), not a debug tool. It's a *view*\n// contract: {schemaVersion, eyebrow, items[]} where the server has already\n// decided the display text (mainText/subText/caption) — no away/home/score\n// object, no raw team codes. The old sport-grouped/raw-code drift echo\n// survives as `x-effective-*` response headers instead of a body field —\n// see render/json.ts's header for why it moved out of the body.\n//\n// png shows as many games as fit legibly in the requested canvas, and\n// reports the rest as a \"+N more\" line rather than rendering them too small\n// to read (or, as it did before, overflowing the canvas and clipping them\n// away silently). Widen or heighten the canvas to see more games.\n//\n// ---- /config/* — the stateful config layer (docs/widget-config-plan.md) ----\n//\n// A helper (parent/caretaker) sets favorite teams/sports from a browser;\n// the receiver (widget) never sees a picker, only its own device id.\n//\n// GET /config/new blank picker form\n// POST /config/new creates a config from the submitted\n// sports[]/teams[], redirects to /config/:id\n// GET /config/:id view/edit that config — the URL itself is\n// the capability token; there are no\n// accounts, so \"bookmark this link\" is the\n// only way back in\n// POST /config/:id saves edited sports[]/teams[]\n// GET /config/:id/personalization presentation settings — currently\n// just the intraday-vs-day completed-game\n// filter; stored separately from sports/\n// teams (its own JSON column) since it's a\n// different question (\"how to show it\" vs\n// \"what to show\")\n// POST /config/:id/personalization saves that\n// GET /config/:id/pair offers code-based pairing plus a select\n// for reassigning an existing device\n// POST /config/:id/pair reassigns the selected existing device\n// to this config\n// POST /config/:id/code mints a short, reusable-until-expiry\n// pairing code for that config\n// GET /config/:id/preview renders what /config/resolve would\n// currently hand the widget for this\n// config — runs the same live path as `/`,\n// not a stored snapshot\n// POST /config/:id/devices/:deviceId sets a human-friendly name (\"dad\",\n// \"mom\") on a device already paired to that\n// config — for the configurator's own\n// benefit telling devices apart; never read\n// by /config/resolve or the app\n// POST /pair {code, device} JSON body from the app;\n// binds device -> config\n// GET /config/resolve ?device=&d=x&tz= — looks up\n// the device's config and 302s to `/` with\n// format=json baked in (this route has no\n// format= param at all: its one consumer is\n// the native json timeline provider) and\n// w=/h= parsed from d=. cache-control:\n// no-store, since this URL is constant per\n// device while its target can change.\n//\n// Only sports[]/teams[] are stored — day/tz/w/h/format stay live per-request\n// facts, never helper preferences (see the plan doc's rationale). Submitted\n// sports/teams are filtered against lib/catalog.ts's SPORTS/TEAMS before\n// storage, but that's a defensive filter, not the real validator: the actual\n// safety net is that /config/resolve's redirect lands back on `/`, where\n// resolveParams validates exactly as it does for any other caller.\n\nimport { Hono } from \"npm:hono\";\nimport { SPORTS, TEAMS } from \"./lib/catalog.ts\";\nimport {\n buildResolvedUrl,\n DEFAULT_PERSONALIZATION,\n type StoredConfig,\n} from \"./lib/config.ts\";\nimport {\n createConfig,\n createPairingCode,\n generateConfigName,\n getConfig,\n getDeviceStatus,\n getPersonalization,\n linkExistingDevice,\n listAllConfigs,\n listDevicesForConfig,\n listExpiredPairingCodes,\n listLinkableDevices,\n pairDevice,\n renameConfig,\n renameDevice,\n resolveDevice,\n saveDeviceToken,\n updateConfig,\n updatePersonalization,\n} from \"./lib/configStore.ts\";\nimport {\n formatDateLabel,\n resolveClientOffsetSeconds,\n windowDatesFor,\n} from \"./lib/dates.ts\";\nimport { pickNextSlate } from \"./lib/games.ts\";\nimport { resolveParams } from \"./lib/params.ts\";\nimport { notifyConfigDevices } from \"./lib/push.ts\";\nimport { fetchScores } from \"./lib/sleeper.ts\";\nimport { renderHtml } from \"./render/html.ts\";\nimport { renderJson } from \"./render/json.ts\";\nimport { renderPng } from \"./render/png.ts\";\nimport {\n configDevicesDocument,\n configIndexDocument,\n configNewDocument,\n configPairDocument,\n configPersonalizationDocument,\n configPreviewDocument,\n type ConfigPreviewItem,\n configSettingsDocument,\n} from \"./render/configHtml.ts\";\nimport { backgroundForHue, randomHue } from \"./render/theme.ts\";\n\nasync function gamesHandler(req: Request): Promise {\n const url = new URL(req.url);\n const dayParam = url.searchParams.get(\"day\");\n // \"next\" is the default — an omitted `day` (the common case, since it's\n // the only value that needs no explicit widget config) gets the\n // nearest-upcoming-game scan starting today. `today`/`tomorrow` are still\n // opt-in exact matches for which value gets echoed/labeled, but as of the\n // 2026-08-26 relaxation they only move where the scan starts (see\n // windowDatesFor) — anything else, including an absent param, resolves to\n // \"next\", which starts at the same place \"today\" does.\n const day = dayParam === \"today\"\n ? \"today\"\n : dayParam === \"tomorrow\"\n ? \"tomorrow\"\n : \"next\";\n const format = url.searchParams.get(\"format\") ?? \"html\";\n\n // Repeated params (`?teams[]=sparks&teams[]=lakers`), matching Sleeper's\n // own convention rather than a comma-joined list.\n const resolved = resolveParams(\n url.searchParams.getAll(\"sports[]\"),\n url.searchParams.getAll(\"teams[]\"),\n );\n\n // Same silent-coercion trap sports[]/teams[]/tz already guard against: an\n // unrecognized `day` was falling through to a default with nothing echoing\n // it. The ios-client spec names a bad `day` as *the* malformed-request\n // example, so it gets the same rejected-echo treatment as everything else.\n // An absent `day` is not an error — it's the new default — so only a\n // present-but-unrecognized value lands in `rejected`.\n if (\n dayParam !== null && dayParam !== \"today\" && dayParam !== \"tomorrow\" &&\n dayParam !== \"next\"\n ) {\n resolved.rejected.push(`day:${dayParam}`);\n }\n\n // `?tz=` — seconds east of GMT, e.g. iOS's own\n // TimeZone.current.secondsFromGMT() — is what `today`/`tomorrow` resolve\n // against and what game times render in. Already has DST folded in by\n // whoever sent it, so no zone table lookup happens on this side. Defaults\n // to Pacific's live offset. An unrecognised value falls back to that\n // default and joins `rejected` rather than erroring, same drift-echo\n // `resolveParams` uses for sports[]/teams[].\n const { offsetSeconds: clientOffsetSeconds, rejected: rejectedTz } =\n resolveClientOffsetSeconds(\n url.searchParams.get(\"tz\"),\n );\n if (rejectedTz) resolved.rejected.push(rejectedTz);\n\n // Every `day` value scans the same 3-day window now, just anchored at a\n // different start date — see windowDatesFor for what \"today\"/\"tomorrow\"\n // mean post-relaxation.\n const dates = windowDatesFor(day, clientOffsetSeconds);\n // One /scores round trip per candidate date, all in flight at once — not\n // scanned serially, and not the undocumented full-season dumps Sleeper\n // also exposes (up to 14MB for mlb's daily slate, measured live). See\n // docs/widget-next-up-plan.md.\n const gamesByDate = await Promise.all(\n dates.map((d) => fetchScores(d, resolved.sports)),\n );\n const picked = pickNextSlate(\n dates,\n gamesByDate,\n resolved.sports,\n resolved.teams,\n );\n\n // `resolvedDate` is what the json contract echoes in `x-effective-date`;\n // `date` is what render/png and render/html use for card copy, which\n // always needs a concrete date even when nothing was found. They only\n // diverge when the window is exhausted: `resolvedDate` goes null (nothing\n // in the window qualified — an honest \"not found\", distinct from a real\n // date with zero games), while `date` falls back to the window's first\n // (start) date so the empty-state render still has something to anchor\n // its label to.\n const date = picked?.date ?? dates[0];\n const bySport = picked?.bySport ?? [];\n const resolvedDate = picked?.date ?? null;\n\n // See buildResolvedUrl (lib/config.ts) for who sets this and why it's\n // never a value a caller would type by hand.\n const hideCompleted = url.searchParams.get(\"hideCompleted\") === \"1\";\n\n if (format === \"json\") {\n return renderJson(\n bySport,\n day,\n resolved,\n clientOffsetSeconds,\n resolvedDate,\n hideCompleted,\n );\n }\n if (format === \"png\") {\n return renderPng({\n bySport,\n dateLabel: formatDateLabel(date, day),\n width: Number(url.searchParams.get(\"w\")) || 329,\n height: Number(url.searchParams.get(\"h\")) || 155,\n // The randomness lives here, at the edge, so the tree stays pure.\n background: backgroundForHue(randomHue()),\n rejected: resolved.rejected,\n clientOffsetSeconds,\n });\n }\n return renderHtml(bySport, day, clientOffsetSeconds);\n}\n\n// Repeated checkbox values (`sports[]`/`teams[]`) survive Hono's\n// `parseBody({ all: true })` as an array; a single one comes back as a bare\n// string, and none at all comes back undefined. Normalizing here is what\n// lets the route handlers treat all three cases the same way.\nfunction asArray(value: unknown): string[] {\n if (Array.isArray(value)) {\n return value.filter((v): v is string => typeof v === \"string\");\n }\n if (typeof value === \"string\") return [value];\n return [];\n}\n\nfunction filterKnown(values: string[], allowed: string[]): string[] {\n return values.filter((v) => allowed.includes(v));\n}\n\nconst TEAM_SLUGS = Object.keys(TEAMS);\n\nconst app = new Hono();\n\napp.get(\"/\", (c) => gamesHandler(c.req.raw));\n\n// Prototype-stage only, no auth: every config row, linked by real id. See\n// render/configHtml.ts's configIndexDocument header for why that's an\n// accepted bypass here and not a pattern to repeat once /config needs\n// real access control.\napp.get(\"/config\", async (c) => {\n const configs = await listAllConfigs();\n return c.html(configIndexDocument(configs));\n});\n\n// Generated here, not inside createConfig, so the configurator sees the\n// default name before the row exists and can change or clear it in the\n// same submit — see lib/configStore.ts's createConfig header.\napp.get(\"/config/new\", (c) => {\n return c.html(\n configNewDocument({\n formAction: \"/config/new\",\n config: { sports: [], teams: [] },\n name: generateConfigName(),\n }),\n );\n});\n\napp.post(\"/config/new\", async (c) => {\n const body = await c.req.parseBody({ all: true });\n const config = {\n sports: filterKnown(asArray(body[\"sports[]\"]), SPORTS),\n teams: filterKnown(asArray(body[\"teams[]\"]), TEAM_SLUGS),\n };\n const name = typeof body[\"name\"] === \"string\"\n ? body[\"name\"].trim() || null\n : null;\n const { id } = await createConfig(config, name);\n return c.redirect(`/config/${id}`);\n});\n\n// A device that's never paired (a pre-config install, or one whose pairing\n// row got wiped — see lib/configStore.ts's device_configs table) has no\n// StoredConfig at all, and buildResolvedUrl's own \"empty means all sports\"\n// rule would otherwise dump the entire slate on it. That rule is correct for\n// an actually-empty *config* (a helper who unchecked everything on purpose);\n// it's wrong as the fallback for *no config*, which this route is the only\n// place that distinguishes. Hard-coding the pre-config-era default here,\n// rather than writing a real \"default\" config row via lib/configStore.ts,\n// keeps every other layer's contract exactly as-is: getConfig/resolveDevice\n// still return null for \"nothing on file\", buildResolvedUrl still treats an\n// empty StoredConfig as \"all sports\", and a paired device with a genuinely\n// empty config still gets that. This is purely what an unpaired redirect\n// carries.\nconst LEGACY_DEFAULT_CONFIG: StoredConfig = {\n sports: [],\n teams: [\"fever\", \"sparks\", \"dodgers\"],\n};\n\n// Must be registered before /config/:id below — \"resolve\" would otherwise\n// match that route's :id param and 404 out of getConfig(\"resolve\"), which is\n// the widget's only data path silently going dead.\napp.get(\"/config/resolve\", async (c) => {\n const url = new URL(c.req.url);\n const deviceId = url.searchParams.get(\"device\");\n const stored = deviceId ? await resolveDevice(deviceId) : null;\n const target = buildResolvedUrl(\n stored ?? LEGACY_DEFAULT_CONFIG,\n stored?.personalization ?? DEFAULT_PERSONALIZATION,\n {\n d: url.searchParams.get(\"d\"),\n tz: url.searchParams.get(\"tz\"),\n },\n );\n // Response.redirect is broken on Val Town — a plain 302 Response with an\n // explicit Location header is the documented workaround. cache-control is\n // explicit too: unlike `/`, this URL is constant per device while its\n // target can silently change underneath it, so nothing here should be\n // cached at any layer.\n return new Response(null, {\n status: 302,\n headers: { Location: target, \"cache-control\": \"no-store\" },\n });\n});\n\n// Shared across every /config/:id render below — pulled out so the four\n// handlers that redraw this page can't drift from each other on how a\n// device's rename form gets its action URL.\nfunction deviceActionPath(id: string): (deviceId: string) => string {\n return (deviceId) => `/config/${id}/devices/${encodeURIComponent(deviceId)}`;\n}\n\n// The settings sub-route — just the sports/teams form. Device list and\n// pairing live at their own routes below, reached via the shared top nav\n// (render/configHtml.ts's configNav) rather than being inline here.\napp.get(\"/config/:id\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n return c.html(\n configSettingsDocument({\n id,\n formAction: `/config/${id}`,\n config,\n name: config.name,\n }),\n );\n});\n\napp.post(\"/config/:id\", async (c) => {\n const id = c.req.param(\"id\");\n const existing = await getConfig(id);\n if (!existing) return c.text(\"Not found\", 404);\n\n const body = await c.req.parseBody({ all: true });\n const config = {\n sports: filterKnown(asArray(body[\"sports[]\"]), SPORTS),\n teams: filterKnown(asArray(body[\"teams[]\"]), TEAM_SLUGS),\n };\n const name = typeof body[\"name\"] === \"string\" ? body[\"name\"] : \"\";\n await updateConfig(id, config);\n await renameConfig(id, name);\n // Best-effort: a push failure (missing APNs credentials, a dead token,\n // Apple being down) must never break saving the config itself, so this\n // is swallowed rather than awaited into the response's success path.\n await notifyConfigDevices(id).catch(() => undefined);\n return c.html(\n configSettingsDocument({\n id,\n formAction: `/config/${id}`,\n config,\n name: name.trim() || null,\n saved: true,\n }),\n );\n});\n\n// The presentation-settings sub-route — separate from Settings above (see\n// render/configHtml.ts's configPersonalizationDocument header) and from\n// buildResolvedUrl's Personalization param that this eventually feeds.\napp.get(\"/config/:id/personalization\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n const personalization = await getPersonalization(id);\n return c.html(\n configPersonalizationDocument({\n id,\n formAction: `/config/${id}/personalization`,\n personalization,\n }),\n );\n});\n\napp.post(\"/config/:id/personalization\", async (c) => {\n const id = c.req.param(\"id\");\n const existing = await getConfig(id);\n if (!existing) return c.text(\"Not found\", 404);\n\n const body = await c.req.parseBody({ all: true });\n const personalization = {\n intradayFilter: body[\"intradayFilter\"] === \"intraday\",\n };\n await updatePersonalization(id, personalization);\n // Same best-effort push as Settings' save: this changes what the widget\n // shows just as much as sports/teams does.\n await notifyConfigDevices(id).catch(() => undefined);\n return c.html(\n configPersonalizationDocument({\n id,\n formAction: `/config/${id}/personalization`,\n personalization,\n saved: true,\n }),\n );\n});\n\napp.get(\"/config/:id/devices\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n const devices = await listDevicesForConfig(id);\n return c.html(\n configDevicesDocument({\n id,\n devices,\n deviceActionPath: deviceActionPath(id),\n }),\n );\n});\n\napp.get(\"/config/:id/pair\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n const [expiredCodes, devices] = await Promise.all([\n listExpiredPairingCodes(id),\n listLinkableDevices(id),\n ]);\n return c.html(\n configPairDocument({\n id,\n codeActionPath: `/config/${id}/code`,\n linkActionPath: `/config/${id}/pair`,\n devices,\n expiredCodes,\n linked: c.req.query(\"linked\") === \"1\",\n }),\n );\n});\n\napp.post(\"/config/:id/pair\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n\n const body = await c.req.parseBody();\n const deviceId = String(body.deviceId ?? \"\").trim();\n if (!deviceId) return c.text(\"Choose a device\", 400);\n\n const linked = await linkExistingDevice(id, deviceId);\n if (!linked) return c.text(\"Device not available\", 422);\n return c.redirect(`/config/${id}/pair?linked=1`);\n});\n\napp.post(\"/config/:id/code\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n\n const pairing = await createPairingCode(id);\n const [expiredCodes, devices] = await Promise.all([\n listExpiredPairingCodes(id),\n listLinkableDevices(id),\n ]);\n return c.html(\n configPairDocument({\n id,\n codeActionPath: `/config/${id}/code`,\n linkActionPath: `/config/${id}/pair`,\n devices,\n pairing,\n expiredCodes,\n }),\n );\n});\n\n// Runs this config through the exact same live path `/config/resolve`\n// would redirect a device to — buildResolvedUrl gives the query string,\n// gamesHandler is the same function app.get(\"/\", ...) calls below, format\n// is always \"json\" per buildResolvedUrl — rather than reimplementing\n// slate-picking or caching a snapshot that could drift from what the\n// widget actually sees. That means a real Sleeper round trip on every\n// load, same as `/` itself; a failure there (network, Sleeper down) is\n// caught and shown as this page's own error state instead of a 500.\napp.get(\"/config/:id/preview\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n\n try {\n const personalization = await getPersonalization(id);\n const target = buildResolvedUrl(config, personalization);\n const response = await gamesHandler(\n new Request(new URL(target, c.req.url)),\n );\n const payload = (await response.json()) as { items: ConfigPreviewItem[] };\n return c.html(\n configPreviewDocument({\n id,\n ok: true,\n items: payload.items,\n rawJson: JSON.stringify(payload, null, 2),\n }),\n );\n } catch (err) {\n return c.html(\n configPreviewDocument({\n id,\n ok: false,\n error: err instanceof Error ? err.message : String(err),\n }),\n );\n }\n});\n\n// The configurator naming a device from the /config/:id/devices page —\n// \"dad\"/\"mom\"/etc, so they can tell paired devices apart. Redirects back\n// (PRG) rather than re-rendering directly so a page refresh after saving\n// doesn't re-post — back to the devices sub-route now, not the settings\n// page that used to own this section.\napp.post(\"/config/:id/devices/:deviceId\", async (c) => {\n const id = c.req.param(\"id\");\n const deviceId = c.req.param(\"deviceId\");\n const body = await c.req.parseBody({ all: true });\n const name = typeof body[\"name\"] === \"string\" ? body[\"name\"] : \"\";\n await renameDevice(deviceId, name);\n return c.redirect(`/config/${id}/devices`);\n});\n\n// The receiver's half of pairing — an ordinary JSON request from app code,\n// not the image-serving path, so a real 4xx here is fine (the \"never 4xx\"\n// rule in this file is specifically about a broken image in WidgetKit).\napp.post(\"/pair\", async (c) => {\n let body: unknown;\n try {\n body = await c.req.json();\n } catch {\n return c.json({ ok: false }, 400);\n }\n const { code, device } = (body ?? {}) as { code?: unknown; device?: unknown };\n if (typeof code !== \"string\" || typeof device !== \"string\") {\n return c.json({ ok: false }, 400);\n }\n\n const result = await pairDevice(code, device);\n if (result.ok) return c.json(result, 200);\n if (result.reason === \"expired\") {\n return c.json({ ok: false, message: \"expired\" }, 422);\n }\n return c.json({ ok: false }, 404);\n});\n\n// AppDelegate.swift uploads its APNs token here on every\n// didRegisterForRemoteNotificationsWithDeviceToken — unconditionally, not\n// just once, since tokens rotate. Independent of /pair on purpose: see the\n// device_tokens table comment in lib/configStore.ts.\napp.post(\"/device/token\", async (c) => {\n let body: unknown;\n try {\n body = await c.req.json();\n } catch {\n return c.json({ ok: false }, 400);\n }\n const { device, token } = (body ?? {}) as {\n device?: unknown;\n token?: unknown;\n };\n if (typeof device !== \"string\" || typeof token !== \"string\") {\n return c.json({ ok: false }, 400);\n }\n\n await saveDeviceToken(device, token);\n return c.json({ ok: true });\n});\n\n// Prototype-level diagnostics for the app's paired screen — not part of the\n// receiver's real data path (that's /config/resolve). Never errors past 200:\n// an unpaired or unknown device id just gets { paired: false }, same\n// never-fail posture as the rest of this val's device-facing routes.\n//\n// KNOWN GAP (2026-08-28): this route 404s on jade.beer (the custom domain)\n// while working on the val.run URL, even after redeploy and even nested\n// under /config/* — every other route works on both, so whatever's stale is\n// on the domain side, not a Hono routing issue in this file. Whoever owns\n// jade.beer's setup needs to look at it; the iOS client hits val.run\n// directly for this one call in the meantime.\napp.get(\"/config/status/:deviceId\", async (c) => {\n const deviceId = c.req.param(\"deviceId\");\n const status = await getDeviceStatus(deviceId);\n if (!status) return c.json({ deviceId, paired: false });\n return c.json({\n deviceId,\n paired: true,\n configId: status.configId,\n name: status.name,\n sports: status.sports,\n teams: status.teams,\n });\n});\n\napp.onError((err) => Promise.reject(err));\n\nexport default app.fetch;","// sports-today — val.town HTTP val (plusjade/sports-today, file main.ts)\n//\n// Live at: https://plusjade--f0eeffb89a9311f19bb61607ee4eb77e.web.val.run/\n//\n// That URL is derived from this file's val.town file id, NOT its path — so\n// this file must only ever be updated in place. Deleting and recreating\n// main.ts (or renaming it) mints a new id and a new URL, silently pointing\n// the iOS widget at a dead endpoint while the new one returns a healthy\n// 200. Verify `links.endpoint` still ends in f0eeffb8… after any deploy.\n//\n// Deploy process, and which files under lib/ and render/ ship alongside\n// this one: docs/valtown-brief.md.\n//\n// ---- module map ----\n//\n// lib/catalog.ts the static tables (sports, channels, teams)\n// lib/text.ts lib/color.ts lib/dates.ts domain-free pure helpers\n// lib/channels.ts lib/teams.ts lib/games.ts lib/params.ts\n// pure application logic over those tables\n// lib/config.ts pure: stored-config + per-request facts -> the query\n// string /config/resolve redirects to\n// lib/sleeper.ts lib/configStore.ts lib/push.ts the only outbound\n// I/O (Sleeper, this val's own std/sqlite state, and\n// APNs silent push, respectively)\n// render/theme.ts the palette\n// render/layout.ts render/metrics.ts the png fit math: how much fits in\n// the canvas, and how wide a string will draw\n// render/json.ts render/html.ts render targets (pure + a wrapper)\n// render/configHtml.ts pure: the helper's config-picker HTML\n// render/png-tree.ts pure: slate -> satori element tree\n// render/png.ts impure: wasm, fonts, satori, resvg\n//\n// Everything except lib/sleeper.ts, lib/configStore.ts, lib/push.ts and\n// render/png.ts is pure and covered by tests/ under bin/ci; those four do\n// real I/O (Sleeper, this val's own sqlite storage, APNs, and wasm/font\n// loading, respectively) and are covered by hitting the endpoint instead.\n//\n// ---- erasable TypeScript, and the one rule that bites ----\n//\n// bin/ci runs the tests under `node --experimental-strip-types`, which\n// deletes type syntax without understanding it. Keep every file to erasable\n// TypeScript (type annotations and type aliases only — no enums, namespaces\n// or parameter properties), and **import every type with the `type`\n// modifier**: `import { type Game, transformScores }`. A plain\n// `import { Game }` survives stripping as a runtime import and dies with\n// \"does not provide an export named 'Game'\" — including when the module\n// also exports real values. Deno is more forgiving, so this fails in CI\n// rather than on the val. (This file itself is never imported by a test —\n// there's no main.test.ts — so its `npm:hono` import never reaches the\n// strip-types runner. Don't let that change: if a test ever imports\n// main.ts, that specifier breaks bin/ci.)\n//\n// ---- / — the stateless data route (unchanged) ----\n//\n// Usage:\n// ?day=today|tomorrow|next (default: next; anything else is dropped into\n// `effective.rejected` on json and falls back to\n// next, same drift-echo as sports[]/teams[]/tz.\n// Alpha-stage relaxation (2026-08-26): every value\n// scans the same 3-day window — in parallel, one\n// /scores call per date, never serial — and\n// returns the earliest date in it with a\n// qualifying game. `today`/`tomorrow` only move\n// where the window starts (today = the client's\n// local today, tomorrow = +1 day; `next` starts at\n// the same place `today` does, so the two are\n// functionally identical); they no longer mean an\n// exact single date. A live-right-now favorite\n// still wins outright whenever it falls in the\n// window. No date in the window qualifies -> the\n// same empty-slate render a quiet day always had.\n// See docs/widget-next-up-plan.md for why this is\n// bounded rather than a real schedule lookup.)\n// ?format=html|json|png (default: html)\n// ?w=&h= (png only, ignored by json — default 329x155, an\n// iOS \"medium\" widget-ish size)\n// ?sports[]=nfl|wnba|mlb|nba (repeated; default: all four)\n// ?teams[]=sparks|fever|dodgers|... (repeated; see TEAMS in lib/catalog.ts)\n// ?tz=-25200 (seconds east of GMT, e.g. iOS's\n// TimeZone.current.secondsFromGMT();\n// default: Pacific's live offset. What\n// `day` resolves against and what game\n// times render in — see lib/dates.ts)\n// ?hideCompleted=1 (format=json only; omits items whose\n// status is final instead of leaving\n// them in the list captioned END —\n// the intraday-vs-day-granularity\n// personalization, lib/config.ts's\n// Personalization.intradayFilter.\n// Never set by hand: /config/resolve\n// derives it from the stored config\n// and bakes it into the redirect.)\n//\n// teams[] wins: any valid team switches to team mode, where sports[] is\n// ignored and the fetch list is derived from the selected teams. Unknown\n// values are dropped, never fatal — a 4xx renders as a broken image in\n// WidgetKit — and echoed back in `effective` (json) plus a \"! ignored:\" line\n// on the png, so a typo in the iOS repo is visible instead of silent.\n//\n// format=json is the SwiftUI widget's real data contract (schemaVersion 2,\n// mirrors the Codable types at Shared/WidgetPayload.swift in the iOS repo,\n// dateDecodingStrategy = .secondsSince1970), not a debug tool. It's a *view*\n// contract: {schemaVersion, eyebrow, items[]} where the server has already\n// decided the display text (mainText/subText/caption) — no away/home/score\n// object, no raw team codes. The old sport-grouped/raw-code drift echo\n// survives as `x-effective-*` response headers instead of a body field —\n// see render/json.ts's header for why it moved out of the body.\n//\n// png shows as many games as fit legibly in the requested canvas, and\n// reports the rest as a \"+N more\" line rather than rendering them too small\n// to read (or, as it did before, overflowing the canvas and clipping them\n// away silently). Widen or heighten the canvas to see more games.\n//\n// ---- /config/* — the stateful config layer (docs/widget-config-plan.md) ----\n//\n// A helper (parent/caretaker) sets favorite teams/sports from a browser;\n// the receiver (widget) never sees a picker, only its own device id.\n//\n// GET /devices read-only index of device_configs; links\n// to referenced configs that still exist\n// GET /config/new blank picker form\n// POST /config/new creates a config from the submitted\n// sports[]/teams[], redirects to /config/:id\n// GET /config/:id view/edit that config — the URL itself is\n// the capability token; there are no\n// accounts, so \"bookmark this link\" is the\n// only way back in\n// POST /config/:id saves edited sports[]/teams[]\n// GET /config/:id/personalization presentation settings — currently\n// just the intraday-vs-day completed-game\n// filter; stored separately from sports/\n// teams (its own JSON column) since it's a\n// different question (\"how to show it\" vs\n// \"what to show\")\n// POST /config/:id/personalization saves that\n// GET /config/:id/pair offers code-based pairing plus a select\n// for reassigning an existing device\n// POST /config/:id/pair reassigns the selected existing device\n// to this config\n// POST /config/:id/code mints a short, reusable-until-expiry\n// pairing code for that config\n// GET /config/:id/preview renders what /config/resolve would\n// currently hand the widget for this\n// config — runs the same live path as `/`,\n// not a stored snapshot\n// POST /config/:id/devices/:deviceId sets a human-friendly name (\"dad\",\n// \"mom\") on a device already paired to that\n// config — for the configurator's own\n// benefit telling devices apart; never read\n// by /config/resolve or the app\n// POST /pair {code, device} JSON body from the app;\n// binds device -> config\n// GET /config/resolve ?device=&d=x&tz= — looks up\n// the device's config and 302s to `/` with\n// format=json baked in (this route has no\n// format= param at all: its one consumer is\n// the native json timeline provider) and\n// w=/h= parsed from d=. cache-control:\n// no-store, since this URL is constant per\n// device while its target can change.\n//\n// Only sports[]/teams[] are stored — day/tz/w/h/format stay live per-request\n// facts, never helper preferences (see the plan doc's rationale). Submitted\n// sports/teams are filtered against lib/catalog.ts's SPORTS/TEAMS before\n// storage, but that's a defensive filter, not the real validator: the actual\n// safety net is that /config/resolve's redirect lands back on `/`, where\n// resolveParams validates exactly as it does for any other caller.\n\nimport { Hono } from \"npm:hono\";\nimport { SPORTS, TEAMS } from \"./lib/catalog.ts\";\nimport {\n buildResolvedUrl,\n DEFAULT_PERSONALIZATION,\n type StoredConfig,\n} from \"./lib/config.ts\";\nimport {\n createConfig,\n createPairingCode,\n generateConfigName,\n getConfig,\n getDeviceStatus,\n getPersonalization,\n linkExistingDevice,\n listAllConfigs,\n listAllDeviceConfigs,\n listDevicesForConfig,\n listExpiredPairingCodes,\n listLinkableDevices,\n pairDevice,\n renameConfig,\n renameDevice,\n resolveDevice,\n saveDeviceToken,\n updateConfig,\n updatePersonalization,\n} from \"./lib/configStore.ts\";\nimport {\n formatDateLabel,\n resolveClientOffsetSeconds,\n windowDatesFor,\n} from \"./lib/dates.ts\";\nimport { pickNextSlate } from \"./lib/games.ts\";\nimport { resolveParams } from \"./lib/params.ts\";\nimport { notifyConfigDevices } from \"./lib/push.ts\";\nimport { fetchScores } from \"./lib/sleeper.ts\";\nimport { renderHtml } from \"./render/html.ts\";\nimport { renderJson } from \"./render/json.ts\";\nimport { renderPng } from \"./render/png.ts\";\nimport {\n configDevicesDocument,\n configIndexDocument,\n configNewDocument,\n configPairDocument,\n configPersonalizationDocument,\n configPreviewDocument,\n type ConfigPreviewItem,\n configSettingsDocument,\n deviceConfigIndexDocument,\n} from \"./render/configHtml.ts\";\nimport { backgroundForHue, randomHue } from \"./render/theme.ts\";\n\nasync function gamesHandler(req: Request): Promise {\n const url = new URL(req.url);\n const dayParam = url.searchParams.get(\"day\");\n // \"next\" is the default — an omitted `day` (the common case, since it's\n // the only value that needs no explicit widget config) gets the\n // nearest-upcoming-game scan starting today. `today`/`tomorrow` are still\n // opt-in exact matches for which value gets echoed/labeled, but as of the\n // 2026-08-26 relaxation they only move where the scan starts (see\n // windowDatesFor) — anything else, including an absent param, resolves to\n // \"next\", which starts at the same place \"today\" does.\n const day = dayParam === \"today\"\n ? \"today\"\n : dayParam === \"tomorrow\"\n ? \"tomorrow\"\n : \"next\";\n const format = url.searchParams.get(\"format\") ?? \"html\";\n\n // Repeated params (`?teams[]=sparks&teams[]=lakers`), matching Sleeper's\n // own convention rather than a comma-joined list.\n const resolved = resolveParams(\n url.searchParams.getAll(\"sports[]\"),\n url.searchParams.getAll(\"teams[]\"),\n );\n\n // Same silent-coercion trap sports[]/teams[]/tz already guard against: an\n // unrecognized `day` was falling through to a default with nothing echoing\n // it. The ios-client spec names a bad `day` as *the* malformed-request\n // example, so it gets the same rejected-echo treatment as everything else.\n // An absent `day` is not an error — it's the new default — so only a\n // present-but-unrecognized value lands in `rejected`.\n if (\n dayParam !== null && dayParam !== \"today\" && dayParam !== \"tomorrow\" &&\n dayParam !== \"next\"\n ) {\n resolved.rejected.push(`day:${dayParam}`);\n }\n\n // `?tz=` — seconds east of GMT, e.g. iOS's own\n // TimeZone.current.secondsFromGMT() — is what `today`/`tomorrow` resolve\n // against and what game times render in. Already has DST folded in by\n // whoever sent it, so no zone table lookup happens on this side. Defaults\n // to Pacific's live offset. An unrecognised value falls back to that\n // default and joins `rejected` rather than erroring, same drift-echo\n // `resolveParams` uses for sports[]/teams[].\n const { offsetSeconds: clientOffsetSeconds, rejected: rejectedTz } =\n resolveClientOffsetSeconds(\n url.searchParams.get(\"tz\"),\n );\n if (rejectedTz) resolved.rejected.push(rejectedTz);\n\n // Every `day` value scans the same 3-day window now, just anchored at a\n // different start date — see windowDatesFor for what \"today\"/\"tomorrow\"\n // mean post-relaxation.\n const dates = windowDatesFor(day, clientOffsetSeconds);\n // One /scores round trip per candidate date, all in flight at once — not\n // scanned serially, and not the undocumented full-season dumps Sleeper\n // also exposes (up to 14MB for mlb's daily slate, measured live). See\n // docs/widget-next-up-plan.md.\n const gamesByDate = await Promise.all(\n dates.map((d) => fetchScores(d, resolved.sports)),\n );\n const picked = pickNextSlate(\n dates,\n gamesByDate,\n resolved.sports,\n resolved.teams,\n );\n\n // `resolvedDate` is what the json contract echoes in `x-effective-date`;\n // `date` is what render/png and render/html use for card copy, which\n // always needs a concrete date even when nothing was found. They only\n // diverge when the window is exhausted: `resolvedDate` goes null (nothing\n // in the window qualified — an honest \"not found\", distinct from a real\n // date with zero games), while `date` falls back to the window's first\n // (start) date so the empty-state render still has something to anchor\n // its label to.\n const date = picked?.date ?? dates[0];\n const bySport = picked?.bySport ?? [];\n const resolvedDate = picked?.date ?? null;\n\n // See buildResolvedUrl (lib/config.ts) for who sets this and why it's\n // never a value a caller would type by hand.\n const hideCompleted = url.searchParams.get(\"hideCompleted\") === \"1\";\n\n if (format === \"json\") {\n return renderJson(\n bySport,\n day,\n resolved,\n clientOffsetSeconds,\n resolvedDate,\n hideCompleted,\n );\n }\n if (format === \"png\") {\n return renderPng({\n bySport,\n dateLabel: formatDateLabel(date, day),\n width: Number(url.searchParams.get(\"w\")) || 329,\n height: Number(url.searchParams.get(\"h\")) || 155,\n // The randomness lives here, at the edge, so the tree stays pure.\n background: backgroundForHue(randomHue()),\n rejected: resolved.rejected,\n clientOffsetSeconds,\n });\n }\n return renderHtml(bySport, day, clientOffsetSeconds);\n}\n\n// Repeated checkbox values (`sports[]`/`teams[]`) survive Hono's\n// `parseBody({ all: true })` as an array; a single one comes back as a bare\n// string, and none at all comes back undefined. Normalizing here is what\n// lets the route handlers treat all three cases the same way.\nfunction asArray(value: unknown): string[] {\n if (Array.isArray(value)) {\n return value.filter((v): v is string => typeof v === \"string\");\n }\n if (typeof value === \"string\") return [value];\n return [];\n}\n\nfunction filterKnown(values: string[], allowed: string[]): string[] {\n return values.filter((v) => allowed.includes(v));\n}\n\nconst TEAM_SLUGS = Object.keys(TEAMS);\n\nconst app = new Hono();\n\napp.get(\"/\", (c) => gamesHandler(c.req.raw));\n\n// Prototype-stage only, no auth: these two indexes enumerate real device\n// associations and config capability ids. /devices intentionally has no\n// inbound navigation; neither index is a pattern to carry forward once the\n// configurator gets real access control.\napp.get(\"/devices\", async (c) => {\n const devices = await listAllDeviceConfigs();\n return c.html(deviceConfigIndexDocument(devices));\n});\n\napp.get(\"/config\", async (c) => {\n const configs = await listAllConfigs();\n return c.html(configIndexDocument(configs));\n});\n\n// Generated here, not inside createConfig, so the configurator sees the\n// default name before the row exists and can change or clear it in the\n// same submit — see lib/configStore.ts's createConfig header.\napp.get(\"/config/new\", (c) => {\n return c.html(\n configNewDocument({\n formAction: \"/config/new\",\n config: { sports: [], teams: [] },\n name: generateConfigName(),\n }),\n );\n});\n\napp.post(\"/config/new\", async (c) => {\n const body = await c.req.parseBody({ all: true });\n const config = {\n sports: filterKnown(asArray(body[\"sports[]\"]), SPORTS),\n teams: filterKnown(asArray(body[\"teams[]\"]), TEAM_SLUGS),\n };\n const name = typeof body[\"name\"] === \"string\"\n ? body[\"name\"].trim() || null\n : null;\n const { id } = await createConfig(config, name);\n return c.redirect(`/config/${id}`);\n});\n\n// A device that's never paired (a pre-config install, or one whose pairing\n// row got wiped — see lib/configStore.ts's device_configs table) has no\n// StoredConfig at all, and buildResolvedUrl's own \"empty means all sports\"\n// rule would otherwise dump the entire slate on it. That rule is correct for\n// an actually-empty *config* (a helper who unchecked everything on purpose);\n// it's wrong as the fallback for *no config*, which this route is the only\n// place that distinguishes. Hard-coding the pre-config-era default here,\n// rather than writing a real \"default\" config row via lib/configStore.ts,\n// keeps every other layer's contract exactly as-is: getConfig/resolveDevice\n// still return null for \"nothing on file\", buildResolvedUrl still treats an\n// empty StoredConfig as \"all sports\", and a paired device with a genuinely\n// empty config still gets that. This is purely what an unpaired redirect\n// carries.\nconst LEGACY_DEFAULT_CONFIG: StoredConfig = {\n sports: [],\n teams: [\"fever\", \"sparks\", \"dodgers\"],\n};\n\n// Must be registered before /config/:id below — \"resolve\" would otherwise\n// match that route's :id param and 404 out of getConfig(\"resolve\"), which is\n// the widget's only data path silently going dead.\napp.get(\"/config/resolve\", async (c) => {\n const url = new URL(c.req.url);\n const deviceId = url.searchParams.get(\"device\");\n const stored = deviceId ? await resolveDevice(deviceId) : null;\n const target = buildResolvedUrl(\n stored ?? LEGACY_DEFAULT_CONFIG,\n stored?.personalization ?? DEFAULT_PERSONALIZATION,\n {\n d: url.searchParams.get(\"d\"),\n tz: url.searchParams.get(\"tz\"),\n },\n );\n // Response.redirect is broken on Val Town — a plain 302 Response with an\n // explicit Location header is the documented workaround. cache-control is\n // explicit too: unlike `/`, this URL is constant per device while its\n // target can silently change underneath it, so nothing here should be\n // cached at any layer.\n return new Response(null, {\n status: 302,\n headers: { Location: target, \"cache-control\": \"no-store\" },\n });\n});\n\n// Shared across every /config/:id render below — pulled out so the four\n// handlers that redraw this page can't drift from each other on how a\n// device's rename form gets its action URL.\nfunction deviceActionPath(id: string): (deviceId: string) => string {\n return (deviceId) => `/config/${id}/devices/${encodeURIComponent(deviceId)}`;\n}\n\n// The settings sub-route — just the sports/teams form. Device list and\n// pairing live at their own routes below, reached via the shared top nav\n// (render/configHtml.ts's configNav) rather than being inline here.\napp.get(\"/config/:id\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n return c.html(\n configSettingsDocument({\n id,\n formAction: `/config/${id}`,\n config,\n name: config.name,\n }),\n );\n});\n\napp.post(\"/config/:id\", async (c) => {\n const id = c.req.param(\"id\");\n const existing = await getConfig(id);\n if (!existing) return c.text(\"Not found\", 404);\n\n const body = await c.req.parseBody({ all: true });\n const config = {\n sports: filterKnown(asArray(body[\"sports[]\"]), SPORTS),\n teams: filterKnown(asArray(body[\"teams[]\"]), TEAM_SLUGS),\n };\n const name = typeof body[\"name\"] === \"string\" ? body[\"name\"] : \"\";\n await updateConfig(id, config);\n await renameConfig(id, name);\n // Best-effort: a push failure (missing APNs credentials, a dead token,\n // Apple being down) must never break saving the config itself, so this\n // is swallowed rather than awaited into the response's success path.\n await notifyConfigDevices(id).catch(() => undefined);\n return c.html(\n configSettingsDocument({\n id,\n formAction: `/config/${id}`,\n config,\n name: name.trim() || null,\n saved: true,\n }),\n );\n});\n\n// The presentation-settings sub-route — separate from Settings above (see\n// render/configHtml.ts's configPersonalizationDocument header) and from\n// buildResolvedUrl's Personalization param that this eventually feeds.\napp.get(\"/config/:id/personalization\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n const personalization = await getPersonalization(id);\n return c.html(\n configPersonalizationDocument({\n id,\n formAction: `/config/${id}/personalization`,\n personalization,\n }),\n );\n});\n\napp.post(\"/config/:id/personalization\", async (c) => {\n const id = c.req.param(\"id\");\n const existing = await getConfig(id);\n if (!existing) return c.text(\"Not found\", 404);\n\n const body = await c.req.parseBody({ all: true });\n const personalization = {\n intradayFilter: body[\"intradayFilter\"] === \"intraday\",\n };\n await updatePersonalization(id, personalization);\n // Same best-effort push as Settings' save: this changes what the widget\n // shows just as much as sports/teams does.\n await notifyConfigDevices(id).catch(() => undefined);\n return c.html(\n configPersonalizationDocument({\n id,\n formAction: `/config/${id}/personalization`,\n personalization,\n saved: true,\n }),\n );\n});\n\napp.get(\"/config/:id/devices\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n const devices = await listDevicesForConfig(id);\n return c.html(\n configDevicesDocument({\n id,\n devices,\n deviceActionPath: deviceActionPath(id),\n }),\n );\n});\n\napp.get(\"/config/:id/pair\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n const [expiredCodes, devices] = await Promise.all([\n listExpiredPairingCodes(id),\n listLinkableDevices(id),\n ]);\n return c.html(\n configPairDocument({\n id,\n codeActionPath: `/config/${id}/code`,\n linkActionPath: `/config/${id}/pair`,\n devices,\n expiredCodes,\n linked: c.req.query(\"linked\") === \"1\",\n }),\n );\n});\n\napp.post(\"/config/:id/pair\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n\n const body = await c.req.parseBody();\n const deviceId = String(body.deviceId ?? \"\").trim();\n if (!deviceId) return c.text(\"Choose a device\", 400);\n\n const linked = await linkExistingDevice(id, deviceId);\n if (!linked) return c.text(\"Device not available\", 422);\n return c.redirect(`/config/${id}/pair?linked=1`);\n});\n\napp.post(\"/config/:id/code\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n\n const pairing = await createPairingCode(id);\n const [expiredCodes, devices] = await Promise.all([\n listExpiredPairingCodes(id),\n listLinkableDevices(id),\n ]);\n return c.html(\n configPairDocument({\n id,\n codeActionPath: `/config/${id}/code`,\n linkActionPath: `/config/${id}/pair`,\n devices,\n pairing,\n expiredCodes,\n }),\n );\n});\n\n// Runs this config through the exact same live path `/config/resolve`\n// would redirect a device to — buildResolvedUrl gives the query string,\n// gamesHandler is the same function app.get(\"/\", ...) calls below, format\n// is always \"json\" per buildResolvedUrl — rather than reimplementing\n// slate-picking or caching a snapshot that could drift from what the\n// widget actually sees. That means a real Sleeper round trip on every\n// load, same as `/` itself; a failure there (network, Sleeper down) is\n// caught and shown as this page's own error state instead of a 500.\napp.get(\"/config/:id/preview\", async (c) => {\n const id = c.req.param(\"id\");\n const config = await getConfig(id);\n if (!config) return c.text(\"Not found\", 404);\n\n try {\n const personalization = await getPersonalization(id);\n const target = buildResolvedUrl(config, personalization);\n const response = await gamesHandler(\n new Request(new URL(target, c.req.url)),\n );\n const payload = (await response.json()) as { items: ConfigPreviewItem[] };\n return c.html(\n configPreviewDocument({\n id,\n ok: true,\n items: payload.items,\n rawJson: JSON.stringify(payload, null, 2),\n }),\n );\n } catch (err) {\n return c.html(\n configPreviewDocument({\n id,\n ok: false,\n error: err instanceof Error ? err.message : String(err),\n }),\n );\n }\n});\n\n// The configurator naming a device from the /config/:id/devices page —\n// \"dad\"/\"mom\"/etc, so they can tell paired devices apart. Redirects back\n// (PRG) rather than re-rendering directly so a page refresh after saving\n// doesn't re-post — back to the devices sub-route now, not the settings\n// page that used to own this section.\napp.post(\"/config/:id/devices/:deviceId\", async (c) => {\n const id = c.req.param(\"id\");\n const deviceId = c.req.param(\"deviceId\");\n const body = await c.req.parseBody({ all: true });\n const name = typeof body[\"name\"] === \"string\" ? body[\"name\"] : \"\";\n await renameDevice(deviceId, name);\n return c.redirect(`/config/${id}/devices`);\n});\n\n// The receiver's half of pairing — an ordinary JSON request from app code,\n// not the image-serving path, so a real 4xx here is fine (the \"never 4xx\"\n// rule in this file is specifically about a broken image in WidgetKit).\napp.post(\"/pair\", async (c) => {\n let body: unknown;\n try {\n body = await c.req.json();\n } catch {\n return c.json({ ok: false }, 400);\n }\n const { code, device } = (body ?? {}) as { code?: unknown; device?: unknown };\n if (typeof code !== \"string\" || typeof device !== \"string\") {\n return c.json({ ok: false }, 400);\n }\n\n const result = await pairDevice(code, device);\n if (result.ok) return c.json(result, 200);\n if (result.reason === \"expired\") {\n return c.json({ ok: false, message: \"expired\" }, 422);\n }\n return c.json({ ok: false }, 404);\n});\n\n// AppDelegate.swift uploads its APNs token here on every\n// didRegisterForRemoteNotificationsWithDeviceToken — unconditionally, not\n// just once, since tokens rotate. Independent of /pair on purpose: see the\n// device_tokens table comment in lib/configStore.ts.\napp.post(\"/device/token\", async (c) => {\n let body: unknown;\n try {\n body = await c.req.json();\n } catch {\n return c.json({ ok: false }, 400);\n }\n const { device, token } = (body ?? {}) as {\n device?: unknown;\n token?: unknown;\n };\n if (typeof device !== \"string\" || typeof token !== \"string\") {\n return c.json({ ok: false }, 400);\n }\n\n await saveDeviceToken(device, token);\n return c.json({ ok: true });\n});\n\n// Prototype-level diagnostics for the app's paired screen — not part of the\n// receiver's real data path (that's /config/resolve). Never errors past 200:\n// an unpaired or unknown device id just gets { paired: false }, same\n// never-fail posture as the rest of this val's device-facing routes.\n//\n// KNOWN GAP (2026-08-28): this route 404s on jade.beer (the custom domain)\n// while working on the val.run URL, even after redeploy and even nested\n// under /config/* — every other route works on both, so whatever's stale is\n// on the domain side, not a Hono routing issue in this file. Whoever owns\n// jade.beer's setup needs to look at it; the iOS client hits val.run\n// directly for this one call in the meantime.\napp.get(\"/config/status/:deviceId\", async (c) => {\n const deviceId = c.req.param(\"deviceId\");\n const status = await getDeviceStatus(deviceId);\n if (!status) return c.json({ deviceId, paired: false });\n return c.json({\n deviceId,\n paired: true,\n configId: status.configId,\n name: status.name,\n sports: status.sports,\n teams: status.teams,\n });\n});\n\napp.onError((err) => Promise.reject(err));\n\nexport default app.fetch;","createdAt",["D",1788290293174],"branchVersion","branchId","9635267c-e84d-4621-be8a-af9e5052d6d5",{"_32":49,"_34":50,"_35":51,"_37":53,"_40":54,"_42":14,"_43":44,"_26":27},{"_32":49,"_34":50,"_35":51,"_37":52},true,"render/configHtml.ts","2157ed5c-a31a-11f1-8fad-1607ee4eb77e","configHtml.ts","script","// The helper's server-rendered config picker — plain HTML forms, no\n// client-side JS, the same \"template string\" shape render/html.ts already\n// uses for the games view. Every `config*Document` export here is pure and\n// is what the tests assert against; main.ts wraps each in a Response\n// (Hono's `c.html`).\n//\n// Checkboxes are generated from lib/catalog.ts's SPORTS/TEAMS — the same\n// tables lib/params.ts validates `/`'s sports[]/teams[] against. That's what\n// makes an invalid selection structurally hard to submit here, rather than\n// something a second validator has to catch on write. See\n// docs/widget-config-plan.md's \"Validation\" section for why there's\n// deliberately no rejection/echo mechanism on this page: the real safety net\n// is resolveParams, which still runs when /config/resolve's redirect lands\n// on `/`.\n//\n// ---- one page per concern, not one page for everything ----\n//\n// This used to be a single `configPageDocument` rendering the settings\n// form, the pairing-code section, and the device list all inline on\n// GET/POST /config/:id — every helper action landed back on that one\n// giant page. It's now six documents behind six routes (main.ts):\n// GET /config (configIndexDocument, every config row), GET/POST /config/:id\n// (configSettingsDocument, the sports/teams form only), GET/POST\n// /config/:id/personalization (configPersonalizationDocument, presentation\n// settings — see its own header for why this is a separate document/row\n// column from Settings rather than a field bolted onto that form),\n// GET /config/:id/devices (configDevicesDocument, list + rename),\n// GET/POST /config/:id/pair plus POST /config/:id/code\n// (configPairDocument, link an existing device or mint/show a code), and\n// GET /config/:id/preview (configPreviewDocument, a\n// read-only render of what /config/resolve would currently hand the widget\n// for this config — see its own header below for how it gets that data).\n// The five id-scoped documents share one persistent top nav (`configNav`)\n// so a helper can move between them without going back through the index.\n// GET /config/new keeps its own document (configNewDocument): there's no\n// id yet to hang a nav on, and nothing paired, codeable, or previewable\n// until the config is actually saved.\n\nimport { SPORTS, TEAMS } from \"../lib/catalog.ts\";\nimport { type StoredConfig } from \"../lib/config.ts\";\nimport { titleCase } from \"../lib/text.ts\";\n\n// Deliberately not imported from lib/configStore.ts (the module that\n// actually produces these) — this file stays decoupled from the impure\n// sqlite layer the same way it's decoupled from Sleeper, matching the\n// StoredConfig-from-lib/config.ts pattern below.\nexport type PairedDeviceView = {\n deviceId: string;\n name: string | null;\n createdAt: string;\n pushRegistered: boolean;\n tokenUpdatedAt: string | null;\n};\n\n// What GET /config/:id/pair's expired-codes section lists — past pairing\n// codes for this config that are no longer usable.\nexport type ExpiredCodeView = {\n code: string;\n createdAt: string;\n expiresAt: string;\n};\n\n// Mirrors lib/config.ts's Personalization, same redeclare-don't-import\n// convention as ConfigPreviewItem below.\nexport type PersonalizationView = { intradayFilter: boolean };\n\n// Mirrors render/json.ts's WidgetItem — deliberately redeclared rather than\n// imported. render/json.ts is pure, so importing its type wouldn't break\n// the decoupling this file otherwise keeps from impure modules, but this\n// file's own convention (ConfigRow beside ConfigSummary, PairedDeviceView\n// beside PairedDevice) is a view type per document, not a shared one, so\n// the preview stays consistent with that rather than being the one\n// exception.\nexport type ConfigPreviewItem = {\n id: string;\n mainText: string;\n subText: string;\n caption: string | null;\n emphasized: boolean;\n timestamp: number;\n};\n\n// What GET /config lists — one row per config, enough to tell them apart\n// without opening each one. `deviceCount` is the only field that isn't a\n// direct column read (lib/configStore.ts's listAllConfigs joins it), kept\n// here anyway since disambiguating configs is this page's entire job.\nexport type ConfigRow = {\n id: string;\n name: string | null;\n sports: string[];\n teams: string[];\n updatedAt: string;\n deviceCount: number;\n};\n\n// device names and ids both originate as free-form input from whatever\n// called POST /pair, not from the closed catalogs sports/team checkboxes\n// draw from — so, unlike most of this file, they need escaping before\n// landing in HTML. Config ids are UUIDs this val mints itself\n// (crypto.randomUUID() in lib/configStore.ts), never free text, so they're\n// interpolated as-is everywhere below, same as formAction always has been.\nfunction escapeHtml(value: string): string {\n return value.replace(/&/g, \"&\").replace(//g,\n \">\",\n ).replace(/\"/g, \""\");\n}\n\nfunction sportCheckboxes(selected: string[]): string {\n return SPORTS.map((sport) => {\n const checked = selected.includes(sport) ? \" checked\" : \"\";\n return ` ${sport.toUpperCase()}`;\n }).join(\" \");\n}\n\n// Grouped by sport (SPORTS order) rather than one flat ~110-entry list —\n// the same \"pick a sport, then a team\" structure widget-ios-brief.md\n// explicitly rejected for the *receiver's* seven-team picker doesn't apply\n// here: the helper is choosing from the full catalog, not a small starter\n// list, and a flat list of 110 checkboxes is the harder one to scan.\nfunction teamCheckboxesBySport(selected: string[]): string {\n return SPORTS.map((sport) => {\n const slugs = Object.entries(TEAMS)\n .filter(([, ref]) => ref.sport === sport)\n .map(([slug]) => slug);\n if (!slugs.length) return \"\";\n const boxes = slugs\n .map((slug) => {\n const checked = selected.includes(slug) ? \" checked\" : \"\";\n return ` ${\n titleCase(slug)\n }`;\n })\n .join(\" \");\n return `

${sport.toUpperCase()}${boxes}

`;\n }).join(\"\");\n}\n\n// The index's one-line summary of what a config actually resolves to —\n// same \"empty means all sports, teams beat sports\" precedence buildResolvedUrl\n// (lib/config.ts) and `/`'s resolveParams apply at request time, just\n// described in words instead of computed into a redirect.\nfunction summarizeSelection(config: StoredConfig): string {\n if (config.teams.length) {\n return config.teams.map((slug) => titleCase(slug)).join(\", \");\n }\n if (config.sports.length) {\n return config.sports.map((sport) => sport.toUpperCase()).join(\", \");\n }\n return \"All sports\";\n}\n\n// One row per paired device, each its own form so naming one doesn't\n// require re-submitting the others. Blank means never named — the\n// placeholder, not a value, so an unnamed device saves as null rather than\n// the literal placeholder text. Metadata (device id, paired-since, push\n// status) is read-only context alongside the rename form — this page is\n// still the only place a helper can tell paired devices apart.\nfunction deviceListMarkup(\n devices: PairedDeviceView[],\n actionPath: (deviceId: string) => string,\n): string {\n if (!devices.length) return \"

No devices paired yet.

\";\n const rows = devices\n .map((device) => {\n const safeId = escapeHtml(device.deviceId);\n const safeName = device.name ? escapeHtml(device.name) : \"\";\n const pairedSince = escapeHtml(\n new Date(device.createdAt).toLocaleString(),\n );\n const pushStatus = device.pushRegistered\n ? `Push registered${\n device.tokenUpdatedAt\n ? ` (updated ${\n escapeHtml(new Date(device.tokenUpdatedAt).toLocaleString())\n })`\n : \"\"\n }`\n : \"Push not registered\";\n return `

Device: ${safeId}
Paired since: ${pairedSince}
Push: ${pushStatus}

\n \n

`;\n })\n .join(\"\");\n return `

${rows}`;\n}\n\n// Below the current live code (if any) on GET /config/:id/pair — old codes\n// for this config that no longer work, so a helper can tell \"this one's\n// dead, mint a new one\" from \"did I already send this code.\"\nfunction expiredCodesMarkup(codes: ExpiredCodeView[]): string {\n if (!codes.length) return \"\";\n const rows = codes\n .map((c) => {\n return `\n ${escapeHtml(c.code)}\n ${escapeHtml(new Date(c.createdAt).toLocaleString())}\n ${escapeHtml(new Date(c.expiresAt).toLocaleString())}\n `;\n })\n .join(\"\");\n return `

Expired codes

\n \n \n ${rows}\n

Code	Created	Expired

`;\n}\n\n// GET /config/:id/preview's item table — the same WidgetItem shape\n// render/json.ts's widgetPayload emits, laid out the way the widget itself\n// would present it (a local time instead of a raw unix timestamp) so a\n// helper can sanity-check ordering and text without decoding the JSON by\n// eye.\nfunction previewItemsMarkup(items: ConfigPreviewItem[]): string {\n if (!items.length) {\n return \"

No items — nothing in this config's window right now.

\";\n }\n const rows = items\n .map((item) => {\n const when = escapeHtml(new Date(item.timestamp * 1000).toLocaleString());\n return `\n ${when}\n ${escapeHtml(item.mainText)}\n ${escapeHtml(item.subText)}\n ${item.caption ? escapeHtml(item.caption) : \"\"}\n ${item.emphasized ? \"Yes\" : \"\"}\n `;\n })\n .join(\"\");\n return `\n \n ${rows}\n

When	Main	Sub	Caption	Emphasized

`;\n}\n\nconst PAGE_STYLE = `\n body { font-family: system-ui, -apple-system, sans-serif; max-width: 640px; margin: 2rem auto; padding: 0 1rem; color: #1a1a1a; line-height: 1.4; }\n h1 { font-size: 1.4rem; }\n h2 { font-size: 1.1rem; }\n fieldset { border: 1px solid #ddd; border-radius: 6px; margin: 0.75rem 0; padding: 0.5rem 1rem; }\n legend { font-weight: 600; padding: 0 0.25rem; }\n label { display: inline-block; margin: 0.3rem 0.85rem 0.3rem 0; }\n button { background: #2563eb; color: #fff; border: none; border-radius: 4px; padding: 0.5rem 1rem; font-size: 0.95rem; cursor: pointer; }\n button:hover { background: #1d4ed8; }\n section { margin-top: 2rem; padding-top: 1rem; border-top: 1px solid #eee; }\n ul.devices { list-style: none; padding: 0; }\n ul.devices li { margin: 0.9rem 0; padding-bottom: 0.9rem; border-bottom: 1px solid #eee; }\n ul.devices form { display: flex; gap: 0.5rem; }\n dl.device-meta { display: flex; flex-wrap: wrap; gap: 0 1.5rem; margin: 0 0 0.5rem; }\n dl.device-meta div { display: flex; gap: 0.35rem; }\n dl.device-meta dt { color: #666; font-size: 0.8rem; text-transform: uppercase; letter-spacing: 0.02em; }\n dl.device-meta dd { margin: 0; font-size: 0.85rem; }\n dl.device-meta dd.device-id { font-family: ui-monospace, monospace; }\n input[type=\"text\"] { flex: 1; padding: 0.4rem 0.6rem; border: 1px solid #ccc; border-radius: 4px; font-size: 0.95rem; }\n select { padding: 0.4rem 0.6rem; border: 1px solid #ccc; border-radius: 4px; font-size: 0.95rem; background: #fff; }\n .link-device-form { display: flex; flex-wrap: wrap; gap: 0.5rem; }\n .link-device-form select { flex: 1; min-width: 12rem; }\n .breadcrumb { margin: 0 0 0.75rem; }\n .breadcrumb a { color: #2563eb; text-decoration: none; font-size: 0.9rem; }\n nav.config-nav { display: flex; gap: 1.25rem; margin: 0 0 1.5rem; border-bottom: 1px solid #ddd; }\n nav.config-nav a { color: #2563eb; text-decoration: none; padding-bottom: 0.6rem; font-size: 0.95rem; }\n nav.config-nav a.active { color: #1a1a1a; font-weight: 600; border-bottom: 2px solid #2563eb; }\n table.config-index { width: 100%; border-collapse: collapse; margin-top: 1rem; }\n table.config-index th, table.config-index td { text-align: left; padding: 0.5rem 0.6rem; border-bottom: 1px solid #eee; font-size: 0.95rem; }\n table.config-index th { color: #666; font-weight: 600; font-size: 0.8rem; text-transform: uppercase; letter-spacing: 0.02em; }\n table.config-index td:first-child:not(:has(.config-id)) { font-family: ui-monospace, monospace; font-size: 0.85rem; }\n .config-id { font-family: ui-monospace, monospace; font-size: 0.8rem; color: #666; }\n pre { background: #f6f6f6; border: 1px solid #eee; border-radius: 6px; padding: 0.75rem 1rem; overflow-x: auto; font-size: 0.8rem; line-height: 1.5; }\n`;\n\nfunction pageShell(title: string, body: string): string {\n return `\n\n\n\n\n${title}\n\n\n\n${body}\n\n`;\n}\n\ntype ConfigNavActive =\n | \"preview\"\n | \"settings\"\n | \"personalization\"\n | \"devices\"\n | \"pair\";\n\n// The persistent top nav every id-scoped sub-page shares, so moving between\n// the form, personalization, the device list, the pairing flow, and the\n// preview never routes back through the index. `active` just marks which\n// tab is current — every route is a real page, not a client-side view\n// swap, so this is plain server-rendered markup with no JS involved.\nfunction configNav(id: string, active: ConfigNavActive): string {\n const tabs: { key: ConfigNavActive; href: string; label: string }[] = [\n { key: \"preview\", href: `/config/${id}/preview`, label: \"Preview\" },\n { key: \"settings\", href: `/config/${id}`, label: \"Settings\" },\n {\n key: \"personalization\",\n href: `/config/${id}/personalization`,\n label: \"Personalization\",\n },\n { key: \"devices\", href: `/config/${id}/devices`, label: \"Devices\" },\n { key: \"pair\", href: `/config/${id}/pair`, label: \"Pair\" },\n ];\n const links = tabs\n .map((tab) =>\n `${tab.label}`\n )\n .join(\"\");\n return ``;\n}\n\n// GET /config. Prototype-stage only: this lists every config's id as a live\n// link, which is exactly the \"unguessable capability URL\" every other page\n// in this file (and docs/valtown-brief.md) otherwise treats as sensitive —\n// bookmark-only, never logged, never enumerable. Explicitly requested as an\n// acceptable bypass while there's no auth story yet; do not carry this\n// page's behavior forward once /config gets real access control.\nexport function configIndexDocument(configs: ConfigRow[]): string {\n const rows = configs\n .map((row) => {\n const safeId = escapeHtml(row.id);\n // A named config leads with that name (what generateConfigName gave\n // it, or whatever the configurator renamed it to) and keeps the id\n // underneath in monospace — still visible and copyable, just not the\n // headline anymore. A pre-migration config with no name yet falls\n // back to exactly the old behavior: the id as the link text, nothing\n // underneath.\n const label = row.name ? escapeHtml(row.name) : safeId;\n const idSubtext = row.name\n ? `
${safeId}`\n : \"\";\n return `\n ${label}${idSubtext}\n ${escapeHtml(summarizeSelection(row))}\n ${row.deviceCount}\n ${escapeHtml(new Date(row.updatedAt).toLocaleString())}\n `;\n })\n .join(\"\");\n const body = `\n

All configs

+ New config

\n \n \n ${rows || ``}\n

Config	Favorites	Devices	Updated
No configs yet.

`;\n return pageShell(\"Widget favorites — All configs\", body);\n}\n\nexport type ConfigNewOptions = {\n formAction: string;\n config: StoredConfig;\n name: string;\n};\n\n// GET /config/new. No id yet, so no top nav — Settings/Devices/Pair/Preview\n// only make sense once POST /config/new has actually created a row. `name`\n// is generated eagerly by the caller (main.ts calls\n// lib/configStore.ts's generateConfigName before rendering this page, not\n// after creating the row) so the configurator sees the default here and\n// can edit or clear it before the config even exists, rather than only\n// discovering it after the fact on the Settings page.\nexport function configNewDocument(opts: ConfigNewOptions): string {\n const { formAction, config, name } = opts;\n const body = `\n \n

Widget favorites

\n `;\n return pageShell(\"Widget favorites — New\", body);\n}\n\nexport type ConfigSettingsOptions = {\n id: string;\n formAction: string;\n config: StoredConfig;\n name: string | null;\n saved?: boolean;\n};\n\n// GET/POST /config/:id. The sports/teams form, plus the config's own name\n// — auto-generated at creation (lib/configStore.ts's generateConfigName)\n// but editable here like any other setting, in the same submit. Device\n// list and pairing moved to their own routes/documents below.\nexport function configSettingsDocument(opts: ConfigSettingsOptions): string {\n const { id, formAction, config, name, saved } = opts;\n const safeName = name ? escapeHtml(name) : \"\";\n const body = `\n ${configNav(id, \"settings\")}\n

Widget favorites

\n ${saved ? \"

Saved.

\" : \"\"}\n `;\n return pageShell(\"Widget favorites — Settings\", body);\n}\n\nexport type ConfigPersonalizationOptions = {\n id: string;\n formAction: string;\n personalization: PersonalizationView;\n saved?: boolean;\n};\n\n// GET/POST /config/:id/personalization — presentation settings, kept\n// separate from Settings' sports/teams (\"what to show\") on purpose: this\n// is \"how to show it,\" a different question with its own growth path\n// (lib/configStore.ts's configs.personalization is a JSON column\n// specifically so more of these can land here later without touching the\n// sports/teams half of the row or this route's URL). The first setting is\n// the intraday-vs-day filter: whether a completed game keeps showing\n// (captioned END) for the rest of its day, or disappears from the list\n// the moment it ends. Rendered as a always submits one of its two\n// named values.\nexport function configPersonalizationDocument(\n opts: ConfigPersonalizationOptions,\n): string {\n const { id, formAction, personalization, saved } = opts;\n const body = `\n ${configNav(id, \"personalization\")}\n

Personalization

\n ${saved ? \"

Saved.

\" : \"\"}\n `;\n return pageShell(\"Widget favorites — Personalization\", body);\n}\n\nexport type ConfigDevicesOptions = {\n id: string;\n devices: PairedDeviceView[];\n deviceActionPath: (deviceId: string) => string;\n};\n\n// GET /config/:id/devices.\nexport function configDevicesDocument(opts: ConfigDevicesOptions): string {\n const { id, devices, deviceActionPath } = opts;\n const body = `\n ${configNav(id, \"devices\")}\n

Paired devices

\n ${deviceListMarkup(devices, deviceActionPath)}`;\n return pageShell(\"Widget favorites — Devices\", body);\n}\n\nexport type LinkableDeviceView = { deviceId: string; name: string | null };\n\nexport type ConfigPairOptions = {\n id: string;\n codeActionPath: string;\n linkActionPath: string;\n devices: LinkableDeviceView[];\n pairing?: { code: string; expiresAt: string } | null;\n expiredCodes: ExpiredCodeView[];\n linked?: boolean;\n};\n\n// GET /config/:id/pair, POST /config/:id/pair, and POST\n// /config/:id/code share this page. The select only contains existing device\n// rows owned by another config; submitting it reassigns that association.\nexport function configPairDocument(opts: ConfigPairOptions): string {\n const {\n id,\n codeActionPath,\n linkActionPath,\n devices,\n pairing,\n expiredCodes,\n linked,\n } = opts;\n const deviceOptions = devices.map((device) => {\n const safeId = escapeHtml(device.deviceId);\n const label = device.name\n ? `${escapeHtml(device.name)} — ${safeId}`\n : safeId;\n return ``;\n }).join(\"\");\n const linkForm = deviceOptions\n ? ``\n : \"

Every known device is already linked to this config.

\";\n const body = `\n ${configNav(id, \"pair\")}\n

Pair a device

\n ${linked ? \"

Device linked.

\" : \"\"}\n

Link an existing device

\n ${linkForm}\n

Pair with a code

\n \n ${\n pairing\n ? `

Code: ${pairing.code} — enter this in the app. Expires ${\n new Date(pairing.expiresAt).toLocaleString()\n }. Reusable until then, so the same code can pair more than one device.

`\n : \"\"\n }\n

\n ${expiredCodesMarkup(expiredCodes)}`;\n return pageShell(\"Widget favorites — Pair a device\", body);\n}\n\nexport type ConfigPreviewOptions =\n | { id: string; ok: true; items: ConfigPreviewItem[]; rawJson: string }\n | { id: string; ok: false; error: string };\n\n// GET /config/:id/preview — a read-only render of what /config/resolve\n// would currently hand the widget for this exact config: the same items\n// list as a table (for a quick sanity check) plus the full response\n// pretty-printed in a

 (for inspecting the exact contract, the way a\n// helper would otherwise need curl or the browser's devtools to see). This\n// is genuinely live: main.ts's handler runs the same slate-picking path\n// `/` itself does — real outbound Sleeper calls, not a canned fixture — so\n// `ok: false` is a real possibility (e.g. Sleeper unreachable) that gets\n// its own error state rather than a broken page.\nexport function configPreviewDocument(opts: ConfigPreviewOptions): string {\n  const { id } = opts;\n  const body = `\n    ${configNav(id, \"preview\")}\n    Preview
\n    ${\n    opts.ok\n      ? `${previewItemsMarkup(opts.items)}\n    \n      Raw response
\n      ${escapeHtml(opts.rawJson)}
\n    
`\n      : `Couldn't build a preview: ${escapeHtml(opts.error)}
`\n  }`;\n  return pageShell(\"Widget favorites — Preview\", body);\n}","// The helper's server-rendered config picker — plain HTML forms, no\n// client-side JS, the same \"template string\" shape render/html.ts already\n// uses for the games view. Every `config*Document` export here is pure and\n// is what the tests assert against; main.ts wraps each in a Response\n// (Hono's `c.html`).\n//\n// Checkboxes are generated from lib/catalog.ts's SPORTS/TEAMS — the same\n// tables lib/params.ts validates `/`'s sports[]/teams[] against. That's what\n// makes an invalid selection structurally hard to submit here, rather than\n// something a second validator has to catch on write. See\n// docs/widget-config-plan.md's \"Validation\" section for why there's\n// deliberately no rejection/echo mechanism on this page: the real safety net\n// is resolveParams, which still runs when /config/resolve's redirect lands\n// on `/`.\n//\n// ---- one page per concern, not one page for everything ----\n//\n// This used to be a single `configPageDocument` rendering the settings\n// form, the pairing-code section, and the device list all inline on\n// GET/POST /config/:id — every helper action landed back on that one\n// giant page. It's now six documents behind six routes (main.ts):\n// GET /config (configIndexDocument, every config row), GET/POST /config/:id\n// (configSettingsDocument, the sports/teams form only), GET/POST\n// /config/:id/personalization (configPersonalizationDocument, presentation\n// settings — see its own header for why this is a separate document/row\n// column from Settings rather than a field bolted onto that form),\n// GET /config/:id/devices (configDevicesDocument, list + rename),\n// GET/POST /config/:id/pair plus POST /config/:id/code\n// (configPairDocument, link an existing device or mint/show a code), and\n// GET /config/:id/preview (configPreviewDocument, a\n// read-only render of what /config/resolve would currently hand the widget\n// for this config — see its own header below for how it gets that data).\n// The five id-scoped documents share one persistent top nav (`configNav`)\n// so a helper can move between them without going back through the index.\n// GET /config/new keeps its own document (configNewDocument): there's no\n// id yet to hang a nav on, and nothing paired, codeable, or previewable\n// until the config is actually saved.\n\nimport { SPORTS, TEAMS } from \"../lib/catalog.ts\";\nimport { type StoredConfig } from \"../lib/config.ts\";\nimport { titleCase } from \"../lib/text.ts\";\n\n// Deliberately not imported from lib/configStore.ts (the module that\n// actually produces these) — this file stays decoupled from the impure\n// sqlite layer the same way it's decoupled from Sleeper, matching the\n// StoredConfig-from-lib/config.ts pattern below.\nexport type PairedDeviceView = {\n  deviceId: string;\n  name: string | null;\n  createdAt: string;\n  pushRegistered: boolean;\n  tokenUpdatedAt: string | null;\n};\n\n// What GET /config/:id/pair's expired-codes section lists — past pairing\n// codes for this config that are no longer usable.\nexport type ExpiredCodeView = {\n  code: string;\n  createdAt: string;\n  expiresAt: string;\n};\n\n// Mirrors lib/config.ts's Personalization, same redeclare-don't-import\n// convention as ConfigPreviewItem below.\nexport type PersonalizationView = { intradayFilter: boolean };\n\n// Mirrors render/json.ts's WidgetItem — deliberately redeclared rather than\n// imported. render/json.ts is pure, so importing its type wouldn't break\n// the decoupling this file otherwise keeps from impure modules, but this\n// file's own convention (ConfigRow beside ConfigSummary, PairedDeviceView\n// beside PairedDevice) is a view type per document, not a shared one, so\n// the preview stays consistent with that rather than being the one\n// exception.\nexport type ConfigPreviewItem = {\n  id: string;\n  mainText: string;\n  subText: string;\n  caption: string | null;\n  emphasized: boolean;\n  timestamp: number;\n};\n\n// What GET /config lists — one row per config, enough to tell them apart\n// without opening each one. `deviceCount` is the only field that isn't a\n// direct column read (lib/configStore.ts's listAllConfigs joins it), kept\n// here anyway since disambiguating configs is this page's entire job.\nexport type ConfigRow = {\n  id: string;\n  name: string | null;\n  sports: string[];\n  teams: string[];\n  updatedAt: string;\n  deviceCount: number;\n};\n\n// device names and ids both originate as free-form input from whatever\n// called POST /pair, not from the closed catalogs sports/team checkboxes\n// draw from — so, unlike most of this file, they need escaping before\n// landing in HTML. Config ids are UUIDs this val mints itself\n// (crypto.randomUUID() in lib/configStore.ts), never free text, so they're\n// interpolated as-is everywhere below, same as formAction always has been.\nfunction escapeHtml(value: string): string {\n  return value.replace(/&/g, \"&\").replace(//g,\n    \">\",\n  ).replace(/\"/g, \""\");\n}\n\nfunction sportCheckboxes(selected: string[]): string {\n  return SPORTS.map((sport) => {\n    const checked = selected.includes(sport) ? \" checked\" : \"\";\n    return ` ${sport.toUpperCase()}`;\n  }).join(\" \");\n}\n\n// Grouped by sport (SPORTS order) rather than one flat ~110-entry list —\n// the same \"pick a sport, then a team\" structure widget-ios-brief.md\n// explicitly rejected for the *receiver's* seven-team picker doesn't apply\n// here: the helper is choosing from the full catalog, not a small starter\n// list, and a flat list of 110 checkboxes is the harder one to scan.\nfunction teamCheckboxesBySport(selected: string[]): string {\n  return SPORTS.map((sport) => {\n    const slugs = Object.entries(TEAMS)\n      .filter(([, ref]) => ref.sport === sport)\n      .map(([slug]) => slug);\n    if (!slugs.length) return \"\";\n    const boxes = slugs\n      .map((slug) => {\n        const checked = selected.includes(slug) ? \" checked\" : \"\";\n        return ` ${\n          titleCase(slug)\n        }`;\n      })\n      .join(\" \");\n    return `${sport.toUpperCase()}${boxes}
`;\n  }).join(\"\");\n}\n\n// The index's one-line summary of what a config actually resolves to —\n// same \"empty means all sports, teams beat sports\" precedence buildResolvedUrl\n// (lib/config.ts) and `/`'s resolveParams apply at request time, just\n// described in words instead of computed into a redirect.\nfunction summarizeSelection(config: StoredConfig): string {\n  if (config.teams.length) {\n    return config.teams.map((slug) => titleCase(slug)).join(\", \");\n  }\n  if (config.sports.length) {\n    return config.sports.map((sport) => sport.toUpperCase()).join(\", \");\n  }\n  return \"All sports\";\n}\n\n// One row per paired device, each its own form so naming one doesn't\n// require re-submitting the others. Blank means never named — the\n// placeholder, not a value, so an unnamed device saves as null rather than\n// the literal placeholder text. Metadata (device id, paired-since, push\n// status) is read-only context alongside the rename form — this page is\n// still the only place a helper can tell paired devices apart.\nfunction deviceListMarkup(\n  devices: PairedDeviceView[],\n  actionPath: (deviceId: string) => string,\n): string {\n  if (!devices.length) return \"No devices paired yet.
\";\n  const rows = devices\n    .map((device) => {\n      const safeId = escapeHtml(device.deviceId);\n      const safeName = device.name ? escapeHtml(device.name) : \"\";\n      const pairedSince = escapeHtml(\n        new Date(device.createdAt).toLocaleString(),\n      );\n      const pushStatus = device.pushRegistered\n        ? `Push registered${\n          device.tokenUpdatedAt\n            ? ` (updated ${\n              escapeHtml(new Date(device.tokenUpdatedAt).toLocaleString())\n            })`\n            : \"\"\n        }`\n        : \"Push not registered\";\n      return `\n        \n          Device
${safeId}
\n          Paired since
${pairedSince}
\n          Push
${pushStatus}
\n        
\n        \n          \n          \n        
\n      
`;\n    })\n    .join(\"\");\n  return `${rows}
`;\n}\n\n// Below the current live code (if any) on GET /config/:id/pair — old codes\n// for this config that no longer work, so a helper can tell \"this one's\n// dead, mint a new one\" from \"did I already send this code.\"\nfunction expiredCodesMarkup(codes: ExpiredCodeView[]): string {\n  if (!codes.length) return \"\";\n  const rows = codes\n    .map((c) => {\n      return `\n        ${escapeHtml(c.code)}\n        ${escapeHtml(new Date(c.createdAt).toLocaleString())}\n        ${escapeHtml(new Date(c.expiresAt).toLocaleString())}\n      `;\n    })\n    .join(\"\");\n  return `\n    Expired codes
\n    \n      \n      ${rows}\n    Code Created Expired
\n  
`;\n}\n\n// GET /config/:id/preview's item table — the same WidgetItem shape\n// render/json.ts's widgetPayload emits, laid out the way the widget itself\n// would present it (a local time instead of a raw unix timestamp) so a\n// helper can sanity-check ordering and text without decoding the JSON by\n// eye.\nfunction previewItemsMarkup(items: ConfigPreviewItem[]): string {\n  if (!items.length) {\n    return \"No items — nothing in this config's window right now.
\";\n  }\n  const rows = items\n    .map((item) => {\n      const when = escapeHtml(new Date(item.timestamp * 1000).toLocaleString());\n      return `\n        ${when}\n        ${escapeHtml(item.mainText)}\n        ${escapeHtml(item.subText)}\n        ${item.caption ? escapeHtml(item.caption) : \"\"}\n        ${item.emphasized ? \"Yes\" : \"\"}\n      `;\n    })\n    .join(\"\");\n  return `\n    \n    ${rows}\n  When Main Sub Caption Emphasized
`;\n}\n\nconst PAGE_STYLE = `\n  body { font-family: system-ui, -apple-system, sans-serif; max-width: 640px; margin: 2rem auto; padding: 0 1rem; color: #1a1a1a; line-height: 1.4; }\n  h1 { font-size: 1.4rem; }\n  h2 { font-size: 1.1rem; }\n  fieldset { border: 1px solid #ddd; border-radius: 6px; margin: 0.75rem 0; padding: 0.5rem 1rem; }\n  legend { font-weight: 600; padding: 0 0.25rem; }\n  label { display: inline-block; margin: 0.3rem 0.85rem 0.3rem 0; }\n  button { background: #2563eb; color: #fff; border: none; border-radius: 4px; padding: 0.5rem 1rem; font-size: 0.95rem; cursor: pointer; }\n  button:hover { background: #1d4ed8; }\n  section { margin-top: 2rem; padding-top: 1rem; border-top: 1px solid #eee; }\n  ul.devices { list-style: none; padding: 0; }\n  ul.devices li { margin: 0.9rem 0; padding-bottom: 0.9rem; border-bottom: 1px solid #eee; }\n  ul.devices form { display: flex; gap: 0.5rem; }\n  dl.device-meta { display: flex; flex-wrap: wrap; gap: 0 1.5rem; margin: 0 0 0.5rem; }\n  dl.device-meta div { display: flex; gap: 0.35rem; }\n  dl.device-meta dt { color: #666; font-size: 0.8rem; text-transform: uppercase; letter-spacing: 0.02em; }\n  dl.device-meta dd { margin: 0; font-size: 0.85rem; }\n  dl.device-meta dd.device-id { font-family: ui-monospace, monospace; }\n  input[type=\"text\"] { flex: 1; padding: 0.4rem 0.6rem; border: 1px solid #ccc; border-radius: 4px; font-size: 0.95rem; }\n  select { padding: 0.4rem 0.6rem; border: 1px solid #ccc; border-radius: 4px; font-size: 0.95rem; background: #fff; }\n  .link-device-form { display: flex; flex-wrap: wrap; gap: 0.5rem; }\n  .link-device-form select { flex: 1; min-width: 12rem; }\n  .breadcrumb { margin: 0 0 0.75rem; }\n  .breadcrumb a { color: #2563eb; text-decoration: none; font-size: 0.9rem; }\n  nav.config-nav { display: flex; gap: 1.25rem; margin: 0 0 1.5rem; border-bottom: 1px solid #ddd; }\n  nav.config-nav a { color: #2563eb; text-decoration: none; padding-bottom: 0.6rem; font-size: 0.95rem; }\n  nav.config-nav a.active { color: #1a1a1a; font-weight: 600; border-bottom: 2px solid #2563eb; }\n  table.config-index { width: 100%; border-collapse: collapse; margin-top: 1rem; }\n  table.config-index th, table.config-index td { text-align: left; padding: 0.5rem 0.6rem; border-bottom: 1px solid #eee; font-size: 0.95rem; }\n  table.config-index th { color: #666; font-weight: 600; font-size: 0.8rem; text-transform: uppercase; letter-spacing: 0.02em; }\n  table.config-index td:first-child:not(:has(.config-id)) { font-family: ui-monospace, monospace; font-size: 0.85rem; }\n  .config-id { font-family: ui-monospace, monospace; font-size: 0.8rem; color: #666; }\n  pre { background: #f6f6f6; border: 1px solid #eee; border-radius: 6px; padding: 0.75rem 1rem; overflow-x: auto; font-size: 0.8rem; line-height: 1.5; }\n`;\n\nfunction pageShell(title: string, body: string): string {\n  return `\n\n\n\n\n${title}\n\n\n\n${body}\n\n`;\n}\n\ntype ConfigNavActive =\n  | \"preview\"\n  | \"settings\"\n  | \"personalization\"\n  | \"devices\"\n  | \"pair\";\n\n// The persistent top nav every id-scoped sub-page shares, so moving between\n// the form, personalization, the device list, the pairing flow, and the\n// preview never routes back through the index. `active` just marks which\n// tab is current — every route is a real page, not a client-side view\n// swap, so this is plain server-rendered markup with no JS involved.\nfunction configNav(id: string, active: ConfigNavActive): string {\n  const tabs: { key: ConfigNavActive; href: string; label: string }[] = [\n    { key: \"preview\", href: `/config/${id}/preview`, label: \"Preview\" },\n    { key: \"settings\", href: `/config/${id}`, label: \"Settings\" },\n    {\n      key: \"personalization\",\n      href: `/config/${id}/personalization`,\n      label: \"Personalization\",\n    },\n    { key: \"devices\", href: `/config/${id}/devices`, label: \"Devices\" },\n    { key: \"pair\", href: `/config/${id}/pair`, label: \"Pair\" },\n  ];\n  const links = tabs\n    .map((tab) =>\n      `${tab.label}`\n    )\n    .join(\"\");\n  return `← All configs
${links}
`;\n}\n\n// GET /config. Prototype-stage only: this lists every config's id as a live\n// link, which is exactly the \"unguessable capability URL\" every other page\n// in this file (and docs/valtown-brief.md) otherwise treats as sensitive —\n// bookmark-only, never logged, never enumerable. Explicitly requested as an\n// acceptable bypass while there's no auth story yet; do not carry this\n// page's behavior forward once /config gets real access control.\nexport function configIndexDocument(configs: ConfigRow[]): string {\n  const rows = configs\n    .map((row) => {\n      const safeId = escapeHtml(row.id);\n      // A named config leads with that name (what generateConfigName gave\n      // it, or whatever the configurator renamed it to) and keeps the id\n      // underneath in monospace — still visible and copyable, just not the\n      // headline anymore. A pre-migration config with no name yet falls\n      // back to exactly the old behavior: the id as the link text, nothing\n      // underneath.\n      const label = row.name ? escapeHtml(row.name) : safeId;\n      const idSubtext = row.name\n        ? `
${safeId}`\n        : \"\";\n      return `\n        ${label}${idSubtext}\n        ${escapeHtml(summarizeSelection(row))}\n        ${row.deviceCount}\n        ${escapeHtml(new Date(row.updatedAt).toLocaleString())}\n      `;\n    })\n    .join(\"\");\n  const body = `\n    All configs
\n    + New config
\n    \n      \n      ${rows || ``}\n    Config Favorites Devices Updated
No configs yet.
`;\n  return pageShell(\"Widget favorites — All configs\", body);\n}\n\nexport type DeviceConfigRow = {\n  deviceId: string;\n  name: string | null;\n  configId: string;\n  configName: string | null;\n  configFound: boolean;\n  createdAt: string;\n};\n\n// GET /devices is intentionally not linked from the current configurator\n// layout. It is a read-only view of device_configs, with a config link only\n// when the LEFT JOIN in configStore confirms the referenced row still exists.\nexport function deviceConfigIndexDocument(devices: DeviceConfigRow[]): string {\n  const rows = devices.map((device) => {\n    const safeDeviceId = escapeHtml(device.deviceId);\n    const safeConfigId = escapeHtml(device.configId);\n    const safeName = device.name ? escapeHtml(device.name) : \"—\";\n    const configLabel = device.configName ? escapeHtml(device.configName) : safeConfigId;\n    const configIdSubtext = device.configName\n      ? `
${safeConfigId}`\n      : \"\";\n    const configCell = device.configFound\n      ? `${configLabel}${configIdSubtext}`\n      : `${safeConfigId}
Missing config`;\n    return `\n      ${safeDeviceId}\n      ${safeName}\n      ${configCell}\n      ${escapeHtml(new Date(device.createdAt).toLocaleString())}\n    `;\n  }).join(\"\");\n  const body = `\n    Devices
\n    \n      \n      ${rows || ``}\n    Device Name Config Linked
No devices yet.
`;\n  return pageShell(\"Widget favorites — Devices\", body);\n}\n\nexport type ConfigNewOptions = {\n  formAction: string;\n  config: StoredConfig;\n  name: string;\n};\n\n// GET /config/new. No id yet, so no top nav — Settings/Devices/Pair/Preview\n// only make sense once POST /config/new has actually created a row. `name`\n// is generated eagerly by the caller (main.ts calls\n// lib/configStore.ts's generateConfigName before rendering this page, not\n// after creating the row) so the configurator sees the default here and\n// can edit or clear it before the config even exists, rather than only\n// discovering it after the fact on the Settings page.\nexport function configNewDocument(opts: ConfigNewOptions): string {\n  const { formAction, config, name } = opts;\n  const body = `\n    ← All configs
\n    Widget favorites
\n    \n      \n        Name\n        \n      
\n      \n        Sports (used only when no teams below are selected)\n        ${sportCheckboxes(config.sports)}\n      
\n      ${teamCheckboxesBySport(config.teams)}\n      \n    
`;\n  return pageShell(\"Widget favorites — New\", body);\n}\n\nexport type ConfigSettingsOptions = {\n  id: string;\n  formAction: string;\n  config: StoredConfig;\n  name: string | null;\n  saved?: boolean;\n};\n\n// GET/POST /config/:id. The sports/teams form, plus the config's own name\n// — auto-generated at creation (lib/configStore.ts's generateConfigName)\n// but editable here like any other setting, in the same submit. Device\n// list and pairing moved to their own routes/documents below.\nexport function configSettingsDocument(opts: ConfigSettingsOptions): string {\n  const { id, formAction, config, name, saved } = opts;\n  const safeName = name ? escapeHtml(name) : \"\";\n  const body = `\n    ${configNav(id, \"settings\")}\n    Widget favorites
\n    ${saved ? \"Saved.
\" : \"\"}\n    \n      \n        Name\n        \n      
\n      \n        Sports (used only when no teams below are selected)\n        ${sportCheckboxes(config.sports)}\n      
\n      ${teamCheckboxesBySport(config.teams)}\n      \n    
`;\n  return pageShell(\"Widget favorites — Settings\", body);\n}\n\nexport type ConfigPersonalizationOptions = {\n  id: string;\n  formAction: string;\n  personalization: PersonalizationView;\n  saved?: boolean;\n};\n\n// GET/POST /config/:id/personalization — presentation settings, kept\n// separate from Settings' sports/teams (\"what to show\") on purpose: this\n// is \"how to show it,\" a different question with its own growth path\n// (lib/configStore.ts's configs.personalization is a JSON column\n// specifically so more of these can land here later without touching the\n// sports/teams half of the row or this route's URL). The first setting is\n// the intraday-vs-day filter: whether a completed game keeps showing\n// (captioned END) for the rest of its day, or disappears from the list\n// the moment it ends. Rendered as a  always submits one of its two\n// named values.\nexport function configPersonalizationDocument(\n  opts: ConfigPersonalizationOptions,\n): string {\n  const { id, formAction, personalization, saved } = opts;\n  const body = `\n    ${configNav(id, \"personalization\")}\n    Personalization
\n    ${saved ? \"Saved.
\" : \"\"}\n    \n      \n        Ended games\n        \n      
\n      \n    
`;\n  return pageShell(\"Widget favorites — Personalization\", body);\n}\n\nexport type ConfigDevicesOptions = {\n  id: string;\n  devices: PairedDeviceView[];\n  deviceActionPath: (deviceId: string) => string;\n};\n\n// GET /config/:id/devices.\nexport function configDevicesDocument(opts: ConfigDevicesOptions): string {\n  const { id, devices, deviceActionPath } = opts;\n  const body = `\n    ${configNav(id, \"devices\")}\n    Paired devices
\n    ${deviceListMarkup(devices, deviceActionPath)}`;\n  return pageShell(\"Widget favorites — Devices\", body);\n}\n\nexport type LinkableDeviceView = { deviceId: string; name: string | null };\n\nexport type ConfigPairOptions = {\n  id: string;\n  codeActionPath: string;\n  linkActionPath: string;\n  devices: LinkableDeviceView[];\n  pairing?: { code: string; expiresAt: string } | null;\n  expiredCodes: ExpiredCodeView[];\n  linked?: boolean;\n};\n\n// GET /config/:id/pair, POST /config/:id/pair, and POST\n// /config/:id/code share this page. The select only contains existing device\n// rows owned by another config; submitting it reassigns that association.\nexport function configPairDocument(opts: ConfigPairOptions): string {\n  const {\n    id,\n    codeActionPath,\n    linkActionPath,\n    devices,\n    pairing,\n    expiredCodes,\n    linked,\n  } = opts;\n  const deviceOptions = devices.map((device) => {\n    const safeId = escapeHtml(device.deviceId);\n    const label = device.name\n      ? `${escapeHtml(device.name)} — ${safeId}`\n      : safeId;\n    return ``;\n  }).join(\"\");\n  const linkForm = deviceOptions\n    ? `\n        \n        \n      
`\n    : \"Every known device is already linked to this config.
\";\n  const body = `\n    ${configNav(id, \"pair\")}\n    Pair a device
\n    ${linked ? \"Device linked.
\" : \"\"}\n    \n      Link an existing device
\n      ${linkForm}\n    
\n    \n      Pair with a code
\n      
\n      ${\n    pairing\n      ? `Code: ${pairing.code} — enter this in the app. Expires ${\n        new Date(pairing.expiresAt).toLocaleString()\n      }. Reusable until then, so the same code can pair more than one device.
`\n      : \"\"\n  }\n    
\n    ${expiredCodesMarkup(expiredCodes)}`;\n  return pageShell(\"Widget favorites — Pair a device\", body);\n}\n\nexport type ConfigPreviewOptions =\n  | { id: string; ok: true; items: ConfigPreviewItem[]; rawJson: string }\n  | { id: string; ok: false; error: string };\n\n// GET /config/:id/preview — a read-only render of what /config/resolve\n// would currently hand the widget for this exact config: the same items\n// list as a table (for a quick sanity check) plus the full response\n// pretty-printed in a  (for inspecting the exact contract, the way a\n// helper would otherwise need curl or the browser's devtools to see). This\n// is genuinely live: main.ts's handler runs the same slate-picking path\n// `/` itself does — real outbound Sleeper calls, not a canned fixture — so\n// `ok: false` is a real possibility (e.g. Sleeper unreachable) that gets\n// its own error state rather than a broken page.\nexport function configPreviewDocument(opts: ConfigPreviewOptions): string {\n  const { id } = opts;\n  const body = `\n    ${configNav(id, \"preview\")}\n    Preview
\n    ${\n    opts.ok\n      ? `${previewItemsMarkup(opts.items)}\n    \n      Raw response
\n      ${escapeHtml(opts.rawJson)}
\n    
`\n      : `Couldn't build a preview: ${escapeHtml(opts.error)}
`\n  }`;\n  return pageShell(\"Widget favorites — Preview\", body);\n}",["D",1788290293174],{"_32":58,"_34":59,"_35":51,"_37":61,"_40":62,"_42":14,"_43":44,"_26":27},{"_32":58,"_34":59,"_35":51,"_37":60},"lib/configStore.ts","2157b1f2-a31a-11f1-8fad-1607ee4eb77e","configStore.ts","// The val's only persistent state, and its only other outbound I/O besides\n// lib/sleeper.ts's Sleeper calls — see that file's header for why pure logic\n// lives elsewhere. This one isn't reachable from tests/ either (bin/ci runs\n// under `node --experimental-strip-types`, which can't resolve the\n// `https://esm.town/...` specifier below), so it's verified by hitting the\n// deployed endpoint's /config/* routes instead, same as sleeper.ts and\n// render/png.ts. See docs/widget-config-plan.md for the schema rationale:\n// `configs` holds the helper-set favorite teams/sports (an attribute of one\n// config, stored as JSON, not a joined table); `device_configs` is the one\n// association this prototype needs (a device belongs to at most one config,\n// enforced by device_id being its primary key — re-pairing replaces, not\n// duplicates); `pairing_codes` is short-lived and reusable until it expires,\n// on purpose, so one code can pair several family devices to the same\n// config without regenerating it each time.\n\nimport { sqlite } from \"https://esm.town/v/std/sqlite/main.ts\";\nimport { DEFAULT_PERSONALIZATION, type Personalization, type StoredConfig } from \"./config.ts\";\n\nconst CODE_ALPHABET = \"ABCDEFGHJKMNPQRSTUVWXYZ23456789\"; // no 0/O/1/I/L — read aloud over a phone call\nconst CODE_LENGTH = 6;\nconst CODE_TTL_SECONDS = 30 * 60;\n\nlet schemaReady: Promise | null = null;\n\n// Idempotent (CREATE TABLE IF NOT EXISTS), but memoized per process so a\n// warm val doesn't re-run three statements on every request — only the first\n// call after a cold start actually hits sqlite. The memo is cleared on\n// failure, not just on success: caching a rejected promise here would turn\n// one transient sqlite hiccup into every subsequent request in this process\n// failing until the val recycles.\nexport function ensureSchema(): Promise {\n  if (!schemaReady) {\n    schemaReady = sqlite.batch([\n      {\n        sql: `CREATE TABLE IF NOT EXISTS configs (\n          id TEXT PRIMARY KEY,\n          sports TEXT NOT NULL DEFAULT '[]',\n          teams TEXT NOT NULL DEFAULT '[]',\n          created_at TEXT NOT NULL,\n          updated_at TEXT NOT NULL\n        )`,\n        args: [],\n      },\n      {\n        sql: `CREATE TABLE IF NOT EXISTS pairing_codes (\n          code TEXT PRIMARY KEY,\n          config_id TEXT NOT NULL,\n          expires_at TEXT NOT NULL,\n          created_at TEXT NOT NULL\n        )`,\n        args: [],\n      },\n      {\n        sql: `CREATE TABLE IF NOT EXISTS device_configs (\n          device_id TEXT PRIMARY KEY,\n          config_id TEXT NOT NULL,\n          created_at TEXT NOT NULL,\n          name TEXT\n        )`,\n        args: [],\n      },\n      {\n        // Keyed by device_id independently of device_configs (not a FK) so\n        // an APNs token can land before pairing does — AppDelegate.swift\n        // uploads it on every app launch, regardless of pairing state.\n        // lib/push.ts joins this against device_configs at send time to\n        // find who to notify for a given config.\n        sql: `CREATE TABLE IF NOT EXISTS device_tokens (\n          device_id TEXT PRIMARY KEY,\n          apns_token TEXT NOT NULL,\n          updated_at TEXT NOT NULL\n        )`,\n        args: [],\n      },\n    ])\n      .then(() => undefined)\n      // A device_configs table created before the `name` column existed\n      // won't pick it up from CREATE TABLE IF NOT EXISTS above — ALTER TABLE\n      // is the migration path (see the sqlite-storage skill), and it's run\n      // outside the batch/transaction above so its expected failure on an\n      // already-migrated table (duplicate column) doesn't roll back the rest\n      // of schema setup.\n      .then(() => sqlite.execute(\"ALTER TABLE device_configs ADD COLUMN name TEXT\").then(() => undefined).catch(() => undefined))\n      // Same story for configs.name (added alongside generateConfigName\n      // below): a config row created before this column existed won't pick\n      // it up from CREATE TABLE IF NOT EXISTS, and its name stays NULL\n      // until the configurator sets one — that's the backwards-compat\n      // story, not a backfill.\n      .then(() => sqlite.execute(\"ALTER TABLE configs ADD COLUMN name TEXT\").then(() => undefined).catch(() => undefined))\n      // configs.personalization: a JSON blob (see lib/config.ts's\n      // Personalization) rather than its own column-per-setting, so a\n      // later addition to that shape needs no further ALTER TABLE. A\n      // pre-migration or never-set row is NULL, which parsePersonalization\n      // below treats as DEFAULT_PERSONALIZATION — today's existing\n      // behavior, not a backfill.\n      .then(() => sqlite.execute(\"ALTER TABLE configs ADD COLUMN personalization TEXT\").then(() => undefined).catch(() => undefined))\n      .catch((err) => {\n        schemaReady = null;\n        throw err;\n      });\n  }\n  return schemaReady;\n}\n\nfunction nowIso(): string {\n  return new Date().toISOString();\n}\n\n// pairing_codes.expires_at is a val-scoped (not branch-scoped) TEXT column,\n// so a branch that writes it in a different format — e.g. dev's epoch-second\n// integers, coerced to strings like \"1788040820.0\" by SQLite's TEXT affinity\n// — lands in the same table main reads. A naive string compare treats every\n// such row as permanently expired, since \"1...\" always sorts below the \"2...\"\n// ISO strings main writes. Parse defensively so a stray non-ISO row can't\n// silently break pairing for a code that hasn't actually expired.\nfunction expiresAtMs(value: string): number {\n  const asFloat = Number(value);\n  if (Number.isFinite(asFloat) && /^-?\\d+(\\.\\d+)?$/.test(value.trim())) {\n    return asFloat * 1000;\n  }\n  return Date.parse(value);\n}\n\nfunction randomCode(): string {\n  const bytes = new Uint8Array(CODE_LENGTH);\n  crypto.getRandomValues(bytes);\n  return Array.from(bytes, (b) => CODE_ALPHABET[b % CODE_ALPHABET.length]).join(\"\");\n}\n\n// ---- automatic config names ----\n//\n// A config name is a label for the configurator's own benefit (\"which of\n// my three configs is this\"), not an identifier — the UUID stays the\n// capability token. That's why generateConfigName below is the non-\n// unique-checked half of the two-generator pattern it's ported from (a\n// Ruby SlugGenerator that also had a DB-uniqueness-checked `generate` for\n// actual unique slugs): there's no DB round-trip here, no retry-on-\n// collision, just a locally-random word pair. Word lists and the reserved-\n// word filter are carried over verbatim from that source; RESERVED_WORDS\n// doesn't currently intersect either list, but it's cheap insurance\n// against a future edit to either list introducing a collision.\nconst RESERVED_WORDS = new Set([\n  \"admin\", \"api\", \"app\", \"assets\", \"billing\", \"blog\", \"cable\", \"cdn\", \"claim\", \"contact\",\n  \"dev\", \"dns\", \"ftp\", \"help\", \"imap\", \"localhost\", \"mail\", \"manage\", \"me\", \"media\", \"monitor\",\n  \"news\", \"ns1\", \"ns2\", \"platform\", \"pop3\", \"postmaster\", \"provision\", \"root\", \"smtp\",\n  \"staging\", \"status\", \"store\", \"support\", \"system\", \"vpn\", \"webmaster\", \"www\",\n]);\n\nconst ADJECTIVES = [\n  \"amber\", \"ancient\", \"arctic\", \"bold\", \"brave\", \"bright\", \"brisk\", \"calm\", \"cedar\",\n  \"cherry\", \"cider\", \"citrus\", \"clear\", \"clever\", \"cobalt\", \"cozy\", \"crisp\", \"crystal\",\n  \"daring\", \"dawn\", \"deep\", \"dew\", \"eager\", \"early\", \"easy\", \"fern\", \"fierce\", \"flash\",\n  \"fresh\", \"gentle\", \"giant\", \"glacial\", \"golden\", \"grand\", \"happy\", \"hollow\",\n  \"humble\", \"icy\", \"indigo\", \"island\", \"ivory\", \"jade\", \"jolly\", \"keen\", \"kind\",\n  \"lemon\", \"light\", \"lively\", \"lucky\", \"lush\", \"lunar\", \"maple\", \"merry\", \"mild\",\n  \"mint\", \"misty\", \"modern\", \"mossy\", \"muted\", \"mystic\", \"nimble\", \"noble\", \"oak\",\n  \"ocean\", \"olive\", \"open\", \"pacific\", \"pastel\", \"peaceful\", \"peach\", \"pine\",\n  \"plum\", \"polar\", \"proud\", \"quiet\", \"radiant\", \"rapid\", \"rare\", \"rocky\",\n  \"royal\", \"rustic\", \"sage\", \"sandy\", \"serene\", \"shady\", \"sharp\", \"silver\",\n  \"sleek\", \"slim\", \"smart\", \"smooth\", \"snappy\", \"solar\", \"solid\", \"starry\",\n  \"steady\", \"stone\", \"sunny\", \"swift\", \"tawny\", \"teal\", \"tiny\", \"tranquil\",\n  \"velvet\", \"vibrant\", \"vivid\", \"warm\", \"wild\", \"windy\", \"wise\", \"witty\",\n  \"wooden\", \"woven\", \"youthful\", \"zenith\",\n];\n\nconst NOUNS = [\n  \"anchor\", \"apple\", \"arrow\", \"atlas\", \"axle\", \"badger\", \"banjo\", \"barrel\", \"basil\",\n  \"beacon\", \"bear\", \"beaver\", \"bison\", \"blade\", \"bloom\", \"bluebird\", \"boulder\",\n  \"brook\", \"cabin\", \"canoe\", \"cardinal\", \"cedar\", \"chest\", \"chimney\", \"clover\",\n  \"comet\", \"coral\", \"coyote\", \"crest\", \"crystal\", \"dagger\", \"dew\", \"dolphin\",\n  \"echo\", \"ember\", \"falcon\", \"fawn\", \"fern\", \"finch\", \"flame\", \"flint\", \"float\",\n  \"foal\", \"forge\", \"fox\", \"frost\", \"gazelle\", \"gem\", \"glade\", \"grove\", \"harbor\",\n  \"hawk\", \"helm\", \"heron\", \"holly\", \"horizon\", \"hummingbird\", \"ivy\", \"jaguar\",\n  \"jasper\", \"jay\", \"kayak\", \"kettle\", \"kite\", \"lark\", \"laurel\", \"leaf\", \"lemon\",\n  \"lily\", \"linden\", \"lobster\", \"loon\", \"lynx\", \"maple\", \"meadow\", \"meteor\", \"mint\",\n  \"moon\", \"moss\", \"mountain\", \"oak\", \"orbit\", \"otter\", \"oyster\", \"palm\", \"panda\",\n  \"parrot\", \"pearl\", \"pelican\", \"pine\", \"plover\", \"poppy\", \"prism\", \"quail\",\n  \"quartz\", \"raven\", \"reef\", \"ridge\", \"ripple\", \"river\", \"robin\", \"rocket\",\n  \"rose\", \"sage\", \"salmon\", \"sandpiper\", \"shore\", \"skylark\", \"slate\", \"sparrow\",\n  \"sprout\", \"spruce\", \"stag\", \"starling\", \"stone\", \"stream\", \"summit\", \"swift\",\n  \"teal\", \"thorn\", \"tide\", \"timber\", \"torch\", \"trail\", \"trout\", \"tulip\", \"turtle\",\n  \"valley\", \"vine\", \"violet\", \"vista\", \"wave\", \"willow\", \"wolf\", \"wren\", \"zenith\",\n];\n\n// Exported so main.ts's GET /config/new can generate a candidate eagerly\n// and show it in the form — see createConfig below for why generation\n// moved out of creation itself.\nexport function generateConfigName(): string {\n  for (let attempt = 0; attempt < 10; attempt++) {\n    const adjective = ADJECTIVES[Math.floor(Math.random() * ADJECTIVES.length)];\n    const noun = NOUNS[Math.floor(Math.random() * NOUNS.length)];\n    if (RESERVED_WORDS.has(adjective) || RESERVED_WORDS.has(noun)) continue;\n    return `${adjective}-${noun}`;\n  }\n  return `config-${crypto.randomUUID().slice(0, 8)}`;\n}\n\n// The name is the caller's to supply, not generated in here — main.ts's\n// GET /config/new calls generateConfigName() eagerly so the configurator\n// sees the default and gets a chance to change it before the row even\n// exists, and POST /config/new passes back whatever that form submits\n// (edited, untouched, or cleared). A pre-migration row's NULL, and a\n// deliberately-cleared name here, look identical — both are just \"no name\n// on file,\" which is the point of the column being nullable.\nexport async function createConfig(\n  config: StoredConfig = { sports: [], teams: [] },\n  name: string | null = null,\n): Promise<{ id: string }> {\n  await ensureSchema();\n  const id = crypto.randomUUID();\n  const ts = nowIso();\n  await sqlite.execute({\n    sql: \"INSERT INTO configs (id, name, sports, teams, created_at, updated_at) VALUES (?, ?, ?, ?, ?, ?)\",\n    args: [id, name, JSON.stringify(config.sports), JSON.stringify(config.teams), ts, ts],\n  });\n  return { id };\n}\n\nexport type ConfigRecord = StoredConfig & { name: string | null };\n\nexport async function getConfig(id: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({ sql: \"SELECT sports, teams, name FROM configs WHERE id = ?\", args: [id] });\n  const row = result.rows[0] as { sports: string; teams: string; name: string | null } | undefined;\n  if (!row) return null;\n  return { sports: JSON.parse(row.sports), teams: JSON.parse(row.teams), name: row.name };\n}\n\n// The configurator overriding (or clearing) generateConfigName's default —\n// same empty-string-is-null convention as renameDevice below, and the same\n// \"own label, not an identifier\" reasoning: names don't have to be unique,\n// so there's no collision check here either.\nexport async function renameConfig(id: string, name: string | null): Promise {\n  await ensureSchema();\n  const trimmed = name?.trim() || null;\n  const result = await sqlite.execute({\n    sql: \"UPDATE configs SET name = ?, updated_at = ? WHERE id = ?\",\n    args: [trimmed, nowIso(), id],\n  });\n  return result.rowsAffected > 0;\n}\n\n// Silently trusts its caller has already filtered sports/teams against\n// lib/catalog.ts — see render/configHtml.ts, whose checkboxes are generated\n// from that same table, which is what makes an invalid value structurally\n// hard to submit in the first place. The real safety net is downstream:\n// /config/resolve's redirect lands on `/`, where resolveParams validates\n// again regardless of what's stored here. Two independent validators would\n// only be able to drift from each other.\nexport async function updateConfig(id: string, config: StoredConfig): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: \"UPDATE configs SET sports = ?, teams = ?, updated_at = ? WHERE id = ?\",\n    args: [JSON.stringify(config.sports), JSON.stringify(config.teams), nowIso(), id],\n  });\n  return result.rowsAffected > 0;\n}\n\n// Shared by getPersonalization and resolveDevice below — a malformed or\n// absent blob (NULL column, JSON that doesn't parse, or a value missing\n// intradayFilter) all fall back to DEFAULT_PERSONALIZATION rather than\n// erroring, same never-fail posture as this file's other readers.\nfunction parsePersonalization(raw: string | null): Personalization {\n  if (!raw) return DEFAULT_PERSONALIZATION;\n  try {\n    const parsed = JSON.parse(raw) as { intradayFilter?: unknown };\n    return { intradayFilter: parsed.intradayFilter === true };\n  } catch {\n    return DEFAULT_PERSONALIZATION;\n  }\n}\n\n// What GET /config/:id/personalization reads — the \"how to present it\"\n// half of a config, kept in its own column from updateConfig's \"what to\n// show\" half above (see lib/config.ts's Personalization header for why).\nexport async function getPersonalization(id: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({ sql: \"SELECT personalization FROM configs WHERE id = ?\", args: [id] });\n  const row = result.rows[0] as { personalization: string | null } | undefined;\n  return parsePersonalization(row?.personalization ?? null);\n}\n\n// The configurator's side of POST /config/:id/personalization. Bumps\n// updated_at like updateConfig does — a personalization change is a\n// widget-visible change to this config the same way sports/teams are.\nexport async function updatePersonalization(id: string, personalization: Personalization): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: \"UPDATE configs SET personalization = ?, updated_at = ? WHERE id = ?\",\n    args: [JSON.stringify(personalization), nowIso(), id],\n  });\n  return result.rowsAffected > 0;\n}\n\nexport type ConfigSummary = {\n  id: string;\n  name: string | null;\n  sports: string[];\n  teams: string[];\n  createdAt: string;\n  updatedAt: string;\n  deviceCount: number;\n};\n\n// What GET /config (the prototype-stage index of every config — see\n// render/configHtml.ts's configIndexDocument for why that route is allowed\n// to list every id) reads. A LEFT JOIN + COUNT rather than a second\n// per-row query: the index's whole purpose is telling configs apart, and\n// device count is effectively free at this table's scale (a handful of\n// configs, not a paginated one).\nexport async function listAllConfigs(): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute(\n    `SELECT c.id, c.name, c.sports, c.teams, c.created_at, c.updated_at, COUNT(dc.device_id) AS device_count\n     FROM configs c\n     LEFT JOIN device_configs dc ON dc.config_id = c.id\n     GROUP BY c.id\n     ORDER BY c.updated_at DESC`,\n  );\n  return (\n    result.rows as {\n      id: string;\n      name: string | null;\n      sports: string;\n      teams: string;\n      created_at: string;\n      updated_at: string;\n      device_count: number;\n    }[]\n  ).map((row) => ({\n    id: row.id,\n    name: row.name,\n    sports: JSON.parse(row.sports),\n    teams: JSON.parse(row.teams),\n    createdAt: row.created_at,\n    updatedAt: row.updated_at,\n    deviceCount: row.device_count,\n  }));\n}\n\n// Reusable until it expires (not single-use) — one code lets a helper pair\n// every device in a family to the same config without regenerating it per\n// device. Collisions are astronomically unlikely at this scale and are left\n// unhandled rather than retried, matching this codebase's general posture of\n// not engineering for inputs that can't realistically occur.\nexport async function createPairingCode(configId: string): Promise<{ code: string; expiresAt: string }> {\n  await ensureSchema();\n  const code = randomCode();\n  const now = new Date();\n  const ts = now.toISOString();\n  const expiresAt = new Date(now.getTime() + CODE_TTL_SECONDS * 1000).toISOString();\n  await sqlite.execute({\n    sql: \"INSERT INTO pairing_codes (code, config_id, expires_at, created_at) VALUES (?, ?, ?, ?)\",\n    args: [code, configId, expiresAt, ts],\n  });\n  return { code, expiresAt };\n}\n\nexport type ExpiredPairingCode = { code: string; expiresAt: string; createdAt: string };\n\n// What GET /config/:id/pair lists below the live-code section — this\n// config's past pairing codes that are no longer usable. Nothing prunes\n// pairing_codes, so old rows just sit there; filtering happens in JS with\n// expiresAtMs rather than a SQL string compare on expires_at, for the same\n// cross-branch-format reason expiresAtMs's own header explains.\nexport async function listExpiredPairingCodes(configId: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: \"SELECT code, expires_at, created_at FROM pairing_codes WHERE config_id = ? ORDER BY created_at DESC\",\n    args: [configId],\n  });\n  const now = Date.now();\n  return (result.rows as { code: string; expires_at: string; created_at: string }[])\n    .filter((row) => expiresAtMs(row.expires_at) < now)\n    .map((row) => ({ code: row.code, expiresAt: row.expires_at, createdAt: row.created_at }));\n}\n\n// The receiver's half of pairing: it already has its own device id (client-\n// generated, per docs/widget-config-plan.md) and types in the code the\n// helper's browser is showing. The upsert on device_id (the pivot table's\n// primary key) is what makes re-pairing replace an existing binding rather\n// than duplicate it.\nexport async function pairDevice(\n  code: string,\n  deviceId: string,\n): Promise<{ ok: true; configId: string } | { ok: false; reason: \"not_found\" | \"expired\" }> {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: \"SELECT config_id, expires_at FROM pairing_codes WHERE code = ?\",\n    args: [code.trim().toUpperCase()],\n  });\n  const row = result.rows[0] as { config_id: string; expires_at: string } | undefined;\n  if (!row) return { ok: false, reason: \"not_found\" };\n  if (expiresAtMs(row.expires_at) < Date.now()) return { ok: false, reason: \"expired\" };\n\n  // Upsert rather than INSERT OR REPLACE: REPLACE deletes and reinserts the\n  // whole row, which would wipe out a name the configurator already set on\n  // this device the moment it re-pairs to a different config. ON CONFLICT\n  // DO UPDATE only touches config_id/created_at, leaving name untouched.\n  await sqlite.execute({\n    sql: `INSERT INTO device_configs (device_id, config_id, created_at, name) VALUES (?, ?, ?, NULL)\n          ON CONFLICT(device_id) DO UPDATE SET config_id = excluded.config_id, created_at = excluded.created_at`,\n    args: [deviceId, row.config_id, nowIso()],\n  });\n  return { ok: true, configId: row.config_id };\n}\n\n// The configurator's side of naming: they're the one looking at a list of\n// paired devices trying to tell \"dad\" from \"mom\", so naming happens on the\n// /config/:id page, not at pairing time. Empty string is treated the same\n// as null (an unnamed device), not stored as a zero-length name.\nexport async function renameDevice(deviceId: string, name: string | null): Promise {\n  await ensureSchema();\n  const trimmed = name?.trim() || null;\n  const result = await sqlite.execute({\n    sql: \"UPDATE device_configs SET name = ? WHERE device_id = ?\",\n    args: [trimmed, deviceId],\n  });\n  return result.rowsAffected > 0;\n}\n\nexport type PairedDevice = {\n  deviceId: string;\n  name: string | null;\n  createdAt: string;\n  pushRegistered: boolean;\n  tokenUpdatedAt: string | null;\n};\n\n// What /config/:id/devices lists so the configurator can see and name each\n// device paired to that config. LEFT JOINed against device_tokens (not a\n// second per-row query) so the page can also show whether a device has\n// registered for push and when its token last updated — device_tokens is\n// keyed by device_id independently of device_configs (see ensureSchema's\n// header), so a paired device with no token upload yet just gets nulls here.\nexport async function listDevicesForConfig(configId: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: `SELECT dc.device_id, dc.name, dc.created_at, dt.updated_at AS token_updated_at\n          FROM device_configs dc\n          LEFT JOIN device_tokens dt ON dt.device_id = dc.device_id\n          WHERE dc.config_id = ?\n          ORDER BY dc.created_at`,\n    args: [configId],\n  });\n  return (\n    result.rows as { device_id: string; name: string | null; created_at: string; token_updated_at: string | null }[]\n  ).map((row) => ({\n    deviceId: row.device_id,\n    name: row.name,\n    createdAt: row.created_at,\n    pushRegistered: row.token_updated_at != null,\n    tokenUpdatedAt: row.token_updated_at,\n  }));\n}\n\nexport type LinkableDevice = { deviceId: string; name: string | null };\n\n// Existing device rows that can be reassigned to this config. Devices\n// already linked here are excluded so the pairing form only offers actions\n// that would change an association.\nexport async function listLinkableDevices(configId: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: `SELECT device_id, name\n          FROM device_configs\n          WHERE config_id <> ?\n          ORDER BY COALESCE(name, device_id), device_id`,\n    args: [configId],\n  });\n  return (result.rows as { device_id: string; name: string | null }[]).map((row) => ({\n    deviceId: row.device_id,\n    name: row.name,\n  }));\n}\n\n// Reassign an existing device without creating a row from an arbitrary form\n// value. As with code-based pairing, the name survives and created_at marks\n// when the device became associated with this config.\nexport async function linkExistingDevice(configId: string, deviceId: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: `UPDATE device_configs\n          SET config_id = ?, created_at = ?\n          WHERE device_id = ? AND config_id <> ?`,\n    args: [configId, nowIso(), deviceId, configId],\n  });\n  return result.rowsAffected === 1;\n}\n\nexport type DeviceStatus = { configId: string; name: string | null; sports: string[]; teams: string[] };\n\n// What the app's diagnostics screen reads (GET /device/:deviceId) — this\n// device's full pairing status, not just the sports/teams resolveDevice()\n// below returns for the redirect path. Kept separate so that route's\n// never-null-error contract doesn't grow fields it doesn't need.\nexport async function getDeviceStatus(deviceId: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: `SELECT dc.config_id, dc.name, c.sports, c.teams FROM device_configs dc\n          JOIN configs c ON c.id = dc.config_id\n          WHERE dc.device_id = ?`,\n    args: [deviceId],\n  });\n  const row = result.rows[0] as { config_id: string; name: string | null; sports: string; teams: string } | undefined;\n  if (!row) return null;\n  return { configId: row.config_id, name: row.name, sports: JSON.parse(row.sports), teams: JSON.parse(row.teams) };\n}\n\nexport type ResolvedDeviceConfig = StoredConfig & { personalization: Personalization };\n\n// What /config/resolve calls. Returns null for an unknown or never-paired\n// device — not an error, just \"nothing to apply\" — which is what lets that\n// route fall back to the existing all-sports default instead of failing.\n// Carries personalization alongside sports/teams (one query, not a second\n// round trip) since buildResolvedUrl needs both to build the redirect.\nexport async function resolveDevice(deviceId: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: `SELECT c.sports, c.teams, c.personalization FROM device_configs dc\n          JOIN configs c ON c.id = dc.config_id\n          WHERE dc.device_id = ?`,\n    args: [deviceId],\n  });\n  const row = result.rows[0] as { sports: string; teams: string; personalization: string | null } | undefined;\n  if (!row) return null;\n  return {\n    sports: JSON.parse(row.sports),\n    teams: JSON.parse(row.teams),\n    personalization: parsePersonalization(row.personalization),\n  };\n}\n\n// The receiver's half of push registration (POST /device/token,\n// AppDelegate.swift's didRegisterForRemoteNotificationsWithDeviceToken) —\n// upsert, not insert, since tokens rotate and re-registering is expected,\n// not an error. Independent of device_configs on purpose: see the\n// device_tokens table comment above ensureSchema.\nexport async function saveDeviceToken(deviceId: string, token: string): Promise {\n  await ensureSchema();\n  await sqlite.execute({\n    sql: `INSERT INTO device_tokens (device_id, apns_token, updated_at) VALUES (?, ?, ?)\n          ON CONFLICT(device_id) DO UPDATE SET apns_token = excluded.apns_token, updated_at = excluded.updated_at`,\n    args: [deviceId, token, nowIso()],\n  });\n}\n\nexport async function deleteDeviceToken(deviceId: string): Promise {\n  await ensureSchema();\n  await sqlite.execute({ sql: \"DELETE FROM device_tokens WHERE device_id = ?\", args: [deviceId] });\n}\n\n// What lib/push.ts's notifyConfigDevices calls: every APNs token currently\n// belonging to a device paired to this config. A device paired but never\n// registered for push (or one whose token upload hasn't landed yet) simply\n// doesn't appear here — same \"nothing to do\" posture as resolveDevice.\nexport async function getTokensForConfig(configId: string): Promise<{ deviceId: string; token: string }[]> {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: `SELECT dt.device_id, dt.apns_token FROM device_tokens dt\n          JOIN device_configs dc ON dc.device_id = dt.device_id\n          WHERE dc.config_id = ?`,\n    args: [configId],\n  });\n  return (result.rows as { device_id: string; apns_token: string }[]).map((row) => ({\n    deviceId: row.device_id,\n    token: row.apns_token,\n  }));\n}\n","// The val's only persistent state, and its only other outbound I/O besides\n// lib/sleeper.ts's Sleeper calls — see that file's header for why pure logic\n// lives elsewhere. This one isn't reachable from tests/ either (bin/ci runs\n// under `node --experimental-strip-types`, which can't resolve the\n// `https://esm.town/...` specifier below), so it's verified by hitting the\n// deployed endpoint's /config/* routes instead, same as sleeper.ts and\n// render/png.ts. See docs/widget-config-plan.md for the schema rationale:\n// `configs` holds the helper-set favorite teams/sports (an attribute of one\n// config, stored as JSON, not a joined table); `device_configs` is the one\n// association this prototype needs (a device belongs to at most one config,\n// enforced by device_id being its primary key — re-pairing replaces, not\n// duplicates); `pairing_codes` is short-lived and reusable until it expires,\n// on purpose, so one code can pair several family devices to the same\n// config without regenerating it each time.\n\nimport { sqlite } from \"https://esm.town/v/std/sqlite/main.ts\";\nimport { DEFAULT_PERSONALIZATION, type Personalization, type StoredConfig } from \"./config.ts\";\n\nconst CODE_ALPHABET = \"ABCDEFGHJKMNPQRSTUVWXYZ23456789\"; // no 0/O/1/I/L — read aloud over a phone call\nconst CODE_LENGTH = 6;\nconst CODE_TTL_SECONDS = 30 * 60;\n\nlet schemaReady: Promise | null = null;\n\n// Idempotent (CREATE TABLE IF NOT EXISTS), but memoized per process so a\n// warm val doesn't re-run three statements on every request — only the first\n// call after a cold start actually hits sqlite. The memo is cleared on\n// failure, not just on success: caching a rejected promise here would turn\n// one transient sqlite hiccup into every subsequent request in this process\n// failing until the val recycles.\nexport function ensureSchema(): Promise {\n  if (!schemaReady) {\n    schemaReady = sqlite.batch([\n      {\n        sql: `CREATE TABLE IF NOT EXISTS configs (\n          id TEXT PRIMARY KEY,\n          sports TEXT NOT NULL DEFAULT '[]',\n          teams TEXT NOT NULL DEFAULT '[]',\n          created_at TEXT NOT NULL,\n          updated_at TEXT NOT NULL\n        )`,\n        args: [],\n      },\n      {\n        sql: `CREATE TABLE IF NOT EXISTS pairing_codes (\n          code TEXT PRIMARY KEY,\n          config_id TEXT NOT NULL,\n          expires_at TEXT NOT NULL,\n          created_at TEXT NOT NULL\n        )`,\n        args: [],\n      },\n      {\n        sql: `CREATE TABLE IF NOT EXISTS device_configs (\n          device_id TEXT PRIMARY KEY,\n          config_id TEXT NOT NULL,\n          created_at TEXT NOT NULL,\n          name TEXT\n        )`,\n        args: [],\n      },\n      {\n        // Keyed by device_id independently of device_configs (not a FK) so\n        // an APNs token can land before pairing does — AppDelegate.swift\n        // uploads it on every app launch, regardless of pairing state.\n        // lib/push.ts joins this against device_configs at send time to\n        // find who to notify for a given config.\n        sql: `CREATE TABLE IF NOT EXISTS device_tokens (\n          device_id TEXT PRIMARY KEY,\n          apns_token TEXT NOT NULL,\n          updated_at TEXT NOT NULL\n        )`,\n        args: [],\n      },\n    ])\n      .then(() => undefined)\n      // A device_configs table created before the `name` column existed\n      // won't pick it up from CREATE TABLE IF NOT EXISTS above — ALTER TABLE\n      // is the migration path (see the sqlite-storage skill), and it's run\n      // outside the batch/transaction above so its expected failure on an\n      // already-migrated table (duplicate column) doesn't roll back the rest\n      // of schema setup.\n      .then(() => sqlite.execute(\"ALTER TABLE device_configs ADD COLUMN name TEXT\").then(() => undefined).catch(() => undefined))\n      // Same story for configs.name (added alongside generateConfigName\n      // below): a config row created before this column existed won't pick\n      // it up from CREATE TABLE IF NOT EXISTS, and its name stays NULL\n      // until the configurator sets one — that's the backwards-compat\n      // story, not a backfill.\n      .then(() => sqlite.execute(\"ALTER TABLE configs ADD COLUMN name TEXT\").then(() => undefined).catch(() => undefined))\n      // configs.personalization: a JSON blob (see lib/config.ts's\n      // Personalization) rather than its own column-per-setting, so a\n      // later addition to that shape needs no further ALTER TABLE. A\n      // pre-migration or never-set row is NULL, which parsePersonalization\n      // below treats as DEFAULT_PERSONALIZATION — today's existing\n      // behavior, not a backfill.\n      .then(() => sqlite.execute(\"ALTER TABLE configs ADD COLUMN personalization TEXT\").then(() => undefined).catch(() => undefined))\n      .catch((err) => {\n        schemaReady = null;\n        throw err;\n      });\n  }\n  return schemaReady;\n}\n\nfunction nowIso(): string {\n  return new Date().toISOString();\n}\n\n// pairing_codes.expires_at is a val-scoped (not branch-scoped) TEXT column,\n// so a branch that writes it in a different format — e.g. dev's epoch-second\n// integers, coerced to strings like \"1788040820.0\" by SQLite's TEXT affinity\n// — lands in the same table main reads. A naive string compare treats every\n// such row as permanently expired, since \"1...\" always sorts below the \"2...\"\n// ISO strings main writes. Parse defensively so a stray non-ISO row can't\n// silently break pairing for a code that hasn't actually expired.\nfunction expiresAtMs(value: string): number {\n  const asFloat = Number(value);\n  if (Number.isFinite(asFloat) && /^-?\\d+(\\.\\d+)?$/.test(value.trim())) {\n    return asFloat * 1000;\n  }\n  return Date.parse(value);\n}\n\nfunction randomCode(): string {\n  const bytes = new Uint8Array(CODE_LENGTH);\n  crypto.getRandomValues(bytes);\n  return Array.from(bytes, (b) => CODE_ALPHABET[b % CODE_ALPHABET.length]).join(\"\");\n}\n\n// ---- automatic config names ----\n//\n// A config name is a label for the configurator's own benefit (\"which of\n// my three configs is this\"), not an identifier — the UUID stays the\n// capability token. That's why generateConfigName below is the non-\n// unique-checked half of the two-generator pattern it's ported from (a\n// Ruby SlugGenerator that also had a DB-uniqueness-checked `generate` for\n// actual unique slugs): there's no DB round-trip here, no retry-on-\n// collision, just a locally-random word pair. Word lists and the reserved-\n// word filter are carried over verbatim from that source; RESERVED_WORDS\n// doesn't currently intersect either list, but it's cheap insurance\n// against a future edit to either list introducing a collision.\nconst RESERVED_WORDS = new Set([\n  \"admin\", \"api\", \"app\", \"assets\", \"billing\", \"blog\", \"cable\", \"cdn\", \"claim\", \"contact\",\n  \"dev\", \"dns\", \"ftp\", \"help\", \"imap\", \"localhost\", \"mail\", \"manage\", \"me\", \"media\", \"monitor\",\n  \"news\", \"ns1\", \"ns2\", \"platform\", \"pop3\", \"postmaster\", \"provision\", \"root\", \"smtp\",\n  \"staging\", \"status\", \"store\", \"support\", \"system\", \"vpn\", \"webmaster\", \"www\",\n]);\n\nconst ADJECTIVES = [\n  \"amber\", \"ancient\", \"arctic\", \"bold\", \"brave\", \"bright\", \"brisk\", \"calm\", \"cedar\",\n  \"cherry\", \"cider\", \"citrus\", \"clear\", \"clever\", \"cobalt\", \"cozy\", \"crisp\", \"crystal\",\n  \"daring\", \"dawn\", \"deep\", \"dew\", \"eager\", \"early\", \"easy\", \"fern\", \"fierce\", \"flash\",\n  \"fresh\", \"gentle\", \"giant\", \"glacial\", \"golden\", \"grand\", \"happy\", \"hollow\",\n  \"humble\", \"icy\", \"indigo\", \"island\", \"ivory\", \"jade\", \"jolly\", \"keen\", \"kind\",\n  \"lemon\", \"light\", \"lively\", \"lucky\", \"lush\", \"lunar\", \"maple\", \"merry\", \"mild\",\n  \"mint\", \"misty\", \"modern\", \"mossy\", \"muted\", \"mystic\", \"nimble\", \"noble\", \"oak\",\n  \"ocean\", \"olive\", \"open\", \"pacific\", \"pastel\", \"peaceful\", \"peach\", \"pine\",\n  \"plum\", \"polar\", \"proud\", \"quiet\", \"radiant\", \"rapid\", \"rare\", \"rocky\",\n  \"royal\", \"rustic\", \"sage\", \"sandy\", \"serene\", \"shady\", \"sharp\", \"silver\",\n  \"sleek\", \"slim\", \"smart\", \"smooth\", \"snappy\", \"solar\", \"solid\", \"starry\",\n  \"steady\", \"stone\", \"sunny\", \"swift\", \"tawny\", \"teal\", \"tiny\", \"tranquil\",\n  \"velvet\", \"vibrant\", \"vivid\", \"warm\", \"wild\", \"windy\", \"wise\", \"witty\",\n  \"wooden\", \"woven\", \"youthful\", \"zenith\",\n];\n\nconst NOUNS = [\n  \"anchor\", \"apple\", \"arrow\", \"atlas\", \"axle\", \"badger\", \"banjo\", \"barrel\", \"basil\",\n  \"beacon\", \"bear\", \"beaver\", \"bison\", \"blade\", \"bloom\", \"bluebird\", \"boulder\",\n  \"brook\", \"cabin\", \"canoe\", \"cardinal\", \"cedar\", \"chest\", \"chimney\", \"clover\",\n  \"comet\", \"coral\", \"coyote\", \"crest\", \"crystal\", \"dagger\", \"dew\", \"dolphin\",\n  \"echo\", \"ember\", \"falcon\", \"fawn\", \"fern\", \"finch\", \"flame\", \"flint\", \"float\",\n  \"foal\", \"forge\", \"fox\", \"frost\", \"gazelle\", \"gem\", \"glade\", \"grove\", \"harbor\",\n  \"hawk\", \"helm\", \"heron\", \"holly\", \"horizon\", \"hummingbird\", \"ivy\", \"jaguar\",\n  \"jasper\", \"jay\", \"kayak\", \"kettle\", \"kite\", \"lark\", \"laurel\", \"leaf\", \"lemon\",\n  \"lily\", \"linden\", \"lobster\", \"loon\", \"lynx\", \"maple\", \"meadow\", \"meteor\", \"mint\",\n  \"moon\", \"moss\", \"mountain\", \"oak\", \"orbit\", \"otter\", \"oyster\", \"palm\", \"panda\",\n  \"parrot\", \"pearl\", \"pelican\", \"pine\", \"plover\", \"poppy\", \"prism\", \"quail\",\n  \"quartz\", \"raven\", \"reef\", \"ridge\", \"ripple\", \"river\", \"robin\", \"rocket\",\n  \"rose\", \"sage\", \"salmon\", \"sandpiper\", \"shore\", \"skylark\", \"slate\", \"sparrow\",\n  \"sprout\", \"spruce\", \"stag\", \"starling\", \"stone\", \"stream\", \"summit\", \"swift\",\n  \"teal\", \"thorn\", \"tide\", \"timber\", \"torch\", \"trail\", \"trout\", \"tulip\", \"turtle\",\n  \"valley\", \"vine\", \"violet\", \"vista\", \"wave\", \"willow\", \"wolf\", \"wren\", \"zenith\",\n];\n\n// Exported so main.ts's GET /config/new can generate a candidate eagerly\n// and show it in the form — see createConfig below for why generation\n// moved out of creation itself.\nexport function generateConfigName(): string {\n  for (let attempt = 0; attempt < 10; attempt++) {\n    const adjective = ADJECTIVES[Math.floor(Math.random() * ADJECTIVES.length)];\n    const noun = NOUNS[Math.floor(Math.random() * NOUNS.length)];\n    if (RESERVED_WORDS.has(adjective) || RESERVED_WORDS.has(noun)) continue;\n    return `${adjective}-${noun}`;\n  }\n  return `config-${crypto.randomUUID().slice(0, 8)}`;\n}\n\n// The name is the caller's to supply, not generated in here — main.ts's\n// GET /config/new calls generateConfigName() eagerly so the configurator\n// sees the default and gets a chance to change it before the row even\n// exists, and POST /config/new passes back whatever that form submits\n// (edited, untouched, or cleared). A pre-migration row's NULL, and a\n// deliberately-cleared name here, look identical — both are just \"no name\n// on file,\" which is the point of the column being nullable.\nexport async function createConfig(\n  config: StoredConfig = { sports: [], teams: [] },\n  name: string | null = null,\n): Promise<{ id: string }> {\n  await ensureSchema();\n  const id = crypto.randomUUID();\n  const ts = nowIso();\n  await sqlite.execute({\n    sql: \"INSERT INTO configs (id, name, sports, teams, created_at, updated_at) VALUES (?, ?, ?, ?, ?, ?)\",\n    args: [id, name, JSON.stringify(config.sports), JSON.stringify(config.teams), ts, ts],\n  });\n  return { id };\n}\n\nexport type ConfigRecord = StoredConfig & { name: string | null };\n\nexport async function getConfig(id: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({ sql: \"SELECT sports, teams, name FROM configs WHERE id = ?\", args: [id] });\n  const row = result.rows[0] as { sports: string; teams: string; name: string | null } | undefined;\n  if (!row) return null;\n  return { sports: JSON.parse(row.sports), teams: JSON.parse(row.teams), name: row.name };\n}\n\n// The configurator overriding (or clearing) generateConfigName's default —\n// same empty-string-is-null convention as renameDevice below, and the same\n// \"own label, not an identifier\" reasoning: names don't have to be unique,\n// so there's no collision check here either.\nexport async function renameConfig(id: string, name: string | null): Promise {\n  await ensureSchema();\n  const trimmed = name?.trim() || null;\n  const result = await sqlite.execute({\n    sql: \"UPDATE configs SET name = ?, updated_at = ? WHERE id = ?\",\n    args: [trimmed, nowIso(), id],\n  });\n  return result.rowsAffected > 0;\n}\n\n// Silently trusts its caller has already filtered sports/teams against\n// lib/catalog.ts — see render/configHtml.ts, whose checkboxes are generated\n// from that same table, which is what makes an invalid value structurally\n// hard to submit in the first place. The real safety net is downstream:\n// /config/resolve's redirect lands on `/`, where resolveParams validates\n// again regardless of what's stored here. Two independent validators would\n// only be able to drift from each other.\nexport async function updateConfig(id: string, config: StoredConfig): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: \"UPDATE configs SET sports = ?, teams = ?, updated_at = ? WHERE id = ?\",\n    args: [JSON.stringify(config.sports), JSON.stringify(config.teams), nowIso(), id],\n  });\n  return result.rowsAffected > 0;\n}\n\n// Shared by getPersonalization and resolveDevice below — a malformed or\n// absent blob (NULL column, JSON that doesn't parse, or a value missing\n// intradayFilter) all fall back to DEFAULT_PERSONALIZATION rather than\n// erroring, same never-fail posture as this file's other readers.\nfunction parsePersonalization(raw: string | null): Personalization {\n  if (!raw) return DEFAULT_PERSONALIZATION;\n  try {\n    const parsed = JSON.parse(raw) as { intradayFilter?: unknown };\n    return { intradayFilter: parsed.intradayFilter === true };\n  } catch {\n    return DEFAULT_PERSONALIZATION;\n  }\n}\n\n// What GET /config/:id/personalization reads — the \"how to present it\"\n// half of a config, kept in its own column from updateConfig's \"what to\n// show\" half above (see lib/config.ts's Personalization header for why).\nexport async function getPersonalization(id: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({ sql: \"SELECT personalization FROM configs WHERE id = ?\", args: [id] });\n  const row = result.rows[0] as { personalization: string | null } | undefined;\n  return parsePersonalization(row?.personalization ?? null);\n}\n\n// The configurator's side of POST /config/:id/personalization. Bumps\n// updated_at like updateConfig does — a personalization change is a\n// widget-visible change to this config the same way sports/teams are.\nexport async function updatePersonalization(id: string, personalization: Personalization): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: \"UPDATE configs SET personalization = ?, updated_at = ? WHERE id = ?\",\n    args: [JSON.stringify(personalization), nowIso(), id],\n  });\n  return result.rowsAffected > 0;\n}\n\nexport type ConfigSummary = {\n  id: string;\n  name: string | null;\n  sports: string[];\n  teams: string[];\n  createdAt: string;\n  updatedAt: string;\n  deviceCount: number;\n};\n\n// What GET /config (the prototype-stage index of every config — see\n// render/configHtml.ts's configIndexDocument for why that route is allowed\n// to list every id) reads. A LEFT JOIN + COUNT rather than a second\n// per-row query: the index's whole purpose is telling configs apart, and\n// device count is effectively free at this table's scale (a handful of\n// configs, not a paginated one).\nexport async function listAllConfigs(): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute(\n    `SELECT c.id, c.name, c.sports, c.teams, c.created_at, c.updated_at, COUNT(dc.device_id) AS device_count\n     FROM configs c\n     LEFT JOIN device_configs dc ON dc.config_id = c.id\n     GROUP BY c.id\n     ORDER BY c.updated_at DESC`,\n  );\n  return (\n    result.rows as {\n      id: string;\n      name: string | null;\n      sports: string;\n      teams: string;\n      created_at: string;\n      updated_at: string;\n      device_count: number;\n    }[]\n  ).map((row) => ({\n    id: row.id,\n    name: row.name,\n    sports: JSON.parse(row.sports),\n    teams: JSON.parse(row.teams),\n    createdAt: row.created_at,\n    updatedAt: row.updated_at,\n    deviceCount: row.device_count,\n  }));\n}\n\nexport type DeviceConfigSummary = {\n  deviceId: string;\n  name: string | null;\n  configId: string;\n  configName: string | null;\n  configFound: boolean;\n  createdAt: string;\n};\n\n// GET /devices is an association index, so the device_configs row remains\n// authoritative even when its config_id is orphaned. The LEFT JOIN only\n// decides whether the renderer may turn that capability id into a link.\nexport async function listAllDeviceConfigs(): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute(\n    `SELECT dc.device_id, dc.name, dc.config_id, dc.created_at,\n            c.id AS existing_config_id, c.name AS config_name\n     FROM device_configs dc\n     LEFT JOIN configs c ON c.id = dc.config_id\n     ORDER BY COALESCE(dc.name, dc.device_id), dc.device_id`,\n  );\n  return (\n    result.rows as {\n      device_id: string;\n      name: string | null;\n      config_id: string;\n      created_at: string;\n      existing_config_id: string | null;\n      config_name: string | null;\n    }[]\n  ).map((row) => ({\n    deviceId: row.device_id,\n    name: row.name,\n    configId: row.config_id,\n    configName: row.config_name,\n    configFound: row.existing_config_id != null,\n    createdAt: row.created_at,\n  }));\n}\n\n// Reusable until it expires (not single-use) — one code lets a helper pair\n// every device in a family to the same config without regenerating it per\n// device. Collisions are astronomically unlikely at this scale and are left\n// unhandled rather than retried, matching this codebase's general posture of\n// not engineering for inputs that can't realistically occur.\nexport async function createPairingCode(configId: string): Promise<{ code: string; expiresAt: string }> {\n  await ensureSchema();\n  const code = randomCode();\n  const now = new Date();\n  const ts = now.toISOString();\n  const expiresAt = new Date(now.getTime() + CODE_TTL_SECONDS * 1000).toISOString();\n  await sqlite.execute({\n    sql: \"INSERT INTO pairing_codes (code, config_id, expires_at, created_at) VALUES (?, ?, ?, ?)\",\n    args: [code, configId, expiresAt, ts],\n  });\n  return { code, expiresAt };\n}\n\nexport type ExpiredPairingCode = { code: string; expiresAt: string; createdAt: string };\n\n// What GET /config/:id/pair lists below the live-code section — this\n// config's past pairing codes that are no longer usable. Nothing prunes\n// pairing_codes, so old rows just sit there; filtering happens in JS with\n// expiresAtMs rather than a SQL string compare on expires_at, for the same\n// cross-branch-format reason expiresAtMs's own header explains.\nexport async function listExpiredPairingCodes(configId: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: \"SELECT code, expires_at, created_at FROM pairing_codes WHERE config_id = ? ORDER BY created_at DESC\",\n    args: [configId],\n  });\n  const now = Date.now();\n  return (result.rows as { code: string; expires_at: string; created_at: string }[])\n    .filter((row) => expiresAtMs(row.expires_at) < now)\n    .map((row) => ({ code: row.code, expiresAt: row.expires_at, createdAt: row.created_at }));\n}\n\n// The receiver's half of pairing: it already has its own device id (client-\n// generated, per docs/widget-config-plan.md) and types in the code the\n// helper's browser is showing. The upsert on device_id (the pivot table's\n// primary key) is what makes re-pairing replace an existing binding rather\n// than duplicate it.\nexport async function pairDevice(\n  code: string,\n  deviceId: string,\n): Promise<{ ok: true; configId: string } | { ok: false; reason: \"not_found\" | \"expired\" }> {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: \"SELECT config_id, expires_at FROM pairing_codes WHERE code = ?\",\n    args: [code.trim().toUpperCase()],\n  });\n  const row = result.rows[0] as { config_id: string; expires_at: string } | undefined;\n  if (!row) return { ok: false, reason: \"not_found\" };\n  if (expiresAtMs(row.expires_at) < Date.now()) return { ok: false, reason: \"expired\" };\n\n  // Upsert rather than INSERT OR REPLACE: REPLACE deletes and reinserts the\n  // whole row, which would wipe out a name the configurator already set on\n  // this device the moment it re-pairs to a different config. ON CONFLICT\n  // DO UPDATE only touches config_id/created_at, leaving name untouched.\n  await sqlite.execute({\n    sql: `INSERT INTO device_configs (device_id, config_id, created_at, name) VALUES (?, ?, ?, NULL)\n          ON CONFLICT(device_id) DO UPDATE SET config_id = excluded.config_id, created_at = excluded.created_at`,\n    args: [deviceId, row.config_id, nowIso()],\n  });\n  return { ok: true, configId: row.config_id };\n}\n\n// The configurator's side of naming: they're the one looking at a list of\n// paired devices trying to tell \"dad\" from \"mom\", so naming happens on the\n// /config/:id page, not at pairing time. Empty string is treated the same\n// as null (an unnamed device), not stored as a zero-length name.\nexport async function renameDevice(deviceId: string, name: string | null): Promise {\n  await ensureSchema();\n  const trimmed = name?.trim() || null;\n  const result = await sqlite.execute({\n    sql: \"UPDATE device_configs SET name = ? WHERE device_id = ?\",\n    args: [trimmed, deviceId],\n  });\n  return result.rowsAffected > 0;\n}\n\nexport type PairedDevice = {\n  deviceId: string;\n  name: string | null;\n  createdAt: string;\n  pushRegistered: boolean;\n  tokenUpdatedAt: string | null;\n};\n\n// What /config/:id/devices lists so the configurator can see and name each\n// device paired to that config. LEFT JOINed against device_tokens (not a\n// second per-row query) so the page can also show whether a device has\n// registered for push and when its token last updated — device_tokens is\n// keyed by device_id independently of device_configs (see ensureSchema's\n// header), so a paired device with no token upload yet just gets nulls here.\nexport async function listDevicesForConfig(configId: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: `SELECT dc.device_id, dc.name, dc.created_at, dt.updated_at AS token_updated_at\n          FROM device_configs dc\n          LEFT JOIN device_tokens dt ON dt.device_id = dc.device_id\n          WHERE dc.config_id = ?\n          ORDER BY dc.created_at`,\n    args: [configId],\n  });\n  return (\n    result.rows as { device_id: string; name: string | null; created_at: string; token_updated_at: string | null }[]\n  ).map((row) => ({\n    deviceId: row.device_id,\n    name: row.name,\n    createdAt: row.created_at,\n    pushRegistered: row.token_updated_at != null,\n    tokenUpdatedAt: row.token_updated_at,\n  }));\n}\n\nexport type LinkableDevice = { deviceId: string; name: string | null };\n\n// Existing device rows that can be reassigned to this config. Devices\n// already linked here are excluded so the pairing form only offers actions\n// that would change an association.\nexport async function listLinkableDevices(configId: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: `SELECT device_id, name\n          FROM device_configs\n          WHERE config_id <> ?\n          ORDER BY COALESCE(name, device_id), device_id`,\n    args: [configId],\n  });\n  return (result.rows as { device_id: string; name: string | null }[]).map((row) => ({\n    deviceId: row.device_id,\n    name: row.name,\n  }));\n}\n\n// Reassign an existing device without creating a row from an arbitrary form\n// value. As with code-based pairing, the name survives and created_at marks\n// when the device became associated with this config.\nexport async function linkExistingDevice(configId: string, deviceId: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: `UPDATE device_configs\n          SET config_id = ?, created_at = ?\n          WHERE device_id = ? AND config_id <> ?`,\n    args: [configId, nowIso(), deviceId, configId],\n  });\n  return result.rowsAffected === 1;\n}\n\nexport type DeviceStatus = { configId: string; name: string | null; sports: string[]; teams: string[] };\n\n// What the app's diagnostics screen reads (GET /device/:deviceId) — this\n// device's full pairing status, not just the sports/teams resolveDevice()\n// below returns for the redirect path. Kept separate so that route's\n// never-null-error contract doesn't grow fields it doesn't need.\nexport async function getDeviceStatus(deviceId: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: `SELECT dc.config_id, dc.name, c.sports, c.teams FROM device_configs dc\n          JOIN configs c ON c.id = dc.config_id\n          WHERE dc.device_id = ?`,\n    args: [deviceId],\n  });\n  const row = result.rows[0] as { config_id: string; name: string | null; sports: string; teams: string } | undefined;\n  if (!row) return null;\n  return { configId: row.config_id, name: row.name, sports: JSON.parse(row.sports), teams: JSON.parse(row.teams) };\n}\n\nexport type ResolvedDeviceConfig = StoredConfig & { personalization: Personalization };\n\n// What /config/resolve calls. Returns null for an unknown or never-paired\n// device — not an error, just \"nothing to apply\" — which is what lets that\n// route fall back to the existing all-sports default instead of failing.\n// Carries personalization alongside sports/teams (one query, not a second\n// round trip) since buildResolvedUrl needs both to build the redirect.\nexport async function resolveDevice(deviceId: string): Promise {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: `SELECT c.sports, c.teams, c.personalization FROM device_configs dc\n          JOIN configs c ON c.id = dc.config_id\n          WHERE dc.device_id = ?`,\n    args: [deviceId],\n  });\n  const row = result.rows[0] as { sports: string; teams: string; personalization: string | null } | undefined;\n  if (!row) return null;\n  return {\n    sports: JSON.parse(row.sports),\n    teams: JSON.parse(row.teams),\n    personalization: parsePersonalization(row.personalization),\n  };\n}\n\n// The receiver's half of push registration (POST /device/token,\n// AppDelegate.swift's didRegisterForRemoteNotificationsWithDeviceToken) —\n// upsert, not insert, since tokens rotate and re-registering is expected,\n// not an error. Independent of device_configs on purpose: see the\n// device_tokens table comment above ensureSchema.\nexport async function saveDeviceToken(deviceId: string, token: string): Promise {\n  await ensureSchema();\n  await sqlite.execute({\n    sql: `INSERT INTO device_tokens (device_id, apns_token, updated_at) VALUES (?, ?, ?)\n          ON CONFLICT(device_id) DO UPDATE SET apns_token = excluded.apns_token, updated_at = excluded.updated_at`,\n    args: [deviceId, token, nowIso()],\n  });\n}\n\nexport async function deleteDeviceToken(deviceId: string): Promise {\n  await ensureSchema();\n  await sqlite.execute({ sql: \"DELETE FROM device_tokens WHERE device_id = ?\", args: [deviceId] });\n}\n\n// What lib/push.ts's notifyConfigDevices calls: every APNs token currently\n// belonging to a device paired to this config. A device paired but never\n// registered for push (or one whose token upload hasn't landed yet) simply\n// doesn't appear here — same \"nothing to do\" posture as resolveDevice.\nexport async function getTokensForConfig(configId: string): Promise<{ deviceId: string; token: string }[]> {\n  await ensureSchema();\n  const result = await sqlite.execute({\n    sql: `SELECT dt.device_id, dt.apns_token FROM device_tokens dt\n          JOIN device_configs dc ON dc.device_id = dt.device_id\n          WHERE dc.config_id = ?`,\n    args: [configId],\n  });\n  return (result.rows as { device_id: string; apns_token: string }[]).map((row) => ({\n    deviceId: row.device_id,\n    token: row.apns_token,\n  }));\n}\n",["D",1788290293174],"id","27c7d349-8dc0-4ddf-8288-3f5cab6fe8a0","app-clarkview",["D",1787009561780],"deletedAt","legacyEnvVars","privacy","public","httpPrivacy","description","The main web app and server API for Clark View","imageUrl","b0a8da26-58e7-4d19-8b5c-eedf487df9a9","pinnedFileId","pinPreview","pinMigrated","screenshotVersion","likeCount",0,"orgId","5a10edca-919b-4a78-babb-71908f69af93","tursoName","27c7d3498dc04ddf82883f5cab6fe8a0","tursoHostname","27c7d3498dc04ddf82883f5cab6fe8a0-val-town.aws-us-east-2.turso.io","tursoMeasuredAt",["D",1789532458193],"pinned","userPerm","r","valPerm","blobPerm","rw","emailPerm","sqlitePerm","projectPerm","telemetryPerm","user",{"_118":117,"_125":121},"org",{"_118":117,"_119":-5,"_120":121,"_18":75,"_122":123,"_124":27},"branch",{"_13":107,"_34":108,"_63":44,"_109":64,"_110":-5,"_111":-5,"_112":-5,"_113":-5,"_114":-5,"_115":65,"_116":117},"isOwned",346,"main","projectId","forkedBranchId","forkedBranchVersion","forkedProjectPrivacy","forkedProjectId","forkedProjectOrgId","projectName","userHandle","plusjade","handle","displayName","avatar","https://img.clerk.com/eyJ0eXBlIjoicHJveHkiLCJzcmMiOiJodHRwczovL2ltYWdlcy5jbGVyay5kZXYvb2F1dGhfZ2l0aHViL2ltZ18yVHpab25kTlBTM3M3WmpCa3NMSTd5akVwWksuanBlZyJ9","tier","free","canRestrictVals","profileImageUrl","branchName","","adoptOrgId",{"_63":64,"_34":65,"_40":382,"_67":-5,"_68":27,"_69":70,"_71":70,"_72":73,"_74":-5,"_18":75,"_76":-5,"_77":27,"_78":-5,"_79":-5,"_80":81,"_82":83,"_84":85,"_86":87,"_88":383,"_90":-5,"_91":92,"_93":92,"_94":95,"_96":95,"_97":95,"_98":92,"_99":92,"_100":384,"_102":385,"_104":386,"_106":27},"tree",[190,203,213,214],"files",[190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214],"counts",{"_177":81,"_178":179,"_180":81,"_181":182,"_183":184},"contents",[148,149,150,151],"upstreamProject","upstreamBranch","emptyEnvVars","flags",[],"hasHttpFiles","grants","orgs","customDomains",{},{"_63":172,"_34":173,"_32":174,"_153":-5,"_43":44,"_42":169,"_154":47,"_40":175,"_13":81,"_35":164,"_37":-5,"_26":27,"_157":-5,"_29":176},{"_63":166,"_34":167,"_32":168,"_153":-5,"_43":44,"_42":169,"_154":47,"_40":170,"_13":81,"_35":164,"_37":-5,"_26":27,"_157":-5,"_29":171},{"_63":159,"_34":160,"_32":161,"_153":-5,"_43":44,"_42":162,"_154":47,"_40":163,"_13":81,"_35":164,"_37":-5,"_26":27,"_157":-5,"_29":165},{"_63":152,"_34":30,"_32":33,"_153":-5,"_43":44,"_42":14,"_154":27,"_40":155,"_13":156,"_35":36,"_37":39,"_26":27,"_157":-5,"_29":158},"e6c203f1-21ab-4642-8c9d-d15747364f47","parentId","latest",["D",1788290293174],57,"label",[30],"7517392b-b300-4c80-a9d0-b69efbe3d395","tools","01a01d40-8e3d-7608-8d1b-9da477d55829",22,["D",1787197165114],"directory",[160],"f263cf9e-8f1d-4380-9798-e3c7da81523d","render","01a01c4d-2bf2-7199-84aa-8d4f0f0369a5",19,["D",1787181214708],[167],"e9eb5144-29ac-407f-8d97-f9c2b132f233","lib","01a01c4d-2bf2-7199-84aa-883b3a9a9d0b",["D",1787181214708],[173],"pulls","branches",50,"forks","envVars",{"_185":188,"_189":81},"connections",{"_185":186,"_187":81},"count",1,"unfilledCount",17,"emptyCount",{"_63":172,"_34":173,"_32":174,"_153":-5,"_43":44,"_42":169,"_154":47,"_40":379,"_13":81,"_35":164,"_37":-5,"_26":27,"_157":-5,"_216":380,"_29":381},{"_63":370,"_34":371,"_32":372,"_153":174,"_43":44,"_42":373,"_154":27,"_40":374,"_13":375,"_35":51,"_37":376,"_26":27,"_157":-5,"_216":377,"_29":378},{"_63":363,"_34":364,"_32":365,"_153":174,"_43":44,"_42":169,"_154":27,"_40":366,"_13":81,"_35":51,"_37":367,"_26":27,"_157":-5,"_216":368,"_29":369},{"_63":356,"_34":357,"_32":358,"_153":174,"_43":44,"_42":169,"_154":27,"_40":359,"_13":81,"_35":51,"_37":360,"_26":27,"_157":-5,"_216":361,"_29":362},{"_63":348,"_34":349,"_32":350,"_153":174,"_43":44,"_42":351,"_154":27,"_40":352,"_13":264,"_35":51,"_37":353,"_26":27,"_157":-5,"_216":354,"_29":355},{"_63":344,"_34":59,"_32":58,"_153":174,"_43":44,"_42":14,"_154":27,"_40":345,"_13":339,"_35":51,"_37":61,"_26":27,"_157":-5,"_216":346,"_29":347},{"_63":336,"_34":337,"_32":338,"_153":174,"_43":44,"_42":339,"_154":27,"_40":340,"_13":249,"_35":51,"_37":341,"_26":27,"_157":-5,"_216":342,"_29":343},{"_63":329,"_34":330,"_32":331,"_153":174,"_43":44,"_42":286,"_154":27,"_40":332,"_13":249,"_35":51,"_37":333,"_26":27,"_157":-5,"_216":334,"_29":335},{"_63":322,"_34":323,"_32":324,"_153":174,"_43":44,"_42":169,"_154":27,"_40":325,"_13":81,"_35":51,"_37":326,"_26":27,"_157":-5,"_216":327,"_29":328},{"_63":314,"_34":315,"_32":316,"_153":174,"_43":44,"_42":317,"_154":27,"_40":318,"_13":81,"_35":51,"_37":319,"_26":27,"_157":-5,"_216":320,"_29":321},{"_63":307,"_34":308,"_32":309,"_153":174,"_43":44,"_42":169,"_154":27,"_40":310,"_13":81,"_35":51,"_37":311,"_26":27,"_157":-5,"_216":312,"_29":313},{"_63":299,"_34":300,"_32":301,"_153":174,"_43":44,"_42":302,"_154":27,"_40":303,"_13":264,"_35":51,"_37":304,"_26":27,"_157":-5,"_216":305,"_29":306},{"_63":292,"_34":293,"_32":294,"_153":174,"_43":44,"_42":169,"_154":27,"_40":295,"_13":81,"_35":51,"_37":296,"_26":27,"_157":-5,"_216":297,"_29":298},{"_63":166,"_34":167,"_32":168,"_153":-5,"_43":44,"_42":169,"_154":47,"_40":289,"_13":81,"_35":164,"_37":-5,"_26":27,"_157":-5,"_216":290,"_29":291},{"_63":284,"_34":50,"_32":49,"_153":168,"_43":44,"_42":14,"_154":27,"_40":285,"_13":286,"_35":51,"_37":53,"_26":27,"_157":-5,"_216":287,"_29":288},{"_63":277,"_34":278,"_32":279,"_153":168,"_43":44,"_42":247,"_154":27,"_40":280,"_13":186,"_35":51,"_37":281,"_26":27,"_157":-5,"_216":282,"_29":283},{"_63":268,"_34":269,"_32":270,"_153":168,"_43":44,"_42":271,"_154":27,"_40":272,"_13":273,"_35":51,"_37":274,"_26":27,"_157":-5,"_216":275,"_29":276},{"_63":260,"_34":261,"_32":262,"_153":168,"_43":44,"_42":162,"_154":27,"_40":263,"_13":264,"_35":51,"_37":265,"_26":27,"_157":-5,"_216":266,"_29":267},{"_63":253,"_34":254,"_32":255,"_153":168,"_43":44,"_42":162,"_154":27,"_40":256,"_13":186,"_35":51,"_37":257,"_26":27,"_157":-5,"_216":258,"_29":259},{"_63":244,"_34":245,"_32":246,"_153":168,"_43":44,"_42":247,"_154":27,"_40":248,"_13":249,"_35":51,"_37":250,"_26":27,"_157":-5,"_216":251,"_29":252},{"_63":237,"_34":238,"_32":239,"_153":168,"_43":44,"_42":162,"_154":27,"_40":240,"_13":186,"_35":51,"_37":241,"_26":27,"_157":-5,"_216":242,"_29":243},{"_63":229,"_34":230,"_32":231,"_153":168,"_43":44,"_42":232,"_154":27,"_40":233,"_13":81,"_35":51,"_37":234,"_26":27,"_157":-5,"_216":235,"_29":236},{"_63":222,"_34":223,"_32":224,"_153":168,"_43":44,"_42":169,"_154":27,"_40":225,"_13":81,"_35":51,"_37":226,"_26":27,"_157":-5,"_216":227,"_29":228},{"_63":159,"_34":160,"_32":161,"_153":-5,"_43":44,"_42":162,"_154":47,"_40":219,"_13":81,"_35":164,"_37":-5,"_26":27,"_157":-5,"_216":220,"_29":221},{"_63":152,"_34":30,"_32":33,"_153":-5,"_43":44,"_42":14,"_154":27,"_40":215,"_13":156,"_35":36,"_37":39,"_26":27,"_157":-5,"_216":217,"_29":218},["D",1788290293174],"children",[],[30],["D",1787197165114],[],[160],"0e5396a2-7a54-4485-be69-d3cf6fc96739","theme.ts","9a132426-9c23-11f1-b7ac-1607ee4eb77e",["D",1787181214708],"// ---- palette ----\n//\n// The widget's whole reason for existing is at-a-glance, low-vision\n// scannability, so contrast is the constraint everything else bends around:\n// near-white text on a near-black card, ~19:1.\n//\n// The color *math* lives in lib/color.ts. This file is the palette built on\n// top of it — the values, not the conversions.\n\nimport { hslToRgb } from \"../lib/color.ts\";\n\nexport const FG = \"#ffffff\";\nexport const MUTED = \"#c9c9d2\";\nexport const BORDER = \"rgba(255,255,255,0.14)\";\n\n// Background varies by hue per request, and *only* by hue. Lightness and\n// saturation are held fixed, which is what keeps the randomization safe:\n// perceived brightness is carried by lightness, so rotating hue at a\n// constant 5% lightness walks around the color wheel without ever getting\n// lighter. Every hue lands in a narrow contrast band (~18.9:1 to ~19.9:1\n// against FG) rather than one hue being readable and another washing out.\n//\n// Saturation is deliberately low. At 30% the tint reads as \"this card has a\n// color\" without becoming a colored card — above that, low lightness starts\n// looking muddy rather than tinted.\nconst BG_LIGHTNESS = 0.05;\nconst BG_SATURATION = 0.3;\n\n// Translucent, not solid: the iOS widget renders this full-bleed with no\n// rounding of our own, so an opaque fill would fight whatever corner\n// treatment the widget host applies. High opacity preserves the contrast\n// the low-vision case depends on regardless of what sits behind it.\nconst BG_ALPHA = 0.88;\n\nexport function backgroundForHue(hue: number): string {\n  const [r, g, b] = hslToRgb(hue, BG_SATURATION, BG_LIGHTNESS);\n  return `rgba(${r},${g},${b},${BG_ALPHA})`;\n}\n\n// Kept separate from backgroundForHue so the color math stays pure and\n// testable across every hue, with the randomness injected at the caller.\n// main.ts is that caller: it picks the hue and passes the resolved color\n// down, which is what keeps the png tree deterministic and assertable.\nexport function randomHue(): number {\n  return Math.floor(Math.random() * 360);\n}\n",[],[167,223],"69307ebe-1db6-4576-8bdd-30a4b24a0091","templates.ts","20098910-a49b-11f1-90bd-1607ee4eb77e",64,["D",1788112158935],"// The template bridge: the explicit boundary between the games data shape\n// (EnrichedGame, lib/games.ts's Sleeper-derived domain object) and the\n// widget's view shape (WidgetItem's text fields, render/json.ts). Before\n// this file, render/json.ts's widgetItem() built mainText/subText/caption\n// with inline template-literal string concatenation — the *only*\n// presentation this val could produce was however that function happened to\n// be written. A WidgetItemTemplate names that presentation as a value\n// instead, so a personalized or seasonal variant is a new template, not a\n// new code path through widgetItem().\n//\n// Pure, no I/O — same boundary discipline as everything else under lib/ and\n// render/ except sleeper.ts/configStore.ts/push.ts/png.ts.\n//\n// ---- scope of v0 ----\n//\n// Deliberately just string interpolation plus a fixed prefix/suffix wrap —\n// no conditionals, no loops, no template-defined helpers. Every field that\n// needs real branching logic (channel fallback-chain text, team-code ->\n// display-name lookup, live/final/scheduled status resolution) stays\n// ordinary TypeScript in render/json.ts and is handed to the template as an\n// already-computed context value (`channelText`, `away`, `home`); the\n// template only ever arranges those values into text. That split is what\n// keeps `interpolate` itself trivial and total (it cannot throw or loop\n// forever on untrusted template text) while still letting a template author\n// reorder, wrap, or drop those values freely.\n//\n// `DEFAULT_WIDGET_TEMPLATE` below is the exact current presentation,\n// expressed as data. Any other WidgetItemTemplate value is \"customized in\n// isolation\": construct one and pass it explicitly to widgetPayload/\n// renderJson — there is no registry or per-device lookup yet. Sourcing a\n// template from stored per-config preference (lib/configStore.ts, the same\n// place sports/teams already live) is the next iteration, once there's an\n// actual second template to select between; building that lookup now, with\n// nothing to look up, is exactly the speculative path this val's other\n// modules avoid.\n\nexport type TemplateContext = Record;\n\n// `{{ dotted.path }}` only — no filters, no expressions. A path that\n// resolves to null/undefined (a typo'd key, or a context this template\n// wasn't written for) renders as \"\" rather than throwing: a widget item\n// with a blank field is a display bug worth noticing, but it must never be\n// a 500 that breaks the whole response, same \"never fatal\" posture as every\n// other request-shaped value in this val.\nexport function interpolate(input: string, context: TemplateContext): string {\n  return input.replace(/\\{\\{\\s*([\\w.]+)\\s*\\}\\}/g, (_, path: string) => {\n    const value = path.split(\".\").reduce((obj, key) => (obj as Record | null | undefined)?.[key], context);\n    return value == null ? \"\" : String(value);\n  });\n}\n\n// A fixed prefix/suffix wrapped around one interpolated value — the\n// \"personalize this field\" primitive: literal text that isn't itself part\n// of the interpolated template string, so a personalization doesn't have to\n// duplicate the underlying template to add a decoration around it. Both\n// optional; a field with neither is exactly `interpolate(template, ctx)`.\nexport type FieldTemplate = {\n  template: string;\n  prefix?: string;\n  suffix?: string;\n};\n\nexport function renderField(field: FieldTemplate, context: TemplateContext): string {\n  return `${field.prefix ?? \"\"}${interpolate(field.template, context)}${field.suffix ?? \"\"}`;\n}\n\n// Every free-text field render/json.ts's widgetItem() produces, named as\n// templates instead of code. Deliberately not every WidgetItem field:\n// `emphasized` is a boolean view instruction and `timestamp` is raw data\n// the client formats itself (see Shared/WidgetPayload.swift in the iOS\n// repo) — neither is text, so neither belongs in a string-interpolation\n// template. `caption` has exactly the two variants the live game states\n// need; \"scheduled\" has no template because `caption: null` for that state\n// is itself the contract (it tells the client to format `timestamp` as a\n// local start time), not a string this val ever sends.\nexport type WidgetItemTemplate = {\n  mainText: FieldTemplate;\n  subText: FieldTemplate;\n  caption: {\n    live: FieldTemplate;\n    final: FieldTemplate;\n  };\n};\n\n// Reproduces today's presentation: \"{{away}} @ {{home}}\" (with a per-sport\n// emoji ahead of it — `{{sportEmoji}}` is \"🏀 \" for wnba and \"\" for every\n// other sport, computed in render/json.ts from lib/catalog.ts's\n// SPORT_EMOJI and handed in as a context value, the same \"branching logic\n// stays in TypeScript, the template just arranges it\" split channelText\n// already uses), the channel text render/json.ts already computes, and the\n// bare \"LIVE\"/\"END\" captionFor used to return as literals. render/json.ts\n// now composes against this value instead of string-building inline; every\n// existing caller that never passes a template gets this exact output.\nexport const DEFAULT_WIDGET_TEMPLATE: WidgetItemTemplate = {\n  mainText: { template: \"{{sportEmoji}}{{away}} @ {{home}}\" },\n  subText: { template: \"{{channelText}}\" },\n  caption: {\n    live: { template: \"LIVE\" },\n    final: { template: \"END\" },\n  },\n};\n",[],[167,230],"6e27eff6-fa38-4436-b71e-688bec4d358b","png.ts","9a131472-9c23-11f1-b7ac-1607ee4eb77e",["D",1787197165114],"// The png render target's *impure* half: wasm init, font fetch, satori and\n// resvg. Nothing here decides what the card says — that is png-tree.ts,\n// which is pure and covered by tests/png-tree.test.ts. This file is only\n// covered by hitting the deployed endpoint.\n//\n// The png format is the piece that answers the iOS-widget question: a\n// WidgetKit \"Image from URL\" timeline entry can point straight at\n// .../?format=png&day=today and the widget stays a dumb  — all the\n// schedule/channel logic stays server-side, same as this app's existing\n// Rails view.\n\nimport satori from \"npm:satori\";\nimport { Resvg, initWasm } from \"npm:@resvg/resvg-wasm\";\nimport { pngTree, type PngCard } from \"./png-tree.ts\";\n\n// Module-scope caches: val.town reuses the Deno process across requests\n// when possible, so a cold WASM init / font fetch only has to happen once\n// per warm process, not once per request.\nlet wasmReady: Promise | null = null;\nlet regularFontPromise: Promise | null = null;\nlet boldFontPromise: Promise | null = null;\n\nfunction ensureWasm() {\n  if (!wasmReady) wasmReady = initWasm(fetch(\"https://unpkg.com/@resvg/resvg-wasm/index_bg.wasm\"));\n  return wasmReady;\n}\n\nfunction fetchFont(weight: number) {\n  return fetch(`https://cdn.jsdelivr.net/fontsource/fonts/jetbrains-mono@latest/latin-${weight}-normal.ttf`)\n    .then((r) => r.arrayBuffer())\n    .then((buf) => new Uint8Array(buf));\n}\n\nfunction regularFont() {\n  return (regularFontPromise ??= fetchFont(400));\n}\n\n// 800, not 700: JetBrains Mono's own bold reads noticeably lighter than\n// Inter's did at the same weight number — a monospace face's stems have to\n// share the cell with more whitespace per glyph on average, so matching\n// Inter's visual punch on the team-name line took the heaviest weight\n// fontsource serves this font at. Picked by eye against the render.\nfunction boldFont() {\n  return (boldFontPromise ??= fetchFont(800));\n}\n\nexport async function renderPng(card: PngCard): Promise {\n  await ensureWasm();\n\n  const svg = await satori(pngTree(card), {\n    width: card.width,\n    height: card.height,\n    fonts: [\n      { name: \"mono\", data: await regularFont(), weight: 400, style: \"normal\" },\n      { name: \"mono\", data: await boldFont(), weight: 800, style: \"normal\" },\n    ],\n  });\n\n  const png = new Resvg(svg).render().asPng();\n  return new Response(png, { headers: { \"content-type\": \"image/png\", \"cache-control\": \"public, max-age=60\" } });\n}\n",[],[167,238],"845c8ec4-bc49-458b-9ac6-7fe8f4f378ac","png-tree.ts","9a12ce86-9c23-11f1-b7ac-1607ee4eb77e",24,["D",1787202302479],4,"// The png render target's *pure* half: everything from a slate of games to\n// the satori element tree, with no wasm, no font fetch and no network. That\n// split is the point — every png bug this file's comments describe (clipping,\n// the undercounted \"+N more\", the channel name running off the side) was a\n// tree-and-layout bug, and this way tests/png-tree.test.ts can catch the next\n// one without a rendering runtime. png.ts is the impure half.\n//\n// Sized and weighted for low-vision scannability rather than the dense\n// multi-game table the html/json formats use: each game is two side-by-side\n// panels — the two teams stacked bold and large on the left (white on\n// near-black, ~19.5:1), time over channel muted on the right.\n\nimport { DEFAULT_CLIENT_OFFSET_SECONDS, shiftByOffset } from \"../lib/dates.ts\";\nimport { flattenByStartTime, type EnrichedGame, type GamesBySport } from \"../lib/games.ts\";\nimport { teamLabel } from \"../lib/teams.ts\";\nimport {\n  CHANNEL_UNIT,\n  type ContentWidths,\n  EMPTY_UNIT,\n  GAP_UNIT,\n  HEADER_UNIT,\n  MATCHUP_UNIT,\n  MAX_GAMES_SHOWN,\n  MERIDIEM_GAP_UNIT,\n  MERIDIEM_UNIT,\n  MORE_UNIT,\n  TIME_UNIT,\n  pngLayout,\n} from \"./layout.ts\";\nimport { textWidth } from \"./metrics.ts\";\nimport { BORDER, FG, MUTED } from \"./theme.ts\";\n\n// Satori's element shape. Deliberately loose on `children` — the tree nests\n// nodes, arrays of nodes and bare strings, and pinning that precisely buys\n// nothing here (nothing type-checks this file; bin/ci strips types rather\n// than compiling them).\nexport type SatoriNode = {\n  type: string;\n  props: { style?: Record; children?: unknown };\n};\n\n// `background` is passed in, never computed here: the hue is randomised per\n// request, and a tree that reached for Math.random would not be assertable.\n// main.ts injects the resolved color — see randomHue in theme.ts.\nexport type PngCard = {\n  bySport: GamesBySport;\n  dateLabel: string;\n  width: number;\n  height: number;\n  background: string;\n  rejected?: string[];\n  // Display-only: the GMT offset (seconds east of GMT) game times render in.\n  // The resolution of `?tz=` (or its default) happens once, in main.ts, and\n  // flows down to here and to formatDateLabel's caller alike, so a request\n  // never mixes times from two different offsets on one card.\n  clientOffsetSeconds?: number;\n};\n\n// Time and channel are separate values, not one string, because the row\n// draws them as two stacked right-justified lines. Kept to two lines per\n// game — the thing that made this legible in the first place.\n//\n// The clock and the meridiem come back apart because the row draws them at\n// different sizes, \"AM\" superscripted off the clock. Split on any whitespace\n// rather than on a literal \" \": recent ICU puts U+202F (narrow no-break\n// space) in this position, and the val runs on a Deno whose ICU is not the\n// one bin/ci runs these tests under. `\\s` covers both, and neither half\n// carries the separator into the width budget afterwards.\nexport function timeParts(\n  game: EnrichedGame,\n  offsetSeconds: number = DEFAULT_CLIENT_OFFSET_SECONDS,\n): { clock: string; meridiem: string } {\n  const [clock, meridiem = \"\"] = shiftByOffset(new Date(game.start_time), offsetSeconds)\n    .toLocaleTimeString(\"en-US\", { timeZone: \"UTC\", hour: \"numeric\", minute: \"2-digit\" })\n    .split(/\\s+/);\n  return { clock, meridiem };\n}\n\n// The channel's name *and* its DirecTV number — \"ESPN · 206\", where this\n// line used to carry the bare number as \"CH 206\". The number is the half\n// that took real work to get right (NATIONAL_CHANNELS hard-codes locally\n// assigned numbers for the affiliates that have no true national one), so\n// the name is added beside it rather than in place of it.\n//\n// Uses `label`, not `name`: the display form, dictionary-mapped down to\n// something widget-sized (\"Amazon Prime Video\" → \"AMZN\") and chopped if it\n// is regional free text. `name` keeps the raw string for the json format.\n//\n// `channelInfo` fills this in for national, streaming *and* regional\n// channels, so the only silent case left is a game Sleeper sent no channel\n// for at all. That flips this line from rare to near-universal: under the\n// bare-number version most rows drew nothing here, since the dictionary's\n// coverage is deliberately partial. The right panel is therefore usually two\n// lines now, which costs no height (it is still shorter than the team stack\n// that sets ROW_HEIGHT) but does compete for width.\n//\n// No \"TBD\" for the empty case — an absent line already reads as unknown, and\n// the HTML view's \"TBD\" belongs to a surface with room for it.\nexport function channelLabel(game: EnrichedGame): string | null {\n  const { label, directv_channel } = game.channel;\n  if (!label) return null;\n  return directv_channel ? `${label} · ${directv_channel}` : label;\n}\n\n// Drawn only when something was rejected, so the normal card is unchanged\n// and the appearance of this line is itself the signal. Kept in MUTED rather\n// than a new warning colour: every colour on this card has to clear contrast\n// against a randomised background hue, and MUTED is already covered by the\n// 360-hue assertions in tests/theme.test.ts.\n// Deliberately just a count, not the offending values. This has to fit on\n// ONE line at every canvas width — listing the tokens wrapped to two lines\n// on a large widget and pushed the card past its padding. The PNG's job is\n// to say \"something is wrong\"; `effective.rejected` in the json format is\n// where you find out what.\nexport function rejectionNote(rejected: string[]): string {\n  return `! ${rejected.length} ignored`;\n}\n\n// Tracked here rather than inline in the style below because the width\n// budget has to account for it: satori adds it after every character, so a\n// ten-character date carries ten more pixels than its glyphs measure.\nconst HEADER_LETTER_SPACING = 1;\n\nconst EMPTY_LABEL = \"No games\";\n\n// ---- how wide this card wants to be ----\n//\n// The layout used to model only height, and satori's response to a row that\n// is too wide is to shrink the panels — clipping the time, or dropping it\n// entirely. pngLayout now caps the scale so that cannot happen, and these\n// are the numbers it caps against: the natural width of every line, at scale\n// 1, measured through render/metrics.ts.\n//\n// It lives on this side of the seam because width is a fact about the *tree*\n// — which string is drawn at which size, and which panels sit beside each\n// other — and pngLayout should not have to know that a row is a team stack\n// next to a time stack. Keep the two in step: a line added to the tree\n// without a matching term here is a line the budget cannot see.\n\n// A row is the widest team line, a gutter, then the widest meta line. Both\n// panels are their own natural width (neither wraps), so the row is their\n// sum and not the larger of them.\nexport function rowWidth(game: EnrichedGame, offsetSeconds: number = DEFAULT_CLIENT_OFFSET_SECONDS): number {\n  const teams = Math.max(\n    textWidth(teamLabel(game.sport, game.away) ?? \"\", MATCHUP_UNIT, 800),\n    textWidth(teamLabel(game.sport, game.home) ?? \"\", MATCHUP_UNIT, 800),\n  );\n  const { clock, meridiem } = timeParts(game, offsetSeconds);\n  const time = textWidth(clock, TIME_UNIT) + (meridiem ? MERIDIEM_GAP_UNIT + textWidth(meridiem, MERIDIEM_UNIT) : 0);\n  const channel = channelLabel(game);\n  const meta = Math.max(time, channel ? textWidth(channel, CHANNEL_UNIT) : 0);\n  return teams + GAP_UNIT + meta;\n}\n\n// `chrome` is every line whose presence does not depend on how many games\n// were budgeted. \"+N more\" is measured against the whole slate rather than\n// the eventual hidden count — that count is what pngLayout is being asked to\n// decide, and the full count is an upper bound on its digits.\nexport function contentWidths(\n  games: EnrichedGame[],\n  dateLabel: string,\n  rejected: string[],\n  offsetSeconds: number = DEFAULT_CLIENT_OFFSET_SECONDS,\n): ContentWidths {\n  const header = textWidth(dateLabel.toUpperCase(), HEADER_UNIT) + dateLabel.length * HEADER_LETTER_SPACING;\n  return {\n    chrome: Math.max(\n      header,\n      textWidth(`+${games.length} more`, MORE_UNIT),\n      rejected.length ? textWidth(rejectionNote(rejected), MORE_UNIT) : 0,\n      games.length ? 0 : textWidth(EMPTY_LABEL, EMPTY_UNIT),\n    ),\n    rows: games.map((g) => rowWidth(g, offsetSeconds)),\n  };\n}\n\nexport function pngTree({\n  bySport,\n  dateLabel,\n  width,\n  height,\n  background,\n  rejected = [],\n  clientOffsetSeconds = DEFAULT_CLIENT_OFFSET_SECONDS,\n}: PngCard): SatoriNode {\n  // Pass the full slate size to pngLayout, not a slice of it —\n  // MAX_GAMES_SHOWN goes in as a ceiling on rendered rows so that games\n  // above it still get counted into \"+N more\" rather than dropping out of\n  // the total silently.\n  // Chronological, not sport-grouped — this canvas has no sport headings, so\n  // grouping here reads as a broken sort and biases truncation. See\n  // flattenByStartTime.\n  const games = flattenByStartTime(bySport);\n  const layout = pngLayout(\n    width,\n    height,\n    games.length,\n    MAX_GAMES_SHOWN,\n    rejected.length ? 1 : 0,\n    contentWidths(games, dateLabel, rejected, clientOffsetSeconds),\n  );\n  const visible = games.slice(0, layout.shown);\n\n  // Two panels side by side rather than two stacked full-width lines: teams\n  // stack left-justified on the left, time over channel stacks right-\n  // justified on the right. The teams carry no \"@\"/\"vs\" — their stacking is\n  // what says they're a matchup, and dropping the separator buys width for\n  // the bigger type. Alignment is done with flex (alignItems), not\n  // textAlign: satori implements only a subset of CSS and flex alignment is\n  // the part that's reliable there.\n  // lineHeight 1.0 and no gap between the two team codes: they are all-caps\n  // with no descenders, so the tight leading costs nothing legible, and the\n  // pair reads as one unit rather than two unrelated lines. It is also what\n  // pays for the second game on a medium widget — at 1.1 leading the row\n  // costs 121pt against a 120pt budget and 329x155 silently falls back to a\n  // one-game card. See ROW_HEIGHT in layout.ts.\n  const teamLine = (label: string | null) => ({\n    type: \"div\",\n    props: {\n      style: { display: \"flex\", fontSize: layout.matchupFontSize, fontWeight: 800, lineHeight: 1 },\n      children: label,\n    },\n  });\n\n  // No overflow or ellipsis styling here, and none needed: the panels are\n  // flexShrink 0 and pngLayout has already picked a scale at which the whole\n  // row fits, measured through render/metrics.ts. That is the fix for the\n  // spill this comment used to describe — a long channel name on a big canvas\n  // running off the side. Two earlier answers to it are worth not repeating:\n  // `minWidth: 0` made it worse (the box shrank, the text kept its width and\n  // spilled leftward, so the panels overlapped instead of one truncating),\n  // and shortening the channel label upstream in lib/channels.ts helped that\n  // one line while leaving the time — which is not bounded by\n  // MAX_CHANNEL_LABEL — to overflow first. Shortening the strings is still\n  // worth doing for its own sake; it just cannot be the guard.\n  //\n  // flexShrink 0 is also the fallback if the budget is ever wrong: checked by\n  // rendering with the budget deliberately disabled, a row too wide now spills\n  // past the right edge and is visibly cut, where before it silently lost the\n  // whole panel. Visible-and-wrong beats missing-and-quiet.\n  const metaLine = (text: string, fontSize: number) => ({\n    type: \"div\",\n    props: { style: { display: \"flex\", fontSize, lineHeight: 1.1 }, children: text },\n  });\n\n  // \"10:10\" at the meta size with \"AM\" riding above it, rather than one\n  // \"10:10 AM\" string. Top-aligned in a flex row: satori has no baseline\n  // alignment and no vertical-align, and this reads as a superscript because\n  // the two line boxes start together. The meridiem is the least informative\n  // part of the line — the card covers one day — so it gives up its size to\n  // the clock and its width to the row.\n  const timeLine = (game: EnrichedGame) => {\n    const { clock, meridiem } = timeParts(game, clientOffsetSeconds);\n    return {\n      type: \"div\",\n      props: {\n        style: { display: \"flex\", flexDirection: \"row\", alignItems: \"flex-start\", gap: layout.meridiemGap },\n        children: [\n          metaLine(clock, layout.timeFontSize),\n          ...(meridiem ? [metaLine(meridiem, layout.meridiemFontSize)] : []),\n        ],\n      },\n    };\n  };\n\n  const row = (game: EnrichedGame) => {\n    const channel = channelLabel(game);\n    return {\n      type: \"div\",\n      props: {\n        style: {\n          display: \"flex\",\n          flexDirection: \"row\",\n          justifyContent: \"space-between\",\n          alignItems: \"flex-start\",\n          width: \"100%\",\n          // A gutter the two panels cannot close, so a wide row degrades into\n          // \"tight\" rather than \"touching\".\n          gap: layout.gap,\n        },\n        children: [\n          {\n            type: \"div\",\n            props: {\n              style: { display: \"flex\", flexDirection: \"column\", alignItems: \"flex-start\", flexShrink: 0 },\n              // Real names where TEAMS knows one, raw Sleeper code otherwise.\n              // Only the png substitutes: `away`/`home` stay as the API's\n              // codes in the json format, which is the drift-detection\n              // surface and has to keep reporting what Sleeper actually sent.\n              children: [\n                teamLine(teamLabel(game.sport, game.away)),\n                teamLine(teamLabel(game.sport, game.home)),\n              ],\n            },\n          },\n          {\n            type: \"div\",\n            props: {\n              style: {\n                display: \"flex\",\n                flexDirection: \"column\",\n                alignItems: \"flex-end\",\n                flexShrink: 0,\n                gap: layout.rowGap,\n                color: MUTED,\n              },\n              children: [timeLine(game), ...(channel ? [metaLine(channel, layout.channelFontSize)] : [])],\n            },\n          },\n        ],\n      },\n    };\n  };\n\n  // Dropped games are counted, never silently omitted — the widget should\n  // say \"there is more\" rather than imply the day is only this long.\n  const moreRow = {\n    type: \"div\",\n    props: {\n      style: { display: \"flex\", fontSize: layout.moreFontSize, color: MUTED },\n      children: `+${layout.hidden} more`,\n    },\n  };\n\n  // ---- the eyebrow ----\n  //\n  // A navigation header, not the first line of the content: pinned to the top\n  // edge, full width, left justified. Left justification is the stretched\n  // column child plus a text node that starts at its left — not textAlign,\n  // which satori only partly implements.\n  //\n  // Pinning it is why the outer column stopped centering and the games moved\n  // into their own `body` node below. Centering the whole stack put the\n  // eyebrow wherever the content happened to end up, which on a card with\n  // vertical slack (any canvas where the width cap or widthScale binds before\n  // the height budget) floated it away from the top edge along with the rows.\n  // Now the outer column is top-aligned and `body` claims the leftover height\n  // with flexGrow, so the games stay centered in what is left while this line\n  // stays put. The two halves of that are a pair — drop either and the\n  // eyebrow silently goes back to riding with the rows.\n  //\n  // It carries \"TODAY ·\" / \"TOMORROW ·\" ahead of the date (see\n  // formatDateLabel), which roughly doubles its width and can make it the\n  // widest line on the card: \"TOMORROW · WED AUG 19\" measures 308 against a\n  // widest real game row of ~261, so on a sparse slate it is now what the\n  // width budget caps the scale against, costing about 6% of type size there.\n  // Accounted for, not accidental — contentWidths measures this string, so\n  // the cost is a slightly smaller card and never a clipped one.\n  //\n  // Two nodes, not one, and both flexShrink 0 — each defends a different\n  // axis, which is also why the row panels carry the same property. The outer\n  // one is a column item, so its 0 keeps the header's *height* from being\n  // squeezed when the content overruns. The inner one is a row item, so its 0\n  // keeps the text at its natural *width* rather than letting satori wrap it:\n  // a bare string in a full-width div breaks to a second line, and a two-line\n  // header silently blows CHROME_HEIGHT — the clipping class layout.ts exists\n  // to prevent. Spilling visibly past the edge is the better failure.\n  //\n  // The type styling sits on the inner node rather than inheriting from the\n  // outer, so that a width measured off this tree (tests/png-tree.test.ts\n  // reads each node's own style) sees the same fontSize and letterSpacing\n  // contentWidths budgeted for.\n  const eyebrow = {\n    type: \"div\",\n    props: {\n      style: { display: \"flex\", flexShrink: 0, width: \"100%\" },\n      children: [\n        {\n          type: \"div\",\n          props: {\n            style: {\n              display: \"flex\",\n              flexShrink: 0,\n              fontSize: layout.headerFontSize,\n              color: MUTED,\n              textTransform: \"uppercase\",\n              letterSpacing: HEADER_LETTER_SPACING,\n            },\n            children: dateLabel,\n          },\n        },\n      ],\n    },\n  };\n\n  // Everything under the eyebrow, in one node so it can be centered\n  // independently of it. The gap here is the same value the outer column\n  // uses, so the vertical metrics are unchanged: the card still spends one\n  // gap between the eyebrow and the first row, and one between every pair\n  // below it. CHROME_HEIGHT and ROW_HEIGHT still describe this layout.\n  const body = {\n    type: \"div\",\n    props: {\n      style: {\n        display: \"flex\",\n        flexDirection: \"column\",\n        justifyContent: \"center\",\n        flexGrow: 1,\n        width: \"100%\",\n        gap: layout.gap,\n      },\n      children: [\n        ...(visible.length\n          ? visible.map(row)\n          : [\n              {\n                type: \"div\",\n                props: {\n                  style: { display: \"flex\", fontSize: layout.emptyFontSize, color: MUTED },\n                  children: EMPTY_LABEL,\n                },\n              },\n            ]),\n        ...(layout.hidden > 0 ? [moreRow] : []),\n        ...(rejected.length\n          ? [\n              {\n                type: \"div\",\n                props: {\n                  style: { display: \"flex\", fontSize: layout.moreFontSize, color: MUTED },\n                  children: rejectionNote(rejected),\n                },\n              },\n            ]\n          : []),\n      ],\n    },\n  };\n\n  return {\n    type: \"div\",\n    props: {\n      style: {\n        width,\n        height,\n        display: \"flex\",\n        flexDirection: \"column\",\n        backgroundColor: background,\n        borderWidth: 1,\n        borderStyle: \"solid\",\n        borderColor: BORDER,\n        color: FG,\n        fontFamily: \"mono\",\n        padding: layout.padding,\n        gap: layout.gap,\n      },\n      children: [eyebrow, body],\n    },\n  };\n}\n",[],[167,245],"9e15a0eb-0b59-4a0a-a363-f590fde16508","metrics.ts","ca5a40ba-9c37-11f1-9069-1607ee4eb77e",["D",1787197165114],"// How wide a string will be when satori draws it. Pure, and the only reason\n// the png layout can model width at all.\n//\n// Why this exists: nothing in the layout used to model width, only height —\n// so a slate with few games picked a large scale and the row outgrew the\n// canvas sideways. It did not fail gracefully. Satori shrinks flex children\n// to fit, so a mild overflow clipped the time mid-glyph (\"10:10 AM\" cut to\n// \"10:10 AM|\") and a large one collapsed the whole right panel to zero width\n// and drew nothing at all — a card that silently omits the kickoff time,\n// which is most of what the widget is for. Both reproduced at 1100x1146 with\n// one game. See docs/widget-param-contract.md.\n//\n// Why a single constant, not a table: render/png.ts loads JetBrains Mono, a\n// true monospace face, and a monospace face gives every glyph the same\n// advance width by definition — measuring is summing per-character advances,\n// and the sum of N identical terms is just N times one of them. Verified\n// against the font's own hmtx table (tools/font-widths.mjs's read-out\n// method, run by hand against jetbrains-mono@latest): one distinct advance\n// value — 0.600em — across the full ASCII printable range, the four extra\n// glyphs this app draws (·, …, ’, —), and every weight from 100 to 800. The\n// one exception is combining diacritical marks, which the font correctly\n// gives a zero advance (they stack on the preceding base letter, monospace\n// or not) — charging 0.6em for one anyway is an over-measure, the same safe\n// direction the old per-glyph fallback erred in, and a smaller one.\n//\n// `weight` stays in the signature so call sites don't change and so a\n// future proportional face doesn't silently mismeasure — but it no longer\n// affects the answer, unlike the old Inter tables where bold ran up to 8%\n// wider than regular per character.\nconst ADVANCE = 0.6;\n\nexport function textWidth(text: string, fontSize: number, _weight = 400): number {\n  return [...text].length * ADVANCE * fontSize;\n}\n",[],[167,254],"ddd3509b-4655-4086-a2a7-a195bbcbc4a8","layout.ts","9a129d58-9c23-11f1-b7ac-1607ee4eb77e",["D",1787197165114],2,"// ---- png layout ----\n//\n// Pure, so tests/layout.test.ts can cover it without a rendering runtime.\n// It sits beside png-tree.ts rather than under lib/ because the two are one\n// unit: the tree derives every font size and gap from the same numbers this\n// fit calculation uses, and when they lived apart the layout silently\n// outgrew the canvas.\n//\n// The metrics below are the vertical cost of each piece at scale 1,\n// calibrated against actual satori output rather than derived from the font\n// sizes (satori's line-height and flex-gap rounding don't match a naive\n// fontSize * lineHeight sum closely enough to fit a 155px canvas).\n\nconst BASE_WIDTH = 329;\n\n// The 1px border costs 2px in each axis, unscaled.\nconst BORDER = 2;\n\n// ---- the card at scale 1 ----\n//\n// Every size the card draws, before scaling. They are named here rather than\n// left as literals in the returned object because the width budget below has\n// to know how wide the card's text will be at scale 1, and png-tree.ts is the\n// side that knows which string goes at which size. Both sides have to mean\n// the same numbers, so there is one copy of them.\n//\n// 14, not the 24 this started at. The iOS widget renders this card\n// full-bleed, so the padding is the whole margin — and the design is bold\n// type on a dark card, which does not want the airy inset a text-heavy app\n// would. It buys twice: 20pt of row width back for the budget below, and, on\n// a canvas where height sets the scale, 20pt of height that turns into\n// larger type instead of blank border. Rendered at 14, 18 and 24 and picked\n// by eye at 987x465; 14 leaves the header about 7pt off the corner, which is\n// still clear of a medium widget's ~22pt corner radius.\nexport const PADDING_UNIT = 14;\nexport const GAP_UNIT = 20;\nexport const ROW_GAP_UNIT = 4;\n// 18, down from 22: JetBrains Mono's even rhythm and taller x-height read\n// clearly at a smaller size than Inter did here, and the eyebrow is a\n// navigation label, not content — it can afford to give width back to the\n// budget. Picked by eye against the render, not derived.\nexport const HEADER_UNIT = 18;\nexport const MATCHUP_UNIT = 44;\nexport const TIME_UNIT = 28;\n// The meridiem rides above the clock as a superscript: same line, smaller\n// face, so \"10:10\" gets the size and \"AM\" only has to be present. Worth\n// doing because the clock is the second thing read on the card after the\n// teams, and \" AM\" was costing it a fifth of the row's meta width.\nexport const MERIDIEM_UNIT = 17;\nexport const MERIDIEM_GAP_UNIT = 3;\n// Deliberately the same number as MORE_UNIT rather than TIME_UNIT: the\n// channel is the lowest of the three priorities on a row (team, then time,\n// then channel), and it is the longest string — \"SportsNet · 691\" is wider\n// than either team line on a short matchup. Matching the \"+N more\" size\n// keeps the card at three type sizes rather than four while taking ~15% off\n// the widest thing the width budget has to fit.\n//\n// 20, down from 24, for the same reason as HEADER_UNIT above: a monospace\n// face's even, disambiguated glyphs (the dotted zero alone separates \"0\"\n// from \"O\" in a channel code) hold up at a smaller size than Inter's did,\n// and this is the widest string on most rows — every point given back here\n// is width the matchup line's scale can spend instead.\nexport const CHANNEL_UNIT = 20;\nexport const MORE_UNIT = 20;\nexport const EMPTY_UNIT = 32;\n\n// How much of the canvas's width the content is allowed to claim. The 3%\n// held back covers the two places this budget is approximate: satori's own\n// measurement rounds a text run to whole pixels (measured against\n// render/metrics.ts at up to 0.7% wider than predicted), and the font sizes\n// the card actually draws are these units *rounded*, not the exact product.\n// Both are sub-pixel per line; the margin is deliberately larger than the\n// error rather than tuned to it, because the cost of being wrong is a\n// clipped time and the cost of being conservative is 3% of a font size.\nconst WIDTH_FIT = 0.97;\n\n// Everything that isn't a game row: vertical padding + the date header +\n// the gap under it.\n// Exported so the tests assert against these numbers rather than their own\n// copy of them — a private constant plus a duplicate in the test is how a\n// layout guard silently goes stale.\nexport const CHROME_HEIGHT = 74;\n\n// One game row plus the gap above it. The row is two side-by-side panels —\n// away over home (bold, matchup size) on the left, time over channel (muted)\n// on the right — so its height is the *taller* panel, the left one: two\n// matchup-size lines at lineHeight 1, tight against each other. The right\n// panel is shorter and never binds.\n//\n// 108 is not slack: a medium widget's whole budget for two games is\n// (153/0.43 - CHROME_HEIGHT - MORE_ROW_HEIGHT) / 2 = 119.9, so 1.1 leading on\n// the team lines — which costs 121 — drops 329x155 back to a single game.\n// (That margin was 2pt before the padding came down to 14; the 10pt it\n// bought back is the only reason this is not still knife-edge.)\n//\n// Measured against the render, not derived: row pitch at 1100x1146 came out\n// 187px at scale 1.544 (121 * 1.544 = 186.8) for the 1.1-leading version\n// this replaced.\nexport const ROW_HEIGHT = 108;\n\n// The \"+N more\" line is a row of its own — budget it, or truncating puts\n// back the overflow it was meant to remove.\nexport const MORE_ROW_HEIGHT = 42;\n\n// Legibility floor, as a **fraction of the canvas's natural scale** — not an\n// absolute scale value. This design exists for at-a-glance, low-vision\n// reading; below roughly this fraction the matchup line stops being\n// scannable. Games that don't fit above the floor are dropped to a \"+N more\"\n// count rather than shrunk into illegibility.\n//\n// Why a fraction and not an absolute number: the caller passes *pixels*, but\n// a widget's legibility is about *points*. The same physical widget rendered\n// at @3x has 3x the pixels, and an absolute floor let those extra pixels buy\n// extra rows instead of sharper text. Measured under the old absolute floor,\n// the same medium widget showed 2 games at 329x155 (19pt matchup line) and 8\n// games at 987x465 (7pt) — pixel density silently changing how much content\n// a widget holds, and shrinking the text to a size this design exists to\n// avoid. Multiplying by widthScale makes the floor track the render density,\n// so a given physical widget shows the same games at 1x, 2x and 3x.\n//\n// 0.43 is a deliberate trade made by the user, calibrated at 329x155 where\n// widthScale is exactly 1.0 and this therefore still means an absolute 0.43\n// (≈19px matchup line): it fits 2 games instead of 1 at the default medium\n// widget size. Raise it toward 0.6 if the smaller line turns out to be hard\n// to read at a glance.\n//\n// It used to be knife-edge: at 24pt padding two games needed 153/352 =\n// 0.4347, so 0.44 would have rejected the second one and silently given back\n// the one-game card. Dropping the padding to 14 moved that threshold to\n// 153/332 = 0.4608, so there is now real room above this number — but the\n// same rule applies to spending it. Change this value by re-rendering and\n// counting games, not by reasoning about it.\nexport const MIN_SCALE = 0.43;\nconst MAX_SCALE = 6;\n\n// Backstop only — the legibility floor above is the real limiter now that it\n// scales with render density. At every actual widget size the floor binds\n// first (a large widget tops out at 6 games, a medium at 2, whatever density\n// it's rendered at), so this ceiling never fires in practice. It stays as a\n// guard against a pathological ?w=/?h= producing a canvas tall enough to ask\n// for dozens of rows.\n//\n// Do not lower it to shape what the widget shows — that's the floor's job,\n// and a ceiling applied outside pngLayout would cap `shown` without telling\n// it, which is how \"+N more\" undercounted before. It is passed as `maxShown`\n// for exactly that reason.\nexport const MAX_GAMES_SHOWN = 10;\n\n// The card's *natural* width at scale 1: one entry per game in draw order,\n// plus the lines that are on the card whatever the game count (the date\n// header, \"+N more\", the drift marker, \"No games\"). The caller measures them\n// because it owns the strings — see contentWidths in png-tree.ts.\nexport type ContentWidths = { chrome: number; rows: number[] };\n\nexport type PngLayout = {\n  shown: number;\n  hidden: number;\n  scale: number;\n  padding: number;\n  gap: number;\n  rowGap: number;\n  headerFontSize: number;\n  matchupFontSize: number;\n  timeFontSize: number;\n  meridiemFontSize: number;\n  meridiemGap: number;\n  channelFontSize: number;\n  moreFontSize: number;\n  emptyFontSize: number;\n};\n\n// Chooses how many games can be drawn at a legible size in the given\n// canvas, and the scale to draw them at. Never returns a count that\n// overflows: the previous version floored the scale at MIN_SCALE and\n// rendered every game regardless, so a 4-game slate at 329x155 produced\n// ~1.8x more content than canvas, centered — clipping the top matchup and\n// dropping the last game off the bottom with no indication either was lost.\n//\n// `count` must be the size of the WHOLE slate, not a pre-truncated slice:\n// `hidden` is derived from it, so passing an already-capped count makes the\n// \"+N more\" line undercount and games disappear unannounced — the same\n// failure, just moved. Use `maxShown` for any hard ceiling on rendered rows.\n// `noteRows` budgets any extra single-line rows the renderer will draw below\n// the games (currently just the \"! N ignored\" drift marker). They must be\n// declared here rather than appended by the caller: the marker was first\n// drawn outside this budget and immediately ate the bottom padding on a\n// medium canvas, where chrome + 2 rows + \"+N more\" already fills the height\n// exactly. That is the clipping bug this function exists to prevent.\nexport function pngLayout(\n  width: number,\n  height: number,\n  count: number,\n  maxShown = Infinity,\n  noteRows = 0,\n  widths: ContentWidths = { chrome: 0, rows: [] },\n): PngLayout {\n  const widthScale = Math.min(width / BASE_WIDTH, MAX_SCALE);\n  const usable = height - BORDER;\n\n  // Relative to the canvas, so the floor means the same physical text size\n  // whatever density the caller renders at. At BASE_WIDTH this is exactly\n  // MIN_SCALE, which is where the 0.43 trade was calibrated.\n  const minScale = MIN_SCALE * widthScale;\n\n  const budget = (rows: number, withMore: boolean) =>\n    CHROME_HEIGHT + rows * ROW_HEIGHT + (withMore ? MORE_ROW_HEIGHT : 0) + noteRows * MORE_ROW_HEIGHT;\n\n  const scaleFor = (rows: number, withMore: boolean) => Math.min(widthScale, usable / budget(rows, withMore));\n\n  let shown = 0;\n  for (let n = Math.min(count, maxShown); n >= 1; n--) {\n    if (scaleFor(n, n < count) >= minScale) {\n      shown = n;\n      break;\n    }\n  }\n\n  // A canvas too small for even one legible row still shows that one game,\n  // shrunk below the floor. A clipped matchup reads as wrong; a small one\n  // only reads as small.\n  const forced = count > 0 && shown === 0;\n  if (forced) shown = 1;\n\n  const hidden = count - shown;\n  const heightScale = forced\n    ? Math.min(widthScale, usable / budget(1, hidden > 0))\n    : Math.max(scaleFor(shown, hidden > 0), minScale);\n\n  // ---- the width budget ----\n  //\n  // Everything above this line is about height. That used to be the whole\n  // function, and it is why a card could still be wrong: fewer games means a\n  // taller row budget, which means a bigger scale, which widens the row\n  // against a canvas that never grew. Satori does not overflow gracefully —\n  // it shrinks flex children to fit, so a mild overrun clipped the time\n  // mid-glyph and a large one collapsed the right panel to zero width and\n  // drew no time at all. One game at 1100x1146 did both, depending on how\n  // long the team names were.\n  //\n  // Applied to the scale only, never to the row count, for two reasons. It\n  // cannot help: dropping a game does not narrow the widest row that is\n  // left. And letting it add rows instead would hand the extra height back as\n  // more content at a smaller size, which is exactly the trade MIN_SCALE\n  // exists to refuse. So `shown` is settled by height alone, and this can\n  // only ever make the same card smaller.\n  //\n  // For the same reason it is allowed below the legibility floor: when a name\n  // is too long for the canvas at any legible size, the choice is between\n  // small and clipped, and the rest of this file already answers that one the\n  // same way (see `forced` above). A clipped matchup reads as wrong; a small\n  // one only reads as small.\n  const widthCap = (rows: number) => {\n    // Chrome first and a zero after it, so this is defined for the empty\n    // slate (no rows at all) as well as for a caller that passes no widths.\n    const natural = Math.max(widths.chrome, 0, ...widths.rows.slice(0, rows));\n    if (natural <= 0) return Infinity;\n    return ((width - BORDER) * WIDTH_FIT) / (natural + 2 * PADDING_UNIT);\n  };\n\n  const scale = Math.min(heightScale, widthCap(shown));\n\n  return {\n    shown,\n    hidden,\n    scale,\n    padding: Math.round(PADDING_UNIT * scale),\n    gap: Math.round(GAP_UNIT * scale),\n    rowGap: Math.round(ROW_GAP_UNIT * scale),\n    headerFontSize: Math.round(HEADER_UNIT * scale),\n    matchupFontSize: Math.round(MATCHUP_UNIT * scale),\n    timeFontSize: Math.round(TIME_UNIT * scale),\n    meridiemFontSize: Math.round(MERIDIEM_UNIT * scale),\n    meridiemGap: Math.round(MERIDIEM_GAP_UNIT * scale),\n    channelFontSize: Math.round(CHANNEL_UNIT * scale),\n    moreFontSize: Math.round(MORE_UNIT * scale),\n    emptyFontSize: Math.round(EMPTY_UNIT * scale),\n  };\n}\n",[],[167,261],"3a96a0b9-9e23-44a7-8275-6f744d35094b","json.ts","9a12931c-9c23-11f1-b7ac-1607ee4eb77e",103,["D",1788144327706],11,"// The json render target — the SwiftUI widget's real data contract, mirrored\n// by the Codable types at Shared/WidgetPayload.swift in the iOS repo (decoded\n// with dateDecodingStrategy = .secondsSince1970). `widgetPayload` is pure and\n// is what the tests assert against; `renderJson` adds the response headers\n// and wraps it in a Response.\n//\n// schemaVersion 2 replaces the earlier away/home/score/status shape (see git\n// history / docs/valtown-brief.md for what schemaVersion 1 looked like).\n// This is now a *view* contract, not a data contract: the server decides\n// exactly what text to show (mainText/subText/caption/eyebrow) and the\n// client is a dumb template with no knowledge of \"teams\", \"scores\" or\n// \"games\". There is deliberately no away/home object and no score field, and\n// no `effective` echo in the body — the spec that drove this is explicit\n// that the response is scoped to exactly {schemaVersion, eyebrow, items[]},\n// since the body no longer echoes any team id for a client to cross-check\n// against. The old debug echo (mode/sports/teams/rejected/tz/date) still\n// exists, as `x-effective-*` response headers instead of a body field —\n// outside the Codable contract, so it costs the client nothing, and it's\n// what docs/valtown-brief.md's dev-vs-prod diff step now reads.\n//\n// Schema changes: only add fields, never remove/repurpose one, without\n// bumping schemaVersion.\n//\n// ---- the games-data -> view-text boundary (render/templates.ts) ----\n//\n// mainText/subText/caption used to be built with inline template-literal\n// string concatenation right here — the one presentation this val could\n// produce was however this file happened to construct those three strings.\n// That construction now goes through render/templates.ts's\n// WidgetItemTemplate instead: widgetItem() computes the *data* (team\n// display names, channel text, live/final/scheduled status — all real\n// TypeScript, since that's genuine branching logic, not text arrangement)\n// into a TemplateContext, then renders each free-text field through the\n// template. Every export below takes an optional `template` parameter\n// defaulting to DEFAULT_WIDGET_TEMPLATE, so every existing caller (main.ts\n// never passes one) gets byte-identical output — \"customized in isolation\"\n// per render/templates.ts's header means constructing a different\n// WidgetItemTemplate value and passing it explicitly; there's no lookup or\n// registry yet.\n\nimport { SPORT_EMOJI } from \"../lib/catalog.ts\";\nimport { type ChannelInfo } from \"../lib/channels.ts\";\nimport { flattenByStartTime, type EnrichedGame, type GamesBySport } from \"../lib/games.ts\";\nimport { type ResolvedParams } from \"../lib/params.ts\";\nimport { teamLabel } from \"../lib/teams.ts\";\nimport {\n  DEFAULT_WIDGET_TEMPLATE,\n  renderField,\n  type TemplateContext,\n  type WidgetItemTemplate,\n} from \"./templates.ts\";\n\ntype Status = \"scheduled\" | \"live\" | \"final\";\n\n// Sleeper's own vocabulary is inconsistent across sports and even across\n// captures of the same sport (nfl games have shown up as both \"scheduled\"\n// and \"pre_game\" for the same not-yet-started state — confirmed against\n// live captures and test/fixtures/files/sleeper/scores_nfl_wnba.json). This\n// maps every value seen live to the three states the widget cares about;\n// anything else falls back to \"scheduled\" (never fatal — an item the\n// client can't parse is worse than one that's guessed wrong) and is echoed\n// via the `x-effective-rejected` header so a genuine drift in Sleeper's\n// vocabulary is visible instead of silently swallowed.\nconst STATUS_MAP: Record = {\n  scheduled: \"scheduled\",\n  pre_game: \"scheduled\",\n  postponed: \"scheduled\",\n  delayed: \"scheduled\",\n  in_game: \"live\",\n  in_progress: \"live\",\n  live: \"live\",\n  halftime: \"live\",\n  complete: \"final\",\n  final: \"final\",\n  closed: \"final\",\n};\n\nfunction normalizeStatus(raw: string | null): { status: Status; rejected: string | null } {\n  if (raw && STATUS_MAP[raw]) return { status: STATUS_MAP[raw], rejected: null };\n  return { status: \"scheduled\", rejected: raw ? `status:${raw}` : null };\n}\n\ntype WidgetItem = {\n  id: string;\n  mainText: string;\n  subText: string;\n  caption: string | null;\n  emphasized: boolean;\n  timestamp: number;\n};\n\n// `caption: null` is a protocol value, not just \"no status\" — it tells the\n// client to format `timestamp` itself as a local start time. Only the live\n// case is emphasized; scheduled and final both get the dim treatment. The\n// live/final caption *text* comes from the template; which state gets\n// emphasis, and that \"scheduled\" gets no caption at all, stays here — that\n// part isn't text arrangement, it's the status/emphasis decision itself.\nfunction captionFor(\n  status: Status,\n  template: WidgetItemTemplate,\n  context: TemplateContext,\n): { caption: string | null; emphasized: boolean } {\n  if (status === \"live\") return { caption: renderField(template.caption.live, context), emphasized: true };\n  if (status === \"final\") return { caption: renderField(template.caption.final, context), emphasized: false };\n  return { caption: null, emphasized: false };\n}\n\n// subText's channel metadata, built from exactly what channelInfo already\n// gives every other render target — nothing invented for this format. A\n// national channel's directv_channel is the differentiator (that's the one\n// number lib/catalog.ts had to hand-assign for affiliates with no true\n// national one); a streaming channel has no directv_channel but does carry\n// a device note (\"computer only\"). \"TBD\" matches render/html.ts's fallback\n// for the one case channelInfo can't fill in at all: no channel string sent.\n//\n// This is real branching logic, not text arrangement, so it stays plain\n// TypeScript rather than moving into the template — its result feeds the\n// template as the `channelText` context value instead.\nfunction channelText(channel: ChannelInfo): string {\n  if (!channel.label) return \"TBD\";\n  if (channel.directv_channel) return `${channel.label} · ${channel.directv_channel}`;\n  if (channel.note) return `${channel.label} · ${channel.note}`;\n  return channel.label;\n}\n\nfunction widgetItem(\n  game: EnrichedGame,\n  template: WidgetItemTemplate,\n): { item: WidgetItem; status: Status; rejectedStatus: string | null } {\n  const { status, rejected } = normalizeStatus(game.statusRaw);\n  const away = teamLabel(game.sport, game.away) ?? game.away ?? \"\";\n  const home = teamLabel(game.sport, game.home) ?? game.home ?? \"\";\n  // Trailing space folded in here, not the template, so DEFAULT_WIDGET_\n  // TEMPLATE's \"{{sportEmoji}}{{away}} @ {{home}}\" never has to special-case\n  // an empty emoji into a leading blank.\n  const emoji = SPORT_EMOJI[game.sport];\n  const context: TemplateContext = {\n    away,\n    home,\n    sport: game.sport,\n    channel: game.channel,\n    channelText: channelText(game.channel),\n    sportEmoji: emoji ? `${emoji} ` : \"\",\n  };\n  const { caption, emphasized } = captionFor(status, template, context);\n  return {\n    item: {\n      // Falls back to a value that's at least stable across polls of the\n      // same game (the contract's actual requirement) on the rare chance\n      // Sleeper omits game_id — real captures always carry it.\n      id: game.id ?? `${game.sport}:${game.away}-${game.home}:${game.start_time}`,\n      mainText: renderField(template.mainText, context),\n      subText: renderField(template.subText, context),\n      caption,\n      emphasized,\n      // Unix epoch seconds, UTC — game.start_time is Sleeper's own\n      // milliseconds. Getting this wrong (sending ms) decodes on the client\n      // as a timestamp ~57,000 years out; nothing in a passing TS-side test\n      // would catch that, only a pinned integer does.\n      timestamp: Math.floor(game.start_time / 1000),\n    },\n    status,\n    rejectedStatus: rejected,\n  };\n}\n\n// `hideCompleted` is the intraday-vs-day-granularity personalization\n// (lib/config.ts's Personalization, carried here via /config/resolve's\n// `hideCompleted=1` query param — see buildResolvedUrl). Filtering on the\n// status this function already computes, not on caption text: a final\n// game's caption is template-configurable (\"END\" is just\n// DEFAULT_WIDGET_TEMPLATE's choice), so it isn't a reliable filter key,\n// while `status` is the actual live/final/scheduled classification.\nfunction buildItems(\n  bySport: GamesBySport,\n  hideCompleted = false,\n  template: WidgetItemTemplate = DEFAULT_WIDGET_TEMPLATE,\n): { item: WidgetItem; status: Status; rejectedStatus: string | null }[] {\n  const built = flattenByStartTime(bySport).map((game) => widgetItem(game, template));\n  return hideCompleted ? built.filter((b) => b.status !== \"final\") : built;\n}\n\n// `eyebrow` is deprecated per the ios-client spec (2026-08-26): the client\n// now derives per-game timing display from each item's own `timestamp`\n// rather than reading the card-level word. Still populated — schemaVersion\n// 2 requires it and dropping the key needs its own bump — but it stays the\n// same bare `day.toUpperCase()` literal (\"TODAY\"/\"TOMORROW\"/\"NEXT\") it always\n// was; nothing has to carry the resolved date for `day=next` here, since\n// each item already does via `timestamp`.\nexport function widgetPayload(\n  bySport: GamesBySport,\n  day: string,\n  hideCompleted = false,\n  template: WidgetItemTemplate = DEFAULT_WIDGET_TEMPLATE,\n) {\n  return {\n    schemaVersion: 2,\n    eyebrow: day.toUpperCase(),\n    items: buildItems(bySport, hideCompleted, template).map((b) => b.item),\n  };\n}\n\n// The drift-detection echo that used to live in the json body's `effective`\n// block, now as header values (strings only — headers can't carry nested\n// JSON). Pure, so it's testable without constructing a Response.\nexport function effectiveHeaders(\n  resolved: ResolvedParams,\n  statusRejections: string[],\n  clientOffsetSeconds: number,\n  resolvedDate: string | null,\n): Record {\n  return {\n    \"x-effective-mode\": resolved.mode,\n    \"x-effective-sports\": resolved.sports.join(\",\"),\n    \"x-effective-teams\": resolved.teams.map((t) => `${t.sport}:${t.code}`).join(\",\"),\n    \"x-effective-rejected\": [...resolved.rejected, ...statusRejections].join(\",\"),\n    \"x-effective-utc-offset-seconds\": String(clientOffsetSeconds),\n    \"x-effective-date\": resolvedDate ?? \"\",\n  };\n}\n\nexport function renderJson(\n  bySport: GamesBySport,\n  day: string,\n  resolved: ResolvedParams,\n  clientOffsetSeconds: number,\n  resolvedDate: string | null,\n  hideCompleted = false,\n  template: WidgetItemTemplate = DEFAULT_WIDGET_TEMPLATE,\n): Response {\n  const built = buildItems(bySport, hideCompleted, template);\n  const payload = {\n    schemaVersion: 2,\n    eyebrow: day.toUpperCase(),\n    items: built.map((b) => b.item),\n  };\n  const statusRejections = built.map((b) => b.rejectedStatus).filter((s): s is string => s !== null);\n  return Response.json(payload, {\n    headers: {\n      \"cache-control\": \"public, max-age=60\",\n      ...effectiveHeaders(resolved, statusRejections, clientOffsetSeconds, resolvedDate),\n    },\n  });\n}\n",[],[167,269],"ce215247-792d-40e8-8c3f-d1bfda440494","html.ts","9a1284c6-9c23-11f1-b7ac-1607ee4eb77e",["D",1787202302479],"// The html render target — the dense, sport-grouped table, as opposed to\n// the png's two-panel card. `htmlDocument` is pure and is what the tests\n// assert against; `renderHtml` is the Response wrapper.\n\nimport { DEFAULT_CLIENT_OFFSET_SECONDS, offsetLabel, shiftByOffset } from \"../lib/dates.ts\";\nimport { type GamesBySport } from \"../lib/games.ts\";\n\nexport function htmlDocument(\n  bySport: GamesBySport,\n  dateLabel: string,\n  clientOffsetSeconds: number = DEFAULT_CLIENT_OFFSET_SECONDS,\n): string {\n  const rows = bySport\n    .map(\n      ({ sport, games }) => `\n        ${sport.toUpperCase()}
\n        \n          ${games\n            .map((game) => {\n              const clock = shiftByOffset(new Date(game.start_time), clientOffsetSeconds).toLocaleTimeString(\n                \"en-US\",\n                { timeZone: \"UTC\", hour: \"numeric\", minute: \"2-digit\" },\n              );\n              const time = `${clock} ${offsetLabel(clientOffsetSeconds)}`;\n              const ch = game.channel;\n              const channelText =\n                ch.category === \"unknown\"\n                  ? \"TBD\"\n                  : `${ch.name}${ch.directv_channel ? ` · DirecTV ${ch.directv_channel}` : ch.note ? ` (${ch.note})` : \"\"}`;\n              return ``;\n            })\n            .join(\"\")}\n        ${game.away} @ ${game.home} ${time} ${channelText}
`,\n    )\n    .join(\"\");\n\n  const body = bySport.length ? rows : `No games ${dateLabel}.
`;\n\n  return `${dateLabel[0].toUpperCase()}${dateLabel.slice(1)}'s Games
${body}`;\n}\n\nexport function renderHtml(bySport: GamesBySport, dateLabel: string, clientOffsetSeconds?: number): Response {\n  return new Response(htmlDocument(bySport, dateLabel, clientOffsetSeconds), {\n    headers: { \"content-type\": \"text/html; charset=utf-8\" },\n  });\n}\n",[],[167,278],"0b0f9c39-f58e-4383-bda7-4e405eb1e0dc",["D",1788290293174],30,[],[167,50],["D",1787181214708],[204,205,206,207,208,209,210,211,212],[167],"024c4403-569e-428d-b508-34c61b0d7ba6","text.ts","9a127c38-9c23-11f1-b7ac-1607ee4eb77e",["D",1787181214708],"// Pure string helpers. Domain-free: nothing here knows about games,\n// channels or teams, which is what keeps them safe to call from anywhere\n// in lib/ without creating an import cycle.\n\n// A blunt chop rather than a width measurement — see MAX_CHANNEL_LABEL in\n// catalog.ts for why that is all this needs to be.\nexport function chop(text: string, max: number): string {\n  return text.length <= max ? text : `${text.slice(0, max - 1)}…`;\n}\n\nexport function titleCase(slug: string): string {\n  return slug\n    .split(\"-\")\n    .map((word) => word.charAt(0).toUpperCase() + word.slice(1))\n    .join(\" \");\n}\n",[],[173,293],"a488a0c5-de27-449a-8519-3ffc3977ee28","teams.ts","9a126e1e-9c23-11f1-b7ac-1607ee4eb77e",25,["D",1787278206578],"// Display names for the teams catalog.ts knows about. Pure.\n\nimport { TEAMS } from \"./catalog.ts\";\nimport { titleCase } from \"./text.ts\";\n\n// ---- display names ----\n//\n// Derived from TEAMS rather than declared as a second table, and that is the\n// whole point: a parallel TEAM_NAMES would carry the same (sport, code) pairs\n// a second time, and the two would drift the first time someone corrected a\n// code in one of them. Adding a team to TEAMS now buys both the favorites\n// filter and the display name in one edit.\n//\n// Keyed on `sport:code`, never on the bare code, for the reason spelled out\n// above TEAMS: `IND` is the Fever, the Colts *and* the Pacers, so a bare-code\n// index would label a Colts game \"Fever\". The key includes the sport for the\n// same reason the favorites table stores a pair.\nconst TEAM_LABELS: Record = Object.fromEntries(\n  Object.entries(TEAMS).map(([slug, ref]) => [`${ref.sport}:${ref.code}`, titleCase(slug)]),\n);\n\n// Falls back to the raw code, which is the honest thing to draw for a team\n// this table doesn't cover yet — nfl, wnba and mlb are fully mapped, but\n// nba is still deferred, so the fallback stays a live case there, and a\n// card mixes \"Lakers\" with \"PHX\". Callers get whatever TEAMS knows and\n// nothing is invented.\nexport function teamLabel(sport: string, code: string | null): string | null {\n  if (!code) return code;\n  return TEAM_LABELS[`${sport}:${code}`] ?? code;\n}\n\n// ---- the reverse of TEAMS: (sport, code) -> slug ----\n//\n// The widget json format sends away.id/home.id, and per docs/widget-ios-brief.md\n// those must be the exact slugs the iOS side is hardcoded to send in\n// teams[] — the slug *is* the id vocabulary, not a separate one. Derived\n// from TEAMS for the same reason TEAM_LABELS is: a hand-maintained second\n// table would drift the first time a code changed in one but not the other.\n// `Object.fromEntries` keeps the last entry on a key collision, which would\n// silently mean two slugs mapping to one id — safe here only because\n// tests/teams.test.ts's round-trip over every TEAMS entry already fails loud\n// if any (sport, code) pair is reused by two slugs.\nconst TEAM_SLUGS: Record = Object.fromEntries(\n  Object.entries(TEAMS).map(([slug, ref]) => [`${ref.sport}:${ref.code}`, slug]),\n);\n\n// Falls back to the raw code for a team TEAMS doesn't cover (nba, mostly) —\n// same \"nothing invented\" rule as teamLabel. An opponent team without a slug\n// still needs *some* id; the raw code is the honest one, and it's never used\n// for teams[] filtering since only slugs are accepted there.\nexport function teamId(sport: string, code: string | null): string | null {\n  if (!code) return code;\n  return TEAM_SLUGS[`${sport}:${code}`] ?? code;\n}\n",[],[173,300],"b463100f-fc59-48d9-964f-66f0e2ab005a","sleeper.ts","9a126266-9c23-11f1-b7ac-1607ee4eb77e",["D",1787181214708],"// The val's only outbound I/O. Everything else under lib/ is pure, which is\n// what lets tests/ run the whole slate pipeline against captured fixtures\n// with no network — this file is the seam they stop at, and the deployed\n// endpoint is what covers it (see docs/HANDOFF.md).\n\nimport { SPORTS } from \"./catalog.ts\";\nimport { type Game } from \"./games.ts\";\n\nexport async function fetchScores(date: string, sports: string[] = SPORTS): Promise {\n  const url = new URL(\"https://api.sleeper.app/scores\");\n  for (const sport of sports) url.searchParams.append(\"sports[]\", sport);\n  url.searchParams.set(\"date\", date);\n\n  const res = await fetch(url);\n  if (!res.ok) throw new Error(`Sleeper /scores returned ${res.status}`);\n  return (await res.json()) ?? [];\n}\n",[],[173,308],"70864817-4ae1-452b-80f2-2762e849c9b4","push.ts","583645a8-a324-11f1-a668-1607ee4eb77e",39,["D",1787951191922],"// The third source of real outbound I/O in this val (Apple's APNs,\n// alongside lib/sleeper.ts's Sleeper calls and lib/configStore.ts's\n// sqlite). Not reachable from tests/ for the same reason those two aren't\n// (see main.ts's header) — this hits the live APNs endpoint directly, so\n// it's verified by pairing a real device and editing its config, not a\n// deterministic test.\n//\n// What this buys: without it, a helper editing sports/teams in the browser\n// only reaches paired widgets whenever WidgetKit's own budget next refreshes\n// them (ClarkViewWidget.swift's Provider polls hourly, on its own schedule,\n// with no guarantee of exactly when). A silent push (content-available, no\n// alert/sound/badge — never shown to the person using the device) tells the\n// app to call WidgetCenter.reloadTimelines immediately instead — see\n// AppDelegate.swift in the iOS repo. It's a latency improvement on the\n// happy path, not a delivery guarantee: iOS throttles background pushes to\n// a handful per hour and drops them entirely for a force-quit app, so the\n// polling path stays load-bearing regardless.\n//\n// Auth: a signed ES256 JWT (RFC 7519) using an APNs Auth Key — one key\n// signs pushes for every app tied to this Apple team, no per-app cert.\n// WebCrypto's ECDSA signature is already raw r||s, which is what the JWT\n// wants directly — no DER conversion needed.\n//\n// Requires four env vars this val doesn't ship with by default:\n// APNS_KEY_ID, APNS_TEAM_ID, APNS_AUTH_KEY (the .p8 file's contents,\n// PEM-armored), and optionally APNS_TOPIC (defaults to the bundle id\n// below) / APNS_ENV (\"production\" once the App Store build ships;\n// defaults to sandbox, matching aps-environment=development in\n// clark_view.entitlements). Until those are set, sendSilentPush is a no-op\n// — see the null check in authToken.\n\nimport { deleteDeviceToken, getTokensForConfig } from \"./configStore.ts\";\n\nconst APNS_KEY_ID = Deno.env.get(\"APNS_KEY_ID\");\nconst APNS_TEAM_ID = Deno.env.get(\"APNS_TEAM_ID\");\nconst APNS_AUTH_KEY = Deno.env.get(\"APNS_AUTH_KEY\");\nconst APNS_TOPIC = Deno.env.get(\"APNS_TOPIC\") ?? \"plusjade.clark-view\";\nconst APNS_HOST = Deno.env.get(\"APNS_ENV\") === \"production\" ? \"api.push.apple.com\" : \"api.sandbox.push.apple.com\";\n\nfunction base64UrlFromBytes(bytes: Uint8Array): string {\n  let binary = \"\";\n  for (const byte of bytes) binary += String.fromCharCode(byte);\n  return btoa(binary).replace(/\\+/g, \"-\").replace(/\\//g, \"_\").replace(/=+$/, \"\");\n}\n\nfunction base64UrlFromString(value: string): string {\n  return base64UrlFromBytes(new TextEncoder().encode(value));\n}\n\n// .p8 files are PEM: base64 PKCS#8 wrapped in BEGIN/END lines. WebCrypto's\n// importKey(\"pkcs8\", ...) wants the raw DER bytes underneath, not the PEM\n// armor.\nfunction pkcs8KeyFromPem(pem: string): Promise {\n  const der = pem\n    .replace(/-----BEGIN PRIVATE KEY-----/, \"\")\n    .replace(/-----END PRIVATE KEY-----/, \"\")\n    .replace(/\\s+/g, \"\");\n  const bytes = Uint8Array.from(atob(der), (c) => c.charCodeAt(0));\n  return crypto.subtle.importKey(\"pkcs8\", bytes, { name: \"ECDSA\", namedCurve: \"P-256\" }, false, [\"sign\"]);\n}\n\nlet cachedToken: { jwt: string; mintedAt: number } | null = null;\n// Apple allows reusing one token for up to 60 minutes and rate-limits how\n// often a new one can be minted — refresh a bit early, not on every call.\nconst TOKEN_TTL_SECONDS = 50 * 60;\n\nasync function authToken(): Promise {\n  if (!APNS_KEY_ID || !APNS_TEAM_ID || !APNS_AUTH_KEY) return null;\n  const now = Math.floor(Date.now() / 1000);\n  if (cachedToken && now - cachedToken.mintedAt < TOKEN_TTL_SECONDS) return cachedToken.jwt;\n\n  const header = base64UrlFromString(JSON.stringify({ alg: \"ES256\", kid: APNS_KEY_ID }));\n  const claims = base64UrlFromString(JSON.stringify({ iss: APNS_TEAM_ID, iat: now }));\n  const signingInput = `${header}.${claims}`;\n  const key = await pkcs8KeyFromPem(APNS_AUTH_KEY);\n  const signature = await crypto.subtle.sign(\n    { name: \"ECDSA\", hash: \"SHA-256\" },\n    key,\n    new TextEncoder().encode(signingInput),\n  );\n  const jwt = `${signingInput}.${base64UrlFromBytes(new Uint8Array(signature))}`;\n  cachedToken = { jwt, mintedAt: now };\n  return jwt;\n}\n\n// Returns whether the token looks permanently dead (410 Unregistered, or a\n// 400 BadDeviceToken — the aps-environment/sandbox-vs-production mismatch\n// case) so the caller can prune it instead of retrying it forever. Missing\n// credentials or a transient APNs error both come back as a quiet `ok:\n// false, deadToken: false` — never thrown, matching this val's\n// never-fail-the-caller posture on every other device-facing route.\nexport async function sendSilentPush(token: string): Promise<{ ok: boolean; deadToken: boolean }> {\n  const jwt = await authToken();\n  if (!jwt) return { ok: false, deadToken: false };\n\n  const response = await fetch(`https://${APNS_HOST}/3/device/${token}`, {\n    method: \"POST\",\n    headers: {\n      authorization: `bearer ${jwt}`,\n      \"apns-topic\": APNS_TOPIC,\n      \"apns-push-type\": \"background\",\n      \"apns-priority\": \"5\",\n    },\n    body: JSON.stringify({ aps: { \"content-available\": 1 } }),\n  });\n  if (response.ok) return { ok: true, deadToken: false };\n\n  const reason = await response.json().then((body) => (body as { reason?: string })?.reason).catch(() => null);\n  return { ok: false, deadToken: response.status === 410 || reason === \"BadDeviceToken\" };\n}\n\n// Called after a config's sports/teams change (main.ts's POST /config/:id).\n// Pushes every device currently paired to that config, best-effort — one\n// bad token never blocks another device's push, and a push failure here\n// never fails the config save itself (see main.ts's try/catch around this\n// call).\nexport async function notifyConfigDevices(configId: string): Promise {\n  const devices = await getTokensForConfig(configId);\n  await Promise.all(devices.map(async ({ deviceId, token }) => {\n    const { deadToken } = await sendSilentPush(token);\n    if (deadToken) await deleteDeviceToken(deviceId);\n  }));\n}\n",[],[173,315],"f8e28c8e-8db7-47ad-b65d-3744db4b484d","params.ts","9a1248ee-9c23-11f1-b7ac-1607ee4eb77e",["D",1787181214708],"// The URL contract: raw `sports[]` / `teams[]` query values in, a resolved\n// fetch-and-filter plan out. Pure — no I/O — so the whole contract is\n// testable under bin/ci.\n\nimport { MAX_TEAMS, SPORTS, TEAMS, type TeamRef } from \"./catalog.ts\";\n\nexport type ResolvedParams = {\n  mode: \"teams\" | \"sports\";\n  sports: string[];\n  teams: TeamRef[];\n  rejected: string[];\n};\n\n// Two modes, not an intersection. Any valid team puts us in team mode, where\n// `sports[]` is ignored and the fetch list is derived from the selected\n// teams instead. Intersecting them lets `sports[]=nfl&teams[]=dodgers`\n// produce an empty widget that looks exactly like a quiet day.\n//\n// Nothing here throws or signals an error status: a 4xx renders as a broken\n// image in WidgetKit, which is worse than slightly wrong content. Unknown\n// values are dropped into `rejected` for the caller to echo, which is what\n// makes drift between the iOS repo and this one visible instead of silent.\nexport function resolveParams(sportsParam: string[] = [], teamsParam: string[] = []): ResolvedParams {\n  const rejected: string[] = [];\n\n  const clean = (values: string[]) => [\n    ...new Set(values.map((v) => v.trim().toLowerCase()).filter(Boolean)),\n  ];\n\n  // Sports are validated even in team mode, where they're otherwise unused:\n  // a typo should surface as drift rather than hide behind a team filter.\n  const sports = clean(sportsParam).filter((s) => {\n    if (SPORTS.includes(s)) return true;\n    rejected.push(s);\n    return false;\n  });\n\n  const teams: TeamRef[] = [];\n  for (const slug of clean(teamsParam)) {\n    if (!TEAMS[slug]) rejected.push(slug);\n    else if (teams.length >= MAX_TEAMS) rejected.push(slug);\n    else teams.push(TEAMS[slug]);\n  }\n\n  // Every requested team was unknown -> fall through to sports mode rather\n  // than rendering an empty card. The slugs are already in `rejected`, so\n  // the caller can still say something went wrong.\n  if (teams.length === 0) {\n    return { mode: \"sports\", sports: sports.length ? orderBySports(sports) : [...SPORTS], teams: [], rejected };\n  }\n\n  const derived = orderBySports([...new Set(teams.map((t) => t.sport))]);\n  return { mode: \"teams\", sports: derived, teams, rejected };\n}\n\n// Keeps fetch/group order stable and independent of the order params arrived\n// in, so two widgets with the same selection produce the same card.\nfunction orderBySports(sports: string[]): string[] {\n  return SPORTS.filter((s) => sports.includes(s));\n}\n",[],[173,323],"601572ac-8796-4955-b80e-d9502442668d","games.ts","9a122d64-9c23-11f1-b7ac-1607ee4eb77e",["D",1787784735721],"// The game slate: Sleeper's raw /scores payload in, enriched and grouped\n// games out. Pure — the fetch that produces the input lives in sleeper.ts.\n\nimport { SPORTS, type TeamRef } from \"./catalog.ts\";\nimport { channelInfo, type ChannelInfo } from \"./channels.ts\";\n\n// away_team/home_team ships as a plain string for nfl but as\n// { record, team } for wnba (and mlb) — same shape hazard the Rails view\n// papers over with `dig(...) rescue metadata[\"away_team\"]`.\n//\n// Named for what it returns: Sleeper's abbreviation (\"IND\"), not a name.\n// `teamLabel` in teams.ts is the one that turns that into \"Fever\".\nfunction teamCode(value: unknown): string | null {\n  if (value && typeof value === \"object\") return (value as { team: string }).team;\n  return (value as string) ?? null;\n}\n\n// Same shape hazard as teamCode, on the score instead of the code — and it's\n// two hazards deep. wnba/mlb nest it inside the away_team/home_team object,\n// nfl carries no such object at all and puts it in a sibling\n// metadata.away_score/home_score field instead (confirmed live 2026-08-20 —\n// nfl never populates a score inside away_team, in_game or not). And even\n// among the sports that do nest it, the key isn't the same: mlb calls it\n// `score`, wnba calls it `points` (confirmed live 2026-08-20 against three\n// in-progress wnba games — `score` was absent, `points` had the real total).\n// nba is assumed to share wnba's `points`, both being basketball on the same\n// provider, but that's unverified — no live nba game to check this season.\nfunction teamScore(teamValue: unknown, flatScore: unknown): number | null {\n  if (teamValue && typeof teamValue === \"object\") {\n    const obj = teamValue as { score?: unknown; points?: unknown };\n    const nested = typeof obj.score === \"number\" ? obj.score : obj.points;\n    if (typeof nested === \"number\") return nested;\n  }\n  return typeof flatScore === \"number\" ? flatScore : null;\n}\n\nexport type Game = {\n  sport: string;\n  start_time: number;\n  status?: unknown;\n  game_id?: unknown;\n  metadata: {\n    away_team?: unknown;\n    home_team?: unknown;\n    channel?: string | null;\n    away_score?: unknown;\n    home_score?: unknown;\n  };\n};\n\nexport type EnrichedGame = Game & {\n  away: string | null;\n  home: string | null;\n  channel: ChannelInfo;\n  id: string | null;\n  statusRaw: string | null;\n  awayScore: number | null;\n  homeScore: number | null;\n};\n\nexport type GamesBySport = { sport: string; games: EnrichedGame[] }[];\n\n// The three steps transformScores used to do inline, split out so\n// pickNextSlate can filter the same enriched date by one team at a time\n// instead of re-deriving away/home/channel/id/etc. per team.\nfunction enrichGames(games: Game[]): EnrichedGame[] {\n  return (games ?? []).map((game) => ({\n    ...game,\n    away: teamCode(game.metadata?.away_team),\n    home: teamCode(game.metadata?.home_team),\n    channel: channelInfo(game.metadata?.channel),\n    id: typeof game.game_id === \"string\" || typeof game.game_id === \"number\" ? String(game.game_id) : null,\n    statusRaw: typeof game.status === \"string\" ? game.status : null,\n    awayScore: teamScore(game.metadata?.away_team, game.metadata?.away_score),\n    homeScore: teamScore(game.metadata?.home_team, game.metadata?.home_score),\n  }));\n}\n\n// Matched on the (sport, code) pair, never the bare code — `IND` is three\n// different franchises across wnba/nfl/nba, so a code-only match makes\n// \"fever\" quietly include Colts and Pacers games.\nfunction filterByTeams(enriched: EnrichedGame[], teams: TeamRef[]): EnrichedGame[] {\n  if (!teams.length) return enriched;\n  return enriched.filter((game) =>\n    teams.some((t) => t.sport === game.sport && (game.away === t.code || game.home === t.code)),\n  );\n}\n\nfunction groupBySport(enriched: EnrichedGame[], sports: string[]): GamesBySport {\n  const bySport = Object.groupBy(enriched, (g) => g.sport) as Record;\n  return sports\n    .filter((sport) => bySport[sport]?.length)\n    .map((sport) => ({ sport, games: bySport[sport].toSorted((a, b) => a.start_time - b.start_time) }));\n}\n\n// sports: array like [\"nfl\", \"wnba\"]. games: raw Sleeper /scores payload\n// (already filtered to a single date server-side by the API call itself —\n// this function just shapes what was returned).\nexport function transformScores(games: Game[], sports: string[] = SPORTS, teams: TeamRef[] = []): GamesBySport {\n  return groupBySport(filterByTeams(enrichGames(games), teams), sports);\n}\n\n// Flattens the sport groups into one chronological list, for renderers that\n// don't draw sport headings.\n//\n// The PNG is that renderer. Flattening in SPORTS order instead produced a\n// list that looked time-sorted but wasn't (a 4:30pm wnba game above a 9:35am\n// mlb one, with nothing on the card explaining the jump), and — worse — made\n// truncation sport-biased: whichever sport sorts first claims the visible\n// rows, so a medium widget showing 2 of 17 gave both slots to wnba and put\n// all 15 mlb games behind \"+15 more\". With four sports that can make a whole\n// sport structurally unreachable on the smaller canvases.\n//\n// The HTML view still groups by sport deliberately — it has headings, so the\n// grouping is legible there.\nexport function flattenByStartTime(bySport: GamesBySport): EnrichedGame[] {\n  return bySport.flatMap((group) => group.games).toSorted((a, b) => a.start_time - b.start_time);\n}\n\n// The window-scan decision behind every `day=` value (today/tomorrow/next\n// all resolve through the same scan now — see lib/dates.ts's\n// windowDatesFor), kept pure and separate from the fetch that feeds it\n// (main.ts fetches every date in the window in parallel, then hands the\n// results here in calendar order).\n//\n// Sports mode (no teams[]) walks the dates in order and returns the first\n// one with any qualifying game — never the first one to resolve over the\n// network, which would make the result depend on request timing instead of\n// the calendar.\n//\n// Team mode resolves each favorite independently instead of sharing one\n// \"earliest date\" across all of them. A single shared date silently drops\n// every OTHER favorite whose own next game lands on a later date in the\n// window: `teams[]=sparks&teams[]=fever&teams[]=dodgers` with the Dodgers\n// playing today but Sparks/Fever not until day 2 used to return only the\n// Dodgers game — the scan stopped at day 0 because *a* team qualified,\n// never reaching day 2 to pick up the other two. Each team now gets its own\n// walk over the same window, and the games are unioned; `date` becomes the\n// earliest date represented across all of them (used for the card's\n// overall date label, not a claim every returned game is on that date —\n// each json item still carries its own `timestamp`). Two favorites in the\n// same game are deduped rather than shown twice.\n//\n// `null` means no date in the window qualified for ANY team/sport (a real\n// offseason, most likely, or just an unlucky 3-day window), which the\n// caller renders as the existing empty-slate state rather than an error.\nexport function pickNextSlate(\n  dates: string[],\n  gamesByDate: Game[][],\n  sports: string[] = SPORTS,\n  teams: TeamRef[] = [],\n): { date: string; bySport: GamesBySport } | null {\n  const enrichedByDate = gamesByDate.map((games) => enrichGames(games));\n\n  if (!teams.length) {\n    for (let i = 0; i < dates.length; i++) {\n      const bySport = groupBySport(enrichedByDate[i], sports);\n      if (bySport.length) return { date: dates[i], bySport };\n    }\n    return null;\n  }\n\n  let earliestDate: string | null = null;\n  const matched: EnrichedGame[] = [];\n  for (const team of teams) {\n    for (let i = 0; i < dates.length; i++) {\n      const games = filterByTeams(enrichedByDate[i], [team]);\n      if (games.length) {\n        if (earliestDate === null || dates[i] < earliestDate) earliestDate = dates[i];\n        matched.push(...games);\n        break;\n      }\n    }\n  }\n  if (!matched.length) return null;\n\n  const seen = new Set();\n  const deduped = matched.filter((g) => {\n    const key = g.id ?? `${g.sport}:${g.away}-${g.home}:${g.start_time}`;\n    if (seen.has(key)) return false;\n    seen.add(key);\n    return true;\n  });\n\n  return { date: earliestDate!, bySport: groupBySport(deduped, sports) };\n}\n",[],[173,330],"291434b6-dc3f-4131-9bac-b45dff517ce2","dates.ts","9a121f22-9c23-11f1-b7ac-1607ee4eb77e",29,["D",1787773674097],"// Pure date math for the Sleeper slate. No formatting of games, no I/O —\n// every function here takes an explicit `now` or an ISO string, which is\n// what lets tests/dates.test.ts pin behaviour without freezing the clock.\n\n// Sleeper buckets /scores by Eastern day, not UTC — same fact\n// Sleeper::Client.today_slate_date encodes. This is a server-side fact\n// about Sleeper, never client-supplied, so it stays an IANA name (DST needs\n// a real zone, not an offset) and is untouched by the client offset work\n// below.\nexport const SLEEPER_TIME_ZONE = \"America/New_York\";\n\n// The client's timezone when a request doesn't send `?tz=`, or sends one\n// resolveClientOffsetSeconds rejects. Used two ways: as the IANA name\n// resolveClientOffsetSeconds resolves to a live, DST-correct offset via\n// offsetSecondsForZone, and its offset-seconds shadow below as the default\n// for render/* function signatures, which need a plain number and are never\n// actually hit by a real request (main.ts always passes the resolved\n// value through).\nexport const DEFAULT_CLIENT_TIME_ZONE = \"America/Los_Angeles\";\n\n// PDT, i.e. only correct roughly March-November. Stale for the other four\n// months by design: this is a signature default for pure functions\n// (timeParts, rowWidth, ...) that main.ts never actually relies on, since it\n// always threads through the live value resolveClientOffsetSeconds computed.\n// The real per-request fallback — used when `?tz=` is absent or rejected —\n// is DST-correct because it re-derives from DEFAULT_CLIENT_TIME_ZONE at\n// request time instead of reading this constant. Don't wire this into\n// resolveClientOffsetSeconds's fallback path; that would silently undo that.\nexport const DEFAULT_CLIENT_OFFSET_SECONDS = -25200;\n\n// The calendar date `now` falls on in `timeZone`. en-CA gives YYYY-MM-DD\n// directly, sorted the way ISO date math wants it. IANA-only — this is\n// Sleeper's half of the pipeline (see SLEEPER_TIME_ZONE); the client's half\n// is dateAtOffset below, on purpose kept as a separate function so the two\n// can't be swapped for each other by mistake.\nexport function localDateFor(timeZone: string, now = new Date()): string {\n  return now.toLocaleDateString(\"en-CA\", { timeZone });\n}\n\n// Eastern's calendar date for `now` — the bucket Sleeper's /scores keys on.\n// Anchored off real UTC \"now\", not any app-local notion of \"today\".\nexport function todaySlateDate(now = new Date()): string {\n  return localDateFor(SLEEPER_TIME_ZONE, now);\n}\n\nexport function addDays(isoDate: string, days: number): string {\n  const [y, m, d] = isoDate.split(\"-\").map(Number);\n  const date = new Date(Date.UTC(y, m - 1, d));\n  date.setUTCDate(date.getUTCDate() + days);\n  return date.toISOString().slice(0, 10);\n}\n\n// The client's half of the offset arithmetic: no DST table lookup, because\n// the offset it's given has already had DST folded into it (by the iOS\n// client, or by offsetSecondsForZone's live Intl lookup for the fallback\n// case) — adding seconds is all that's left to do. Shared by dateAtOffset\n// (which calendar day) and the render layer (what wall-clock time), so both\n// answer to the same arithmetic.\nexport function shiftByOffset(instant: Date, offsetSeconds: number): Date {\n  return new Date(instant.getTime() + offsetSeconds * 1000);\n}\n\n// The calendar date `now` falls on at a fixed UTC offset — the client-offset\n// counterpart to localDateFor's IANA version. Deliberately not named\n// localDateFor*: the two take different kinds of timezone value (a name vs\n// a number of seconds) and reading the wrong one as the other would fail\n// only in the three-hour window that made this whole change necessary in\n// the first place.\nexport function dateAtOffset(offsetSeconds: number, now = new Date()): string {\n  return shiftByOffset(now, offsetSeconds).toISOString().slice(0, 10);\n}\n\nconst DAY_OFFSETS: Record = { today: 0, tomorrow: 1 };\n\n// The png's card-copy prefix. Mostly keyed by the same terms as\n// DAY_OFFSETS — two maps rather than one entry with both fields because they\n// answer to different callers, the offset is URL contract and the word is\n// card copy — plus \"next\", which isn't a distinct offset (see\n// windowDatesFor: an unmapped term falls to today's offset, same as\n// DAY_OFFSETS's own `?? 0`) but still wants a word ahead of whichever date\n// in the window actually had a game.\nconst DAY_WORDS: Record = { today: \"Today\", tomorrow: \"Tomorrow\", next: \"Next\" };\n\nexport type SlateDateOptions = { now?: Date; clientOffsetSeconds?: number };\n\n// `today`/`tomorrow` resolve against the *client's* calendar day, not\n// Eastern's. The old version anchored on todaySlateDate (Eastern) directly,\n// which is wrong for three hours of every real-world day: at, say, 10pm\n// Pacific, Eastern has already rolled to the next date, so a Pacific caller\n// asking for \"today\" got tomorrow's slate.\n//\n// The date handed to Sleeper is the client's local date, unconverted — not\n// a further Eastern-coerced value. That's an accepted trade, not a missing\n// step: Sleeper buckets by Eastern day, so for a zone west of Eastern the\n// fetched window is the client's calendar day shifted a few hours earlier\n// (for Pacific: 9pm the previous evening through 9pm today). Games starting\n// after that cutoff fall in Eastern's next bucket and are absent from\n// \"today\" until the following request. Getting that last slice right needs\n// two Eastern buckets fetched and merged, filtered by each game's own\n// `start_time` — real work this task doesn't require, since the bug being\n// fixed here (the day boundary silently rolling 3 hours early, for everyone,\n// every single day) is the one that bites regardless of what's playing.\n// (A client zone east of Eastern — say Asia/Tokyo — is out of scope: this\n// widget has no client that far east.)\nexport function slateDateFor(term: string, opts: SlateDateOptions = {}): string {\n  const { now = new Date(), clientOffsetSeconds = DEFAULT_CLIENT_OFFSET_SECONDS } = opts;\n  const clientToday = dateAtOffset(clientOffsetSeconds, now);\n  return addDays(clientToday, DAY_OFFSETS[term] ?? 0);\n}\n\n// The scan window behind every `day=` value. `days` ascending calendar\n// dates starting wherever `term` resolves to via slateDateFor — so\n// `today`/`tomorrow` only pick the window's *start* now, not a single exact\n// date, and `next` (or any unrecognized term) starts at the same offset\n// `today` does since neither has an entry in DAY_OFFSETS. Alpha-stage\n// relaxation (2026-08-26): `today`/`tomorrow` used to mean an exclusive\n// single date; loosened deliberately since this is a prototype, so the\n// server always scans rather than trusting the caller picked the one date\n// with a game. Sleeper has no team-schedule endpoint to answer \"when is\n// this team's next game\" directly (verified live against api.sleeper.app —\n// the only cheaper options are undocumented full-season dumps, up to 14MB\n// for mlb's daily slate), so the caller fetches one `/scores` request per\n// date in this window (in parallel — see main.ts) and picks the earliest\n// one that has a qualifying game. 3 days, not more: it comfortably covers\n// real in-season gaps (an nfl bye week, a rare mlb off-day) without the\n// window approaching the cost of an actual offseason scan, which is out of\n// scope by design — see docs/widget-next-up-plan.md.\nexport function windowDatesFor(\n  term: string,\n  clientOffsetSeconds: number,\n  opts: { now?: Date; days?: number } = {},\n): string[] {\n  const { now, days = 3 } = opts;\n  const start = slateDateFor(term, { now, clientOffsetSeconds });\n  return Array.from({ length: days }, (_, i) => addDays(start, i));\n}\n\n// The live GMT offset for an IANA zone at `now`, via Intl's own tables — so\n// the fallback path (an absent or rejected `?tz=`) stays DST-correct without\n// this file carrying a DST table of its own. \"longOffset\" is the\n// Intl.DateTimeFormat mode that always renders as \"GMT±HH:MM\", never a zone\n// abbreviation, which is what makes it parseable here.\nfunction offsetSecondsForZone(timeZone: string, now: Date): number {\n  const part = new Intl.DateTimeFormat(\"en-US\", { timeZone, timeZoneName: \"longOffset\" })\n    .formatToParts(now)\n    .find((p) => p.type === \"timeZoneName\")?.value;\n  const match = part && /^GMT([+-])(\\d{1,2}):(\\d{2})$/.exec(part);\n  if (!match) return 0;\n  const sign = match[1] === \"-\" ? -1 : 1;\n  return sign * (Number(match[2]) * 3600 + Number(match[3]) * 60);\n}\n\n// Validates a `?tz=` value: iOS sends TimeZone.current.secondsFromGMT(), an\n// integer seconds-east-of-GMT that already has DST folded in, so there is no\n// DST table to consult on this side — just range-check it. Same rule as\n// sports[]/teams[] in lib/params.ts: never throw on a bad value — a 4xx\n// renders as a broken image in WidgetKit — fall back to a default and let\n// the caller echo the rejected raw value so drift is visible, not silent.\n//\n// The range [-12:00, +14:00] is every real-world UTC offset (Baker Island to\n// Kiribati); anything outside it is a malformed value, not just an unusual\n// zone. `Number.isInteger` also catches non-numeric junk (\"abc\" -> NaN,\n// which fails the check) and fractional seconds (\"3600.5\"), which a bare\n// `parseInt` would silently truncate through.\n//\n// One trade this accepts, deliberately not engineered around: a WidgetKit\n// timeline entry built before a DST transition and rendered after it still\n// carries the pre-transition offset until iOS refreshes the timeline, so a\n// card spanning the transition can show times an hour off for a window. The\n// client owns DST now; this file no longer has the information to catch it.\nexport function resolveClientOffsetSeconds(\n  raw: string | null,\n  now = new Date(),\n): { offsetSeconds: number; rejected: string | null } {\n  const fallback = () => offsetSecondsForZone(DEFAULT_CLIENT_TIME_ZONE, now);\n  if (!raw) return { offsetSeconds: fallback(), rejected: null };\n  const parsed = Number(raw);\n  if (!Number.isInteger(parsed) || parsed < -43200 || parsed > 50400) {\n    return { offsetSeconds: fallback(), rejected: raw };\n  }\n  return { offsetSeconds: parsed, rejected: null };\n}\n\n// \"GMT-7\" / \"GMT+5:30\" / \"GMT\" for zero — the render layer's stand-in for a\n// zone abbreviation now that all it has is a number. No \"PDT\"-style name is\n// derivable from an offset alone (several zones share every offset), so this\n// is the honest version of that label rather than a guess at one.\nexport function offsetLabel(offsetSeconds: number): string {\n  if (offsetSeconds === 0) return \"GMT\";\n  const sign = offsetSeconds < 0 ? \"-\" : \"+\";\n  const abs = Math.abs(offsetSeconds);\n  const hours = Math.floor(abs / 3600);\n  const minutes = Math.floor((abs % 3600) / 60);\n  return `GMT${sign}${hours}${minutes ? \":\" + String(minutes).padStart(2, \"0\") : \"\"}`;\n}\n\n// isoDate is a plain calendar y-m-d (no timezone info), so format it as UTC\n// to avoid drifting a day off depending on the runtime's local timezone.\n//\n// `term` is the ?day= value the date was resolved from, and it leads the\n// label: \"Today · Wed Aug 19\". The date alone made the reader do the\n// lookup — a widget glanced at for two seconds should not have to answer\n// \"is Wed today?\" — and the word is the part that decides whether the card\n// is worth reading at all. Returned in title case; the png's eyebrow\n// uppercases it in CSS, the same way it already did with the bare date.\n//\n// An unrecognised term falls back to the bare date rather than interpolating\n// `undefined`, for the same reason slateDateFor takes `?? 0`: this renders\n// into a widget, where a wrong-looking card is worse than a plain one.\nexport function formatDateLabel(isoDate: string, term: string): string {\n  const [y, m, d] = isoDate.split(\"-\").map(Number);\n  const date = new Date(Date.UTC(y, m - 1, d));\n  const weekday = date.toLocaleDateString(\"en-US\", { timeZone: \"UTC\", weekday: \"short\" });\n  const monthDay = date.toLocaleDateString(\"en-US\", { timeZone: \"UTC\", month: \"short\", day: \"numeric\" });\n  const label = `${weekday} ${monthDay}`;\n  const word = DAY_WORDS[term];\n  return word ? `${word} · ${label}` : label;\n}\n",[],[173,337],"3a3929be-c4ba-41f0-ba5c-f01c7e425de4",["D",1788290293174],[],[173,59],"67f5f6ad-7fd0-480d-9914-14882587e177","config.ts","215780ce-a31a-11f1-8fad-1607ee4eb77e",105,["D",1788144349110],"// The /config/resolve -> / redirect: pure translation from a stored config\n// (favorite teams/sports) plus a receiver's per-request facts (canvas size,\n// client timezone) into the query string the existing stateless `/` route\n// already accepts. No I/O here — the sqlite lookup that produces a\n// StoredConfig lives in lib/configStore.ts instead, which is the impure half\n// bin/ci can't reach (see that file's header).\n//\n// `format` is never a param this file reads: /config/resolve exists only to\n// feed the native SwiftUI timeline provider, so `format=json` is baked into\n// every redirect it builds. See docs/widget-config-plan.md's 2026-08-27\n// amendment for why, and for why `w`/`h` collapse into one\n// `d=x` param here instead of staying separate the way `/`\n// itself still takes them — that part of `/`'s contract is unchanged.\n\nconst DEFAULT_WIDTH = 329;\nconst DEFAULT_HEIGHT = 155;\n\nexport type StoredConfig = { sports: string[]; teams: string[] };\nexport type ResolvePassthrough = { d?: string | null; tz?: string | null };\n\n// A second, separate config concern from StoredConfig above: not what\n// favorites to show, but how to present them. Stored in its own JSON\n// column (lib/configStore.ts's configs.personalization) rather than\n// folded into the sports/teams columns, specifically so more settings can\n// land here later without another migration touching the game-settings\n// half of the row. `intradayFilter: false` (the default — see\n// DEFAULT_PERSONALIZATION) is today's existing behavior: a completed game\n// keeps showing, captioned END, for the rest of its day. `true` omits it\n// from `items` entirely once it's final — see render/json.ts's\n// `hideCompleted` param, which this flows into via the `hideCompleted=1`\n// query param below.\nexport type Personalization = { intradayFilter: boolean };\nexport const DEFAULT_PERSONALIZATION: Personalization = { intradayFilter: false };\n\n// `d=1100x1146` -> {width, height}. Malformed or absent falls back to the\n// same defaults main.ts's own `w=`/`h=` parsing already uses (329x155) —\n// never-error, same posture as every other param this val accepts. A caller\n// sending `d=0x100` or `d=100x0` gets the default too: a zero-sized canvas\n// isn't a smaller-but-valid request, it's malformed the same way a negative\n// or missing one is.\nexport function parseDimensions(raw: string | null | undefined): { width: number; height: number } {\n  const match = raw ? /^(\\d+)x(\\d+)$/.exec(raw.trim()) : null;\n  if (match) {\n    const width = Number(match[1]);\n    const height = Number(match[2]);\n    if (width > 0 && height > 0) return { width, height };\n  }\n  return { width: DEFAULT_WIDTH, height: DEFAULT_HEIGHT };\n}\n\n// Builds the path+query `/config/resolve` redirects to. Repeated `teams[]`/\n// `sports[]` params, matching the shape lib/params.ts's resolveParams already\n// validates on arrival at `/` — that validation is the real safety net, so\n// this function doesn't re-check slugs, it just carries whatever the stored\n// config has. An empty config (no teams, no sports) produces a URL with\n// neither param, which `/` already treats as \"all four sports\" today.\n// `personalization` defaults to DEFAULT_PERSONALIZATION so every existing\n// caller that predates it (and any future one that doesn't care) keeps\n// getting exactly today's behavior — only `intradayFilter: true` adds\n// `hideCompleted=1`, kept out of the query string entirely otherwise\n// rather than sent as `hideCompleted=0`, matching this val's general\n// omit-rather-than-send-a-false posture for optional params.\nexport function buildResolvedUrl(\n  config: StoredConfig,\n  personalization: Personalization = DEFAULT_PERSONALIZATION,\n  passthrough: ResolvePassthrough = {},\n): string {\n  const { width, height } = parseDimensions(passthrough.d);\n  const params = new URLSearchParams();\n  params.set(\"format\", \"json\");\n  params.set(\"w\", String(width));\n  params.set(\"h\", String(height));\n  if (passthrough.tz) params.set(\"tz\", passthrough.tz);\n  for (const sport of config.sports) params.append(\"sports[]\", sport);\n  for (const team of config.teams) params.append(\"teams[]\", team);\n  if (personalization.intradayFilter) params.set(\"hideCompleted\", \"1\");\n  return `/?${params.toString()}`;\n}\n",[],[173,349],"e56a2086-2e44-497b-88f7-1f5181e25104","color.ts","9a12139c-9c23-11f1-b7ac-1607ee4eb77e",["D",1787181214708],"// Pure color math — HSL conversion and WCAG contrast. Domain-free: this\n// file knows nothing about the widget's palette, only how to convert and\n// measure. The palette itself lives in render/theme.ts, which is what makes\n// the 360-hue contrast assertions in tests/theme.test.ts possible without\n// pulling in a renderer.\n\n// Returns 0-255 channels. Standard HSL->RGB; h in degrees, s and l in 0..1.\nexport function hslToRgb(h: number, s: number, l: number): [number, number, number] {\n  const c = (1 - Math.abs(2 * l - 1)) * s;\n  const hp = (((h % 360) + 360) % 360) / 60;\n  const x = c * (1 - Math.abs((hp % 2) - 1));\n  const [r1, g1, b1] =\n    hp < 1 ? [c, x, 0]\n    : hp < 2 ? [x, c, 0]\n    : hp < 3 ? [0, c, x]\n    : hp < 4 ? [0, x, c]\n    : hp < 5 ? [x, 0, c]\n    : [c, 0, x];\n  const m = l - c / 2;\n  return [r1 + m, g1 + m, b1 + m].map((v) => Math.round(v * 255)) as [number, number, number];\n}\n\n// WCAG relative luminance. Channels in 0-255.\nexport function relativeLuminance([r, g, b]: [number, number, number]): number {\n  const channel = (v: number) => {\n    const s = v / 255;\n    return s <= 0.03928 ? s / 12.92 : Math.pow((s + 0.055) / 1.055, 2.4);\n  };\n  return 0.2126 * channel(r) + 0.7152 * channel(g) + 0.0722 * channel(b);\n}\n\n// WCAG contrast ratio between two relative luminances.\nexport function contrastRatio(a: number, b: number): number {\n  const [hi, lo] = a > b ? [a, b] : [b, a];\n  return (hi + 0.05) / (lo + 0.05);\n}\n",[],[173,357],"2a62eef8-4f13-4ae4-b57c-13cbc26f0c38","channels.ts","9a12060e-9c23-11f1-b7ac-1607ee4eb77e",["D",1787181214708],"// Turns Sleeper's raw channel string into the shape every render target\n// reads. Pure — the dictionaries it consults live in catalog.ts.\n\nimport { MAX_CHANNEL_LABEL, NATIONAL_CHANNELS, STREAMING_CHANNELS } from \"./catalog.ts\";\nimport { chop } from \"./text.ts\";\n\n// `name` stays the raw string Sleeper sent — it is the drift-detection\n// value, and the json format has to keep reporting what actually arrived.\n// `label` is the display form: dictionary-mapped where there is a mapping,\n// chopped raw text where there isn't.\nexport type ChannelInfo = {\n  category: string;\n  name: string | null;\n  label: string | null;\n  directv_channel: number | null;\n  note: string | null;\n};\n\nfunction channelMatches(rawChannel: string, key: string) {\n  return new RegExp(`\\\\b${key.replace(/[.*+?^${}()|[\\]\\\\]/g, \"\\\\$&\")}\\\\b`, \"i\").test(rawChannel);\n}\n\nexport function channelInfo(rawChannel: string | null | undefined): ChannelInfo {\n  if (!rawChannel) return { category: \"unknown\", name: null, label: null, directv_channel: null, note: null };\n\n  const nationalKey = Object.keys(NATIONAL_CHANNELS).find((key) => channelMatches(rawChannel, key));\n  if (nationalKey) return { category: \"national\", name: rawChannel, ...NATIONAL_CHANNELS[nationalKey] };\n\n  const streamingKey = Object.keys(STREAMING_CHANNELS).find((key) => channelMatches(rawChannel, key));\n  if (streamingKey) {\n    return { category: \"streaming\", name: rawChannel, directv_channel: null, ...STREAMING_CHANNELS[streamingKey] };\n  }\n\n  return {\n    category: \"regional\",\n    name: rawChannel,\n    label: chop(rawChannel, MAX_CHANNEL_LABEL),\n    directv_channel: null,\n    note: null,\n  };\n}\n",[],[173,364],"d80ec1e8-3127-4b4b-98b4-b6187ee868f7","catalog.ts","9a11c298-9c23-11f1-b7ac-1607ee4eb77e",65,["D",1788112810274],3,"// The static tables the rest of the val reads: what sports exist, how\n// channels map to display forms and DirecTV numbers, and which team slugs\n// the URL accepts. Data only — no functions, no I/O — so every other module\n// can import it without dragging behaviour along.\n//\n// Ported from app/controllers/games_controller.rb.\n\n// Doubles as the fetch list, the allowlist for the `sports[]` param, and\n// the group order in the rendered output. Order is display order, not\n// significance — nfl first because it's the one with a hard weekly cadence.\n//\n// Growing this from nfl+wnba to four sports makes an unfiltered slate large\n// (mlb+wnba alone returned 19 games on 2026-08-18), which is the whole\n// reason the `teams[]` filter exists — see docs/widget-param-contract.md.\nexport const SPORTS = [\"nfl\", \"wnba\", \"mlb\", \"nba\"];\n\n// Per-sport decoration for the widget's mainText template\n// (render/templates.ts's DEFAULT_WIDGET_TEMPLATE), at explicit request.\n// wnba and nba share the basketball emoji — same sport, same ball, just two\n// separate SPORTS entries (see the nba-deferred note on TEAMS above) — nfl\n// gets football, mlb gets baseball. Keyed on the same sport string as\n// SPORTS/TEAMS, not a separate vocabulary. `Partial` because a sport added\n// to SPORTS later has no entry until one is deliberately added here — a\n// plain `Record` would claim every sport already does.\nexport const SPORT_EMOJI: Partial> = {\n  nfl: \"🏈\",\n  wnba: \"🏀\",\n  mlb: \"⚾\",\n  nba: \"🏀\",\n};\n\n// Ported from GamesController::NATIONAL_CHANNELS /\n// GamesController::STREAMING_CHANNELS. See that file for the reasoning\n// behind word-boundary matching (plain substring mislabels \"NBCS-PH\" as an\n// NBC affiliate) and the amzn/amazon dual-key (Sleeper sends the long form\n// for mlb/wnba).\n//\n// `label` is this file's own addition, not in the Rails port: the short form\n// the png draws. It exists because Sleeper's raw strings are not sized for a\n// widget — \"Amazon Prime Video\" is 18 characters and ran off the side of a\n// large card. The values are a small bounded set, so they get a mapping\n// rather than a measuring algorithm. AMZN is Sleeper's own abbreviation for\n// that channel (it sends both forms, hence the dual key below), so this\n// shortens to something the source already uses rather than inventing one.\nexport const NATIONAL_CHANNELS: Record = {\n  abc: { label: \"ABC\", directv_channel: 4, note: null },\n  cbs: { label: \"CBS\", directv_channel: 2, note: null },\n  espn: { label: \"ESPN\", directv_channel: 206, note: null },\n  ion: { label: \"ION\", directv_channel: 305, note: null },\n  nbatv: { label: \"NBATV\", directv_channel: 216, note: null },\n  nbc: { label: \"NBC\", directv_channel: 4, note: null },\n  tbs: { label: \"TBS\", directv_channel: 247, note: null },\n  usa: { label: \"USA\", directv_channel: 242, note: null },\n  sportsnet: { label: \"SportsNet\", directv_channel: 691, note: null },\n};\n\nexport const STREAMING_CHANNELS: Record = {\n  amzn: { label: \"AMZN\", note: \"computer only\" },\n  amazon: { label: \"AMZN\", note: \"computer only\" },\n  peacock: { label: \"Peacock\", note: \"computer only\" },\n};\n\n// The backstop for the one category that has no mapping: a regional channel\n// is whatever free text Sleeper sent, so it cannot be bounded by a\n// dictionary the way the two above are. Real values are already short\n// (SNY, MARQ, NESN, MASN, NBCS-PH), so this only fires on something\n// unusual — a blunt chop rather than a width measurement, which is all a\n// backstop needs to be.\nexport const MAX_CHANNEL_LABEL = 10;\n\n// ---- favorite teams ----\n//\n// Slug -> (sport, Sleeper code). The pair matters: Sleeper's abbreviations\n// are NOT unique across sports. `IND` is the Fever (wnba), the Colts (nfl)\n// and the Pacers (nba) — all three confirmed in live data and captured in\n// test/fixtures/files/sleeper/. Matching a bare code would make \"fever\" pull\n// in Colts and Pacers games. `WAS` (nfl + wnba, while mlb uses `WSH`) plus\n// ATL/MIN/CHI/DET/HOU/TOR/BOS/TB/SEA/PHI/PIT are the same trap, now realized\n// as nfl, wnba and mlb have all grown into it — every one of those codes now\n// names a different franchise depending on sport, which is exactly why the\n// pair (not the bare code) is what's stored.\n//\n// A second, separate collision shows up on the *slug* side, not the code\n// side: two mascots can share a name across sports even when their codes\n// don't collide. `cardinals` (nfl Arizona, code ARI) and `giants` (nfl New\n// York, code NYG) were claimed first, so their mlb namesakes (St. Louis,\n// code STL; San Francisco, code SF) get a city-prefixed slug instead —\n// `st-louis-cardinals`, `san-francisco-giants`. Spelled out rather than\n// abbreviated (`stl-`, `sf-`) because titleCase() only capitalizes each\n// hyphen-split word's first letter — `sf-giants` would render as \"Sf\n// Giants\", not \"SF Giants\". Every other mlb slug is unprefixed.\n//\n// The URL carries slugs, not codes, and this table is the only place the\n// mapping lives. That's deliberate: the iOS app ships a picker, and every\n// app-side change costs a build-number bump on both the app and the widget\n// extension plus an upload. Adding a team here is a val deploy instead. See\n// docs/widget-ios-brief.md.\n//\n// Every code here is asserted against a real captured fixture for its sport\n// — but a fixture only proves the code was valid on its capture date, not\n// that Sleeper still uses it. The runtime echo (rejected/unmatched surfaced\n// to the caller) is the actual drift detector.\nexport type TeamRef = { sport: string; code: string };\n\nexport const TEAMS: Record = {\n  // wnba — all 15 teams for the 2026 season (includes the Valkyries,\n  // Tempo, and Fire expansions), codes confirmed against live\n  // api.sleeper.app/scores responses.\n  dream: { sport: \"wnba\", code: \"ATL\" },\n  sky: { sport: \"wnba\", code: \"CHI\" },\n  sun: { sport: \"wnba\", code: \"CON\" },\n  wings: { sport: \"wnba\", code: \"DAL\" },\n  valkyries: { sport: \"wnba\", code: \"GSV\" },\n  fever: { sport: \"wnba\", code: \"IND\" },\n  sparks: { sport: \"wnba\", code: \"LAS\" },\n  aces: { sport: \"wnba\", code: \"LVA\" },\n  lynx: { sport: \"wnba\", code: \"MIN\" },\n  liberty: { sport: \"wnba\", code: \"NYL\" },\n  fire: { sport: \"wnba\", code: \"PDX\" },\n  mercury: { sport: \"wnba\", code: \"PHO\" },\n  storm: { sport: \"wnba\", code: \"SEA\" },\n  tempo: { sport: \"wnba\", code: \"TOR\" },\n  mystics: { sport: \"wnba\", code: \"WAS\" },\n\n  // nfl — all 32 teams, codes confirmed against live\n  // api.sleeper.app/scores responses.\n  cardinals: { sport: \"nfl\", code: \"ARI\" },\n  falcons: { sport: \"nfl\", code: \"ATL\" },\n  ravens: { sport: \"nfl\", code: \"BAL\" },\n  bills: { sport: \"nfl\", code: \"BUF\" },\n  panthers: { sport: \"nfl\", code: \"CAR\" },\n  bears: { sport: \"nfl\", code: \"CHI\" },\n  bengals: { sport: \"nfl\", code: \"CIN\" },\n  browns: { sport: \"nfl\", code: \"CLE\" },\n  cowboys: { sport: \"nfl\", code: \"DAL\" },\n  broncos: { sport: \"nfl\", code: \"DEN\" },\n  lions: { sport: \"nfl\", code: \"DET\" },\n  packers: { sport: \"nfl\", code: \"GB\" },\n  texans: { sport: \"nfl\", code: \"HOU\" },\n  colts: { sport: \"nfl\", code: \"IND\" },\n  jaguars: { sport: \"nfl\", code: \"JAX\" },\n  chiefs: { sport: \"nfl\", code: \"KC\" },\n  chargers: { sport: \"nfl\", code: \"LAC\" },\n  rams: { sport: \"nfl\", code: \"LAR\" },\n  raiders: { sport: \"nfl\", code: \"LV\" },\n  dolphins: { sport: \"nfl\", code: \"MIA\" },\n  vikings: { sport: \"nfl\", code: \"MIN\" },\n  patriots: { sport: \"nfl\", code: \"NE\" },\n  saints: { sport: \"nfl\", code: \"NO\" },\n  giants: { sport: \"nfl\", code: \"NYG\" },\n  jets: { sport: \"nfl\", code: \"NYJ\" },\n  eagles: { sport: \"nfl\", code: \"PHI\" },\n  steelers: { sport: \"nfl\", code: \"PIT\" },\n  seahawks: { sport: \"nfl\", code: \"SEA\" },\n  \"49ers\": { sport: \"nfl\", code: \"SF\" },\n  buccaneers: { sport: \"nfl\", code: \"TB\" },\n  titans: { sport: \"nfl\", code: \"TEN\" },\n  commanders: { sport: \"nfl\", code: \"WAS\" },\n\n  // mlb — all 30 teams, codes confirmed against live\n  // api.sleeper.app/scores responses. Two mascot names collide with an nfl\n  // slug already in this table (Cardinals, Giants) — those two get a city\n  // prefix; every other mlb slug is unprefixed.\n  athletics: { sport: \"mlb\", code: \"ATH\" },\n  braves: { sport: \"mlb\", code: \"ATL\" },\n  diamondbacks: { sport: \"mlb\", code: \"AZ\" },\n  orioles: { sport: \"mlb\", code: \"BAL\" },\n  \"red-sox\": { sport: \"mlb\", code: \"BOS\" },\n  cubs: { sport: \"mlb\", code: \"CHC\" },\n  reds: { sport: \"mlb\", code: \"CIN\" },\n  guardians: { sport: \"mlb\", code: \"CLE\" },\n  rockies: { sport: \"mlb\", code: \"COL\" },\n  \"white-sox\": { sport: \"mlb\", code: \"CWS\" },\n  tigers: { sport: \"mlb\", code: \"DET\" },\n  astros: { sport: \"mlb\", code: \"HOU\" },\n  royals: { sport: \"mlb\", code: \"KC\" },\n  angels: { sport: \"mlb\", code: \"LAA\" },\n  dodgers: { sport: \"mlb\", code: \"LAD\" },\n  marlins: { sport: \"mlb\", code: \"MIA\" },\n  brewers: { sport: \"mlb\", code: \"MIL\" },\n  twins: { sport: \"mlb\", code: \"MIN\" },\n  mets: { sport: \"mlb\", code: \"NYM\" },\n  yankees: { sport: \"mlb\", code: \"NYY\" },\n  phillies: { sport: \"mlb\", code: \"PHI\" },\n  pirates: { sport: \"mlb\", code: \"PIT\" },\n  padres: { sport: \"mlb\", code: \"SD\" },\n  mariners: { sport: \"mlb\", code: \"SEA\" },\n  \"san-francisco-giants\": { sport: \"mlb\", code: \"SF\" },\n  \"st-louis-cardinals\": { sport: \"mlb\", code: \"STL\" },\n  rays: { sport: \"mlb\", code: \"TB\" },\n  rangers: { sport: \"mlb\", code: \"TEX\" },\n  \"blue-jays\": { sport: \"mlb\", code: \"TOR\" },\n  nationals: { sport: \"mlb\", code: \"WSH\" },\n\n  // nba — left as-is for now, deferred until later.\n  lakers: { sport: \"nba\", code: \"LAL\" },\n  warriors: { sport: \"nba\", code: \"GSW\" },\n};\n\n// This exists to bound a malformed URL, not to express a preference — it\n// must sit above any realistic favorites selection. 12 was fine when the\n// table only had 7 slugs total, but now that wnba (15), nfl (32) and mlb\n// (30) are fully mapped, a user favoriting a whole league — or several —\n// is normal input, not a malformed URL, and a lower cap would reject them\n// with a drift marker for doing nothing wrong. Set with headroom above the\n// eventual four-sport table (nfl+wnba+mlb+nba is ~110 teams) so adding nba\n// later doesn't require raising this again.\nexport const MAX_TEAMS = 120;\n",[],[173,371],["D",1787181214708],[191,192,193,194,195,196,197,198,199,200,201,202],[173],["D",1787009561780],["D",1789532458193],{"_118":117,"_125":121},{"_118":117,"_119":-5,"_120":121,"_18":75,"_122":123,"_124":27},{"_13":107,"_34":108,"_63":44,"_109":64,"_110":-5,"_111":-5,"_112":-5,"_113":-5,"_114":-5,"_115":65,"_116":117},"ctx",{"_100":-5,"_145":420,"_421":422,"_423":424,"_425":27,"_426":27,"_427":27,"_428":47,"_429":-5,"_430":-7,"_431":-7,"_432":81,"_433":27,"_434":27,"_435":-5,"_436":27,"_437":27,"_438":27,"_439":-5},"ENV",{"_391":392,"_393":394,"_395":108,"_396":397,"_398":399,"_400":401,"_402":403,"_404":405,"_406":407,"_408":409,"_410":411,"_412":413,"_414":415,"_416":417,"_418":419},"REACT_APP_SENTRY_DSN","https://586020d86f05489db63a554690acf1e9@o1398359.ingest.sentry.io/6724499","RENDER_GIT_COMMIT","e87eb04e707cf64e7e532c8e8ec395f209e17f15","RENDER_GIT_BRANCH","POSTHOG_API_TOKEN","phc_nmoyuAkStEZuUp69rYlg1DZgrIt19Gx0Y4Hwf8tGgJP","POSTHOG_API_HOST","https://wart.val.town","WEB_API_TEMPLATE","https://{val}.web.val.run","APP_URL","https://www.val.town","MODULE_URL","https://esm.town","VANITY_WEB_API_TEMPLATE","https://{label}.val.run/","DENOLS_URL","https://lsp.val.town","NODE_ENV","production","CLOUDFLARE_TURNSTILE_SITE_KEY","0x4AAAAAACtaIZJH7s9rBMZ6","GOOGLE_CLIENT_ID","875989696899-jtsqkhlbdv5jrlsk8631p7ipjg3c6o62.apps.googleusercontent.com","STRIPE_PUBLISHABLE_KEY","pk_live_51N2zvWEpZTTLipIkVEwXrUG9AT0yeOOEYxszarZT1jpsZV58Ly6wlg3SltZpHN26CUalOBmUSY7adQRQiSkCZz2500qSXNkf8Y","API_URL","https://api.val.town",[],"preferencesKeybindings","default","preferencesTheme","light","preferencesFixers","preferencesCopilot","preferencesSelectionAi","preferencesCloseBrackets","preferencesChatPanelState","preferencesDprint","preferencesDenofmt","notificationCount","flagDenols","isBusinessOrgMember","businessOrgHandle","isBusinessOrgAdmin","isHigherTownieTier","navCollapsed","currentOrgId"]

Diff · v128