testing tools

one high level request that i have as we move this forward: i'd like to move away from using ava for testing across the whole org over time. i dont want to block initial work with this request, but it does seem like a new project is a good opportunity to step back and consider how we could improve things like this.

my preference because of the success that i've had elsewhere with it:

• isolated unit tests use vitest. good support for esm, built in stubbing tooling, broad support for IDE integration
• larger scoped tests, like integration and end-to-end, use cucumber. provides a better structure for sharing common setup fixtures across a broader list of test files, easier for non-maintainers to read through and understand the defined expectations

does this seem like a path that could make sense for our future evolution?

Start by reviewing the repository's existing Ava testing setup and usage. Compare the current organization of isolated, integration, and end-to-end tests with the proposed testing split. Done means establishing whether this direction fits the project and defining a concrete follow-up scope.