archal 0.9.19 → 0.10.0

package/dist/vitest/index.d.ts

@@ -1,3 +1,4 @@
+import { UserWorkspaceConfig } from 'vitest/config';
 import { Reporter } from 'vitest/reporters';
 import { Vitest } from 'vitest/node';
 
@@ -5,7 +6,7 @@ interface ServiceConfig {
     mode: 'route';
     seed?: string;
 }
-type SeedFormat = 'json' | 'markdown';
+type SeedFormat = 'json' | 'sql';
 interface ResolvedRuntime {
     resolvedServices: string[];
     resolvedSeeds: Record<string, string>;
@@ -85,7 +86,7 @@ type SeedClassification = {
 /**
  * Determine whether a seed value is a prebuilt named seed or a developer-
  * provided file path. File paths start with `./', `../`, `/`, or end with
- * `.json` / `.md`.
+ * `.json` / `.sql`.
  */
 declare function classifySeed(value: string): SeedClassification;
 
@@ -177,82 +178,36 @@ declare function clearArchalWebhooks(serviceName: string): Promise<void>;
 declare function waitForArchalWebhook(serviceName: string, matcher: string | WaitForWebhookOptions, options?: WaitForWebhookOptions): Promise<ArchalWebhookDelivery>;
 
 /**
- * Archal Vitest Reporter — sends test results to the Archal dashboard.
+ * Archal Vitest Reporter — observes Vitest lifecycle health.
  *
  * `withArchal()` and `archalVitestProject()` already install this reporter
  * automatically; you only need to reference it manually if you're composing
  * a fully custom vitest config outside those helpers.
  *
- * After each test run, results are POSTed to /api/test-results so they
- * appear in the Archal dashboard alongside scenario traces.
+ * Legacy /api/test-results upload is retired. Benchmark Results ingestion writes
+ * scenario attempts through the Benchmark Run submission API instead.
  */
 
 declare class ArchalReporter implements Reporter {
-    private startTime;
     private ctx;
     private lifecycleMarkerPath;
-    private workspaceReporterMarkerPath;
-    private projects;
     /**
-     * In-flight upload promise for the current run. Vitest v3+ fires both
-     * `onFinished` and `onTestRunEnd` in parallel via `Promise.all` (see
-     * vitest@3.x packages/vitest/src/node/test-run.ts), so without this guard
-     * the reporter uploads results twice and the dashboard shows duplicate
-     * rows. Reset at the start of each run (onTestRunStart / onWatcherRerun)
-     * so watch-mode reruns still upload.
+     * In-flight lifecycle promise for the current run. Vitest v3+ fires both
+     * `onFinished` and `onTestRunEnd` in parallel via `Promise.all`, so without
+     * this guard the reporter emits duplicate diagnostics. Reset at the start
+     * of each run (onTestRunStart / onWatcherRerun) so watch-mode reruns still
+     * report.
      */
-    private activeUpload;
+    private activeLifecycle;
     onInit(ctx: Vitest): void;
-    /**
-     * v3+ canonical start-of-run hook. Resetting the upload guard here lets
-     * watch-mode reruns upload their own results.
-     */
-    onTestRunStart(_specifications?: unknown[]): void;
-    /**
-     * v2 watch-mode start-of-rerun hook. Same purpose as onTestRunStart for
-     * v3+. Vitest v2 has no onTestRunStart, so we reset here instead.
-     */
+    onTestRunStart(_specifications?: readonly unknown[]): void;
     onWatcherRerun(_files?: string[], _trigger?: string): void;
+    onFinished(files?: readonly unknown[], _errors?: readonly unknown[]): Promise<void>;
+    onTestRunEnd(testModules?: readonly unknown[], _unhandledErrors?: readonly unknown[], _reason?: unknown): Promise<void>;
     private decodeConfig;
-    private buildProjectContext;
-    private resolveProjects;
-    /**
-     * vitest v2 calls onFinished with an array of File objects (from @vitest/runner).
-     * Each File extends Suite which has `tasks: Task[]`, and each Task has
-     * `.type` ('test' | 'suite'), `.name`, `.result?.state`, `.result?.duration`.
-     */
-    onFinished(files?: unknown[], _errors?: unknown[]): Promise<void>;
-    /**
-     * vitest v3+ calls onTestRunEnd alongside onFinished (in parallel via
-     * Promise.all). v4 drops onFinished entirely. The argument is an array of
-     * test modules, each with nested children.
-     */
-    onTestRunEnd(testModules?: unknown[]): Promise<void>;
-    /**
-     * Dedupe upload work when Vitest fires multiple end-of-run hooks. In
-     * Vitest v3+ both `onFinished` and `onTestRunEnd` fire from the same
-     * `Promise.all` in TestRun.end(); the first hook to enter wins and the
-     * second awaits the same in-flight upload instead of POSTing a duplicate
-     * row to /api/test-results. The resolved promise is kept on the instance
-     * so any late hook still no-ops — the guard is only cleared at the start
-     * of a new run (onTestRunStart / onWatcherRerun).
-     */
-    private runUploadOnce;
-    private collectAndReport;
-    /**
-     * vitest v2: File extends Suite { tasks: Task[] }.
-     * Task.type is 'test' | 'suite' | 'custom'. Suite tasks recurse.
-     */
-    private collectV2Files;
-    /**
-     * vitest v4: TestModule.children() → TestSuite[].children() → TestCase[]
-     * All accessors are methods (not properties) in v4.
-     */
-    private collectV4Modules;
-    private resolveProjectForFile;
-    private partitionResults;
-    private sendResults;
-    private readSessionId;
+    private resolveProjectName;
+    private runLifecycleOnce;
+    private reportLifecycleComplete;
 }
 
 interface ArchalVitestProjectOptions {
@@ -307,7 +262,7 @@ interface ArchalVitestWorkspaceProjectConfig {
     };
     [key: string]: unknown;
 }
-type ArchalVitestWorkspaceProject = string | ArchalVitestWorkspaceProjectConfig | (() => ArchalVitestWorkspaceProjectConfig | Promise<ArchalVitestWorkspaceProjectConfig>);
+type ArchalVitestWorkspaceProject = string | UserWorkspaceConfig | ArchalVitestWorkspaceProjectConfig | (() => UserWorkspaceConfig | ArchalVitestWorkspaceProjectConfig | Promise<UserWorkspaceConfig | ArchalVitestWorkspaceProjectConfig>);
 type ArchalVitestWorkspaceInput = readonly ArchalVitestWorkspaceProject[];
 /**
  * Create a vitest workspace project that routes requests to Archal hosted clones.
@@ -325,31 +280,12 @@ type ArchalVitestWorkspaceInput = readonly ArchalVitestWorkspaceProject[];
  * single `vitest.config.ts`, use `withArchal()` instead.
  */
 declare function archalVitestProject(options: ArchalVitestProjectOptions, testOptions?: ArchalVitestProjectTestOptions): ArchalVitestWorkspaceProjectConfig;
-/**
- * @deprecated Use {@link withArchal} instead. `archalVitestConfig({ services })`
- * is equivalent to `withArchal({}, { services })`, and `withArchal` additionally
- * preserves any existing `test` block fields (coverage, alias, globalSetup,
- * poolOptions, custom reporters, etc.) — which `archalVitestConfig` cannot
- * accept. This export will remain for a deprecation window; new code should
- * use `withArchal`.
- *
- * Migration:
- * ```ts
- * // before
- * test: archalVitestConfig({ services: { stripe: { mode: 'route' } } })
- * // after
- * test: withArchal({}, { services: { stripe: { mode: 'route' } } })
- * ```
- *
- * For `vitest.workspace.ts` usage, continue to use `archalVitestProject()`.
- */
-declare function archalVitestConfig(options: ArchalVitestProjectOptions, testOptions?: ArchalVitestProjectTestOptions): ArchalVitestBuiltTestConfig;
 /**
  * Root-level Vitest config for workspace users.
  *
  * Vitest only honors reporters from the root config, not from individual
  * workspace projects. Pair this with `vitest.workspace.ts` when using
- * `archalVitestProject()` / `archalVitestWorkspace()` so dashboard upload
+ * `archalVitestProject()` / `archalVitestWorkspace()` so reporter diagnostics
  * remains enabled.
  */
 declare function archalVitestRootConfig(): {
@@ -387,7 +323,7 @@ declare function archalVitestRootConfig(): {
  *     entries are appended. ArchalReporter is appended only when the user's
  *     reporter list doesn't already contain an ArchalReporter instance — so a
  *     config carried over from an older helper or hand-rolled setup doesn't
- *     end up with two reporters double-uploading to `/dashboard/tests`.
+ *     end up with duplicate reporter lifecycle diagnostics.
  *     Vitest's `'default'` reporter is only inserted when the user didn't
  *     specify any reporters of their own.
  *   - `env`: user keys preserved; Archal's required session-config keys added.
@@ -429,4 +365,4 @@ declare function withArchal<T extends Record<string, unknown>>(existingTest: T,
  */
 declare function archalVitestWorkspace<T extends ArchalVitestWorkspaceInput>(projects: T): T;
 
-export { ArchalReporter, type ArchalVitestBuiltTestConfig, type ArchalVitestProjectOptions, type ArchalVitestProjectTestOptions, type PublicSessionSnapshot as ArchalVitestPublicSessionSnapshot, type ArchalVitestWorkspaceInput, type ArchalVitestWorkspaceProject, type ArchalVitestWorkspaceProjectConfig, type ArchalWebhookDelivery, type WaitForWebhookOptions, archalVitestConfig, archalVitestProject, archalVitestRootConfig, archalVitestWorkspace, bootstrapArchalVitestRouting, classifySeed, clearArchalWebhooks, getInstalledArchalVitestRuntime, getInstalledArchalVitestSession, listArchalWebhooks, resetArchalClones, waitForArchalWebhook, withArchal };
+export { ArchalReporter, type ArchalVitestBuiltTestConfig, type ArchalVitestProjectOptions, type ArchalVitestProjectTestOptions, type PublicSessionSnapshot as ArchalVitestPublicSessionSnapshot, type ArchalVitestWorkspaceInput, type ArchalVitestWorkspaceProject, type ArchalVitestWorkspaceProjectConfig, type ArchalWebhookDelivery, type WaitForWebhookOptions, archalVitestProject, archalVitestRootConfig, archalVitestWorkspace, bootstrapArchalVitestRouting, classifySeed, clearArchalWebhooks, getInstalledArchalVitestRuntime, getInstalledArchalVitestSession, listArchalWebhooks, resetArchalClones, waitForArchalWebhook, withArchal };