Summary

Migrate pkg/cli and pkg/api/server.go from constructing recipe.Builder / bundler.Bundler / validator.Validator directly to consuming the github.com/NVIDIA/aicr facade landed in #1072.

Motivation

After #1072 lands the facade, the repository carries three independent wiring paths:

Every change to wiring policy (new constructor option, new pre-flight, new lifecycle hook) has to be applied in all three places. Per CLAUDE.md — "business logic lives in functional packages so CLI and API can both use it" — the facade should be the single aggregation point; CLI and REST become thin presentation layers over aicr.Client.

CLI is also still on the deprecated global-state path; migrating onto aicr.Client retires it.

Acceptance

• pkg/cli/root.go no longer calls recipe.SetDataProvider; bootstraps an aicr.Client per command invocation.
• pkg/api/server.go constructs aicr.Client instances (one per recipe-source configuration), not recipe.Builder / bundler.Bundler directly.
• All existing CLI flags and REST endpoints behave identically (chainsaw e2e + make qualify clean).
• If the facade lacks a knob the CLI/REST need, extend the facade rather than reaching past it; document any such extensions.

Out of scope

• Removing pkg/recipe's SetDataProvider / GetDataProvider — that's feat(recipe): deprecate SetDataProvider / GetDataProvider globals #987.
• Wrapping the facade's alias types — separate child of [Epic]: Post-facade adoption and surface hardening (follow-ups to #1072) #1076.

Related

• [Epic]: Post-facade adoption and surface hardening (follow-ups to #1072) #1076 (epic)
• feat(aicr): top-level Go library facade for in-process consumers #1072 (the facade PR)
• feat(recipe): deprecate SetDataProvider / GetDataProvider globals #987 (sibling: deprecates the globals; this issue removes the last in-tree caller)