fusion/packages/core/vitest.config.ts

import { defineConfig } from "vitest/config";
import { resolve } from "node:path";
import { computeMaxWorkers } from "./src/__test-utils__/vitest-workers";

const maxWorkers = computeMaxWorkers();

const quarantinedCoreTests = [
  /*
  FNXC:CoreTests 2026-06-13-17:43:
  The full workspace suite must not fail on suite-load-sensitive tests that pass standalone or only fail after excessive wall time. Quarantine observed core offenders after package-lane hook timeouts instead of appeasing them with wider hook timeouts.

  FNXC:CoreTests 2026-06-14-02:14:
  FN-6433 re-ran the core quarantine batch after FN-6430's shared fixture cleanup and rescued all five files without timeout or assertion changes. Keep this array empty unless a future quarantine is mirrored in scripts/lib/test-quarantine.json in the same commit.

  FNXC:CoreTests 2026-06-15-03:13:
  FN-6481 observed the disk-backed concurrent write test fail in the changed-package workspace lane with a transient SQLite BEGIN IMMEDIATE lock after the gate had already passed. Quarantine the flaky file instead of widening lock-recovery timeouts or weakening assertions.

  FNXC:CoreTests 2026-06-15-07:39:
  FN-6486 rescued store-concurrent-writes by making the transient lock helper release independent of event-loop timer scheduling, then removed the quarantine in lockstep with scripts/lib/test-quarantine.json. Keep this array empty unless a future observed flake is mirrored in the ledger in the same commit.

  FNXC:CoreTests 2026-06-17-17:21:
  FN-6596 verification observed task-list-format and test-project timing out only in the broad changed-package core lane after the merge gate had passed; both files passed immediate isolated reruns. Quarantine the suite-load flakes without widening timeouts or weakening assertions.

  FNXC:CoreTests 2026-06-17-17:55:
  FN-6592 rescued mission-integration by closing every reopened TaskStore handle and strengthening restart-fidelity assertions across mission hierarchy read paths. Keep the quarantine absent in both this exclude list and scripts/lib/test-quarantine.json unless a future observed flake is mirrored in both files.

  FNXC:CoreTests 2026-06-17-19:03:
  FN-6600 re-ran the core quarantine candidates under the broad-run worker budget and rescued the current core ledger entries without timeout, retry, assertion, or worker-budget appeasement.
  Keep core quarantines mirrored here only when a loaded run still fails after shared teardown cleanup has been ruled out.

  FNXC:CoreTests 2026-06-19-10:00:
  FN-6705 verification observed these five files fail only in the broad changed-package core lane with hook/test timeouts, ENOTEMPTY cleanup, or a missed deferred hook after the same files passed an immediate targeted rerun. Quarantine the suite-load flakes instead of widening timeouts, adding retries, or weakening assertions.

  FNXC:CoreTests 2026-06-19-10:24:
  FN-6705 verification then observed settings-export time out in beforeEach only under the broad changed-package core lane while the targeted file rerun passed in 5.1s. Quarantine the suite-load hook flake instead of increasing hookTimeout.

  FNXC:CoreTests 2026-06-19-14:31:
  FN-6741 reloaded the six 2026-06-19 core quarantine files under the broad @fusion/core lane and rescued them in lockstep with scripts/lib/test-quarantine.json. Keep this array empty; future core suite-load flakes must prove a remaining shared worker-root/temp-redirect or fixture close-order gap before re-quarantining.

  FNXC:CoreTests 2026-06-19-15:05:
  Merge verification for FN-6741 observed store-concurrent-writes fail again under the broad @fusion/core lane with SQLite BEGIN IMMEDIATE lock exhaustion. Re-quarantine that single suite-load lock flake in lockstep with the ledger; keep the other rescued core files loaded.

  FNXC:CoreTests 2026-06-20-05:19:
  FN-6790 found no task-documents quarantine half-state on HEAD and rescued the ENOENT-rename class by quiescing deferred task-created write/hook work on TaskStore.close(). Keep task-documents loaded; do not add a ledger/config exclude unless a new loaded run fails after this lifecycle seam is ruled out.

  FNXC:CoreTests 2026-06-20-09:48:
  FN-6795 reloaded the remaining 2026-06-19 store-concurrent-writes quarantine under the full @fusion/core package lane and no longer reproduced SQLite BEGIN IMMEDIATE exhaustion. Rescue the file by keeping this exclude list empty in lockstep with scripts/lib/test-quarantine.json; future lock flakes need a fresh root-cause seam, not timeout/retry/worker appeasement.

  FNXC:CoreTests 2026-06-25-11:15:
  The SQLite-to-PostgreSQL cutover (feature quarantine-sqlite-internals-tests) quarantines the SQLite-internals test files that exercise SQLite-only behavior (PRAGMA, FTS5, VACUUM, ATTACH DATABASE, sqlite_master, node:sqlite DatabaseSync, migration sequencing) with no PostgreSQL equivalent. PgBackupManager is now the sole production backup path and the legacy SQLite BackupManager is being removed; the 'preserves branch groups' case in backup.test.ts also fails on clean baseline with a node:sqlite ERR_INVALID_ARG_TYPE binding error (TypeError: Provided value cannot be bound to SQLite parameter 1 via sqlite-adapter.ts:96). These files are mirrored in scripts/lib/test-quarantine.json and will be DELETED when the SQLite code is removed (Phase B/C of sqlite-final-removal). PG counterparts exist for backup (postgres/pg-backup.test.ts), FTS (postgres/fts-replacement.test.ts), schema (postgres/schema-applier.test.ts), central/secrets (postgres/central-archive-secrets.test.ts, postgres/secrets-roundtrip.test.ts), and mission store (postgres/satellite-mission-store.test.ts).
  */
  // SQLite-internals quarantine (cutover): see scripts/lib/test-quarantine.json.
  // SQLite-path failures under Node 26 node:sqlite ERR_INVALID_ARG_TYPE binding
  // (quarantined on sight per AGENTS.md flaky-test rule, same cutover batch).
  // Pre-existing load-sensitive PG flake (getRatings ordering under concurrent load);
  // quarantined on sight per AGENTS.md so verify:workspace goes green.
  /*
  FNXC:CoreTests 2026-06-25-16:30:
  The SQLite-to-PostgreSQL cutover (feature delete-sqlite-runtime-final, PHASE A)
  quarantines the remaining non-quarantined test files that construct a SQLite-backed
  store (new TaskStore(..., {inMemoryDb: true}) / new Database(...) / new AgentStore(...)
  with inMemoryDb) or use the sync SQLite data path. The SQLite runtime code
  (Database class, inMemoryDb option, sync prepare()/getDatabase() surface) is being
  deleted in this feature. Per the AGENTS.md flaky-test deletion ratchet, these tests
  are quarantined on sight (not migrated to PG) because they exercise code that will
  be deleted. PG counterparts for the critical invariants exist under
  src/__tests__/postgres/*.pg.test.ts. Mirrored in scripts/lib/test-quarantine.json;
  will be DELETED when the SQLite code is removed.
  */
  /*
  FNXC:CoreTests 2026-06-25-18:00:
  The SQLite-to-PostgreSQL cutover (feature delete-sqlite-runtime-final, SESSION 3 PHASE A)
  quarantines the remaining 74 active test files that import store-test-helpers.ts (which
  constructs TaskStore with inMemoryDb:true) or use inMemoryDb:false / new TaskStore() with
  the sync SQLite data path. These tests exercise the SQLite Database class that is being
  deleted in this feature. Per the AGENTS.md flaky-test deletion ratchet, they are
  quarantined on sight (not migrated to PG) because they test code we are about to delete.
  PG counterparts for critical invariants exist under src/__tests__/postgres/*.pg.test.ts.
  Mirrored in scripts/lib/test-quarantine.json; will be DELETED when the SQLite code is removed.
  */
  /*
  FNXC:SqliteFinalRemoval 2026-06-26-10:15:
  The SQLite Database/CentralDatabase/ArchiveDatabase class bodies were deleted
  (VAL-REMOVAL-005, feature physical-delete-db-class-final). These test files
  exercise the legacy sync SQLite data path — they construct Database/
  CentralDatabase/CentralCore(in non-backend mode)/TaskStore(sync path) directly
  and call init()/prepare()/transaction() which now throw because the SQLite
  runtime is removed. They are quarantined on sight per the AGENTS.md flaky-test
  deletion ratchet (not migrated to PG) because they test code that has been
  deleted. PG counterparts for the critical invariants exist under
  src/__tests__/postgres/*.pg.test.ts (central-core-backend, secrets-roundtrip,
  satellite stores, etc). Mirrored in scripts/lib/test-quarantine.json; these
  files will be DELETED on the 14-day ratchet (2026-07-10) unless rescued.
  */
  "src/__tests__/central-core.test.ts",
  "src/__tests__/central-claim-mutex.test.ts",
  "src/__tests__/central-integration.test.ts",
  "src/__tests__/central-core-docker-node.test.ts",
  "src/__tests__/central-core-ensure-project.test.ts",
  "src/__tests__/central-project-node-mappings.test.ts",
  "src/__tests__/commit-association-diff-backfill.real-git.test.ts",
  "src/__tests__/docker-node-config.test.ts",
  "src/__tests__/first-run.test.ts",
  "src/__tests__/migration-orchestrator.test.ts",
  "src/__tests__/migration.test.ts",
  "src/__tests__/mission-factory-parity.integration.test.ts",
  "src/__tests__/mission-integration.test.ts",
  "src/__tests__/multi-node-dashboard.test.ts",
  "src/__tests__/project-isolation-transition.test.ts",
  "src/__tests__/secrets-store.test.ts",
  "src/__tests__/secrets-sync-passphrase.test.ts",
  "src/__tests__/settings-parity.test.ts",
  "src/__tests__/store-activity.test.ts",
  "src/__tests__/store-handoff-to-review.test.ts",
  "src/__tests__/store-plugin-store-close.test.ts",
  "src/__tests__/store-secrets-store-global-dir.test.ts",
  "src/__tests__/store-settings-sync-passphrase-probe.test.ts",
  "src/__tests__/todo-store.test.ts",
];

