@jskit-ai/agent-docs 0.1.279 → 0.1.281

package/skills/jskit/references/patterns/app/shell-foundation/example/playwright.config.mjs

@@ -1,32 +1,5 @@
 import { defineConfig } from "@playwright/test";
+import { browserTestConfig } from "@jskit-ai/jskit-catalog/browser-tests";
 
-const managedBaseUrl = String(process.env.PLAYWRIGHT_BASE_URL || "")
-  .trim()
-  .replace(/\/+$/u, "");
-const port = String(process.env.PLAYWRIGHT_PORT || "").trim() || "4173";
-const baseURL = managedBaseUrl || `http://127.0.0.1:${port}`;
-const storageState = String(process.env.PLAYWRIGHT_STORAGE_STATE || "").trim();
-
-export default defineConfig({
-  testDir: "./tests/e2e",
-  timeout: 60_000,
-  expect: {
-    timeout: 10_000
-  },
-  use: {
-    baseURL,
-    headless: true,
-    ...(storageState ? { storageState } : {})
-  },
-  ...(managedBaseUrl ? {} : {
-    webServer: {
-      command: "npm run develop",
-      env: {
-        PORT: port
-      },
-      url: `${baseURL}/api/health`,
-      reuseExistingServer: true,
-      timeout: 180_000
-    }
-  })
-});
+// Each Playwright worker gets its own server on the production build; with PLAYWRIGHT_BASE_URL, the managed target.
+export default defineConfig(browserTestConfig({ testDir: "./tests/e2e" }));

package/skills/jskit/references/patterns/app/shell-foundation/example/server.js

@@ -23,6 +23,10 @@ import { surfaceRuntime } from "./server/lib/surfaceRuntime.js";
 /** @typedef {import("@jskit-ai/kernel/server/types").RuntimeEnv} RuntimeEnv */
 
 const SPA_INDEX_FILE = "index.html";
