@pikku/cli 0.12.91 → 0.12.93

package/dist/src/functions/db/migration-provenance.js

@@ -0,0 +1,80 @@
+import { readdirSync, readFileSync } from 'node:fs';
+import { join } from 'node:path';
+/**
+ * The header `db generate` stamps on every migration it writes.
+ *
+ * Matching it is what separates a generated migration from one the project
+ * authored: a file without this line declares the project's own tables, and
+ * anything it creates is app-owned by definition.
+ */
+const GENERATED_HEADER = /^-- Generated by `pikku db generate` from (.+)\.\s*$/m;
+/** `0002-pikku-runtime.sql` → `pikku-runtime`. */
+const MIGRATION_LABEL = /^\d+-(.+)\.sql$/;
+/**
+ * Strip `--` line comments so a `CREATE TABLE` quoted inside a REVIEW note is
+ * not mistaken for one the migration actually runs.
+ */
+const stripComments = (sql) => sql.replace(/--[^\n]*/g, '');
+const CREATE_TABLE = /\bCREATE\s+TABLE\s+(?:IF\s+NOT\s+EXISTS\s+)?([^\s(;]+)/gi;
+/**
+ * Drop the schema qualifier and any quoting, so `"app"."user"` and `user` are
+ * the same key.
+ *
+ * Introspection reports a bare name on SQLite and a qualified one on Postgres,
+ * while a migration may write either — comparing on the bare, unquoted name is
+ * the only form both sides agree on.
+ */
+export function bareUnquotedTableName(name) {
+    const last = name.split('.').pop() ?? name;
+    return last.replace(/^["'`[]|["'`\]]$/g, '');
+}
+/**
+ * Read the table→source map out of a project's migration directory.
+ *
+ * Provenance is decided at `db generate` time, but the schema JSON is written
+ * at `db migrate` time, and the two commands do not have to run together. The
+ * migration files are the durable record that survives between them: each
+ * generated one carries its origin in a header and its source in its filename,
+ * so re-reading them costs a directory scan and needs neither a Better Auth
+ * config load nor a live database.
+ *
+ * Tables absent from the result are app-owned — including every table when the
+ * project has no generated migrations at all.
+ */
+export function readMigrationProvenance(migrationsDir) {
+    const provenance = new Map();
+    let files;
+    try {
+        files = readdirSync(migrationsDir);
+    }
+    catch {
+        // No migrations directory is the ordinary case for a project that has not
+        // run `db generate` yet — every table is app-owned.
+        return provenance;
+    }
+    for (const file of files.filter((f) => f.endsWith('.sql')).sort()) {
+        let sql;
+        try {
+            sql = readFileSync(join(migrationsDir, file), 'utf8');
+        }
+        catch {
+            continue;
+        }
+        const header = GENERATED_HEADER.exec(sql);
+        if (!header)
+            continue;
+        const label = MIGRATION_LABEL.exec(file);
+        if (!label)
+            continue;
+        const source = label[1];
+        const origin = header[1];
+        for (const match of stripComments(sql).matchAll(CREATE_TABLE)) {
+            const table = bareUnquotedTableName(match[1]);
+            // First writer wins: a later migration that recreates a table is fixing
+            // it, not claiming it.
+            if (!provenance.has(table))
+                provenance.set(table, { source, origin });
+        }
+    }
+    return provenance;
+}

package/dist/src/functions/db/schema-sql.d.ts

@@ -0,0 +1,43 @@
+/**
+ * Reading a schema source's own SQL back out, one table at a time.
+ *
+ * A source hands `db generate` both what must exist (`tables`) and what creates
+ * it (`sql`). The column map is a comparison surface — it answers "is this
+ * table there, and does it have these columns" — and it is deliberately lossy:
+ * primary keys, foreign keys, uniqueness, check constraints and indexes are all
+ * absent from it. So the moment the generator has to *create* something, the
+ * only honest source is the SQL, and this is what pulls the relevant part of it
+ * out.
+ */
+/**
+ * Split a SQL script into its top-level statements, semicolons included.
+ *
+ * A naive `split(';')` is wrong in a way that only shows up later: a semicolon
+ * inside a string literal, a quoted identifier or a comment is not a statement
+ * boundary, and cutting there yields two fragments that are each valid-looking
+ * and neither of which does what the original did.
+ */
+export declare function splitStatements(sql: string): string[];
+/**
+ * Reduce a written table name to the form two sources can be compared on.
+ *
+ * The same table is `two_factor` to one writer, `"two_factor"` to Kysely and
+ * `public.two_factor` to Postgres introspection. Dropping the schema qualifier,
+ * the quoting and the case is the only shape all three agree on.
+ */
+export declare function bareTableName(name: string): string;
+/**
+ * Every statement in `sql` that builds `table`, in the order the source wrote
+ * them.
+ *
+ * The `CREATE TABLE` and its indexes, plus any `ALTER TABLE` the source uses to
+ * hang a constraint on it afterwards — which together are what the column list
+ * cannot express. Source order is preserved because it is load-bearing: an
+ * index cannot precede its table, and a table cannot precede one it references.
+ *
+ * An empty result means the source's SQL does not visibly create the table.
+ * That is a real answer rather than a failure — a source may create a table
+ * from something other than a literal `CREATE TABLE` — and the caller is
+ * expected to fall back rather than emit nothing.
+ */
+export declare function tableCreationSql(sql: string, table: string): string[];

package/dist/src/functions/db/schema-sql.js

@@ -0,0 +1,135 @@
+/**
+ * Reading a schema source's own SQL back out, one table at a time.
+ *
+ * A source hands `db generate` both what must exist (`tables`) and what creates
+ * it (`sql`). The column map is a comparison surface — it answers "is this
+ * table there, and does it have these columns" — and it is deliberately lossy:
+ * primary keys, foreign keys, uniqueness, check constraints and indexes are all
+ * absent from it. So the moment the generator has to *create* something, the
+ * only honest source is the SQL, and this is what pulls the relevant part of it
+ * out.
+ */
+/**
+ * Split a SQL script into its top-level statements, semicolons included.
+ *
+ * A naive `split(';')` is wrong in a way that only shows up later: a semicolon
+ * inside a string literal, a quoted identifier or a comment is not a statement
+ * boundary, and cutting there yields two fragments that are each valid-looking
+ * and neither of which does what the original did.
+ */
+export function splitStatements(sql) {
+    const statements = [];
+    let start = 0;
+    let i = 0;
+    const closeQuote = (quote) => {
+        i++;
+        while (i < sql.length) {
+            if (sql[i] === '\\' && quote === "'") {
+                i += 2;
+                continue;
+            }
+            if (sql[i] === quote) {
+                // A doubled quote is an escaped one, not the end of the literal.
+                if (sql[i + 1] === quote) {
+                    i += 2;
+                    continue;
+                }
+                i++;
+                return;
+            }
+            i++;
+        }
+    };
+    while (i < sql.length) {
+        const ch = sql[i];
+        if (ch === "'" || ch === '"' || ch === '`') {
+            closeQuote(ch);
+            continue;
+        }
+        if (ch === '-' && sql[i + 1] === '-') {
+            const end = sql.indexOf('\n', i);
+            i = end === -1 ? sql.length : end + 1;
+            continue;
+        }
+        if (ch === '/' && sql[i + 1] === '*') {
+            const end = sql.indexOf('*/', i + 2);
+            i = end === -1 ? sql.length : end + 2;
+            continue;
+        }
+        // Postgres dollar quoting: everything between `$tag$` and its twin is a
+        // literal, and a function body written that way is full of semicolons.
+        if (ch === '$') {
+            const tag = /^\$[A-Za-z_0-9]*\$/.exec(sql.slice(i));
+            if (tag) {
+                const end = sql.indexOf(tag[0], i + tag[0].length);
+                i = end === -1 ? sql.length : end + tag[0].length;
+                continue;
+            }
+        }
+        if (ch === ';') {
+            const statement = sql.slice(start, i + 1).trim();
+            if (statement.length > 1)
+                statements.push(statement);
+            start = i + 1;
+        }
+        i++;
+    }
+    // A script whose last statement has no trailing semicolon still ran it.
+    const tail = sql.slice(start).trim();
+    if (tail.length > 0)
+        statements.push(tail);
+    return statements;
+}
+/**
+ * Reduce a written table name to the form two sources can be compared on.
+ *
+ * The same table is `two_factor` to one writer, `"two_factor"` to Kysely and
+ * `public.two_factor` to Postgres introspection. Dropping the schema qualifier,
+ * the quoting and the case is the only shape all three agree on.
+ */
+export function bareTableName(name) {
+    const last = name.split('.').pop() ?? name;
+    return last.replace(/^["'`[]|["'`\]]$/g, '').toLowerCase();
+}
+const CREATE_TABLE = /^CREATE\s+(?:TEMP(?:ORARY)?\s+|UNLOGGED\s+)*TABLE\s+(?:IF\s+NOT\s+EXISTS\s+)?([^\s(]+)/i;
+const CREATE_INDEX = /^CREATE\s+(?:UNIQUE\s+)?INDEX\s+(?:CONCURRENTLY\s+)?(?:IF\s+NOT\s+EXISTS\s+)?\S+\s+ON\s+(?:ONLY\s+)?([^\s(]+)/i;
+const ALTER_TABLE = /^ALTER\s+TABLE\s+(?:IF\s+EXISTS\s+)?(?:ONLY\s+)?([^\s(]+)/i;
+/**
+ * Every statement in `sql` that builds `table`, in the order the source wrote
+ * them.
+ *
+ * The `CREATE TABLE` and its indexes, plus any `ALTER TABLE` the source uses to
+ * hang a constraint on it afterwards — which together are what the column list
+ * cannot express. Source order is preserved because it is load-bearing: an
+ * index cannot precede its table, and a table cannot precede one it references.
+ *
+ * An empty result means the source's SQL does not visibly create the table.
+ * That is a real answer rather than a failure — a source may create a table
+ * from something other than a literal `CREATE TABLE` — and the caller is
+ * expected to fall back rather than emit nothing.
+ */
+export function tableCreationSql(sql, table) {
+    const wanted = bareTableName(table);
+    const statements = [];
+    let creates = false;
+    for (const statement of splitStatements(sql)) {
+        const create = CREATE_TABLE.exec(statement);
+        if (create && bareTableName(create[1]) === wanted) {
+            creates = true;
+            statements.push(statement);
+            continue;
+        }
+        const index = CREATE_INDEX.exec(statement);
+        if (index && bareTableName(index[1]) === wanted) {
+            statements.push(statement);
+            continue;
+        }
+        const alter = ALTER_TABLE.exec(statement);
+        if (alter && bareTableName(alter[1]) === wanted) {
+            statements.push(statement);
+        }
+    }
+    // Indexes and alters without the table they belong to would fail on their own,
+    // and their presence says the table came from somewhere this cannot read.
+    return creates ? statements : [];
+}

package/dist/src/functions/db/sqlite/sqlite-kysely.js

@@ -1,4 +1,21 @@
 import { Kysely, SqliteDialect, CamelCasePlugin, } from 'kysely';
+/**
+ * Whether a value is a JSON column's worth of data rather than some other
+ * object that merely happens to be one. A `Map`, a `RegExp` or a class
+ * instance stringifies to `"{}"` or to a partial view of itself, which would
+ * silently persist an empty JSON blob where the caller meant something.
+ *
+ * Kept in lockstep with `isJsonEncodable` in `@pikku/kysely-sqlite`'s
+ * LibsqlWebDialect: whatever binds here under `pikku dev` has to bind the same
+ * way once the app is deployed, or the dev and deployed runtimes disagree
+ * about what a query may do.
+ */
+function isJsonEncodable(v) {
+    if (Array.isArray(v))
+        return true;
+    const proto = Object.getPrototypeOf(v);
+    return proto === Object.prototype || proto === null;
+}
 function coerce(v) {
     if (v === null || v === undefined)
         return null;
@@ -8,8 +25,11 @@ function coerce(v) {
         return v.toISOString();
     if (v instanceof Uint8Array)
         return v;
-    if (typeof v === 'object')
-        return JSON.stringify(v);
+    if (typeof v === 'object') {
+        if (isJsonEncodable(v))
+            return JSON.stringify(v);
+        throw new Error(`sqlite: unsupported argument type ${v.constructor?.name ?? 'object'}`);
+    }
     return v;
 }
 // A statement returns rows when it is a SELECT or carries a RETURNING clause.

package/dist/src/functions/knowledge/render.d.ts

@@ -0,0 +1,3 @@
+import type { KnowledgeIndexResult, KnowledgeValidateResult } from '@pikku/knowledge';
+export declare const renderKnowledgeValidate: (_services: unknown, { ok, notes, findings }: KnowledgeValidateResult) => void;
+export declare const renderKnowledgeIndex: (_services: unknown, { ok, check, files }: KnowledgeIndexResult) => void;

package/dist/src/functions/knowledge/render.js

@@ -0,0 +1,66 @@
+import { added, changed, dim, removed } from '../../fabric/lib/output.js';
+export const renderKnowledgeValidate = (_services, { ok, notes, findings }) => {
+    const errors = findings.filter((f) => f.severity === 'error');
+    const warns = findings.filter((f) => f.severity === 'warn');
+    const infos = findings.filter((f) => f.severity === 'info');
+    for (const finding of [...errors, ...warns, ...infos]) {
+        const icon = finding.severity === 'error'
+            ? removed('✗')
+            : finding.severity === 'warn'
+                ? changed('⚠')
+                : dim('ℹ');
+        console.log(`${icon}  ${finding.message}`);
+        console.log(`   ${dim('fix:')}  ${finding.fixHint}`);
+        console.log();
+    }
+    const counts = [dim(`${notes} note${notes !== 1 ? 's' : ''}`)];
+    if (errors.length) {
+        counts.push(removed(`${errors.length} error${errors.length !== 1 ? 's' : ''}`));
+    }
+    if (warns.length) {
+        counts.push(changed(`${warns.length} warning${warns.length !== 1 ? 's' : ''}`));
+    }
+    console.log('─'.repeat(40));
+    console.log(counts.join('  '));
+    if (ok && warns.length === 0 && errors.length === 0) {
+        console.log(added('✓') + '  ' + dim('the knowledge base is consistent'));
+    }
+    // An error means the base contradicts itself, which a pipeline has to be able
+    // to stop on — so this command reports it the only way a shell can read.
+    if (!ok)
+        process.exitCode = 1;
+};
+export const renderKnowledgeIndex = (_services, { ok, check, files }) => {
+    if (files.length === 0) {
+        console.log(dim('No knowledge notes — nothing to index.'));
+        return;
+    }
+    for (const file of files) {
+        if (file.action === 'unchanged') {
+            console.log(`${dim('=')}  ${dim(file.path)}`);
+        }
+        else if (check) {
+            console.log(`${removed('✗')}  ${file.path} ${dim(`(${file.action})`)}`);
+        }
+        else {
+            console.log(`${added('✓')}  ${file.path} ${dim(`(${file.action})`)}`);
+        }
+    }
+    console.log('─'.repeat(40));
+    if (!check) {
+        const written = files.filter((f) => f.action !== 'unchanged').length;
+        console.log(written === 0
+            ? added('✓') + '  ' + dim('every index was already current')
+            : added('✓') +
+                `  ${written} index file${written !== 1 ? 's' : ''} written`);
+    }
+    else {
+        console.log(ok
+            ? added('✓') + '  ' + dim('every index is current')
+            : removed('✗') +
+                '  ' +
+                'indexes are stale — run `pikku knowledge index`');
+        if (!ok)
+            process.exitCode = 1;
+    }
+};

package/dist/src/functions/knowledge/schemas.d.ts

@@ -0,0 +1,51 @@
+/**
+ * The knowledge command schemas, re-bound to variables declared HERE rather than
+ * imported straight into the command files.
+ *
+ * Two things about how the CLI builds itself make this the only shape that works:
+ *
+ * 1. The build bootstraps with the PUBLISHED CLI and inspector, so the code that
+ *    reads these schemas is whatever npm has, not what is in this worktree. An
+ *    identifier imported from `@pikku/knowledge` resolves to that package's
+ *    `.d.ts`, and importing a declaration file yields a module with no exports at
+ *    all — every one of them is a type. A binding declared in a `.ts` gives the
+ *    inspector a file it can execute, and the import inside it resolves to the
+ *    package's emitted JS.
+ * 2. The command files import `#pikku`, which points at `dist/.pikku/` — output
+ *    that does not exist yet while the bootstrap is running. A schema the
+ *    inspector has to import therefore cannot live beside a wired function.
+ *
+ * `schemaRuntimeFile` in the inspector fixes (1) at the root, so once a release
+ * carrying it is the bootstrap version, (2) is the only reason this file is here.
+ */
+export declare const KnowledgeIndexInputSchema: import("zod").ZodObject<{
+    check: import("zod").ZodOptional<import("zod").ZodBoolean>;
+}, import("zod/v4/core").$strip>;
+export declare const KnowledgeIndexOutputSchema: import("zod").ZodObject<{
+    ok: import("zod").ZodBoolean;
+    check: import("zod").ZodBoolean;
+    files: import("zod").ZodArray<import("zod").ZodObject<{
+        path: import("zod").ZodString;
+        action: import("zod").ZodEnum<{
+            created: "created";
+            updated: "updated";
+            unchanged: "unchanged";
+        }>;
+    }, import("zod/v4/core").$strip>>;
+}, import("zod/v4/core").$strip>;
+export declare const KnowledgeValidateInputSchema: import("zod").ZodObject<{}, import("zod/v4/core").$strip>;
+export declare const KnowledgeValidateOutputSchema: import("zod").ZodObject<{
+    ok: import("zod").ZodBoolean;
+    notes: import("zod").ZodNumber;
+    findings: import("zod").ZodArray<import("zod").ZodObject<{
+        id: import("zod").ZodString;
+        severity: import("zod").ZodEnum<{
+            error: "error";
+            warn: "warn";
+            info: "info";
+        }>;
+        message: import("zod").ZodString;
+        path: import("zod").ZodString;
+        fixHint: import("zod").ZodString;
+    }, import("zod/v4/core").$strip>>;
+}, import("zod/v4/core").$strip>;

package/dist/src/functions/knowledge/schemas.js

@@ -0,0 +1,25 @@
+import { KnowledgeIndexInput, KnowledgeIndexOutput, KnowledgeValidateInput, KnowledgeValidateOutput, } from '@pikku/knowledge';
+/**
+ * The knowledge command schemas, re-bound to variables declared HERE rather than
+ * imported straight into the command files.
+ *
+ * Two things about how the CLI builds itself make this the only shape that works:
+ *
+ * 1. The build bootstraps with the PUBLISHED CLI and inspector, so the code that
+ *    reads these schemas is whatever npm has, not what is in this worktree. An
+ *    identifier imported from `@pikku/knowledge` resolves to that package's
+ *    `.d.ts`, and importing a declaration file yields a module with no exports at
+ *    all — every one of them is a type. A binding declared in a `.ts` gives the
+ *    inspector a file it can execute, and the import inside it resolves to the
+ *    package's emitted JS.
+ * 2. The command files import `#pikku`, which points at `dist/.pikku/` — output
+ *    that does not exist yet while the bootstrap is running. A schema the
+ *    inspector has to import therefore cannot live beside a wired function.
+ *
+ * `schemaRuntimeFile` in the inspector fixes (1) at the root, so once a release
+ * carrying it is the bootstrap version, (2) is the only reason this file is here.
+ */
+export const KnowledgeIndexInputSchema = KnowledgeIndexInput;
+export const KnowledgeIndexOutputSchema = KnowledgeIndexOutput;
+export const KnowledgeValidateInputSchema = KnowledgeValidateInput;
+export const KnowledgeValidateOutputSchema = KnowledgeValidateOutput;

package/dist/src/functions/wirings/credentials/serialize-credentials-types.js

@@ -1,5 +1,12 @@
 import { validateAndBuildCredentialDefinitionsMeta } from '@pikku/core/credential';
 import { getFileImportRelativePath } from '../../../utils/file-import-path.js';
+/**
+ * A display name is the human-facing label a developer wrote, so an apostrophe
+ * in it is ordinary. `JSON.stringify` emits a valid, escaped TypeScript string
+ * literal; interpolating the raw text into a quoted one terminates the string
+ * and the generated file stops parsing.
+ */
+const literal = (value) => JSON.stringify(value);
 export const serializeCredentialsTypes = ({ definitions, schemaLookup, credentialsFile, packageMappings, }) => {
     const credentials = validateAndBuildCredentialDefinitionsMeta(definitions, schemaLookup);
     const credentialEntries = Object.entries(credentials);
@@ -22,7 +29,7 @@ export const serializeCredentialsTypes = ({ definitions, schemaLookup, credentia
         }
         const metaParts = [
             `name: '${name}'`,
-            `displayName: '${meta.displayName}'`,
+            `displayName: ${literal(meta.displayName)}`,
             `type: '${meta.type}'`,
         ];
         if (meta.oauth2) {

package/dist/src/functions/wirings/functions/schemas.js

@@ -1,6 +1,7 @@
 import { pikkuSessionlessFunc } from '#pikku';
 import { saveSchemas } from '../../../utils/serialize-schemas.js';
 import { logCommandInfoAndTime } from '../../../middleware/log-command-info-and-time.js';
+import { partitionRequiredSchemas } from '../scenarios/scenario-schema-partition.js';
 export const pikkuSchemas = pikkuSessionlessFunc({
     func: async ({ logger, config, getInspectorState }) => {
         const visitState = await getInspectorState();
@@ -16,7 +17,18 @@ export const pikkuSchemas = pikkuSessionlessFunc({
             Object.keys(visitState.schemas).length === 0) {
             return undefined;
         }
-        await saveSchemas(logger, config.schemaDirectory, visitState.schemas, visitState.requiredSchemas, config.schema?.supportsImportAttributes ?? true, config.addonName || null);
+        const supportsImportAttributes = config.schema?.supportsImportAttributes ?? true;
+        const { appRequired, scenarioOnly } = partitionRequiredSchemas({
+            functionsMeta: visitState.functions.meta,
+            requiredSchemas: visitState.requiredSchemas,
+            getUniqueName: (name) => visitState.functions.typesMap.getUniqueName(name),
+            schemasFromTypes: config.schemasFromTypes,
+        });
+        await saveSchemas(logger, config.schemaDirectory, visitState.schemas, appRequired, supportsImportAttributes, config.addonName || null);
+        // Always written, even when empty — the scenario bootstrap imports it
+        // unconditionally, and a project that deleted its last scenario must stop
+        // registering the schemas it had.
+        await saveSchemas(logger, config.scenarioSchemaDirectory, visitState.schemas, scenarioOnly, supportsImportAttributes, config.addonName || null, 'scenario schemas');
         return true;
     },
     middleware: [

package/dist/src/functions/wirings/rpc/pikku-command-rpc.js

@@ -2,6 +2,7 @@ import { pikkuSessionlessFunc } from '#pikku';
 import { writeFileInDir } from '../../../utils/file-writer.js';
 import { logCommandInfoAndTime } from '../../../middleware/log-command-info-and-time.js';
 import { getFileImportRelativePath } from '../../../utils/file-import-path.js';
+import { withoutScenarios } from '../scenarios/scenario-partition.js';
 export function filterInternalRPCMeta(internalMeta, functionsMeta) {
     const filteredInternalMeta = {};
     for (const [key, value] of Object.entries(internalMeta)) {
@@ -18,7 +19,11 @@ export const pikkuRPC = pikkuSessionlessFunc({
         // Keep direct function ids and unversioned aliases whose target function
         // survived filtering. Without the second check, aliases like `listCards`
         // get dropped even though `listCards@v2` still exists.
-        const filteredInternalMeta = filterInternalRPCMeta(rpc.internalMeta, functions.meta);
+        // Scenarios are excluded along with the steps they call: a scenario name in
+        // the app's RPC meta is a name a deployed bundle carries and, in principle,
+        // dispatches. Scenario runs don't need the entry — the mapping is the
+        // identity, which is also the fallback when a name is absent.
+        const filteredInternalMeta = filterInternalRPCMeta(rpc.internalMeta, withoutScenarios(functions.meta));
         if (Object.keys(filteredInternalMeta).length > 0) {
             await writeFileInDir(logger, rpcInternalWiringMetaJsonFile, JSON.stringify(filteredInternalMeta, null, 2));
             const jsonImportPath = getFileImportRelativePath(rpcInternalWiringMetaFile, rpcInternalWiringMetaJsonFile, packageMappings);

package/dist/src/functions/wirings/scenarios/register-scenario-instrumentation.d.ts

@@ -0,0 +1,10 @@
+/**
+ * Register the instrumentation into the running dev server's state, so the
+ * scenario runner can reach it over `/rpc/<name>` exactly as before.
+ *
+ * They are registered sessionless: `auth` decides whether a session is
+ * *required*, and a sessioned function would demand one regardless of the flag —
+ * which is what made `scaffold.scenarios: true` (as opposed to `'auth'`) refuse
+ * every call and log a warning about it.
+ */
+export declare const registerScenarioInstrumentation: (requireAuth: boolean) => void;

package/dist/src/functions/wirings/scenarios/register-scenario-instrumentation.js

@@ -0,0 +1,102 @@
+import { readFile } from 'node:fs/promises';
+import { join } from 'node:path';
+import { addFunction } from '@pikku/core/function';
+import { pikkuState } from '@pikku/core/internal';
+import { getStubTracker, isTestRun, } from '@pikku/core/services';
+/**
+ * The instrumentation `pikku scenario run` calls on the server under test:
+ * snapshot/reset live coverage, and reset/read recorded stub calls.
+ *
+ * These are pikku's, not the application's. They were previously scaffolded into
+ * the project as ordinary `pikkuFunc`s, which is why they ended up registered in
+ * the app bootstrap and shipped — `expose: true` — inside every deployed bundle.
+ * Registering them here instead means the only process that has them is the one
+ * that should: a development server. Nothing is generated, nothing is written to
+ * the user's source tree, and a bundle cannot carry what was never in its
+ * bootstrap.
+ *
+ * The bodies are unchanged from the generated ones, minus their schemas: an
+ * instrumentation endpoint with a single optional string argument has nothing to
+ * validate, and dropping the schemas drops the `zod` dependency the scaffold
+ * silently required of every project.
+ */
+const takeLiveCoverage = {
+    func: async ({ coverageService, metaService }) => {
+        if (!coverageService?.takeReport || !metaService?.basePath)
+            return null;
+        let functionsMeta;
+        try {
+            const content = await readFile(join(metaService.basePath, 'function', 'pikku-functions-meta-verbose.gen.json'), 'utf-8');
+            functionsMeta = JSON.parse(content);
+        }
+        catch {
+            return null;
+        }
+        return await coverageService.takeReport(functionsMeta);
+    },
+};
+const resetLiveCoverage = {
+    func: async ({ coverageService }) => {
+        if (!coverageService)
+            return { enabled: false };
+        await coverageService.reset();
+        return { enabled: true };
+    },
+};
+const resetStubs = {
+    func: async () => {
+        getStubTracker().reset();
+        return { enabled: isTestRun() };
+    },
+};
+const getStubCalls = {
+    func: async (_services, data) => getStubTracker().getCalls(data?.service ?? undefined),
+};
+const instrumentation = {
+    pikkuScenarioTakeLiveCoverage: {
+        ...takeLiveCoverage,
+        title: 'Take Live Coverage',
+        description: 'Snapshots the live coverage collected since the server started (or since the last reset) — V8 precise coverage on Node, istanbul instrumentation on Bun — and maps it onto function body spans. Returns null unless the server was started with coverage enabled (pikku dev --coverage).',
+    },
+    pikkuScenarioResetLiveCoverage: {
+        ...resetLiveCoverage,
+        title: 'Reset Live Coverage',
+        description: 'Clears coverage call counts so the next takeLiveCoverage snapshot is attributable to a single scenario run. Reports enabled: false when the server was not started with coverage enabled.',
+    },
+    pikkuScenarioResetStubs: {
+        ...resetStubs,
+        title: 'Reset Stubs',
+        description: 'Clears recorded stub calls so the next getStubCalls result is attributable to a single scenario run. Reports enabled: false when the server was not started in test mode.',
+    },
+    pikkuScenarioGetStubCalls: {
+        ...getStubCalls,
+        title: 'Get Stub Calls',
+        description: 'Returns calls recorded against stubbed/spied services (via the stub()/spy() core utils). Empty unless the server records service calls (pikku dev --test).',
+    },
+};
+/**
+ * Register the instrumentation into the running dev server's state, so the
+ * scenario runner can reach it over `/rpc/<name>` exactly as before.
+ *
+ * They are registered sessionless: `auth` decides whether a session is
+ * *required*, and a sessioned function would demand one regardless of the flag —
+ * which is what made `scaffold.scenarios: true` (as opposed to `'auth'`) refuse
+ * every call and log a warning about it.
+ */
+export const registerScenarioInstrumentation = (requireAuth) => {
+    const meta = pikkuState(null, 'function', 'meta');
+    for (const [name, { func, title, description }] of Object.entries(instrumentation)) {
+        addFunction(name, { func, auth: requireAuth });
+        meta[name] = {
+            pikkuFuncId: name,
+            inputSchemaName: null,
+            outputSchemaName: null,
+            expose: true,
+            sessionless: true,
+            tags: ['pikku'],
+            title,
+            description,
+        };
+    }
+    pikkuState(null, 'function', 'meta', meta);
+};

package/dist/src/functions/wirings/scenarios/scenario-partition.d.ts

@@ -12,6 +12,12 @@ export type WiringFileMap = Map<string, {
  * them in `.pikku/scenarios/`, reachable only from `pikku scenario run`.
  */
 export declare const isScenarioStep: (meta: FunctionsMeta[string] | undefined) => boolean;
+/**
+ * A scenario's own body is a function too, so the app meta used to carry every
+ * scenario's name, schemas and hashes — and a deployed bundle imports that meta
+ * wholesale. Both kinds belong on the scenario side of the split.
+ */
+export declare const isScenarioFunction: (meta: FunctionsMeta[string] | undefined) => boolean;
 export declare const partitionScenarioFunctions: (files: WiringFileMap, functionsMeta: FunctionsMeta) => {
     app: WiringFileMap;
     scenario: WiringFileMap;
@@ -27,3 +33,10 @@ export declare const partitionScenarioWorkflows: (workflowNames: string[], workf
     appFiles: WiringFileMap;
     scenarioFiles: WiringFileMap;
 };
+/**
+ * Drop every scenario and step from a function meta map. The deploy analyzer
+ * reads inspector state rather than the partitioned codegen output, so it needs
+ * the same split applied before it decides what a deployment contains.
+ */
+export declare const withoutScenarios: (functionsMeta: FunctionsMeta) => FunctionsMeta;
+export declare const withoutScenarioWorkflows: (graphMeta: SerializedWorkflowGraphs) => SerializedWorkflowGraphs;