cursedbelt-server 4.18.1 → 4.19.1

package/README.md

@@ -0,0 +1,61 @@
+# cursedbelt-server
+
+The server tier of the cursedbelt split: Hono on Bun, the D1 seam a Worker crosses, the
+binary-server client, the guard, and the fleet standards (retention, activity, notifications,
+engagement). `cursedbelt-core` is below it, the React design system `cursedbelt` above it.
+
+```sh
+bun add cursedbelt-server
+```
+
+## 🔴 The root export is a BARREL — import the leaf
+
+`import … from "cursedbelt-server"` re-exports everything, so it reaches every optional peer and
+`bun:sqlite` at once (the table below). An app that wants one function pays for all of them, and
+on a Worker `wrangler deploy` fails to bundle it. Import the subpath that owns the symbol —
+`cursedbelt-server/login-throttle`, `cursedbelt-server/binary-store`, `cursedbelt-server/d1` —
+never the root. `package.json` `exports` is the list of subpaths.
+
+Why this stays prose: which symbol an app WANTS is decided in the app, and a repo's gate proves
+that repo — so the barrel-importer grep belongs to the generation's tools, not to this package.
+
+## What you install
+
+Most subpaths need nothing beyond `hono` (and `zod` where they validate). These are the only
+ones that statically reach an OPTIONAL peer, or a bun builtin a Worker does not have. The table
+is checked: `src/readmeInstallTable.spec.ts` fails when it disagrees with `src/subpathReach.ts`,
+and `src/barrelsReachNoOptionalPeer.spec.ts` fails when that disagrees with what a bundler
+actually keeps.
+
+| subpath | optional peers it imports | bun builtins it needs |
+|---|---|---|
+| `.` | `kysely`, `kysely-bun-sqlite`, `otplib`, `plainjob` | `bun:sqlite` |
+| `./jobs` | `plainjob` | — |
+| `./d1/backup-local` | — | `bun:sqlite` |
+| `./guard` | — | `bun:sqlite` |
+| `./guard/revocations` | — | `bun:sqlite` |
+| `./sqlite` | — | `bun:sqlite` |
+| `./engagement` | — | `bun:sqlite` |
+
+`sharp` and `@node-rs/argon2` are loaded lazily (`await import()`), so a missing one breaks only
+the feature that asks for it, not the build.
+
+## 🔴 `Bun.serve`'s `websocket` selects an OVERLOAD
+
+It is not an optional field. An options object whose `websocket` may be `undefined` — a
+conditional value or a conditional spread — matches no overload, and TypeScript reports an error
+about the whole options object rather than the one field. Use `serveBun(app, { websocket })`,
+which takes it as a genuinely optional field and makes the two concrete calls itself.
+`src/server/serveBunOverload.spec.ts` runs `tsc` on the trap and goes red when bun's types change.
+
+## Standards
+
+`docs/retention.md`, `docs/activity.md`, `docs/notifications.md`, `docs/engagement.md` — the
+contracts every app that uses those modules is agreeing to. Cite them from an app with the
+package prefix (`cursedbelt-server/docs/retention.md`).
+
+## Verifying
+
+```sh
+cd "$FORGE/libs/cursedbelt-server" && bun run verify
+```

package/dist/server/activity/index.d.ts

@@ -10,7 +10,8 @@
  *
  * ── Retention ───────────────────────────────────────────────────────────────
  * This package never deletes an event. An app whose stream is high-volume opts
