evalgate list hardcodes the provider names instead of asking the registry

[royalpinto007]

What is wanted

evalgate list should ask the provider registry what is registered instead of printing a hardcoded string.

The problem

src/cli/index.ts, cmdList (lines 236-242):

const scorers = defaultScorerRegistry().list().sort();
console.log("Registered scorers:");
for (const s of scorers) console.log(`  - ${s}`);
console.log("\nRegistered providers: mock, openai, anthropic, groq, openrouter");

The scorer half is derived from the registry. The provider half is a string literal. It happens to be correct right now (it matches the five register calls in defaultRegistry, src/providers/registry.ts lines 54-60), but nothing keeps it correct, and it can never reflect a provider registered at runtime, which is exactly what registryFor does for --degrade (line 60).

The reason it was written this way is that ScorerRegistry has a list() method (src/scorers/registry.ts lines 98-101) and ProviderRegistry does not. ProviderRegistry has register, has, and get, and already reads [...this.factories.keys()] internally at line 37 to build its unknown-provider error message.

Steps

1. Add a list(): string[] method to ProviderRegistry in src/providers/registry.ts, returning [...this.factories.keys()]. Mirror the docstring style of ScorerRegistry.list().
2. Use it in cmdList in src/cli/index.ts so providers print in the same bulleted, sorted form as scorers. cmdList currently takes no arguments; passing the registry built by registryFor(args) would also make evalgate list --degrade honest, though a plain defaultRegistry(process.env) is acceptable if you would rather keep the signature.
3. Optionally simplify line 37 of src/providers/registry.ts to reuse the new list().
4. Add a small test, for example in tests/providers.test.ts, asserting defaultRegistry({}).list() contains all five built-ins and that a register("custom", ...) call shows up.

Self-contained, under an hour. Comment below to claim it; I usually reply within a day.

[pachara-n]

Hi, I’d like to work on this issue. I’ll add ProviderRegistry.list(), update the CLI output, and cover it with tests.

[royalpinto007]

It is yours @pachara-n, welcome, and thanks for saying what you plan to do rather than just claiming it.

Your read is right: ScorerRegistry.list() already exists, so ProviderRegistry should expose the same thing and the CLI should ask instead of carrying a hardcoded string that silently drifts.

Before opening the PR, please run npm run lint, npx tsc --noEmit, and the test suite. Shout here if anything is unclear.

One heads-up: there is a 2-open-claim limit per person across these repos, so others get a turn too.