+// Vite names each built file under assets/ after its content (`index-BxY3kz9a.js`), so a browser may keep one for good:
+// a new build references new names. index.html and unhashed files are revalidated on every load.
+const HASHED_ASSET = /^assets\/(?:.+\/)?[^/]+-[\w-]{8}\.[a-z0-9]+$/u;
+const HASHED_ASSET_CACHE = Object.freeze({ maxAge: 365 * 24 * 60 * 60 * 1000, immutable: true });
 const STATIC_GLOBAL_UI_PATHS = Object.freeze([
   "/assets",
   "/favicon.svg",
@@ -157,7 +161,9 @@ async function createServer({ runtimeEnv }) {
     if (hasFileExtension(pathname)) {
       const staticFilePath = toStaticFilePath(pathname);
       if (hasWebBuild && staticFilePath && canServeStaticFile(distRoot, staticFilePath)) {
-        return reply.sendFile(staticFilePath);
+        return HASHED_ASSET.test(staticFilePath)
+          ? reply.sendFile(staticFilePath, HASHED_ASSET_CACHE)
+          : reply.sendFile(staticFilePath);
       }
       return reply.code(404).send({
         message: `Route ${method}:${pathname} not found`,

package/skills/jskit/references/patterns/app/shell-foundation/example/src/components/menus/SectionTabLinkItem.vue

@@ -0,0 +1,42 @@
+<script setup>
+import ShellSectionTabLinkItem from "@jskit-ai/shell-web/client/components/ShellSectionTabLinkItem";
+
+const props = defineProps({
+  label: {
+    type: String,
+    default: ""
+  },
+  to: {
+    type: String,
+    default: ""
+  },
+  icon: {
+    type: String,
+    default: ""
+  },
+  surface: {
+    type: String,
+    default: ""
+  },
+  scopedSuffix: {
+    type: String,
+    default: "/"
+  },
+  unscopedSuffix: {
+    type: String,
+    default: "/"
+  },
+  disabled: {
+    type: Boolean,
+    default: false
+  },
+  exact: {
+    type: Boolean,
+    default: false
+  }
+});
+</script>
+
+<template>
+  <ShellSectionTabLinkItem v-bind="props" />
+</template>

package/skills/jskit/references/patterns/app/shell-foundation/example/src/main.js

@@ -1,10 +1,11 @@
+// Vuetify's styles first, so its stylesheet comes before any component chunk's.
+import "vuetify/styles";
+import "@jskit-ai/material-web/client/material.css";
 import { createApp } from "vue";
 import { createPinia } from "pinia";
 import { QueryClient, VueQueryPlugin } from "@tanstack/vue-query";
 import { createRouter, createWebHistory } from "vue-router/auto";
 import { routes } from "vue-router/auto-routes";
-import "vuetify/styles";
-import "@jskit-ai/material-web/client/material.css";
 import { createVuetify } from "vuetify";
 import { createMaterialVuetifyOptions } from "@jskit-ai/material-web/client";
 import App from "./App.vue";

package/skills/jskit/references/patterns/app/shell-foundation/example/src/pages/home.vue

@@ -14,7 +14,7 @@ import { RouterView } from "vue-router";
 </script>
 
 <template>
-  <ShellLayout title="" subtitle="">
+  <ShellLayout>
     <RouterView />
   </ShellLayout>
 </template>

package/skills/jskit/references/patterns/app/shell-foundation/example/src/views/NotFound.vue

@@ -6,7 +6,7 @@ const message = "The page you requested does not exist.";
 
 <template>
   <!-- The shell's top app bar carries the title, and its navigation leads back into the app. -->
-  <ShellLayout title="Not Found" subtitle="">
+  <ShellLayout title="Not Found">
     <section class="d-flex flex-column align-center text-center on-surface-variant py-16">
       <v-icon icon="$searchOff" size="48" />
       <p class="text-body-large mt-4 mb-0">{{ message }}</p>

package/skills/jskit/references/patterns/app/shell-foundation/example/tests/e2e/startup.spec.ts

@@ -33,3 +33,16 @@ for (const width of [390, 768, 1280]) {
     await expect(page.locator("#startup-shell")).toHaveCount(0);
   });
 }
+
+test("built assets are kept for good and the page itself is revalidated", async ({ page }) => {
+  test.skip(Boolean(process.env.PLAYWRIGHT_BASE_URL), "A managed target's server and proxy set its own caching.");
+  const assets: string[] = [];
+  page.on("response", response => {
+    if (new URL(response.url()).pathname.startsWith("/assets/")) assets.push(response.headers()["cache-control"] ?? "");
+  });
+  const document = await page.goto("/home");
+  await page.waitForLoadState("load");
+  expect(document?.headers()["cache-control"] ?? "").not.toContain("immutable");
+  expect(assets.length).toBeGreaterThan(0);
+  expect(new Set(assets)).toEqual(new Set(["public, max-age=31536000, immutable"]));
+});

package/skills/jskit/references/patterns/app/shell-foundation/example/vite.config.mjs

@@ -4,6 +4,7 @@ import vue from "@vitejs/plugin-vue";
 import vuetify from "vite-plugin-vuetify";
 import VueRouter from "vue-router/vite";
 import { createJskitClientBootstrapPlugin } from "@jskit-ai/kernel/client/vite";
+import { testConcurrency } from "@jskit-ai/jskit-catalog/test-budget";
 
 const configuredDevPort = Number.parseInt(String(process.env.VITE_DEV_PORT || "").trim(), 10);
 const devPort = Number.isInteger(configuredDevPort) && configuredDevPort > 0 ? configuredDevPort : 5173;
@@ -52,7 +53,8 @@ export default defineConfig({
     }
   ],
   test: {
-    include: ["tests/client/**/*.vitest.js"]
+    include: ["tests/client/**/*.vitest.js"],
+    maxWorkers: testConcurrency()
   },
   optimizeDeps: {
     include: ["vuetify/components/**", "vuetify/directives/**"],

package/skills/jskit/references/patterns/auth/accounts-hub/example/package.json

@@ -2,7 +2,7 @@
   "private": true,
   "type": "module",
   "dependencies": {
-    "@jskit-ai/database-runtime-mysql": "0.1.257",
-    "@jskit-ai/oidc-issuer-core": "0.1.18"
+    "@jskit-ai/database-runtime-mysql": "0.1.259",
+    "@jskit-ai/oidc-issuer-core": "0.1.20"
   }
 }

package/skills/jskit/references/patterns/auth/auth-surface/PATTERN.md

@@ -27,8 +27,14 @@ Those choices must be known before adapting the example.
 ## Framework APIs
 
 Use the views, auth guard, HTTP client integration, sign-out runtime, providers,
-and Playwright auth helper exported by `@jskit-ai/auth-web`. Use auth policies
-from `@jskit-ai/auth-core` for server authorization.
+and Playwright auth helper exported by `@jskit-ai/auth-web`. The sign-in, reset
+and sign-out screens show the app's identity: the pages render the app's view
+wrappers (`src/views/auth/`), and each wrapper fills the default view's `brand`
+slot (given `{ compact }`) with `src/components/AppBrand.vue`, the app's name
+as `index.html`'s `<title>` spells it. JSKIT lays the slot out as a pane beside
+the card on wide windows and a row above it on phones; never restyle the views'
+own classes. Use auth policies from `@jskit-ai/auth-core` for server
+authorization.
 
 Every application with accounts includes the managed-preview login. It is
 standard, not optional: adding this pattern adds it, so a managed host's
@@ -92,6 +98,10 @@ a user as a side effect.
 - Public auth routes do not require an existing session.
 - Protected routes use the framework auth policy rather than page-local checks.
 - Login, sign-out, and reset views use the public auth components/composables.
+- The sign-in, reset and sign-out pages render the app's view wrappers, which
+  fill the `brand` slot with the app's identity (`AppBrand.vue`): a person
+  always sees which app they are signing in to. Renaming the app renames
+  `AppBrand.vue` with `index.html`'s `<title>`; the brand adds no heading.
 - A custom login view must preserve the default view's initial session check:
   already authenticated people return to the validated requested destination.
   Process incoming login callbacks before that redirect, and keep signed-out
@@ -102,8 +112,9 @@ a user as a side effect.
 
 ## Example files
 
-`example/` contains concrete route wrappers, editable view wrappers, and the
-client runtime helpers needed by an authentication surface. It also contains
+`example/` contains concrete route wrappers, editable view wrappers that show
+the app's brand (`src/components/AppBrand.vue`), and the client runtime helpers
+needed by an authentication surface. It also contains
 the standard app-owned managed-preview identity executable,
 `tools/preview-identity`. Compose their
 surface and placement declarations into the application's ordinary config and
@@ -116,7 +127,9 @@ placements, and post-auth destinations while retaining the runtime contracts.
 
 ## Verification
 
-Exercise failed and successful login, sign-out, reset, protected navigation,
+Check that the sign-in, reset and sign-out screens show the app's name, in the
+pane on a wide window and in the row on a phone. Exercise failed and successful
+login, sign-out, reset, protected navigation,
 keyboard interaction, warm-cache return navigation, and browser refresh.
 Open the login route with an existing authenticated session and confirm it
 returns to the requested screen; repeat signed out and confirm the form remains.

package/skills/jskit/references/patterns/auth/auth-surface/example/src/components/AppBrand.vue

@@ -0,0 +1,17 @@
+<script setup>
+// The app's identity on its sign-in, reset and sign-out screens. The auth views place it in their brand slot: a pane
+// beside the card on wide windows, and a row above the card on phones (`compact`). It is the app's name as
+// index.html's <title> spells it, so renaming the app renames both. It holds no heading: each screen's h1 is its own.
+defineProps({
+  compact: {
+    type: Boolean,
+    default: false
+  }
+});
+
+const APP_NAME = "Reading Room";
+</script>
+
+<template>
+  <div :class="compact ? 'text-title-medium' : 'text-title-large'" data-testid="app-brand">{{ APP_NAME }}</div>
+</template>

package/skills/jskit/references/patterns/auth/auth-surface/example/src/pages/auth/login.vue

@@ -9,9 +9,9 @@
 </route>
 
 <script setup>
-import DefaultLoginView from "@jskit-ai/auth-web/client/views/DefaultLoginView";
+import LoginView from "@/views/auth/LoginView.vue";
 </script>
 
 <template>
-  <DefaultLoginView />
+  <LoginView />
 </template>

package/skills/jskit/references/patterns/auth/auth-surface/example/src/pages/auth/reset-password.vue

@@ -9,9 +9,9 @@
 </route>
 
 <script setup>
-import DefaultResetPasswordView from "@jskit-ai/auth-web/client/views/DefaultResetPasswordView";
+import ResetPasswordView from "@/views/auth/ResetPasswordView.vue";
 </script>
 
 <template>
-  <DefaultResetPasswordView />
+  <ResetPasswordView />
 </template>

package/skills/jskit/references/patterns/auth/auth-surface/example/src/pages/auth/signout.vue

@@ -9,9 +9,9 @@
 </route>
 
 <script setup>
-import DefaultSignOutView from "@jskit-ai/auth-web/client/views/DefaultSignOutView";
+import SignOutView from "@/views/auth/SignOutView.vue";
 </script>
 
 <template>
-  <DefaultSignOutView />
+  <SignOutView />
 </template>

package/skills/jskit/references/patterns/auth/auth-surface/example/src/views/auth/LoginView.vue

@@ -1,7 +1,12 @@
 <script setup>
 import DefaultLoginView from "@jskit-ai/auth-web/client/views/DefaultLoginView";
+import AppBrand from "@/components/AppBrand.vue";
 </script>
 
 <template>
-  <DefaultLoginView />
+  <DefaultLoginView>
+    <template #brand="{ compact }">
+      <AppBrand :compact="compact" />
+    </template>
+  </DefaultLoginView>
 </template>

package/skills/jskit/references/patterns/auth/auth-surface/example/src/views/auth/ResetPasswordView.vue

@@ -1,7 +1,12 @@
 <script setup>
 import DefaultResetPasswordView from "@jskit-ai/auth-web/client/views/DefaultResetPasswordView";
+import AppBrand from "@/components/AppBrand.vue";
 </script>
 
 <template>
-  <DefaultResetPasswordView />
+  <DefaultResetPasswordView>
+    <template #brand="{ compact }">
+      <AppBrand :compact="compact" />
+    </template>
+  </DefaultResetPasswordView>
 </template>

package/skills/jskit/references/patterns/auth/auth-surface/example/src/views/auth/SignOutView.vue

@@ -1,7 +1,12 @@
 <script setup>
 import DefaultSignOutView from "@jskit-ai/auth-web/client/views/DefaultSignOutView";
+import AppBrand from "@/components/AppBrand.vue";
 </script>
 
 <template>
-  <DefaultSignOutView />
+  <DefaultSignOutView>
+    <template #brand="{ compact }">
+      <AppBrand :compact="compact" />
+    </template>
+  </DefaultSignOutView>
 </template>

package/skills/jskit/references/patterns/auth/oidc-sign-in/example/package.json

@@ -2,7 +2,7 @@
   "private": true,
   "type": "module",
   "dependencies": {
-    "@jskit-ai/auth-provider-oidc-core": "0.2.17",
-    "@jskit-ai/auth-web": "0.2.15"
+    "@jskit-ai/auth-provider-oidc-core": "0.2.19",
+    "@jskit-ai/auth-web": "0.2.17"
   }
 }

package/skills/jskit/references/patterns/auth/supabase-auth/example/package.json

@@ -2,6 +2,6 @@
   "private": true,
   "type": "module",
   "dependencies": {
-    "@jskit-ai/auth-provider-supabase-core": "0.2.12"
+    "@jskit-ai/auth-provider-supabase-core": "0.2.14"
   }
 }

package/skills/jskit/references/patterns/connectors/aws-storage-queries/example/formats/package.json

@@ -2,7 +2,7 @@
   "name": "s3-native-format-example",
   "private": true,
   "type": "module",
-  "scripts": { "test": "node --test --test-concurrency=1 verify-formats.mjs" },
+  "scripts": { "test": "node verify-formats.mjs" },
   "dependencies": {
     "csv-parse": "7.0.2",
     "csv-stringify": "6.8.3",

package/skills/jskit/references/patterns/connectors/calendar-cli/example/package.json

@@ -7,10 +7,10 @@
     "db:migrate:status": "knex --knexfile ./knexfile.js migrate:list"
   },
   "dependencies": {
-    "@jskit-ai/connectors-core": "0.2.11",
-    "@jskit-ai/connector-google-calendar": "0.2.11",
-    "@jskit-ai/database-runtime": "0.1.259",
-    "@jskit-ai/database-runtime-mysql": "0.1.257",
+    "@jskit-ai/connectors-core": "0.2.13",
+    "@jskit-ai/connector-google-calendar": "0.2.13",
+    "@jskit-ai/database-runtime": "0.1.261",
+    "@jskit-ai/database-runtime-mysql": "0.1.259",
     "knex": "^3.1.0"
   }
 }

package/skills/jskit/references/patterns/console/console-surface/example/src/pages/console.vue

@@ -14,7 +14,7 @@ import { RouterView } from "vue-router";
 </script>
 
 <template>
-  <ShellLayout title="" subtitle="">
+  <ShellLayout>
     <RouterView />
   </ShellLayout>
 </template>

package/skills/jskit/references/patterns/crud/json-api-resource-package/example/packages/books/package.json

@@ -9,8 +9,8 @@
     "./shared": "./src/shared/index.js"
   },
   "dependencies": {
-    "@jskit-ai/crud-core": "0.2.11",
-    "@jskit-ai/resource-crud-core": "0.1.201"
+    "@jskit-ai/crud-core": "0.2.13",
+    "@jskit-ai/resource-crud-core": "0.1.203"
   },
   "jskit": {
     "kind": "runtime",

package/skills/jskit/references/patterns/database/mysql-application/PATTERN.md

@@ -61,27 +61,38 @@ metadata. Do not combine it with the PostgreSQL pattern's workflow: a MySQL
 application's workflow has no `postgres` service, `POSTGRES_*` variables, port
 `5432`, or `pg_isready` option.
 
-`example/tests/browser/database.js` is the application-owned browser preparation
-helper. It requires the exact `BROWSER_TEST_DB_NAME`, rejects the ordinary and
-disposable `TEST_DB_NAME` databases,
-retains the schema and migration ledger, applies pending migrations, then clears
-test rows and calls one explicit fixture seed transaction. The seed must restore
-any migration-owned baseline rows the app needs. Call it once before starting
-the isolated test server, never in `beforeEach`. It closes its connections without
-dropping the database. The launcher selects that database only for its own server
-and identity process, disables external effects, and proves actual server identity
-before the suite writes data. It must not edit the normal environment. Provision
-both test databases with exact grants for the application account. A disposable
-integration or migration test must never drop the browser database.
-
-Startup reports whether the schema exists, the number of migrations applied,
-and the migration, fixture-reset and seed durations. Use those measurements to
-diagnose a slow start before rerunning a browser case.
+Tests get their own databases from
+`@jskit-ai/database-runtime/server/testDatabases`. The `test` script runs
+`jskit test --databases`: each Node test file running at once gets its own
+copy of `TEST_DB_NAME` (`<name>`, `<name>_1`, ...), restored from a stored
+snapshot of the current migrations' schema and the rows they write, in
+`node_modules/.cache/jskit-test-databases/`. The snapshot is replayed once, and
+again only when a migration's name or contents or `package-lock.json` change;
+a file that migrates or drops tables leaves its copy to be restored before the
+next file takes it.
+
+`example/tests/e2e/databases.js` is the browser run's `prepare` module for
+`browserTestConfig({ prepare: "tests/e2e/databases.js" })` from
+`@jskit-ai/jskit-catalog/browser-tests`. It gives each Playwright worker's
+server its own copy of `BROWSER_TEST_DB_NAME`, restored from the same kind of
+snapshot and seeded in one transaction by the app's fixture `seed`, which
+restores any migration-owned baseline rows the app needs. Every server serves
+the production build. Both refuse the application's database (`DB_NAME`,
+`DATABASE_URL`'s, the Knex connection's), `PROD_DB_NAME` and the other test
+database and its copies. Provision `TEST_DB_NAME`, `BROWSER_TEST_DB_NAME` and
+their numbered copies with grants for the application account (a `<app>_%`
+grant covers them); a user who may create no copies runs one file or worker at
+a time. Two test runs at once need different database names. Test-only server
+settings that disable external effects (email, payments) go in
+`browserTestConfig({ env })`; a suite that writes data proves the server's
+identity first.
+
+Each preparation reports how many databases it made, whether it replayed the
+migrations for a new snapshot, and the restore and seed durations. Use those
+measurements to diagnose a slow start before rerunning a browser case.
 
 Keep fixtures small for the selected test scope. Run related cases in one suite
