ci: build swift helper before bun test

The Swift helper binary is imported at module-load time via Bun's
`with { type: "file" }` attribute in `src/mac/helper.ts`. Tests that
spawn the swrag CLI as a subprocess (tests/cli.test.ts) or import the
helper module directly (tests/mac/*, tests/bootstrap.test.ts,
tests/doctor.test.ts) fail with "Cannot find module" if the binary
isn't on disk when `bun test` boots.

Locally this works because the developer ran `bun run build` (or
`scripts/build-swift-helper.sh`) at least once. CI never did — both
`ci.yml` and `release.yml` only built the helper inside `bun run build`
which executes AFTER `bun test`. The v0.7.0 release workflow run
exposed this: 10 fail / 7 unhandled-error tests with "Cannot find
module '../../vendor/swrag-helper-darwin-universal'".

Build the helper explicitly between the fixture / dylib steps and the
test step in both workflows.

Author: NikitaHerndlhofer

.github/workflows/ci.yml

@@ -21,4 +21,10 @@ jobs:
         run: bun run tests/fixtures/make-fixtures.ts
       - name: fetch sqlite-vec vendor dylibs
         run: bun run scripts/fetch-vec-dylibs.ts
+      - name: build swift helper
+        # Same rationale as release.yml: src/mac/helper.ts imports the
+        # helper binary at module-load time, so any test that imports it
+        # (directly or via spawning the swrag CLI) needs the binary on
+        # disk before `bun test` runs.
+        run: bash scripts/build-swift-helper.sh
       - run: bun test

.github/workflows/release.yml

@@ -46,6 +46,16 @@ jobs:
       - name: fetch vendor dylibs
         if: steps.check.outputs.skip != 'true'
         run: bun run scripts/fetch-vec-dylibs.ts
+      - name: build swift helper
+        # The Swift helper binary is imported at module-load time via Bun's
+        # `with { type: "file" }` attribute (src/mac/helper.ts). Any test
+        # that spawns the swrag CLI as a subprocess (tests/cli.test.ts) or
+        # imports the helper module (tests/mac/*, tests/bootstrap.test.ts,
+        # tests/doctor.test.ts) fails with "Cannot find module" if the
+        # binary isn't on disk. Build it before the test phase rather
+        # than only inside `bun run build`.
+        if: steps.check.outputs.skip != 'true'
+        run: bash scripts/build-swift-helper.sh
       - if: steps.check.outputs.skip != 'true'
         run: bun test
       - if: steps.check.outputs.skip != 'true'