[osovv]

Why the change

Concurrent bun test processes collide on the shared ambient $XDG_DATA_HOME/vvoc/workflow/<sessionId>/ persistence root — the suite's fixed session IDs plus its before/after hooks that delete those directories make parallel runs fail with LAUNCH_PERSISTENCE_FAILED / ENOENT workflow-state.json.tmp-*.

Special things to note

• No production code changed: persistence keeps its documented $XDG_DATA_HOME/vvoc/workflow/<sessionId>/workflow-state.json contract; only the test file redirects the environment for its own process and restores the caller's value afterwards.
• The workflow persistence block previously pointed XDG_DATA_HOME at import.meta.dirname, materializing state inside the source tree (src/plugins/vvoc/workflow/…) on one path shared by all processes; it now targets the same per-process temp root.
• File-scoped afterAll removes the temp root and restores the caller's XDG_DATA_HOME, so other test files in the same bun test process are unaffected.

Change outline

The whole suite now resolves persistence paths from one pid-suffixed root, set up once per file:

const isolatedDataHome = `/tmp/vvoc-workflow-integration-data-${process.pid}`;

beforeAll(() => {
  rmSync(isolatedDataHome, { recursive: true, force: true });
  mkdirSync(isolatedDataHome, { recursive: true });
  process.env.XDG_DATA_HOME = isolatedDataHome;
});

afterAll(() => {
  // restore previousDataHome, rmSync(isolatedDataHome)
});

Every disk-touching block already resolves session directories from the environment at call time, so the redirect covers them all; the persistence block's own override switches from the shared source-tree path to the same per-process root. Two processes therefore never share a <sessionId> directory, and mid-run hook deletions can no longer hit another process's state.