-invocation. Use the development launcher for ordinary browser checks; test the
-production build separately when needed. Fresh-schema migration proofs are
-separate from browser startup.
+invocation. Fresh-schema migration proofs are separate from browser startup.
 
 ## Variation points
 
@@ -99,11 +110,10 @@ it as `seed` to `prepareDatabaseFromApp()`.
 - Run `npm run db:migrate:status` and the application verification command.
 - Exercise one transaction and one negative connection case.
 - When a seed exists, run `db:prepare` twice and require the second run to be safe.
-- For browser preparation, run a disposable test between two starts: the second applies no
-  old migrations, stale fixture data is removed, baseline rows are restored,
-  foreign-key checks remain enabled, and the normal database is unchanged.
-  Also prove that a new pending migration is applied. Keep this as a regression
-  test when adapting the example; reject a harness that recreates the schema.
+- For the test databases, run the suite twice: the second run restores the
+  stored snapshot instead of replaying the migrations, stale rows are gone,
+  baseline rows are restored, foreign keys are enforced, and the normal
+  database is unchanged. A new migration takes a new snapshot.
 - Confirm `.github/workflows/verify.yml` parses as YAML and declares only the
   `mariadb` service. GitHub reports an unparseable workflow only as a failed
   run with "no jobs were run".

