@happyvertical/smrt-vitest 0.57.46 → 0.57.48

package/AGENTS.md

@@ -18,12 +18,41 @@ Without the plugin → "unregistered class" / "No field metadata found" errors.
 
 ## What the Plugin Does
 
-1. Scans `src/**/*.ts` for SMRT classes via ManifestBuilder
+1. Scans `src/**/*.ts` for SMRT classes via ManifestBuilder into this run's
+   test manifest snapshot (see below)
 2. Discovers `@happyvertical/smrt-*` dependencies from package.json
 3. Loads external manifests via ManifestManager
 4. Registers all classes in ObjectRegistry
 5. Watch mode caveat: manifest only generated at startup — restart vitest after adding new classes/fields
 
+## Test manifest snapshot (#4128)
+
+- Test generation is test-inclusive, so it writes only
+  `.smrt/test-runs/<pid>-<time>-<rand>/manifest.json` (`outputMode:
+  'explicit'`). `.smrt/manifest.json`, `dist/manifest.json` and paired
+  knowledge are production outputs; never write test output there, and do not
+  regenerate production knowledge from a test scan.
+- `config()` publishes the path synchronously in
+  `__SMRT_TEST_MANIFEST_PATHS__` (keyed by root; core's
+  `test-artifacts.ts` owns the read side, parity tested) so forked workers
+  inherit it. `LocalManifestReader.loadLocal()`, the runtime manifest loader and
+  `createIsolatedTestDbFromManifest()` read it first for the registered root
+  only (a dependency's root matches only when its own run registered it).
+- Tests inspecting generated metadata use `getTestManifestPath()`, not a
+  literal `.smrt/manifest.json`.
+- Production consumers refuse `artifactPurpose: 'test'` manifests outside
+  their registered run (#2760), and worker bulk registration skips inline
+  `.test.`/`.spec.` entries (#2750); both are covered by nested-run regressions
+  (`issue-2760-test-then-cli-parity`, `issue-2750` fixture's
+  `inline-fixture.spec.ts`). Processes started outside the run — CLIs,
+  generated servers with a sanitized env — need a production manifest, never
+  the snapshot.
+- The run directory is removed on process exit; startup prunes same-host
+  directories only once their owner PID is gone (any age), and directories
+  with an unprobeable owner (foreign host, missing `owner.json`) once older
+  than a day. Regression:
+  `src/__tests__/issue-4128-concurrent-build-isolation.test.ts`.
+
 ## Pool and isolation (#2897)
 
 Measured on a 333-file, 3,259-test unit suite, 16 cores (follow-up to #2893):
@@ -49,6 +78,31 @@ Measured on a 333-file, 3,259-test unit suite, 16 cores (follow-up to #2893):
   measurements. Lazy-loading `@happyvertical/ai` in core is the
   isolation-preserving lever, tracked separately.
 
+## Workspace source resolution (#2954)
+
+- `getWorkspaceViteAliases()` aliases every exact JavaScript subpath each
+  workspace package exports from `dist/` to the source it is built from,
+  derived from that package's own `exports` map (`dist/<p>.js` ←
+  `src/<p>.ts`, `src/<p>.svelte.ts`, `src/<p>/index.ts`, or the same under
+  `src/lib/`). Hand-written entries in `src/index.ts` win, for layouts the
+  rule cannot infer. A new export is covered with no plugin edit;
+  `issue-2954-workspace-source-resolution.test.ts` fails if any dist export
+  has no derivable source.
+- Workspace `setupFiles` specifiers are mapped to source too (Vitest resolves
+  them outside `resolve.alias`).
+- The plugin is `enforce: 'pre'`, so its `resolveId` runs after Vite's alias
+  step but before Vite's own resolver. A workspace specifier the static
+  aliases did not rewrite (pattern exports such as smrt-ui `./utils/*`) is
+  mapped to its source per import; one whose exports-map target is built
+  JavaScript with no source fails the test, whether that dist file is stale
+  or missing. Exempt: packages a consumer resolves to published entries on
+  purpose (`aliasFilter` drops, or a config alias pointing at a `dist/`
+  file). Explicit file-path imports of a dist (runtime loaders under test)
+  are not specifier resolution and are left alone.
+- Typecheck is separate: packages typechecked with their composite
+  `tsconfig.json` read sibling `.d.ts` from `dist/`; run `pnpm typecheck`
+  (Turbo builds dependencies first); source-resolving typecheck is #4556.
+
 ## Vite 8 (rolldown/oxc) normalization (#2017)
 
 The plugin's `config` hook normalizes three vite 8 behaviors so consumers
@@ -240,4 +294,4 @@ Pattern: render → assert role/name/state → drive with user-event → prove a
 - `src/svelte-setup.ts` — Svelte component-test setup (jest-dom, cleanup, dialog polyfill)
 - `src/svelte.ts` — component-test surface (Testing Library + a11y, one import)
 - `src/a11y.ts` — `expectNoA11yViolations` (axe-core)
-- `src/test-db.ts` — createIsolatedTestDb, createIsolatedTestDbFromManifest, createTestDb
+- `src/test-db.ts` — createIsolatedTestDb, createIsolatedTestDbFromManifest, createTestDb, getTestManifestPath

package/README.md

@@ -83,17 +83,19 @@ settings on vite 8.
 
 The manifest is generated once at vitest startup. Restart vitest after adding new `@smrt()` classes or fields.
 
-### Generated Artifact Coherence
-
-Test startup refreshes the canonical `.smrt/manifest.json` and its paired
-`.smrt/smrt-knowledge.json` together. When `smrtPlugin()` is present, the
-Vitest plugin uses its current agent-surface declarations and effective
-knowledge configuration, including inline plugin options. A standalone
-Vitest configuration preserves prior agent-surface source hashes when it
-cannot rescan them, so changed declarations remain stale rather than being
-incorrectly marked fresh. The monorepo build cache restores this pair with the
-generated server registration entry, so `pnpm build`, `pnpm test`, and a
-cached `pnpm build` leave one coherent artifact snapshot.
+### Test Manifest Snapshot
+
+Test startup scans test-inclusive sources (inline `*.test.ts` fixture classes
+need manifest metadata) and writes the result to a per-run snapshot,
+`.smrt/test-runs/<run>/manifest.json`, never to `.smrt/manifest.json`,
+`dist/manifest.json`, or their paired `smrt-knowledge.json` (#4128). Those
+belong to production builds, so a build or typecheck running alongside a test
+suite can neither replace the suite's manifest nor be replaced by it. Every
+manifest read inside the run — worker registration, the runtime manifest
+loader, `createIsolatedTestDbFromManifest()` — resolves the snapshot first;
+tests that inspect generated metadata read `getTestManifestPath()`. The
+snapshot directory is removed when the run exits, and directories left by
+ended runs are pruned at the next startup.
 
 ### Pool and Isolation