fix(cli): prime build extension contracts

[kojiwakayama]

Summary

Related to veryfront/veryfront-issue-inbox#456: "veryfront build fails for every project since 0.1.1206: build path is the only orchestrateExtensions caller that omits primeContracts". The inbox issue identifies 0.1.1206 as first bad, introduced by 59fe62c / PR #3417, with all local veryfront build runs affected.

This fixes the build-only extension orchestration path by priming the same host-owned registries that dev/serve and eval already seed:

• LLMProviderRegistry for the built-in OpenAI, Anthropic, and Google LLM extensions.
• EvalReportExporterRegistry for the built-in MLflow eval report extension.

The extensions were present and activated. The missing part was the build caller's host registry contract setup, not an optional install.

Root cause

cli/shared/build-extensions.ts was the only orchestrateExtensions caller that activated built-in LLM and eval extensions without primeContracts. Those extensions correctly fail closed when their required registries are neither provided by another extension nor primed by the host.

TDD

• Red: added a regression test in cli/shared/build-extensions.test.ts that asserts setupBuildCliExtensions primes both required contracts.
• Green: setupBuildCliExtensions now passes fresh LLMProviderRegistry and EvalReportExporterRegistry instances into orchestration.
• Refactor: kept the change scoped to the build extension setup and its colocated test.

Verification

• deno test --preload=src/testing/preload.ts --no-check --allow-all cli/shared/build-extensions.test.ts passed after transplant onto origin/main (6 steps).
• Focused 30-step regression suite passed during the TDD reproduction/fix cycle.
• git diff --check passed.
• deno task fmt:check passed.
• deno task lint passed.
• deno check cli/shared/build-extensions.ts cli/shared/build-extensions.test.ts passed.
• deno task build:npm passed during the TDD reproduction/fix cycle.
• Fresh packed-npm consumer build passed during the TDD reproduction/fix cycle.

Summary by CodeRabbit

• Bug Fixes

  • Improved build extension setup by ensuring required language model and evaluation reporting capabilities are available during orchestration.

• Tests

  • Added coverage confirming both capabilities are initialized before build orchestration begins.

[coderabbitai]

📝 Walkthrough

Walkthrough

setupBuildCliExtensions now primes the LLM provider and evaluation report exporter registries before orchestration. Tests verify that both contracts are available.

Changes

Build extension contracts

Layer / File(s)	Summary
Registry priming and validation cli/shared/build-extensions.ts, cli/shared/build-extensions.test.ts	setupBuildCliExtensions initializes both registries through primeContracts. Tests verify that both contracts are provided.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• veryfront/veryfront-code#3413: Introduced setupBuildCliExtensions, which this change extends with registry priming.

Suggested reviewers: kwakayama

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: priming build extension contracts in the CLI.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/build-extension-contracts

---

_{Comment @coderabbitai help to get the list of available commands.}