package/skills/jskit/references/patterns/database/mysql-application/example/package.json

@@ -5,9 +5,10 @@
     "db:prepare": "node ./scripts/prepare-database.js",
     "db:migrate": "knex --knexfile ./knexfile.js migrate:latest",
     "db:migrate:rollback": "knex --knexfile ./knexfile.js migrate:rollback",
-    "db:migrate:status": "knex --knexfile ./knexfile.js migrate:list"
+    "db:migrate:status": "knex --knexfile ./knexfile.js migrate:list",
+    "test": "jskit test --databases"
   },
   "dependencies": {
-    "@jskit-ai/database-runtime-mysql": "0.1.257"
+    "@jskit-ai/database-runtime-mysql": "0.1.259"
   }
 }

package/skills/jskit/references/patterns/database/mysql-application/example/tests/e2e/databases.js

@@ -0,0 +1,25 @@
+import { prepareTestDatabases } from "@jskit-ai/database-runtime/server/testDatabases";
+import knexConfig from "../../knexfile.js";
+
+// The browser run's `prepare` module: `browserTestConfig({ prepare: "tests/e2e/databases.js" })` in
+// playwright.config.mjs runs it once, before the servers start. Every Playwright worker gets its own copy of
+// BROWSER_TEST_DB_NAME (`<name>`, `<name>_1`, ...), restored from the schema snapshot of the current migrations, then
+// seeded; the normal and disposable TEST_DB_NAME databases are refused. It is also given each worker's `baseUrls`,
+// for a server setting that names its own address.
+
+/** The fixtures the specs rely on, including any migration-owned baseline rows the app needs. */
+async function seed(transaction) {
+  await transaction("fixtures").insert({ id: 1, label: "Browser fixture" });
+}
+
+export default async function prepareBrowserDatabases({ workers }) {
+  const { databases, summary } = await prepareTestDatabases({
+    knexConfig,
+    environment: process.env,
+    variable: "BROWSER_TEST_DB_NAME",
+    count: workers,
+    seed
+  });
+  console.log(`[browser-tests] ${summary}.`);
+  return databases.map((database) => ({ DB_NAME: database }));
+}

