@stardeck-customer-apps/testing 0.19.0 → 0.21.0

package/SKILL.md

@@ -293,32 +293,32 @@ expect(app.edge.latestDisplay()?.action).toBe("show");
   - `schemaSql` — inline DDL instead of a file.
   - `seed(db)` — seed rows; re-runs on every `reset()`.
   - `allowNetwork` — permit non-Stardeck outbound fetches (off by default).
-- `app.reset()` — wipe + re-apply schema + re-seed + clear inbox/sessions.
-  Call in `beforeEach`.
-- `app.reset({ mode: "data" })` — available in testing SDK **0.14.0+**. Faster
-  opt-in for stable schemas: truncate ordinary tables in `public`, restart their
-  owned serial/identity sequences, re-run the data-only seed, and clear the same
-  simulator/user/session state as the default. It preserves tables and other
-  schema objects instead of rebuilding them. The default remains full schema
-  reset; `app.reset({ mode: "schema" })` explicitly selects that default.
+- `app.reset()` — restore the database to its state right after schema + seed,
+  and clear inbox/sessions/simulator state. Call in `beforeEach`.
+  Since testing SDK **0.20.0** it restores the rows the schema script inserted
+  and every sequence and identity value without firing app triggers, then
+  re-runs the seed, in about a fifth of the time of the old schema rebuild. If a
+  test ran DDL (CREATE, ALTER, DROP), the next reset rebuilds the schema
+  instead, so tests never need to choose a mode. DDL in the seed stays on the
+  fast path when it can run twice (`CREATE TABLE IF NOT EXISTS`); a seed that
+  fails on its second run makes every reset a rebuild.
+  `app.reset({ mode: "schema" })` forces the full rebuild; `mode: "data"` is an
+  older spelling of the default.
 
   ```ts
-  // Only after verifying this suite keeps its schema fixed and uses a data-only seed:
-  beforeEach(() => app.reset({ mode: "data" }));
+  beforeEach(() => app.reset());
   ```
 
-  Keep `app.reset()` for tests that change schema or depend on INSERTs in the
-  schema script. Also keep full reset for independent sequences, materialized
-  views, partitioned/foreign tables, temporary tables, and custom triggers or
-  cross-schema dependencies. Data mode does not restore those states or detect
-  eligibility; inspect both the tests and seed before opting in. All required
-  baseline rows must come from the data-only seed callback, not schema SQL.
-  Data mode refuses foreign keys requiring a cross-schema cascade. Database and
-  seed errors reject the reset; fix them before running the next test.
+  Reset never
+  cascades into tables outside `public`: a foreign key from another schema into
+  a `public` table rejects the reset with Postgres error `0A000`.
+  The first `createTestApp` for a schema saves a database snapshot under
+  `node_modules/.cache/stardeck-testing/`; later test files boot from it.
+  Deleting that directory is always safe.
 
   Do not use `it.concurrent` or `test.concurrent` with a shared test app: user,
   database, and simulator state are shared within the file. Keep file isolation
-  enabled and let Vitest parallelize files. This option does not change workers
+  enabled and let Vitest parallelize files. Reset does not change workers
   or the platform's test-run deadline.
 
 - `app.asUser(partial?)` — sign in a test user; `getSession()` in app code
@@ -530,8 +530,13 @@ cursor, limit })`; `list()` intentionally keeps its previous array shape.
   production) or `app.starlens.reject("not a receipt")` (the 422 the SDK maps to
   `UnsupportedDocumentError`). An unregistered call fails with a descriptive 502 so a
   test never passes on an invented extraction. `app.starlens.calls` records each
-  request's version, input names/media types (never bytes), schema and
-  instructions — assert your `.describe()` aliases reached the wire there.
+  request's version, effort, input names/media types (never bytes), schema and
+  instructions — assert your `.describe()` aliases and `effort: "high"` retries
+  reached the wire there. `version: "v1"` with `effort: "high"` is refused with the
+  same 400 `unsupported_effort` as production (the SDK throws `ValidationError`). A
+  high request with no image input answers `effort: "low"` as production does;
+  pass `effort: "low"` in `app.starlens.mock(...)` to simulate an image production
+  could not decode.
 
 ### Receipt layout and printer capabilities
 

package/dist/index.d.mts

@@ -536,7 +536,10 @@ interface TestEdge {
 }
 /** One Starlens request the app made, as the simulator saw it (names only, never bytes). */
 interface CapturedStarlensCall {
+    /** As sent (`latest` stays `latest`). */
     version: string;
+    /** As requested; `"low"` when the app did not set one. The reply says what ran. */
+    effort: "low" | "high";
     inputs: {
         name: string;
         mediaType: string | null;
@@ -557,6 +560,12 @@ type StarlensReply = {
         path: string;
         reason: string;
     }[];
+    /**
+     * The effort the reply says ran. Defaults to the requested effort, or `"low"` for a
+     * high request with no image input (production cannot crop a PDF, audio or video).
+     * Set `"low"` to simulate a high request on an image production could not decode.
+     */
+    effort?: "low" | "high";
 } | {
     reject: string;
 };
@@ -633,10 +642,10 @@ interface TestApp {
      */
     issueSession(user?: Partial<TestUser>): SessionTokens;
     /**
-     * Rebuild the schema (default), re-run the seed, and clear simulator/user state.
-     * `mode: "data"` instead truncates ordinary public tables and restarts owned
-     * sequences. Use only with a stable schema and data-only seed; it does not
-     * restore DDL changes, schema-script data, or independent sequences.
+     * Restore the rows and sequence values the schema script left, re-run the
+     * seed, and clear simulator/user state. Any DDL since the last reset triggers a full
+     * schema rebuild instead. `mode: "schema"` forces the rebuild; `mode: "data"`
+     * is an older spelling of the default.
      */
     reset(options?: {
         mode: "schema" | "data";

package/dist/index.d.ts

@@ -536,7 +536,10 @@ interface TestEdge {
 }
 /** One Starlens request the app made, as the simulator saw it (names only, never bytes). */
 interface CapturedStarlensCall {
+    /** As sent (`latest` stays `latest`). */
     version: string;
+    /** As requested; `"low"` when the app did not set one. The reply says what ran. */
+    effort: "low" | "high";
     inputs: {
         name: string;
         mediaType: string | null;
@@ -557,6 +560,12 @@ type StarlensReply = {
         path: string;
         reason: string;
     }[];
+    /**
+     * The effort the reply says ran. Defaults to the requested effort, or `"low"` for a
+     * high request with no image input (production cannot crop a PDF, audio or video).
+     * Set `"low"` to simulate a high request on an image production could not decode.
+     */
+    effort?: "low" | "high";
 } | {
     reject: string;
 };
@@ -633,10 +642,10 @@ interface TestApp {
      */
     issueSession(user?: Partial<TestUser>): SessionTokens;
     /**
-     * Rebuild the schema (default), re-run the seed, and clear simulator/user state.
-     * `mode: "data"` instead truncates ordinary public tables and restarts owned
-     * sequences. Use only with a stable schema and data-only seed; it does not
-     * restore DDL changes, schema-script data, or independent sequences.
+     * Restore the rows and sequence values the schema script left, re-run the
+     * seed, and clear simulator/user state. Any DDL since the last reset triggers a full
+     * schema rebuild instead. `mode: "schema"` forces the rebuild; `mode: "data"`
+     * is an older spelling of the default.
      */
     reset(options?: {
         mode: "schema" | "data";