- * into the fleet standard (`cursedbelt-server/retention`, in this package) by
+ * into the fleet standard (`cursedbelt-server/retention`; the contract is
+ * `docs/retention.md` in this package, and this stream's own is `docs/activity.md`) by
  * declaring the table, which puts the number under the owner's control in the
  * station rather than in a constant here:
  *

package/dist/server/activity/index.js

@@ -10,7 +10,8 @@
  *
  * ── Retention ───────────────────────────────────────────────────────────────
  * This package never deletes an event. An app whose stream is high-volume opts
- * into the fleet standard (`cursedbelt-server/retention`, in this package) by
+ * into the fleet standard (`cursedbelt-server/retention`; the contract is
+ * `docs/retention.md` in this package, and this stream's own is `docs/activity.md`) by
  * declaring the table, which puts the number under the owner's control in the
  * station rather than in a constant here:
  *

package/dist/server/auth/passwordCost.d.ts

@@ -0,0 +1,21 @@
+/** Production: the runtime's own argon2id defaults, with nothing pinned by hand. */
+export declare const PRODUCTION_ARGON2: Bun.Password.Argon2Algorithm;
+/** The floor argon2id accepts — free, and still argon2id. */
+export declare const TEST_ARGON2: Bun.Password.Argon2Algorithm;
+/**
+ * Which cost this process should pay. Takes `env` explicitly so the failure path is
+ * drivable: a check that can only be run under the runner it is deciding about is a
+ * check nobody can prove.
+ */
+export declare function argon2Cost(env?: NodeJS.ProcessEnv): Bun.Password.Argon2Algorithm;
+/**
+ * Hash a secret at the right cost for this process. The one call every app should use;
+ * a bare `Bun.password.hash(x, "argon2id")` pays production's cost in every test.
+ */
+export declare const hashSecret: (secret: string) => Promise<string>;
+/**
+ * Verify a secret against a stored argon2id PHC string — `false`, never a throw, on anything
+ * malformed. `Bun.password` on the Mac; on the Worker the same global is `worker/password.ts`'s
+ * pure-JS shim, which reproduces Bun's hashes byte for byte, so every stored verifier keeps working.
+ */
+export declare const verifySecret: (secret: string, hash: string) => Promise<boolean>;

package/dist/server/auth/passwordCost.js

@@ -0,0 +1,80 @@
+/**
+ * HOW EXPENSIVE ARGON2ID SHOULD BE IN THIS PROCESS — production's cost, unless a test
+ * runner is in charge.
+ *
+ * ## The measurement (2026-09-09)
+ *
+ * Argon2id is slow ON PURPOSE: one hash costs ~66 ms on this Mac, and that slowness IS
+ * the security property. It is also the wrong price to pay six hundred times in a unit
+ * test whose assertion is *"a wrong password is refused"* — that asserts the comparison,
+ * never the cost of the KDF.
+ *
+ * `apps/auth`'s own suite, measured both ways with nothing else changed:
+ *
+ *     production cost   52.85 s
+ *     test cost          7.32 s
+ *
+ * Eighty-six per cent of what was, that morning, the largest single workspace in
+ * `verify:scoped` — paid by every agent on every branch touching auth or any shared
+ * package, and again on every union gate.
+ *
+ * ## Why this is safe to key on the test runtime, stated plainly
+ *
+ * A weakened KDF is the most dangerous thing this module could do, so the argument has
+ * to be better than "the flag is only set in tests".
+ *
+ * `TEST_RUNTIME_ENV_KEYS` is the fleet's existing answer to *"is a test runner in
+ * charge"*, and `app-data` **already refuses to open the owner's real database** when it
+ * is true. A process carrying one of these markers therefore has no production data to
+ * write a weak hash into — it is the same claim, load-bearing in the same direction,
+ * decided in one place. If that guarantee ever weakens, it weakens for the database
+ * first, which is the louder failure.
+ *
+ * The ALGORITHM never changes. Only `memoryCost`/`timeCost` move, argon2 encodes its own
+ * parameters into the hash, and verification is therefore identical — so a stored hash
+ * made under either cost verifies under either cost.
+ *
+ * ## `cursedbelt-server/password`, since 4.19.0 (task 321)
+
+It was `src/kit/passwordCost.ts` in `auth`, `collections`, `patterns` and `vault` — four copies of
+a security-relevant cost decision, one of them (`vault`) already carrying a `verifySecret` the
+others lacked. The test-runtime rule it keys on is `./satellite-door`'s `isTestRuntime`, the same
+predicate that refuses a test the owner's real database, so the two can never disagree about
+whether a runner is in charge. It is not in `cursedauth` because that package has no
+dependencies and this decision must share its predicate, not copy it.
+
+## Why it lives in one place and not in each app
+ *
+ * Five call sites hashed at production cost when this was written — `apps/auth`,
+ * `apps/collections` (×2), `apps/patterns`, `apps/vault` — and a per-app copy of a
+ * security-relevant cost decision is how four of them end up agreeing and the fifth does
+ * not. One module, one test, one place to read.
+ */
+import { isTestRuntime } from "../satellite/door.js";
+/** Production: the runtime's own argon2id defaults, with nothing pinned by hand. */
+export const PRODUCTION_ARGON2 = { algorithm: "argon2id" };
+/** The floor argon2id accepts — free, and still argon2id. */
+export const TEST_ARGON2 = {
+    algorithm: "argon2id",
+    memoryCost: 8,
+    timeCost: 1,
+};
+/**
+ * Which cost this process should pay. Takes `env` explicitly so the failure path is
+ * drivable: a check that can only be run under the runner it is deciding about is a
+ * check nobody can prove.
+ */
+export function argon2Cost(env = process.env) {
+    return isTestRuntime(env) ? TEST_ARGON2 : PRODUCTION_ARGON2;
+}
+/**
+ * Hash a secret at the right cost for this process. The one call every app should use;
+ * a bare `Bun.password.hash(x, "argon2id")` pays production's cost in every test.
+ */
+export const hashSecret = (secret) => Bun.password.hash(secret, argon2Cost());
+/**
+ * Verify a secret against a stored argon2id PHC string — `false`, never a throw, on anything
+ * malformed. `Bun.password` on the Mac; on the Worker the same global is `worker/password.ts`'s
+ * pure-JS shim, which reproduces Bun's hashes byte for byte, so every stored verifier keeps working.
+ */
+export const verifySecret = (secret, hash) => Bun.password.verify(secret, hash).catch(() => false);

package/dist/server/bench/index.d.ts

@@ -38,3 +38,4 @@ export { type CpuBudgetOpts, cpuBudget } from './cpuBudget.js';
 export { type CpuClock, type CpuSpan, fixedCpuClock, processCpuClock, resolveCpuClock, unavailableCpuClock, workerCpuClock, } from './cpuClock.js';
 export { type CpuBudgetReport, type CpuRecorder, type CpuRecorderOpts, createCpuRecorder, percentile, type RouteCpuStats, } from './recorder.js';
 export { BENCH_ORIGIN, type BenchCase, runCpuBench, type RunCpuBenchOpts } from './runBench.js';
+export { parseTailLines, type RecordTailTracesOpts, recordTailTraces, routeMatcher, TAIL_CPU_SOURCE, type TailRecordResult, type TailTraceLike, type TailTrafficRate, tailCpuClock, tailTrafficRate, UNMATCHED_ROUTE, } from './tail.js';

package/dist/server/bench/index.js

@@ -38,3 +38,4 @@ export { cpuBudget } from './cpuBudget.js';
 export { fixedCpuClock, processCpuClock, resolveCpuClock, unavailableCpuClock, workerCpuClock, } from './cpuClock.js';
 export { createCpuRecorder, percentile, } from './recorder.js';
 export { BENCH_ORIGIN, runCpuBench } from './runBench.js';
+export { parseTailLines, recordTailTraces, routeMatcher, TAIL_CPU_SOURCE, tailCpuClock, tailTrafficRate, UNMATCHED_ROUTE, } from './tail.js';

package/dist/server/bench/tail.d.ts

@@ -0,0 +1,110 @@
+/**
+ * The REAL reading: Worker CPU-ms off a tail worker's trace events, fed into the same recorder
+ * and the same assertion the local proxy uses.
+ *
+ * ## Why this shape, and not a clock
+ *
+ * {@link workerCpuClock} is a clock — `start()` then read again — and the isolate never hands a
+ * handler its own CPU time, so there is nothing for it to read inside a request. What Cloudflare
+ * DOES publish is one `cpuTime` per invocation on the trace event a TAIL worker receives (the
+ * same field `wrangler tail --format json` prints — `apps/binary-server/scripts/edgeTail.ts`
+ * already reads it there). So the real number arrives AFTER the request, per request, and the
+ * honest API is to record it then: {@link recordTailTraces} turns trace events into samples on a
+ * recorder built with {@link tailCpuClock}, which stamps `proxy: false`.
+ *
+ * Two ways to get the events, and a consumer needs neither code nor a new Worker for the first:
+ *
+ *   · **`wrangler tail <worker> --format json`** during a bench or a smoke against the live
+ *     Worker — one JSON trace per line, parsed with {@link parseTailLines}.
+ *   · **a Tail Worker** (`tail_consumers` in the producer's wrangler config) whose `tail(events)`
+ *     hands the array straight to {@link recordTailTraces}.
+ *
+ * 🔴 The degenerate guard still applies, deliberately. `cpuTime` is whole milliseconds, so a
+ * route that genuinely costs under 1 ms reads 0 — and a report where EVERY reading is 0 is still
+ * refused, because that is indistinguishable from a reader that is not reading. One real route
+ * above a millisecond anywhere in the window clears it; `allowZeroCpu` is not the fix.
+ *
+ * ## The traffic half
+ *
+ * {@link tailTrafficRate} is requests per day over the window the events span — the number
+ * `deriveCpuBudgetMs({ requestsPerDay })` needs to re-derive the default from THIS generation's
+ * Worker traffic (tasks 342/377) instead of the retired generation's corpus.
+ */
+import type { CpuClock } from './cpuClock.js';
+import type { CpuRecorder } from './recorder.js';
+/** The fields of a Cloudflare `TraceItem` this reads — structural, so no workers-types import. */
+export interface TailTraceLike {
+    /** CPU-ms of the whole invocation, as billed. Absent on runtimes that do not report it. */
+    cpuTime?: number | null;
+    wallTime?: number | null;
+    /** Epoch ms. */
+    eventTimestamp?: number | null;
+    outcome?: string | null;
+    scriptName?: string | null;
+    /** A fetch invocation carries `request`; a cron or queue invocation does not. */
+    event?: {
+        request?: {
+            url?: string;
+            method?: string;
+        } | null;
+    } | null;
+}
+/** Provenance printed on every report built from tail events. */
+export declare const TAIL_CPU_SOURCE = "tail-worker cpuTime";
+/**
+ * The clock for a recorder that is FED rather than started. `proxy: false`: this is the quantity
+ * Cloudflare bills. Its `start()` throws — a tail recorder mounted as `cpuBudget()` middleware is
+ * a wiring mistake, and a span that silently measured nothing is the lie this module refuses.
+ */
+export declare function tailCpuClock(source?: string): CpuClock;
+/**
+ * A `(method, path) → route label` matcher over declared route keys — the recorder's own
+ * `config.routes`, by default — so an app gets tail attribution with no code of its own. The
+ * most literal pattern wins, and a method-specific key beats an any-method one.
+ */
+export declare function routeMatcher(keys: readonly string[]): (method: string, path: string) => string | null;
+/** The label traffic that matched no declared route is recorded under — so `requireDeclared` names it. */
+export declare const UNMATCHED_ROUTE = "(no declared route)";
+export interface RecordTailTracesOpts {
+    /** Map a request to its route label. Default: {@link routeMatcher} over the recorder's declared routes. */
+    route?: (method: string, path: string) => string | null;
+    /** Only this Worker's invocations — a tail consumer may receive several producers. */
+    scriptName?: string;
+}
+export interface TailRecordResult {
+    recorded: number;
+    /** Invocations with no request (cron, queue) — CPU, but no route to charge it to. */
+    notFetch: number;
+    /** Fetch invocations whose trace carried no finite `cpuTime`. */
+    noCpuTime: number;
+    /** Recorded under {@link UNMATCHED_ROUTE}; up to ten distinct paths, so the gap is nameable. */
+    unmatched: number;
+    unmatchedPaths: string[];
+}
+/**
+ * Charge each fetch invocation's billed `cpuTime` to its route on `recorder`.
+ *
+ * 🔴 A trace with no finite `cpuTime` is NOT a zero — it is skipped and counted, so a runtime
+ * that stopped reporting the field reads as "nothing recorded" (and the assertion's `no-samples`
+ * guard reds it) rather than as a confident route that costs nothing.
+ */
+export declare function recordTailTraces(recorder: CpuRecorder, traces: readonly TailTraceLike[], opts?: RecordTailTracesOpts): TailRecordResult;
+/**
+ * `wrangler tail --format json` output → trace events. Tolerates the banner lines wrangler
+ * prints and blank lines; a line that is not a JSON object is skipped, never guessed at.
+ */
+export declare function parseTailLines(text: string): TailTraceLike[];
+export interface TailTrafficRate {
+    /** Fetch invocations in the window. */
+    requests: number;
+    /** First to last `eventTimestamp`, ms. */
+    spanMs: number;
+    /** `requests` scaled to a day — `NaN` when the window is too short to scale honestly. */
+    requestsPerDay: number;
+}
+/**
+ * Requests per day over the window the traces span — what `deriveCpuBudgetMs({ requestsPerDay })`
+ * takes. `NaN` below an hour of window: scaling ten minutes of traffic to a day is a guess with a
+ * decimal point, and a budget derived from it would be quoted as a measurement.
+ */
+export declare function tailTrafficRate(traces: readonly TailTraceLike[], minSpanMs?: number): TailTrafficRate;

package/dist/server/bench/tail.js

@@ -0,0 +1,182 @@
+/**
+ * The REAL reading: Worker CPU-ms off a tail worker's trace events, fed into the same recorder
+ * and the same assertion the local proxy uses.
+ *
+ * ## Why this shape, and not a clock
+ *
+ * {@link workerCpuClock} is a clock — `start()` then read again — and the isolate never hands a
+ * handler its own CPU time, so there is nothing for it to read inside a request. What Cloudflare
+ * DOES publish is one `cpuTime` per invocation on the trace event a TAIL worker receives (the
+ * same field `wrangler tail --format json` prints — `apps/binary-server/scripts/edgeTail.ts`
+ * already reads it there). So the real number arrives AFTER the request, per request, and the
+ * honest API is to record it then: {@link recordTailTraces} turns trace events into samples on a
+ * recorder built with {@link tailCpuClock}, which stamps `proxy: false`.
+ *
+ * Two ways to get the events, and a consumer needs neither code nor a new Worker for the first:
+ *
+ *   · **`wrangler tail <worker> --format json`** during a bench or a smoke against the live
+ *     Worker — one JSON trace per line, parsed with {@link parseTailLines}.
+ *   · **a Tail Worker** (`tail_consumers` in the producer's wrangler config) whose `tail(events)`
+ *     hands the array straight to {@link recordTailTraces}.
+ *
+ * 🔴 The degenerate guard still applies, deliberately. `cpuTime` is whole milliseconds, so a
+ * route that genuinely costs under 1 ms reads 0 — and a report where EVERY reading is 0 is still
+ * refused, because that is indistinguishable from a reader that is not reading. One real route
+ * above a millisecond anywhere in the window clears it; `allowZeroCpu` is not the fix.
+ *
+ * ## The traffic half
+ *
+ * {@link tailTrafficRate} is requests per day over the window the events span — the number
+ * `deriveCpuBudgetMs({ requestsPerDay })` needs to re-derive the default from THIS generation's
+ * Worker traffic (tasks 342/377) instead of the retired generation's corpus.
+ */
+/** Provenance printed on every report built from tail events. */
+export const TAIL_CPU_SOURCE = 'tail-worker cpuTime';
+/**
+ * The clock for a recorder that is FED rather than started. `proxy: false`: this is the quantity
+ * Cloudflare bills. Its `start()` throws — a tail recorder mounted as `cpuBudget()` middleware is
+ * a wiring mistake, and a span that silently measured nothing is the lie this module refuses.
+ */
+export function tailCpuClock(source = TAIL_CPU_SOURCE) {
+    return {
+        source,
+        proxy: false,
+        available: true,
+        start() {
+            throw new Error('tailCpuClock: a tail recorder is FED by recordTailTraces(), never started — the isolate ' +
+                'does not hand a handler its own CPU time. Mount cpuBudget() with processCpuClock() ' +
+                'for the local proxy, and feed this recorder from a tail.');
+        },
+    };
+}
+/** A route key's pattern half: `'GET /api/items/:id'` → `/api/items/:id`, with its method. */
+function splitKey(key) {
+    const m = /^([A-Z]+)\s+(\S+)$/.exec(key.trim());
+    return m ? { method: m[1] ?? null, pattern: m[2] ?? key } : { method: null, pattern: key.trim() };
+}
+/** Hono-style pattern → anchored regex. `:param` (with an optional `{re}`) is one segment, `*` is the rest. */
+function patternRegex(pattern) {
+    let out = '';
+    for (let i = 0; i < pattern.length;) {
+        const rest = pattern.slice(i);
+        const param = /^:[A-Za-z0-9_]+(\{[^}]*\})?\??/.exec(rest);
+        if (param) {
+            out += '[^/]+';
+            i += param[0].length;
+            continue;
+        }
+        const ch = pattern[i];
+        out += ch === '*' ? '.*' : ch.replace(/[.+?^${}()|[\]\\]/g, '\\$&');
+        i += 1;
+    }
+    return new RegExp(`^${out}$`);
+}
+/** How literal a pattern is — the more literal characters, the earlier it is tried. */
+const specificity = (pattern) => pattern.replace(/:[A-Za-z0-9_]+(\{[^}]*\})?\??/g, '').replace(/\*/g, '').length -
+    (pattern.includes('*') ? 1000 : 0);
+/**
+ * A `(method, path) → route label` matcher over declared route keys — the recorder's own
+ * `config.routes`, by default — so an app gets tail attribution with no code of its own. The
+ * most literal pattern wins, and a method-specific key beats an any-method one.
+ */
+export function routeMatcher(keys) {
+    const compiled = keys
+        .map((key) => ({ ...splitKey(key), key }))
+        .map((k) => ({ ...k, re: patternRegex(k.pattern), score: specificity(k.pattern) + (k.method ? 0.5 : 0) }))
+        .sort((a, b) => b.score - a.score);
+    return (method, path) => {
+        for (const k of compiled) {
+            if (k.method && k.method !== method.toUpperCase())
+                continue;
+            if (k.re.test(path))
+                return k.pattern;
+        }
+        return null;
+    };
+}
+/** The label traffic that matched no declared route is recorded under — so `requireDeclared` names it. */
+export const UNMATCHED_ROUTE = '(no declared route)';
+/**
+ * Charge each fetch invocation's billed `cpuTime` to its route on `recorder`.
+ *
+ * 🔴 A trace with no finite `cpuTime` is NOT a zero — it is skipped and counted, so a runtime
+ * that stopped reporting the field reads as "nothing recorded" (and the assertion's `no-samples`
+ * guard reds it) rather than as a confident route that costs nothing.
+ */
+export function recordTailTraces(recorder, traces, opts = {}) {
+    if (recorder.clock.proxy) {
+        throw new Error(`recordTailTraces: the recorder's clock '${recorder.clock.source}' is a PROXY. Tail cpuTime is the ` +
+            'billed quantity — build this recorder with tailCpuClock(), or its report will call real numbers a proxy.');
+    }
+    const route = opts.route ?? routeMatcher(Object.keys(recorder.config.routes ?? {}));
+    const result = { recorded: 0, notFetch: 0, noCpuTime: 0, unmatched: 0, unmatchedPaths: [] };
+    for (const trace of traces) {
+        if (opts.scriptName && trace.scriptName && trace.scriptName !== opts.scriptName)
+            continue;
+        const request = trace.event?.request;
+        if (!request?.url) {
+            result.notFetch += 1;
+            continue;
+        }
+        const cpu = trace.cpuTime;
+        if (typeof cpu !== 'number' || !Number.isFinite(cpu)) {
+            result.noCpuTime += 1;
+            continue;
+        }
+        const method = (request.method ?? 'GET').toUpperCase();
+        let path;
+        try {
+            path = new URL(request.url).pathname;
+        }
+        catch {
+            path = request.url;
+        }
+        const label = route(method, path);
+        if (label === null) {
+            result.unmatched += 1;
+            if (result.unmatchedPaths.length < 10 && !result.unmatchedPaths.includes(`${method} ${path}`)) {
+                result.unmatchedPaths.push(`${method} ${path}`);
+            }
+        }
+        recorder.record(method, label ?? UNMATCHED_ROUTE, cpu);
+        result.recorded += 1;
+    }
+    return result;
+}
+/**
+ * `wrangler tail --format json` output → trace events. Tolerates the banner lines wrangler
+ * prints and blank lines; a line that is not a JSON object is skipped, never guessed at.
+ */
+export function parseTailLines(text) {
+    const out = [];
+    for (const line of text.split('\n')) {
+        const trimmed = line.trim();
+        if (!trimmed.startsWith('{'))
+            continue;
+        try {
+            const parsed = JSON.parse(trimmed);
+            if (parsed && typeof parsed === 'object')
+                out.push(parsed);
+        }
+        catch {
+            // a partial line from an interrupted tail — not a trace
+        }
+    }
+    return out;
+}
+/**
+ * Requests per day over the window the traces span — what `deriveCpuBudgetMs({ requestsPerDay })`
+ * takes. `NaN` below an hour of window: scaling ten minutes of traffic to a day is a guess with a
+ * decimal point, and a budget derived from it would be quoted as a measurement.
+ */
+export function tailTrafficRate(traces, minSpanMs = 60 * 60 * 1000) {
+    const stamps = traces
+        .filter((t) => t.event?.request?.url)
+        .map((t) => t.eventTimestamp)
+        .filter((s) => typeof s === 'number' && Number.isFinite(s))
+        .sort((a, b) => a - b);
+    const requests = stamps.length;
+    const spanMs = requests > 1 ? stamps[requests - 1] - stamps[0] : 0;
+    const requestsPerDay = spanMs >= minSpanMs ? (requests / spanMs) * 86_400_000 : Number.NaN;
+    return { requests, spanMs, requestsPerDay };
+}

