opm/

Package cueenv builds the environment slice a cue/load or mod/modconfig call consults when the caller wants to override CUE_REGISTRY or CUE_CACHE_DIR for that one operation.

Package loader is the kernel's one artifact-loading routine: it builds a single CUE package — from a directory or from an in-memory overlay — and runs the OPM artifact shape gate over the result, and it fetches a published #Module from an OCI registry through CUE's native module machinery.

Package registrytest provides an in-memory OCI registry harness for tests that need catalogs and modules resolvable by import without a live registry.

Package renderstage assembles the single-build render module (enhancement 0019 D9): it reads the two committed cue.mod/module.cue resolutions the render inputs carry, promotes them into the render module's dependency list (D13), checks that list for OPM-namespace coverage (the D13 refusal invariant), compares the two committed lists for catalog version skew (D7/D18), stages the generated render module into a directory, and builds it once in a caller-supplied cue.Context (D8).

Package schematest is a test-only helper for pointing tests at the workspace-local CUE module cache, and for handing a test a CUE module cache directory to build in.

Package sourcetree walks, reads, names and writes the source tree a module.Source describes, in both of its modes: on-disk (Overlay nil, the tree is read from Root on the filesystem) and overlay (every file is an entry of Overlay, its bytes keyed by its absolute path under Root).

Package synth builds an OPM #ModuleInstance CUE value from typed in-memory inputs: caller-supplied identity (name, namespace, values, labels, annotations) against a module the caller already acquired with its staged source.

Package valuesfile renders a values cue.Value as the source of a package file declaring the top-level `values` field.