package/skills/jskit/references/patterns/database/postgres-application/PATTERN.md

@@ -53,6 +53,18 @@ dialect. `example/scripts/prepare-database.js` is the portable
 migrate-then-seed entrypoint for managed sessions and deployments.
 `example/.env.example` names the five connection values without a secret.
 
+Tests get their own databases from
+`@jskit-ai/database-runtime/server/testDatabases`. The `test` script runs
+`jskit test --databases`: each Node test file running at once gets a copy of
+`TEST_DB_NAME`, created from `<TEST_DB_NAME>_snapshot`, a database the
+migrations are replayed into once and again only when a migration changes.
+`example/tests/e2e/databases.js` is the browser run's `prepare` module for
+`browserTestConfig({ prepare: "tests/e2e/databases.js" })` from
+`@jskit-ai/jskit-catalog/browser-tests`: each Playwright worker's server gets
+its own seeded copy of `BROWSER_TEST_DB_NAME`. The database user needs
+`CREATEDB`; without it, Node test files run one at a time on the connected
+database.
+
 `example/.github/workflows/verify.yml` is a normal app-owned CI workflow with
 exactly one database service: `postgres` (`postgres:17`, `POSTGRES_*`
 variables, port `5432`, a `pg_isready` health check). Copy it whole from this

