${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",[],[166,267],"c8e59698-6e33-4bb8-bda2-a45e2b156bd9","configHtml.ts","01a05e65-e8e3-70a5-ba7f-14ffcc91eac6",3,["D",1788290167606],"// 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 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 \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}",[],[166,274],"dcb15083-242a-444d-978c-8e206b859a6b",["D",1788290132196],[193,194,195,196,197,198,199,200,201],[166],"fef995de-f8a5-4810-8860-820a1146e26b","text.ts","01a05e65-e8e3-70a5-ba7f-0f110c629f96","01a05e65-e8e3-70a5-ba7f-1375940a6e69",["D",1788290132196],"// 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",[],[293,286],"lib","82b7e31c-64d2-4c0d-8cd0-e0d2e8e15de0","teams.ts","01a05e65-e8e3-70a5-ba7f-090ce18f7e52",["D",1788290132196],"// 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",[],[293,295],"252e8a6e-f361-408e-a5ef-b93a2a249a34","sleeper.ts","01a05e65-e8e3-70a5-ba7f-06b596cd7798",["D",1788290132196],"// 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",[],[293,302],"372dc129-46f9-49b5-b6b0-c7be3421fc1e","push.ts","01a05e65-e8e3-70a5-ba7f-030a64983455",["D",1788290132196],"// 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",[],[293,309],"993006af-2b82-4b35-a4ed-a40ebc853404","params.ts","01a05e65-e8e3-70a5-ba7e-fcf63eee4963",["D",1788290132196],"// 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",[],[293,316],"0e518349-0df6-4966-9f03-6ecf401e3404","games.ts","01a05e65-e8e3-70a5-ba7e-f90e54c90e88",["D",1788290132196],"// 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",[],[293,323],"669777cf-4328-4539-a5fd-f448ad7bb4d5","dates.ts","01a05e65-e8e3-70a5-ba7e-f725aa0b3a7f",["D",1788290132196],"// 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",[],[293,330],"3682abe8-0c98-42e0-b464-7d40495a59c4","configStore.ts","01a05e65-e8e3-70a5-ba7e-f0dc78f0f024",2,["D",1788290164105],"// 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",[],[293,337],"4c63e010-acf4-4ac1-b8a9-22d89487fc8f","config.ts","01a05e65-e8e3-70a5-ba7e-ef4e00acf814",["D",1788290132196],"// 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",[],[293,345],"78442c2e-2818-418f-af9f-d713d6a2af47","color.ts","01a05e65-e8e3-70a5-ba7e-ebf7db233f96",["D",1788290132196],"// 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",[],[293,352],"b388a49f-0f0d-4c34-9c02-23e9e6d785ca","channels.ts","01a05e65-e8e3-70a5-ba7e-e7154a801d33",["D",1788290132196],"// 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",[],[293,359],"13c8814f-9bc2-40df-92d8-43f60fc5294a","catalog.ts","01a05e65-e8e3-70a5-ba7e-e09cbf07b950",["D",1788290132196],"// 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",[],[293,366],"95119110-2df6-4d30-b252-cfb73ff5034b",["D",1788290132196],[180,181,182,183,184,185,186,187,188,189,190,191],[293],["D",1787009561780],["D",1789532458193],{"_11":12,"_128":76},{"_11":12,"_124":-5,"_75":76,"_30":74,"_125":126,"_127":24},{"_38":114,"_13":16,"_32":35,"_115":78,"_116":64,"_117":118,"_119":82,"_120":78,"_121":41,"_122":14,"_123":12},"ctx",{"_53":-5,"_149":414,"_415":416,"_417":418,"_419":24,"_420":24,"_421":24,"_422":147,"_423":-5,"_424":-7,"_425":-7,"_426":26,"_427":24,"_428":24,"_429":-5,"_430":24,"_431":24,"_432":24,"_433":-5},"ENV",{"_385":386,"_387":388,"_389":65,"_390":391,"_392":393,"_394":395,"_396":397,"_398":399,"_400":401,"_402":403,"_404":405,"_406":407,"_408":409,"_410":411,"_412":413},"REACT_APP_SENTRY_DSN","https://586020d86f05489db63a554690acf1e9@o1398359.ingest.sentry.io/6724499","RENDER_GIT_COMMIT","811aa22498c9b0b5a47e8d778de579cdb990f332","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"]

History · theme.ts