Constant FLUX_GITREPOSITORY_KEY_URL 

pub const FLUX_GITREPOSITORY_KEY_URL: &str = "url";

Canonical Flux v2 GitRepository.spec.url per-CR remote-repo-URL leaf-scalar-axis key every caixa-flux-rendered gitrepository.yaml document declares. The FluxCD source-controller reads spec.url as the git remote URL it clones per-reconcile — the authoritative remote the per-Servico artifact archive is sourced from at every reconcile cycle. A drifted key (e.g. "URL", "gitUrl", "repo", "repository") at the writer site would silently emit a GitRepository whose CRD schema validator drops the URL field as unknown, and the per-Servico artifact would never populate — the downstream HelmRelease.spec.chart.spec.sourceRef reference dangles with an empty artifact at admission, every rendered HelmRelease / Kustomization bundle document downstream silently no-ops at reconcile time with no field naming the URL-key-drift root cause.

Sibling to the already-lifted per-GitRepository-CR spec sub- block keys FLUX_GITREPOSITORY_KEY_REF (84a3c20, the parent container-axis for the spec.ref.{tag,branch,commit} per-shape arm discriminated union) — this constant names the peer per-CR leaf- scalar remote-URL axis on the same top-level spec position. Both axes together completely enumerate the GitRepository.spec.* per- CR sub-block keys caixa-flux’s current cluster_bundle gitrepo template writes (spec.interval reaches through the lifted FLUX_KEY_INTERVAL, spec.url through this constant, spec.ref through FLUX_GITREPOSITORY_KEY_REF), so any future Flux v3 GitRepository schema promotion lands as one caixa-core edit coordinated across the sibling sub-block key axes.

The single source of truth every Flux-v2-per-GitRepository- spec.url-leaf-scalar-axis-naming reaches for — one production consumer today:

• the rendered gitrepository.yaml document’s per-GitRepository spec.url leaf-scalar remote-URL axis (caixa-flux’s cluster_bundle gitrepo template composer’s url: sub-key — the sole production emission site the prior inline "url:" literal sat at).

Every future per-GitRepository renderer (the M4 typed-Aplicacao materializer’s per-Aplicacao GitRepository synthesis for per-aggregator-manifest sources, any future caixa-otel collector-pipeline GitRepository, any future per-cluster snapshot GitRepository the operator emits) inherits the canonical URL leaf-scalar key by construction with no opportunity for per-renderer drift.