package/skills/jskit/references/patterns/database/postgres-application/example/package.json

@@ -5,9 +5,10 @@
     "db:prepare": "node ./scripts/prepare-database.js",
     "db:migrate": "knex --knexfile ./knexfile.js migrate:latest",
     "db:migrate:rollback": "knex --knexfile ./knexfile.js migrate:rollback",
-    "db:migrate:status": "knex --knexfile ./knexfile.js migrate:list"
+    "db:migrate:status": "knex --knexfile ./knexfile.js migrate:list",
+    "test": "jskit test --databases"
   },
   "dependencies": {
-    "@jskit-ai/database-runtime-postgres": "0.1.256"
+    "@jskit-ai/database-runtime-postgres": "0.1.258"
   }
 }

package/skills/jskit/references/patterns/database/postgres-application/example/tests/e2e/databases.js

@@ -0,0 +1,25 @@
+import { prepareTestDatabases } from "@jskit-ai/database-runtime/server/testDatabases";
+import knexConfig from "../../knexfile.js";
+
+// The browser run's `prepare` module: `browserTestConfig({ prepare: "tests/e2e/databases.js" })` in
+// playwright.config.mjs runs it once, before the servers start. Every Playwright worker gets its own copy of
+// BROWSER_TEST_DB_NAME (`<name>`, `<name>_1`, ...), created from the snapshot database of the current migrations with
+// CREATE DATABASE ... TEMPLATE, then seeded; the normal and disposable TEST_DB_NAME databases are refused. The database
+// user needs CREATEDB.
+
+/** The fixtures the specs rely on, including any migration-owned baseline rows the app needs. */
+async function seed(transaction) {
+  await transaction("fixtures").insert({ id: 1, label: "Browser fixture" });
+}
+
+export default async function prepareBrowserDatabases({ workers }) {
+  const { databases, summary } = await prepareTestDatabases({
+    knexConfig,
+    environment: process.env,
+    variable: "BROWSER_TEST_DB_NAME",
+    count: workers,
+    seed
+  });
+  console.log(`[browser-tests] ${summary}.`);
+  return databases.map((database) => ({ DB_NAME: database }));
+}