package/dist/server/d1/index.d.ts

@@ -7,11 +7,10 @@
  * local driver is deliberately as strict as D1 rather than as lenient as Bun.
  *
  * ```ts
- * import { createLocalD1, createRemoteD1, createD1Kysely } from 'cursedbelt-server/d1';
+ * import { createLocalD1, createRemoteD1 } from 'cursedbelt-server/d1';
  *
  * const db = env.DB ? createRemoteD1(env.DB) : createLocalD1(sqlite);
  * const row = await db.prepare('SELECT * FROM people WHERE id = ?').bind(id).first();
- * const ky  = createD1Kysely(db);
  * ```
  */
 export { type BackupPoint, createTimeTravelBackup, type DatabaseBackup, type TimeTravelOpts, } from './backup.js';

package/dist/server/d1/index.js

@@ -7,11 +7,10 @@
  * local driver is deliberately as strict as D1 rather than as lenient as Bun.
  *
  * ```ts
- * import { createLocalD1, createRemoteD1, createD1Kysely } from 'cursedbelt-server/d1';
+ * import { createLocalD1, createRemoteD1 } from 'cursedbelt-server/d1';
  *
  * const db = env.DB ? createRemoteD1(env.DB) : createLocalD1(sqlite);
  * const row = await db.prepare('SELECT * FROM people WHERE id = ?').bind(id).first();
- * const ky  = createD1Kysely(db);
  * ```
  */
 export { createTimeTravelBackup, } from './backup.js';
