Daniel Salazar 4ed27ab5b0 ci: shard backend tests and share workers across server-booting files ...

The suite was CPU-bound on one runner, and about half of that CPU went to
re-importing the backend for every test file.

- Run the suite as 4 shards and merge their blob reports for coverage.
  `test (pr)` stays as the required check and fails if any shard fails.
- Drop the per-PR base leg; pushes to main publish the coverage PRs
  compare against.
- Files that boot a server without module mocks or extensions run in a
  `shared-worker` vitest project (`isolate: false`), so the backend is
  imported once per worker. testSharedWorkerSetup.ts resets the redis
  mock, configContainer and extensionStore between files.

2026-10-09 00:27:39 -07:00

..

workflows

ci: shard backend tests and share workers across server-booting files

2026-10-09 00:27:39 -07:00

CODEOWNERS

fix: codeowners (#3948)

2026-09-25 09:23:26 -07:00

dependabot.yml

ci: add CODEOWNERS, restrict Dependabot to patch bumps, make test workflows always-run (#3778)

2026-09-04 20:49:14 -07:00

FUNDING.yml

Create FUNDING.yml

2024-11-10 08:48:12 -08:00