package/skills/jskit/references/patterns/realtime/realtime-application/example/package.json

@@ -2,7 +2,7 @@
   "private": true,
   "type": "module",
   "dependencies": {
-    "@jskit-ai/realtime": "0.2.16",
-    "@jskit-ai/shell-web": "0.2.13"
+    "@jskit-ai/realtime": "0.2.18",
+    "@jskit-ai/shell-web": "0.2.15"
   }
 }

package/skills/jskit/references/patterns/rewards/google-rewarded/example/googlePublisherTag.js

@@ -72,8 +72,10 @@ function launchGoogleRewardedAd({
 
         let readySeen = false;
         let settled = false;
+        let availabilityTimer = null;
 
         const cleanup = () => {
+          window.clearTimeout(availabilityTimer);
           pubads.removeEventListener("rewardedSlotReady", handleReady);
           pubads.removeEventListener("rewardedSlotGranted", handleGranted);
           pubads.removeEventListener("rewardedSlotClosed", handleClosed);
@@ -120,8 +122,8 @@ function launchGoogleRewardedAd({
           gptServicesEnabled = true;
         }
 
-        googletag.display(slot);
-        window.setTimeout(() => {
+        // Started before display, so a slot that settles at once still clears it.
+        availabilityTimer = window.setTimeout(() => {
           if (settled || readySeen) {
             return;
           }
@@ -131,6 +133,7 @@ function launchGoogleRewardedAd({
             reject(new Error("No rewarded ad was available."));
           });
         }, 10000);
+        googletag.display(slot);
       });
     })
   );