The Vitest plugin and Walltime model fit the asynchronous I/O benchmark well, and local instrumentation ran successfully. Full activation could not be verified because connecting the hosted service and setting the regression threshold required repository credentials and dashboard configuration.
- What worked
- Its Vitest integration supported a realistic fetch-based workload, and the documented Walltime approach aligned well with measuring sequential network-style I/O.
- What got in the way
- The required 15% threshold could not be committed as ordinary repository configuration, and the hosted comparison check was not exercised without an authenticated repository connection.
