note: You are running `vp test` as a Vite+ built-in command. If you meant to run the test npm script, use `vpr test` instead.

 RUN  v5.0.1 /home/ubuntu/wt/pull-request-05

 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > retries a failed stack read after the summary becomes terminal 32ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > explicit refresh reads a changed stack even when its PR summary is unchanged 5ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > snapshots an unsynced link once and writes it to the thread 4ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > asks the host once for a pull request shared by two threads in one project 5ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > isolates a failed project summary refresh and retries it after the other project succeeds 7ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > isolates a failed project stack refresh and retries it after the other project succeeds 6ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > recovers the HTTP port when syncing an older Forgejo link 3ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > dispatches nothing when the host snapshot is unchanged 4ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > refreshes closed links through each project after reopening elsewhere 4ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > stops asking the host once a pull request is merged 4ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > re-reads a merged pull request until the host supplies its merge time 13ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > syncs a pull request a reader saw merge without waiting for the sweep 4ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > discovers externally reopened pull requests after fifteen minutes 12ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > preserves a refresh requested while an older host read is in flight 4ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > reads a burst of requested links in one sweep 4ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > skips the stack read for a pull request the summary places in no stack 3ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > leaves a settled thread's links unread until the thread is unsettled 11ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > auto-links missing native stack layers on active threads only 3ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > keeps existing snapshots and continues when the host fails 2ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > leaves a rate limited host unread until its pause ends 7ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > pauses the host when only its stack read is rate limited 4ms
 ✓ apps/server/src/orchestration-v2/PullRequestSyncReactor.test.ts > PullRequestSyncReactor > reads open links fresh only when a run that ran a merge command ends 4ms

 Test Files  1 passed (1)
      Tests  22 passed (22)
   Start at  11:21:05
   Duration  14.00s (transform 67%, import 30%, setup 1%, tests 1%)

  Transform  transforming modules took 9.20s · 67% of tracked time, re-done on every run
             persist transforms across runs with fsModuleCache: true
             learn more: https://vitest.dev/guide/improving-performance#caching-between-reruns