Constant HELM_CHART_DEPENDENCY_KEY_REPOSITORY 

pub const HELM_CHART_DEPENDENCY_KEY_REPOSITORY: &str = "repository";

Canonical Helm 3 Chart.yaml per-dependencies[]-entry sub-mapping YAML axis-key naming the per-dep chart-registry URL field — the load-bearing serde field-name at caixa-helm’s ChartDependency struct’s repository field. The chart-schema per-dep entry’s repository: value pins the Helm-registry URL (file://…, https://…, oci://…) Helm’s per-dep resolver consults at helm dependency build time to fetch the per-dep chart bytes. At the caixa-helm substrate the default value is the canonical [caixa_helm::DEFAULT_LIBRARY_REPO] pointing at the helmworks file:// path; the future per-edition library-chart re-emission for the OCI registry (once pleme-io/helmworks/charts lands as an OCI-registry-backed chart-source) reaches this axis through a paired scalar-value lift on the per-dep repo axis. A drift on this per-dep sub-key would surface as one of two silent failure modes at chart-vendor time far from the drift site: Helm’s per-dep resolver silently drops the repository scalar from the parsed dep-entry (the per-dep resolver falls back to the “no repository set” shape and refuses to vendor the dep with no repository defined), or the per-dep chart-schema parser silently absorbs a rename drift via #[serde(default)] fall-through at the struct-side and the per-dep repo axis lands under Rust’s "" default — Helm rejects the empty URL at helm dependency build time. Peer to HELM_CHART_DEPENDENCY_KEY_NAME / HELM_CHART_DEPENDENCY_KEY_VERSION / HELM_CHART_DEPENDENCY_KEY_ALIAS on the sibling per-dep sub-key axes. See HELM_CHART_DEPENDENCY_KEY_NAME for the shared per-entry-sub-mapping lift rationale.