@@ -26,13 +25,14 @@ export { createTimeTravelBackup, } from './backup.js';
 // as the note below, one step wider: a barrel must reach neither an optional peer nor a
 // runtime the target platform lacks. `barrelsReachNoOptionalPeer.spec.ts` checks both.
 //
-// 🔴 `./kysely` is deliberately NOT re-exported here — import it from
-// `cursedbelt-server/d1/kysely`. It statically imports `kysely` (real values: `Kysely`,
-// `SqliteAdapter`, `SqliteQueryCompiler`), which is an OPTIONAL peer, so re-exporting it
-// made `import 'cursedbelt-server/d1'` throw `Cannot find package 'kysely'` for every app
-// that does not use the query builder — which per `../db/kysely.ts`'s own header is most
-// of them, since business tables stay on raw statements. Measured 2026-09-18 against the
-// published 4.3.0 tarball. `barrelsReachNoOptionalPeer.spec.ts` is what keeps it out.
+// `./kysely` — a Kysely dialect over this seam, split out as its own `d1/kysely` subpath on
+// 2026-09-18 because it dragged the OPTIONAL `kysely` peer into every `import '…/d1'` — was
+// REMOVED in 4.19.0 (task 472). Measured 2026-09-23: no file under the generation imported
+// it, no app depends on `kysely` at all, and every ported Worker (patterns, collections,
+// music, vault) reached D1 through raw statements on this seam. A dialect nobody wants is
+// surface with a peer attached; if a ported app ever wants a query builder, it comes back
+// with that app as its first consumer, and `barrelsReachNoOptionalPeer.spec.ts` still keeps
+// it out of this barrel.
 export { createPendingWrites, perInvocation } from './invocation.js';
 export { createHttpD1, D1HttpError } from './http.js';
 export { assertBatchSize, assertWithinLimits, chunkForBind, inArray, LIMITS } from './limits.js';

