@happyvertical/smrt-core 0.51.31 → 0.51.33

package/dist/system/retention.d.ts

@@ -1,4 +1,49 @@
-import { DatabaseInterface } from '@happyvertical/sql';
+/**
+ * System-table retention — bounded growth for framework-owned tables (#2375).
+ *
+ * Several `_smrt_*` tables are append-only by construction and were, until
+ * this module, unbounded by default: `_smrt_changes` grew one row per
+ * framework save/delete, `_smrt_ai_usage` one row per AI call (persistence is
+ * on by default, see `config.ts`), `_smrt_contexts` accumulated rows whose
+ * `expires_at` nothing ever enforced, `_smrt_dispatch` retained completed
+ * work until an operator remembered to run `smrt dispatch:cleanup`, and
+ * `_smrt_run_once_claims` (#3080) gains one row per `runOnce()` submission
+ * with nothing pruning completed ones.
+ *
+ * This module supplies the missing half:
+ *
+ * - {@link pruneAiUsage} — the retention API `_smrt_ai_usage` never had.
+ * - {@link pruneExpiredContexts} — enforcement for `_smrt_contexts.expires_at`.
+ * - {@link runRetentionSweep} — one entry point that applies a documented,
+ *   opt-out {@link RetentionPolicy} across every framework-owned table, plus
+ *   any task other packages contribute via {@link registerRetentionTask}
+ *   (`@happyvertical/smrt-jobs` registers job/job-event cleanup;
+ *   `@happyvertical/smrt-users` registers session and token expiry).
+ *
+ * Scheduling is the caller's: `smrt db:prune` is the cron entry point, and a
+ * running `TaskRunner` sweeps on an interval unless configured otherwise.
+ *
+ * ## Failure policy
+ *
+ * A sweep is maintenance, not a transaction. One failing task never aborts the
+ * rest — the failure is captured on that task's {@link RetentionTaskResult}
+ * and the sweep continues. Callers decide what a partial sweep means; the CLI
+ * exits non-zero when any task failed.
+ *
+ * ## Predicate indexes
+ *
+ * Every predicate below is indexed by the system DDL in `system/schema.ts`
+ * (`_smrt_contexts(expires_at)`, `_smrt_ai_usage(tenant_id, created_at)`,
+ * `_smrt_dispatch(status, processed_at)` / `(status, updated_at)`,
+ * `_smrt_run_once_claims(status, completed_at)`) or by the jobs compatibility
+ * path in `system/compatibility.ts` (`_smrt_jobs(status, completed_at)`,
+ * `_smrt_job_events(created_at)`). A new retention predicate must ship with
+ * its index.
+ *
+ * @see https://github.com/happyvertical/smrt/issues/2375
+ * @packageDocumentation
+ */
+import type { DatabaseInterface } from '@happyvertical/sql';
 /** Retention for the append-only change feed (`_smrt_changes`). */
 export interface ChangeFeedRetentionPolicy {
     /** Run this task (default `true`). */

package/dist/system/schema.d.ts

@@ -1,4 +1,10 @@
-import { DatabaseEngine } from '../schema/ddl/types.js';
+/**
+ * SMRT System Tables Schema
+ *
+ * System tables use _smrt_ prefix to avoid conflicts with user tables.
+ * All system tables are created in the same database as user data.
+ */
+import type { DatabaseEngine } from '../schema/ddl/types.js';
 /**
  * Context memory storage
  * Stores remembered context (learned strategies, patterns, selectors) for reuse

package/dist/system-fields.d.ts

@@ -1,4 +1,12 @@
-import { FieldDefinition } from './scanner/types.js';
+/**
+ * Canonical SMRT system fields inherited from `SmrtObject`.
+ *
+ * These fields exist on every persistent object at runtime even when they are
+ * not declared in a child class manifest. Keep this definition lightweight:
+ * presence matters for metadata consumers, while schema generation still owns
+ * the exact SQL defaults and constraints for these columns.
+ */
+import type { FieldDefinition } from './scanner/types.js';
 export declare const SMRT_SYSTEM_FIELDS: Readonly<Record<string, FieldDefinition>>;
 export declare function isInjectedSmrtSystemField(field: unknown): boolean;
 export declare function cloneSmrtSystemFields(): Record<string, FieldDefinition>;

package/dist/test-utils.d.ts

@@ -1,4 +1,10 @@
-import { Mock } from 'vitest';
+/**
+ * Comprehensive test utilities for SMRT framework testing
+ *
+ * Provides unified mocking for collections, objects, and database operations
+ * to support both CLI and API generator testing scenarios.
+ */
+import { type Mock } from 'vitest';
 /**
  * Snapshot ObjectRegistry state and return a restore function for manifest-heavy
  * tests that mutate registry internals at runtime.

package/dist/testing/database.d.ts

@@ -1,4 +1,21 @@
-import { DatabaseInterface } from '@happyvertical/sql';
+/**
+ * Test database utilities for SMRT framework
+ *
+ * Provides `getTestDatabase()` which creates an in-memory database with all
+ * registered SMRT object schemas. Uses the same schema generation logic as
+ * the migration system to ensure consistency between test and production.
+ *
+ * @example
+ * ```typescript
+ * import { getTestDatabase } from '@happyvertical/smrt-core/testing';
+ *
+ * beforeEach(async () => {
+ *   const db = await getTestDatabase();
+ *   collection = await MyCollection.create({ db });
+ * });
+ * ```
+ */
+import type { DatabaseInterface } from '@happyvertical/sql';
 /**
  * Options for creating a test database
  */

package/dist/testing/notifications-stub.d.ts

@@ -1,4 +1,18 @@
-import { DatabaseInterface } from '@happyvertical/sql';
+/**
+ * In-process test double for the sql package's optional notification
+ * capability (`db.notifications`, e.g. Postgres LISTEN/NOTIFY).
+ *
+ * Attaches a push-driven `notify`/`listen` pair to a database handle so tests
+ * can exercise the cross-process / cross-replica paths of the collection cache
+ * (#1498) and the change-signal bus (#1763) against a real in-memory SQLite
+ * database that has no native notification support. `notify` records every
+ * broadcast; `listen` exposes an async iterable that yields whatever `push`
+ * delivers.
+ *
+ * Extracted from `__tests__/issue-1498-collection-cache.test.ts` so the same
+ * double backs the change-signal bus tests without duplicating the stub.
+ */
+import type { DatabaseInterface } from '@happyvertical/sql';
 /** One notification as delivered over the stubbed channel. */
 export interface StubNotification {
     channel: string;

package/dist/tools/tool-executor.d.ts

@@ -1,4 +1,9 @@
-import { SignalBus } from '../signals/bus.js';
+/**
+ * Tool Call Execution for AI Function Calling
+ *
+ * This module handles runtime execution of AI tool calls on SMRT object instances.
+ */
+import type { SignalBus } from '../signals/bus.js';
 /**
  * A dynamically-dispatched tool target (typically a SmrtObject instance, but
  * typed structurally so any object whose method names are resolved at runtime

package/dist/tools/tool-generator.d.ts

@@ -1,5 +1,11 @@
-import { AITool } from '@happyvertical/ai';
-import { MethodDefinition } from '../scanner/types.js';
+/**
+ * Tool Manifest Generation for AI Function Calling
+ *
+ * This module converts TypeScript method definitions from the AST scanner
+ * into AI tool format at build time for use with LLM function calling.
+ */
+import type { AITool } from '@happyvertical/ai';
+import type { MethodDefinition } from '../scanner/types.js';
 /**
  * A JSON Schema fragment. The shape is open-ended (different keywords appear
  * for primitives, arrays, unions, etc.), so values are `unknown`; callers

package/dist/utils/json.d.ts

@@ -1,4 +1,12 @@
-import { JSONAdapter, ParseError, Result, StringifyError } from '@happyvertical/json';
+/**
+ * JSON utilities with optional SIMD acceleration
+ *
+ * Uses @happyvertical/json for faster parsing when available,
+ * with automatic fallback to native JSON.
+ *
+ * Performance: 2-3x faster parsing on large JSON files (680KB manifests)
+ */
+import { type JSONAdapter, type ParseError, type Result, type StringifyError } from '@happyvertical/json';
 /**
  * Parse JSON string with optional SIMD acceleration
  *

package/dist/utils/qualified-names.d.ts

@@ -1,4 +1,13 @@
-import { QualifiedClassName } from '../scanner/types.js';
+/**
+ * Utilities for working with qualified class names in the SMRT framework.
+ *
+ * Qualified names follow the format: "@package/name:ClassName"
+ * Example: "@happyvertical/smrt-core:Product"
+ *
+ * This format uniquely identifies classes across packages, eliminating
+ * name collisions when multiple packages define classes with the same name.
+ */
+import type { QualifiedClassName } from '../scanner/types.js';
 /**
  * Creates a qualified class name from package name and class name.
  *

package/dist/utils/scanner-module.d.ts

@@ -1,5 +1,5 @@
-import { CapabilityClassification, DomainKnowledgePlaybookStep } from '@happyvertical/smrt-types';
-import { SmartObjectManifest } from '../scanner/types.js';
+import type { CapabilityClassification, DomainKnowledgePlaybookStep } from '@happyvertical/smrt-types';
+import type { SmartObjectManifest } from '../scanner/types.js';
 /**
  * The scanner's declared agent surface (#2591), mirrored structurally like the
  * rest of this module.

package/dist/utils.d.ts

@@ -1,4 +1,4 @@
-import { SmrtObject } from './object';
+import type { SmrtObject } from './object';
 import { classnameToTablename, pluralize, toSnakeCase } from './utils/naming.js';
 import { toSafeBooleanInteger, toSafeInteger } from './utils/safe-integer.js';
 export { classnameToTablename, pluralize, toSafeBooleanInteger, toSafeInteger, toSnakeCase, };

package/dist/vite-plugin/api-client-entries.d.ts

@@ -1,4 +1,12 @@
-import { SmartObjectDefinition, SmartObjectManifest } from '../scanner/types.js';
+/**
+ * Manifest -> generated API-client entry selection.
+ *
+ * Runtime client values, Vite ambient declarations, and physical prebuild
+ * declarations must agree on which manifest object owns a collection's
+ * canonical endpoint. Collection classes describe access methods, not row
+ * payloads, so a populated model always wins the shared collection key.
+ */
+import type { SmartObjectDefinition, SmartObjectManifest } from '../scanner/types.js';
 export type ApiClientCrudMethod = 'list' | 'get' | 'create' | 'update' | 'delete' | 'search';
 export interface ApiClientEntry {
     /** Original key in manifest.objects. */

package/dist/vite-plugin/changes-route.d.ts

@@ -1,5 +1,36 @@
-import { SmartObjectManifest } from '../scanner/types';
-import { SvelteKitOptions } from './sveltekit-generator.js';
+/**
+ * SvelteKit `_changes` route generation for the change feed (issue #1758).
+ *
+ * Emits `{routesDir}/_changes/+server.ts` — an auth-guarded, tenant-scoped
+ * GET endpoint over the `_smrt_changes` log, part of the client/mobile sync
+ * contract (PRD #1755). Kept in its own module so `sveltekit-generator.ts`
+ * only carries a one-line registration.
+ *
+ * Design notes:
+ * - **Fail-closed auth** (#1540 posture): the handler requires an
+ *   authenticated principal on `locals`. The feed spans every table, so
+ *   per-model `api: { public }` opt-outs deliberately do not apply.
+ * - **Tenant scoping**: when the project has tenant-scoped objects, the
+ *   route establishes tenant context from `locals` exactly like generated
+ *   collection routes, then reads through
+ *   `getAuthorizedTenantScopedChangesSince()` — a tenant only ever sees its
+ *   own changes plus global rows.
+ * - **Table/row authorization** (#3020): the same call additionally applies
+ *   the consumer-supplied `authorizeChangeFeed`/`isChangeFeedEntryVisible`
+ *   hooks (`@happyvertical/smrt-core`'s `change-feed-authz.ts`), if
+ *   registered — a table-level and row-level seam beyond tenant scope (e.g. a
+ *   station principal reading only its own rows of a table the office can
+ *   read in full). Unregistered, behavior is unchanged from pre-#3020.
+ * - **Database resolution**: the route anchors on the project's first
+ *   generated collection (alphabetical) via the consumer's existing
+ *   `getCollection()` helper, inheriting its configuration, request-scoped
+ *   database support and system-table bootstrap. Multi-database projects
+ *   (per-object `db` overrides) see the anchor collection's feed.
+ * - Cleanup rides the existing generated-route sweep: the emitted file
+ *   starts with {@link AUTO_GENERATED_ROUTE_HEADER}.
+ */
+import type { SmartObjectManifest } from '../scanner/types';
+import type { SvelteKitOptions } from './sveltekit-generator.js';
 /**
  * Pick the class the route resolves its database through: the first
  * non-collection object by sorted manifest key, for determinism across

package/dist/vite-plugin/dev-plane-route.d.ts

@@ -1,4 +1,15 @@
-import { SvelteKitOptions } from './sveltekit-generator.js';
+/**
+ * Generated `_dev/[...tool]/+server.ts` route: the in-app runtime dev-plane
+ * (#2782). Opt-in via `svelteKit: { devPlaneRoute: { enabled: true } }`.
+ *
+ * The route is dev-only twice over: it 404s unless SvelteKit's `dev` flag is
+ * set, and it refuses to start without `SMRT_DEV_MCP_TOKEN`. Everything else
+ * — loopback checks, bearer auth, the positive read-only catalog, the MCP
+ * endpoint — lives in `@happyvertical/smrt-dev-mcp/dev-plane`, which the
+ * generated file imports at consumer runtime. Like `_resources`, the route is
+ * only emitted when that subpath resolves from the consumer.
+ */
+import type { SvelteKitOptions } from './sveltekit-generator.js';
 /** Whether `@happyvertical/smrt-dev-mcp/dev-plane` resolves from the consumer. */
 export declare function consumerHasSmrtDevMcp(projectRoot: string): boolean;
 /** Whether this invocation will own the `_dev/[...tool]` output file. */

package/dist/vite-plugin/events-route.d.ts

@@ -1,5 +1,40 @@
-import { SmartObjectManifest } from '../scanner/types';
-import { SvelteKitOptions } from './sveltekit-generator.js';
+/**
+ * SvelteKit `_events` route generation — live change signals (issue #1763,
+ * SERVER half; parent PRD #1755).
+ *
+ * Emits `{routesDir}/_events/+server.ts` — an auth-guarded, tenant-scoped
+ * Server-Sent-Events endpoint that streams coarse change signals (no row
+ * payloads). It is the push companion to the generated `_changes` route
+ * (#1758). Kept in its own module so `sveltekit-generator.ts` only carries a
+ * one-line registration.
+ *
+ * The stream lifecycle (subscribe, catch-up, heartbeat, teardown) lives in
+ * core's `buildChangeEventStream`, imported by the generated file — so the
+ * emitted route stays THIN and the stream logic is written and tested once.
+ *
+ * Design notes (mirror `changes-route.ts`):
+ * - **Fail-closed auth** (#1540 posture): the handler requires an authenticated
+ *   principal on `locals`. The signal stream spans every table, so per-model
+ *   `api: { public }` opt-outs deliberately do not apply.
+ * - **Tenant scoping**: when the project has tenant-scoped objects, the route
+ *   establishes tenant context from `locals` exactly like the `_changes` route,
+ *   then captures the resolved scope ONCE at connection open and passes it to
+ *   the stream (delivery filters against that fixed value — it cannot
+ *   re-resolve per signal outside the request's ALS context).
+ * - **Table/row authorization** (#3020): `locals` is forwarded to
+ *   `buildChangeEventStream`, which — if the consumer registered
+ *   `authorizeChangeFeed`/`isChangeFeedEntryVisible`
+ *   (`@happyvertical/smrt-core`'s `change-feed-authz.ts`) — resolves the
+ *   allowed tables ONCE at connection open (same reasoning as tenant scope)
+ *   and applies both hooks to catch-up replay AND every live signal before it
+ *   is enqueued. Unregistered, behavior is unchanged from pre-#3020.
+ * - **Database resolution**: anchors on the project's first generated
+ *   collection (alphabetical) via `getCollection()`, exactly as `_changes`.
+ * - Cleanup rides the generated-route sweep: the file starts with
+ *   {@link AUTO_GENERATED_ROUTE_HEADER}.
+ */
+import type { SmartObjectManifest } from '../scanner/types';
+import type { SvelteKitOptions } from './sveltekit-generator.js';
 /**
  * Generate the `_events/+server.ts` route. Returns true when a route was
  * written. Disabled with `sveltekit: { eventsRoute: { enabled: false } }`;

package/dist/vite-plugin/generated-client.d.ts

@@ -1,4 +1,12 @@
-import { SmartObjectManifest } from '../scanner/types.js';
+/**
+ * Shared runtime generator for producer and consumer `@smrt/client` modules.
+ *
+ * Keep runtime values on the same manifest-derived contract as physical and
+ * virtual declarations. In particular, disabled objects, partial CRUD
+ * allowlists, stable collection keys, and custom route signatures must not
+ * diverge between the two plugin entry points.
+ */
+import type { SmartObjectManifest } from '../scanner/types.js';
 export declare const GENERATED_CLIENT_CRUD_METHODS: Set<string>;
 export declare const GENERATED_CLIENT_BASE_METHODS: Set<string>;
 export declare function generateClientModule(manifest: SmartObjectManifest, options?: {

package/dist/vite-plugin/index.d.ts

@@ -1,8 +1,12 @@
-import { DomainKnowledgeAgentSurface, DomainKnowledgeConfig } from '@happyvertical/smrt-types';
-import { Plugin } from 'vite';
-import { SmrtGenerationSnapshotOptions } from '../generation-snapshot.js';
-import { SmartObjectManifest } from '../scanner/types.js';
-import { ScannerAgentSurface, ScannerModule } from '../utils/scanner-module.js';
+/**
+ * Vite plugin for automatic SMRT service generation
+ * Provides virtual modules for REST, MCP, and other services
+ */
+import type { DomainKnowledgeAgentSurface, DomainKnowledgeConfig } from '@happyvertical/smrt-types';
+import type { Plugin } from 'vite';
+import { type SmrtGenerationSnapshotOptions } from '../generation-snapshot.js';
+import { type SmartObjectManifest } from '../scanner/types.js';
+import type { ScannerAgentSurface, ScannerModule } from '../utils/scanner-module.js';
 export { loadVerifiedSmrtGenerationSnapshot, type SerializeSmrtGenerationSnapshotOptions, type SmrtGenerationSnapshotArtifact, type SmrtGenerationSnapshotOptions, type SmrtGenerationSnapshotView, serializeSmrtGenerationSnapshot, sha256SmrtGenerationSnapshot, } from '../generation-snapshot.js';
 export type { CliApiCoherenceViolation, SvelteKitOptions, } from './sveltekit-generator.js';
 export { findCliApiCoherenceViolations, generateSvelteKitRoutes, methodNameToKebab, resolveApiActionRouteConfig, resolveApiActionSet, validateCliIncludeAgainstApi, } from './sveltekit-generator.js';

package/dist/vite-plugin/resources-route.d.ts

@@ -1,4 +1,85 @@
-import { SvelteKitOptions } from './sveltekit-generator.js';
+/**
+ * SvelteKit `_resources` route generation — CLI discovery endpoint (#2663;
+ * parent epic #2655).
+ *
+ * Emits `{routesDir}/_resources/+server.ts`: `GET /api/_resources`, the
+ * endpoint the distributable CLI (`@happyvertical/smrt-app-cli`) reads to
+ * learn which resources and commands it can invoke. Every other generated
+ * route lives in `sveltekit-generator.ts` or a sibling emitter; this one is
+ * kept in its own module for the same reason `changes-route.ts` and
+ * `events-route.ts` are — a one-line registration hook in the shared
+ * generator file.
+ *
+ * ## The dependency constraint
+ *
+ * The handler this route delegates to, `createResourceListHandler`, lives in
+ * `@happyvertical/smrt-users` — and `smrt-users` depends on `smrt-core`, not
+ * the reverse, so core cannot import it directly. That is not a problem for
+ * *emitting* the import: the generated file is written into the consumer's
+ * own `src/routes/`, where `@happyvertical/smrt-users` resolves through the
+ * consumer's own dependency graph, exactly like the `@happyvertical/smrt-tenancy`
+ * import `sveltekit-generator.ts`'s `generateTenantContextHelper` already
+ * emits into tenant-scoped routes (see the comment above that function). The
+ * only question is *when* it is safe to emit — a consumer that never took a
+ * dependency on `smrt-users` must never receive a route whose import cannot
+ * resolve, or a working build turns red.
+ *
+ * ## Detection mechanism
+ *
+ * Unlike the tenancy guard — which reads a semantic signal already present in
+ * the manifest (whether any object is `@TenantScoped`, which itself implies
+ * the app depends on `smrt-tenancy`) — nothing in the manifest indicates
+ * whether a consumer has taken on `smrt-users`. Objects don't declare an
+ * auth dependency; the app does, at the package level.
+ *
+ * So this route uses a **resolvable-dependency check**: does the exact
+ * subpath the generated file imports — `@happyvertical/smrt-users/sveltekit`
+ * — resolve from the consumer's `projectRoot`, via a `createRequire` rooted
+ * at the consumer's own `package.json`? That is stronger than reading
+ * `package.json`'s `dependencies` block (which can list a package that was
+ * never installed) and, unlike a single hardcoded
+ * `node_modules/@happyvertical/smrt-users/package.json` path, it uses
+ * Node's real module resolution — so it also finds the package when a
+ * workspace hoists shared dependencies to an ancestor `node_modules` (npm/
+ * yarn workspaces, or pnpm with `node-linker=hoisted`) rather than
+ * installing them directly under the consumer's own `projectRoot`.
+ * Resolving the `/sveltekit` subpath specifically, rather than the
+ * package's bare `package.json`, matters too: `smrt-users`'s `exports` map
+ * does not list `./package.json`, so resolving that path would throw
+ * `ERR_PACKAGE_PATH_NOT_EXPORTED` even when the package is genuinely
+ * installed — resolving the subpath the route actually imports sidesteps
+ * that and checks precisely the thing that must succeed at build time.
+ *
+ * An explicit `sveltekit: { resourcesRoute: { enabled: false } }` escape
+ * hatch is also available, matching `changesRoute`/`eventsRoute`, for a
+ * consumer that has `smrt-users` installed but wants to keep hand-writing
+ * (or omit) `_resources`.
+ *
+ * ## Preserving a hand-written route
+ *
+ * Every consumer today hand-writes this route (the reference implementation
+ * in the issue). `clearGeneratedRouteFiles` (in `sveltekit-generator.ts`)
+ * already only deletes `+server.ts` files that start with
+ * {@link AUTO_GENERATED_ROUTE_HEADER}, so a hand-written `_resources` route —
+ * which never carries that header — survives the pre-generation sweep
+ * untouched. This emitter additionally checks `existsSync` on the target
+ * path before writing: by the time it runs, anything still there is
+ * necessarily hand-written (a generator-owned copy would already have been
+ * swept), so its mere presence is sufficient to skip generation and leave it
+ * alone.
+ *
+ * Once a consumer's `_resources` route IS generator-owned (no hand-written
+ * file present, `smrt-users` resolvable), its path is generator-owned for
+ * `.gitignore` purposes too — it is included in `generatedRoutePaths` like
+ * any other emitted route, so `updateGitignore` puts it in the managed
+ * block. A project that migrated from a hand-written route to a fully
+ * generated one may still carry a stale `# Application-owned rule` comment
+ * above the same literal path from before the migration; `updateGitignore`
+ * only ever touches its own managed block, so that stale comment is left as
+ * project history for the consumer to clean up — the same way any other
+ * manual `.gitignore` edit outside the managed block is preserved.
+ */
+import type { SvelteKitOptions } from './sveltekit-generator.js';
 /**
  * Whether `@happyvertical/smrt-users/sveltekit` — the exact subpath the
  * generated route imports — is resolvable from the consumer at

package/dist/vite-plugin/sveltekit-generator.d.ts

@@ -1,7 +1,11 @@
-import { DomainKnowledgeConfig } from '@happyvertical/smrt-types';
-import { ApiMethodExposure, WireabilityOptions } from '../generators/custom-action.js';
-import { ApiHttpMethod } from '../registry/types.js';
-import { MethodDefinition, SmartObjectDefinition, SmartObjectManifest } from '../scanner/types';
+/**
+ * SvelteKit route auto-generation from SMRT objects
+ * Generates real TypeScript files in src/routes/api/ based on discovered SMRT objects
+ */
+import type { DomainKnowledgeConfig } from '@happyvertical/smrt-types';
+import { type ApiMethodExposure, type WireabilityOptions } from '../generators/custom-action.js';
+import type { ApiHttpMethod } from '../registry/types.js';
+import type { MethodDefinition, SmartObjectDefinition, SmartObjectManifest } from '../scanner/types';
 export interface SvelteKitOptions {
     enabled: boolean;
     routesDir: string;

package/dist/vite-plugin/sveltekit-route-coordinator.d.ts

@@ -1,6 +1,6 @@
-import { ConfigEnv, Plugin } from 'vite';
-import { SmartObjectManifest } from '../scanner/types.js';
-import { SvelteKitOptions } from './sveltekit-generator.js';
+import type { ConfigEnv, Plugin } from 'vite';
+import type { SmartObjectManifest } from '../scanner/types.js';
+import { type SvelteKitOptions } from './sveltekit-generator.js';
 export type SvelteKitRouteOwner = 'producer' | 'consumer';
 interface RouteContribution {
     owner: SvelteKitRouteOwner;

package/dist/vite-plugin/sync-apply-route.d.ts

@@ -1,5 +1,22 @@
-import { SmartObjectManifest } from '../scanner/types';
-import { SvelteKitOptions } from './sveltekit-generator.js';
+/**
+ * SvelteKit generator for the sync-apply batch write route (#1759).
+ *
+ * Emits ONE route — `{routesDir}/sync/apply/+server.ts` — implementing the
+ * shared web/mobile write contract for every syncable model in the manifest
+ * (models whose API config exposes at least one of create/update/delete). The
+ * generated file is deliberately thin: it maps `object` segments to
+ * collections plus per-model policy data, and delegates all batch processing
+ * to `processSyncApplyBatch` from `@happyvertical/smrt-core` — the same
+ * engine the runtime REST generator uses, so the two transports cannot drift.
+ *
+ * This lives in its own module (rather than sveltekit-generator.ts) so the
+ * shared generator file only needs a one-line registration hook; sibling
+ * work (#1757, #1758) touches the same generator files in parallel.
+ *
+ * Contract documentation: docs/content/architecture/sync-apply-contract.md
+ */
+import type { SmartObjectManifest } from '../scanner/types';
+import type { SvelteKitOptions } from './sveltekit-generator.js';
 declare const MUTATING_ACTIONS: readonly ["create", "update", "delete"];
 type MutatingAction = (typeof MUTATING_ACTIONS)[number];
 /** Per-model data embedded into the generated route. */

package/dist/vite-plugin/web-collections.d.ts

@@ -1,5 +1,28 @@
-import { ToolDescriptor, ToolIdType, ToolRouteDescriptor } from '../generators/tool-schema.js';
-import { FieldDefinition, FieldUIHints, SmartObjectDefinition, SmartObjectManifest } from '../scanner/types.js';
+/**
+ * Manifest → web collection selection (single source of truth).
+ *
+ * The browser client data runtime (`@happyvertical/smrt-web`, #1761) consumes
+ * one typed collection definition per API-exposed REST collection. Four
+ * co-managed emission surfaces need the SAME selection and field rules, or the
+ * emitted runtime values and their declared types drift apart:
+ *
+ *  - the `\0smrt:web` runtime virtual module (JSON literal — {@link generateWebModule})
+ *  - the `@happyvertical/smrt-virt-web` ambient d.ts (vite-plugin)
+ *  - the physical `@smrt/web` d.ts (prebuild, for `tsc`-only consumers)
+ *  - the dependency-free type mirror in `@happyvertical/smrt-web`
+ *
+ * The three generated sites import {@link selectWebCollectionEntries} from
+ * here so the value emission and the type emission can never disagree. The hand-written mirror
+ * is deliberately smrt-dependency-free, so its copy cannot import these types;
+ * keep it textually in sync when the shape here changes. The per-collection SHAPE
+ * (name/objectRef/className/endpoint/idField/actions/fields/relationships) is built by the
+ * ONE {@link buildWebCollectionDefinition}, shared by the runtime emission AND
+ * the #1764 {@link computeWebManifestHash} shape digest — so the emitted shape
+ * and the hashed shape can never drift (a drift would let the hash under-cover a
+ * change → stale client caches).
+ */
+import { type ToolDescriptor, type ToolIdType, type ToolRouteDescriptor } from '../generators/tool-schema.js';
+import type { FieldDefinition, FieldUIHints, SmartObjectDefinition, SmartObjectManifest } from '../scanner/types.js';
 /**
  * The field types that actually reach an emitted web collection definition:
  * everything {@link buildWebFieldDefinitions} does not skip. Relationship

package/dist/vite-plugin/worker-registration.d.ts

@@ -1,4 +1,24 @@
-import { Alias, ResolvedConfig } from 'vite';
+/**
+ * Compiled application registration for out-of-bundle Node processes (#3117).
+ *
+ * A SvelteKit app registers its own `@smrt()` objects through the generated
+ * `smrt-register.ts`, which only the Vite build compiles — and adapter-node
+ * re-bundles the server from its own entries, so that module never exists as
+ * an importable file in `build/`. A deployed task or schedule worker is plain
+ * ESM run by `node`, so without this artifact `ObjectRegistry.getClass()`
+ * cannot resolve any application object and every app-defined job throws
+ * `Unknown object type` before its method runs.
+ *
+ * After a production build, this compiles that same generated module into
+ * `.smrt/runtime/register.js`: one ESM entry that registers the app's local
+ * objects AND its consumed packages' objects (via the `.smrt/register.js` it
+ * imports), with each class's package-qualified identity and isolated
+ * manifest exactly as the web server registers them. Application sources are
+ * bundled; every package import stays external and is resolved from
+ * `node_modules` at runtime, like the rest of the deployed image — so the
+ * worker and `@happyvertical/smrt-core` share one registry.
+ */
+import type { Alias, ResolvedConfig } from 'vite';
 /** Directory (under the project root) the compiled registration is written to. */
 export declare const WORKER_REGISTRATION_DIR = ".smrt/runtime";
 /** Entry file name inside {@link WORKER_REGISTRATION_DIR}. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@happyvertical/smrt-core",
-  "version": "0.51.31",
+  "version": "0.51.33",
   "description": "Core AI agent framework with standardized collections, object-relational mapping, and code generators",
   "author": "HappyVertical",
   "type": "module",
@@ -154,9 +154,9 @@
     "@happyvertical/files": "^0.94.1",
     "@happyvertical/json": "^0.94.1",
     "@happyvertical/logger": "^0.94.1",
-    "@happyvertical/smrt-config": "0.51.31",
-    "@happyvertical/smrt-scanner": "0.51.31",
-    "@happyvertical/smrt-types": "0.51.31",
+    "@happyvertical/smrt-config": "0.51.33",
+    "@happyvertical/smrt-scanner": "0.51.33",
+    "@happyvertical/smrt-types": "0.51.33",
     "@happyvertical/sql": "^0.94.1",
     "@happyvertical/utils": "^0.94.1",
     "@oxc-project/runtime": "^0.150.0",
@@ -166,6 +166,7 @@
     "oxc-transform": "0.150.0",
     "pluralize": "^8.0.0",
     "tsx": "^4.23.13",
+    "vite": "8.1.4",
     "yaml": "^2.9.1"
   },
   "peerDependencies": {
@@ -189,10 +190,8 @@
     "@types/pluralize": "^0.0.33",
     "@xenova/transformers": "^2.17.2",
     "svelte": "^5.57.1",
-    "svelte-check": "4.7.6",
-    "typescript": "5.9.3",
-    "vite": "8.1.4",
-    "vite-plugin-dts": "5.1.0",
+    "svelte-check": "^4.7.6",
+    "typescript": "6.0.3",
     "vitest": "4.1.10"
   },
   "publishConfig": {

package/dist/knowledge-discovery.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"knowledge-discovery.js","names":[],"sources":["../src/knowledge-discovery.ts"],"sourcesContent":["/** Filesystem-only discovery shared by docs snapshots and knowledge indexing. */\nimport type { Dirent } from 'node:fs';\nimport { existsSync, readdirSync, readFileSync, realpathSync } from 'node:fs';\nimport { join } from 'node:path';\n\nexport interface ScopedPackageDirectory {\n  /** Scope entry name; consumers may select by alias rather than manifest name. */\n  name: string;\n  /** Original node_modules path, retained for workspace-relative reporting. */\n  directory: string;\n  /** Resolved path for identity comparisons or absolute snapshot links. */\n  realDirectory: string;\n}\n\n/**\n * Enumerate scope entries without descending into pnpm's linked dependency graph.\n * Selection, workspace discovery and enrichment remain caller policies.\n */\nexport function discoverScopedPackageDirectories(\n  scopeDirectories: string[],\n): ScopedPackageDirectory[] {\n  const packages: ScopedPackageDirectory[] = [];\n  for (const scopeDirectory of new Set(scopeDirectories)) {\n    let entries: Dirent[];\n    try {\n      entries = readdirSync(scopeDirectory, { withFileTypes: true });\n    } catch {\n      continue;\n    }\n    for (const entry of entries) {\n      if (!entry.isDirectory() && !entry.isSymbolicLink()) continue;\n      const directory = join(scopeDirectory, entry.name);\n      try {\n        packages.push({\n          name: entry.name,\n          directory,\n          realDirectory: realpathSync(directory),\n        });\n      } catch {\n        // Dangling links are not installed packages.\n      }\n    }\n  }\n  return packages;\n}\n\n/** Read authored docs only; never load artifacts, package code or object scans. */\nexport function readPackageAgentDoc(\n  directory: string,\n  options: { inspectAdapter?: boolean } = {},\n) {\n  const agentsPath = join(directory, 'AGENTS.md');\n  const claudePath = join(directory, 'CLAUDE.md');\n  const hasAgentsMd = existsSync(agentsPath);\n  const hasClaudeMd = existsSync(claudePath);\n  const agentsContent = hasAgentsMd ? readFileSync(agentsPath, 'utf8') : '';\n  const claudeContent =\n    hasClaudeMd && (!hasAgentsMd || options.inspectAdapter)\n      ? readFileSync(claudePath, 'utf8')\n      : '';\n  const hasClaudeShim = hasClaudeMd && claudeContent.trim() === '@AGENTS.md';\n  const source: 'AGENTS.md' | 'CLAUDE.md' | null = hasAgentsMd\n    ? 'AGENTS.md'\n    : hasClaudeMd && !hasClaudeShim\n      ? 'CLAUDE.md'\n      : null;\n  return {\n    hasAgentsMd,\n    hasClaudeMd,\n    hasClaudeShim,\n    agentsContent,\n    claudeContent,\n    source,\n    content: hasAgentsMd ? agentsContent : source ? claudeContent : null,\n  };\n}\n"],"mappings":";;;;;;;AAkBA,SAAgB,iCACd,kBAC0B;CAC1B,MAAM,WAAqC,CAAC;CAC5C,KAAK,MAAM,kBAAkB,IAAI,IAAI,gBAAgB,GAAG;EACtD,IAAI;EACJ,IAAI;GACF,UAAU,YAAY,gBAAgB,EAAE,eAAe,KAAK,CAAC;EAC/D,QAAQ;GACN;EACF;EACA,KAAK,MAAM,SAAS,SAAS;GAC3B,IAAI,CAAC,MAAM,YAAY,KAAK,CAAC,MAAM,eAAe,GAAG;GACrD,MAAM,YAAY,KAAK,gBAAgB,MAAM,IAAI;GACjD,IAAI;IACF,SAAS,KAAK;KACZ,MAAM,MAAM;KACZ;KACA,eAAe,aAAa,SAAS;IACvC,CAAC;GACH,QAAQ,CAER;EACF;CACF;CACA,OAAO;AACT;;AAGA,SAAgB,oBACd,WACA,UAAwC,CAAC,GACzC;CACA,MAAM,aAAa,KAAK,WAAW,WAAW;CAC9C,MAAM,aAAa,KAAK,WAAW,WAAW;CAC9C,MAAM,cAAc,WAAW,UAAU;CACzC,MAAM,cAAc,WAAW,UAAU;CACzC,MAAM,gBAAgB,cAAc,aAAa,YAAY,MAAM,IAAI;CACvE,MAAM,gBACJ,gBAAgB,CAAC,eAAe,QAAQ,kBACpC,aAAa,YAAY,MAAM,IAC/B;CACN,MAAM,gBAAgB,eAAe,cAAc,KAAK,MAAM;CAC9D,MAAM,SAA2C,cAC7C,cACA,eAAe,CAAC,gBACd,cACA;CACN,OAAO;EACL;EACA;EACA;EACA;EACA;EACA;EACA,SAAS,cAAc,gBAAgB,SAAS,gBAAgB;CAClE;AACF"}