Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/integrator/validator-extension.md`:
- Around line 109-112: Replace the deterministic language in the sentence
discussing the `preferred` vs `required` scheduling behavior: change claims like
"dominates the scheduler's image-locality scoring" and "after which image
locality reinforces (rather than counteracts) the affinity" to softer,
observation-based phrasing such as "has a strong influence on the scheduler's
image-locality scoring on the first run" and "afterward image locality can
support (rather than oppose) the affinity" so the doc describes likely behavior
instead of a guaranteed internal precedence; keep the guidance to prefer
`preferred` and reserve `required` for cases that cannot succeed without exact
co-location.

In `@pkg/api/validator/v1/affinity.go`:
- Around line 69-72: The current block that calls dep.Validate() (inside the
validation for dependency affinity) re-wraps the error using errors.Wrap which
double-wraps an already-coded pkg/errors error; replace the errors.Wrap usage
with errors.PropagateOrWrap(err, errors.ErrCodeInvalidRequest, "invalid
dependencyAffinity") so that DependencyAffinity.Validate() structured errors are
propagated unchanged while non-coded errors get wrapped with
ErrCodeInvalidRequest and the "invalid dependencyAffinity" message.

In `@pkg/validator/catalog/catalog.go`:
- Around line 279-282: The current code double-wraps structured errors from
DependencyAffinity.Validate(); change the return logic in the loop where
dep.Validate() is called (referencing dep.Validate(), v.Name and
dependencyAffinity[j]) to use errors.PropagateOrWrap(err,
errors.ErrCodeInvalidRequest, fmt.Sprintf("validator %q:
dependencyAffinity[%d]", v.Name, j)) instead of errors.Wrap so that
already-coded *errors.StructuredError values from DependencyAffinity.Validate()
are propagated unchanged and non-structured errors get wrapped with the
contextual message.

In `@pkg/validator/validator.go`:
- Around line 287-292: Add a context cancellation check inside the pre-flight
loop that iterates over entries: before calling
v1.BuildOrchestratorAffinity(entry.DependencyAffinity,
validationInput.GetComponentRefs()), select on ctx.Done() and return immediately
with the context error (wrapped appropriately) so the validator stops promptly
when canceled; update the loop that uses variables entries/entry and the
surrounding function to return early on ctx cancellation rather than continuing
work.
- Around line 288-291: The current dependency-affinity pre-flight double-wraps
structured errors returned from v1.BuildOrchestratorAffinity; instead check the
returned err and use errors.PropagateOrWrap(err, errors.ErrCodeInvalidRequest,
fmt.Sprintf("dependencyAffinity pre-flight failed for validator %q",
entry.Name)) so already-coded errors are preserved and uncoded ones get wrapped
with ErrCodeInvalidRequest and the same message; update the error handling
around v1.BuildOrchestratorAffinity accordingly.

In `@recipes/validators/catalog.yaml`:
- Around line 110-118: The comment incorrectly states this is “Required for
determinism” while the configuration uses dependencyAffinity with requirement:
preferred; update the comment text near dependencyAffinity / componentRef:
kube-prometheus-stack / podLabelSelector: app.kubernetes.io/name: prometheus to
indicate this is a best-effort/preferred co-location (not guaranteed), e.g.,
replace “Required for determinism” with wording that reflects
preferred/best-effort behavior so the comment matches the configured
requirement: preferred.

---

Outside diff comments:
In `@pkg/api/validator/v1/README.md`:
- Around line 322-336: The README's Plan(...) parameter list is missing
descriptions for imageRegistryOverride, imageTagOverride, and componentRefs;
update the API reference for the Plan(cat, validationInput, runID, namespace,
version, commit, serviceAccount, imagePullSecrets, tolerations, nodeSelector,
imageRegistryOverride, imageTagOverride, componentRefs) signature by adding
three brief bullet entries: explain imageRegistryOverride as an optional
registry host to override container image pull locations, imageTagOverride as an
optional tag to override validator image tags, and componentRefs as a list/map
of component identifiers (or image references) to pass to validators for
targeted behavior; ensure wording matches the existing style and placement with
the other parameters.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@pkg/api/validator/v1/README.md`:
- Line 337: Update the README description for imageTagOverride (aka
AICR_VALIDATOR_IMAGE_TAG) to clarify it only replaces tags on tag-based image
references and does NOT modify digest-pinned references (the image rewrite logic
preserves digest-pinned refs); keep the note that an empty string disables the
override and ensure the wording explicitly states "tag-based references only"
rather than suggesting digest-pinned refs are affected.