package/dist/server/engagement/api.d.ts

@@ -0,0 +1,71 @@
+/**
+ * The one door engagement needs, and the in-process read of what it recorded.
+ *
+ *   POST /api/engagement/view   → the beacon. SESSION-gated; the user id comes
+ *                                 from the session, never from the body.
+ *
+ * 🔴 **There is no HTTP read surface, on purpose** (task `113`/`268`, 2026-09-22).
+ * `GET /api/admin/engagement` used to sit here behind `SATELLITE_METRICS_TOKEN` —
+ * ONE bearer shared across five production env files, so a leak from any app was
+ * a read on all of them — for a fleet console that lives in the retired
+ * generation. Nothing in this generation read it over HTTP: station's telemetry
+ * page reads each app's sqlite straight off the disk, and the analytics reader
+ * planned after it does the same with `engagement.sqlite`. Recording carries on
+ * regardless; `readAppEngagement` below is the snapshot a same-machine reader
+ * computes from the store. If an HTTP reader is ever wanted, it gets a PER-APP
+ * credential from the generation's secrets store, never a fleet-wide one.
+ *
+ * ── Why the user id is never in the body ────────────────────────────────────
+ * A beacon whose payload names its own user is an endpoint that lets anyone
+ * write anyone's history — and on a private household app that history is the
+ * data. `resolveUser` is supplied by the app's own SSO consumer and is the ONLY
+ * source of a user key; a request that resolves to nobody is a 401 and writes
+ * nothing. `engagement.test.ts` pins that a body-supplied `userKey` is ignored.
+ *
+ * ── Why the recorder is mounted AFTER the session gate ──────────────────────
+ * The opposite of the feedback-kit sync receiver, and for the mirrored reason:
+ * this door has no credential of its own and wants the gate to have run,
+ * because that is what puts the user where `resolveUser` can read them — while
+ * a sync receiver carries its own bearer and must mount BEFORE the gate. The
+ * rule and its reason: `docs/engagement.md` §2 in this package.
+ */
+import { Hono } from "hono";
+import type { Context } from "hono";
+import { type PlaceRef } from "./policy.js";
+import type { EngagementStore } from "./store.js";
+import { type AppEngagement } from "./summary.js";
+export interface EngagementApiOptions {
+    store: EngagementStore;
+    /** The app's own name. */
+    app: string;
+    /**
+     * The allowlist of place ids — the app's `routes.manifest.json` ids. Anything
+     * a client claims that is not in here records as `other`; see `policy.ts`
+     * rule 1 for why this is the whole privacy story.
+     */
+    places: readonly PlaceRef[];
+    /** Resolve the CURRENT request's account. Null → 401, nothing recorded. */
+    resolveUser: (c: Context) => string | null;
+    /** Injectable clock, so the tests are not timing-dependent. */
+    now?: () => number;
+}
+/** The recorder half — session-gated, mounted at `/api/engagement`. */
+export declare function createEngagementRecorder(options: EngagementApiOptions): Hono;
+/** The whole snapshot one app publishes about itself. */
+export interface AppEngagementSnapshot extends AppEngagement {
+    /** The manifest ids this app CAN report — so a reader can show a place
+     *  with zero views, which is the half of the question that is easy to lose. */
+    knownPlaces: string[];
+    returnCurve: Array<{
+        day: string;
+        joined: number;
+        returned: number;
+    }>;
+    retention: {
+        days: number;
+        places: number;
+        users: number;
+        oldestDay: string | null;
+    };
+}
+export declare function readAppEngagement(store: EngagementStore, app: string, now: number, knownPlaces?: readonly PlaceRef[]): AppEngagementSnapshot;