test!: mock-free test architecture

.changeset/testing-workflow-bundle-export.md

@@ -0,0 +1,5 @@
+---
+"@temporal-contract/testing": minor
+---
+
+New `@temporal-contract/testing/workflow-bundle` subpath: `bundleFor` (memoizes a `bundleWorkflowCode` call per `workflowsPath` within a test file), `withTaskQueue` (scopes a contract to a per-test task queue), `nextTaskQueueId` (a reproducible, non-random monotonic id generator), and `fixturePath` (resolves a sibling fixture file relative to the caller's `import.meta.url`, working from both `.ts` source and built output). Backs the mock-free `*.inprocess.spec.ts` test tier and is now the shared home for a path-resolution helper that was previously copy-pasted into every one of those spec files.

.github/workflows/mutation.yml

@@ -0,0 +1,52 @@
+name: Mutation Testing
+permissions:
+  contents: read
+
+# Nightly baseline only — mutation testing is too slow to run per-PR. See
+# stryker.config.json: "break" is null because this establishes a baseline,
+# not a gate.
+#
+# Reading the baseline scores — a runner-scope caveat: `vitest.stryker.config.ts`
+# only composes each mutated package's "unit" Vitest project, deliberately
+# excluding the "integration"/"integration-inprocess" projects (real or
+# time-skipping Temporal servers, too slow to run per-mutant). That means
+# `packages/worker/src/internal.ts`'s score is measured WITHOUT the 11
+# mock-free suites under `packages/worker/src/__tests__/` — notably
+# `rehydration.inprocess.spec.ts`, which is what exercises `internal.ts`'s
+# `ChildWorkflowFailure` branch (around line 401). So `internal.ts`'s mutation
+# score understates its real coverage: it is partly a scope artifact, not
+# purely a test-quality gap. By contrast, `error-tags.ts`'s low score IS a
+# genuine gap — its only assertions in `errors.spec.ts` are tautological
+# (`_tag`-vs-own-constant). Don't read the two the same way.
+on:
+  schedule:
+    - cron: "0 3 * * *"
+  workflow_dispatch:
+
+jobs:
+  mutation:
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    steps:
+      - name: Checkout
+        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+
+      - name: Setup
+        uses: ./.github/actions/setup
+
+      # `test:mutation` (= `pnpm build && stryker run`) builds first: worker's
+      # unit specs import `@temporal-contract/contract` by package name, which
+      # resolves through its `exports` map to `dist/`. `dist/` is gitignored
+      # and nothing else in `setup` builds it, so skipping this leaves a fresh
+      # runner's dry run failing on missing dist output.
+      - name: Run mutation testing
+        run: pnpm test:mutation
+
+      - name: Upload mutation report
+        if: always()
+        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
+        with:
+          name: mutation-report
+          path: reports/mutation/
+          retention-days: 14
+          if-no-files-found: ignore

.gitignore

@@ -30,6 +30,11 @@ Thumbs.db
 
 coverage/
 
+# Stryker mutation testing
+.stryker-tmp/
+reports/mutation/
+stryker.log
+
 # VitePress
 **/.vitepress/cache/
 **/.vitepress/dist/

docs/.vitepress/config.ts

@@ -109,6 +109,13 @@ export default withMermaid(
     base: BASE,
     lang: "en-US",
 
+    // `docs/superpowers/**` holds internal planning/spec documents for this
+    // repo's own development process, not end-user documentation. Without
+    // this exclusion VitePress builds and publishes them like any other
+    // page, and `deploy-docs.yml` (triggered on `push` to `main` with
+    // `paths: ["docs/**"]`) would ship them to the public site.
+    srcExclude: ["superpowers/**"],
+
     // `@btravstack/theme` re-exports VitePress's default theme, which imports
     // `.css`. Externalizing it during SSR makes Node try to `import` those
     // stylesheets and throw `ERR_UNKNOWN_FILE_EXTENSION`. Transform the theme