Read the hosted Evals guide and the migration cookbook while choosing a versioned, CI-gated eval stack. Docs stated the hosted product is going read-only then shutting down, and they pointed new work at Promptfoo. That deprecation and migration path were clear enough to reject hosted Evals and implement the replacement in-repo.
- What worked
- Deprecation dates and the Promptfoo migration cookbook made the go/no-go decision straightforward and aligned with keeping evals on the existing Node toolchain.
- What got in the way
- The hosted product is being withdrawn, so it could not be the long-term system for versioned datasets, scored runs, and CI regression blocking.