export default defineConfig({
  resolve: {
    alias: {
      "@fusion/core": resolve(__dirname, "./src/index.ts"),
      "@fusion/test-utils": resolve(__dirname, "./src/__test-utils__/workspace.ts"),
      "@fusion/plugin-sdk": resolve(__dirname, "../plugin-sdk/src/index.ts"),
    },
  },
  test: {
    include: ["src/**/*.test.ts"],
    exclude: quarantinedCoreTests,
    setupFiles: [
      "./src/__test-utils__/vitest-setup.ts",
    ],
    globalSetup: ["./src/__test-utils__/vitest-teardown.ts"],
    // Must stay "forks". Two thread-unsafe patterns block migration to "threads":
    //
    //   1. vitest-setup.ts:123 — `process.chdir(workerTempDir)` is gated by
    //      `isMainThread`, which is `false` in worker_threads, so each thread
    //      worker never gets its isolated cwd. Tests that rely on cwd being a
    //      disposable temp dir would silently operate in the repo root.
    //
    //   2. Some suites rely on fork-level process/env isolation for setup side effects,
    //      and cannot safely share mutable process state under worker_threads.
    pool: "forks",
    maxWorkers,
    minWorkers: 1,
    fileParallelism: true,
    // Core runs a large SQLite-heavy suite while other workspace packages test concurrently.
    // Use a slightly higher timeout to reduce nondeterministic slow-machine flakes.
    testTimeout: 15_000,
    hookTimeout: 15_000,
    coverage: {
      enabled: false,
      reporter: ["text", "html", "json"],
      reportsDirectory: "./coverage",
      include: ["src/**/*.ts"],
      exclude: ["**/*.test.ts", "**/*.d.ts", "dist/**"],
    },
  },
});