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/user/cli-reference.md`:
- Line 1201: The documentation incorrectly suggests using the `--set-json` flag
with `aicr bundle` to set `agentgateway:allowedSourceRanges`; remove the
`--set-json` remediation path from the sentence that follows the `agentgateway`
warning and instead only instruct users to scope `allowedSourceRanges` via a
recipe `componentRef` override (keep the reference to `aicr bundle`,
`agentgateway`, and `allowedSourceRanges` so readers know the target and where
to apply the override).

In `@pkg/bundler/bundler.go`:
- Around line 1066-1072: Update the warning message constructed in
warnAgentgatewayOpenExposure to remove the unsupported "--set-json" instruction
and instead direct users only to scope the inference-gateway via a recipe
componentRef override; modify the fmt.Sprintf that uses
agentgatewayComponentName and agentgatewaySourceRangesPath so it no longer
suggests "--set-json %s:%s='[\"<cidr>\"]'" and instead references scoping to
trusted networks via a recipe componentRef override (keeping
agentgatewayComponentName and agentgatewaySourceRangesPath in the message for
context).

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 `@validators/conformance/inference_gateway_check.go`:
- Around line 171-200: assessGatewayExposure currently calls
ctx.Clientset.CoreV1().Services(...).List(ctx.Ctx, ...) with no timeout and
scans svcs.Items without checking ctx.Ctx.Done(); wrap the List call in a
context.WithTimeout using the package timeout (e.g.,
defaults.DefaultRequestTimeout), defer cancel(), and pass that timeout context
to Services(...).List; after obtaining svcs, ensure the scan loop over
svcs.Items selects on ctx.Ctx.Done() (or timeoutCtx.Done()) and returns early
with ctx.Ctx.Err() (wrapped as appropriate) if cancelled, so the operation is
bounded and respects cancellation.

In `@validators/conformance/inference_gateway_exposure_test.go`:
- Around line 127-133: The empty-env subtest is not hermetic because envTruthy
reads os.Getenv and the code only calls t.Setenv for non-empty tt.val; always
set the env var for every test case (including the empty string) so each subtest
controls AICR_TEST_ENV_TRUTHY deterministically. Locate the table-driven loop
and the subtest body that currently does `if tt.val != "" {
t.Setenv("AICR_TEST_ENV_TRUTHY", tt.val) }` and replace it by unconditionally
calling `t.Setenv("AICR_TEST_ENV_TRUTHY", tt.val)` before invoking envTruthy to
ensure isolation.

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

Outside diff comments:
In `@validators/conformance/inference_gateway_exposure_test.go`:
- Around line 92-94: The test is non-hermetic because it only sets
requireScopedGatewayEnv when tt.requireScoped is true; always set the env var so
the subtest can't inherit parent state: inside the subtest block that currently
checks tt.requireScoped, replace the conditional with a
t.Setenv(requireScopedGatewayEnv, "true") when tt.requireScoped is true and
t.Setenv(requireScopedGatewayEnv, "") when false (same pattern used in
TestEnvTruthy), ensuring the env var is explicitly set for both branches so
envTruthy sees a controlled value.

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 `@validators/conformance/inference_gateway_check.go`:
- Around line 193-225: The code only treats an empty
svc.Spec.LoadBalancerSourceRanges as "open" but must also treat an explicit
"0.0.0.0/0" entry as open; update the logic where openSvcs is populated (the
block referencing svc.Spec.LoadBalancerSourceRanges and openSvcs) to append
svc.Name when either the slice is empty OR any element equals "0.0.0.0/0" (and
optionally "::/0" if you want IPv6 coverage), keep the summary output for
sourceRanges as-is (showing "<empty>" for empty and joined values otherwise),
and ensure the existing failure path that constructs msg and checks
envTruthy(requireScopedGatewayEnv) still triggers for these newly-detected open
services so the guardrail isn't bypassed.

In `@validators/conformance/inference_gateway_exposure_test.go`:
- Around line 92-94: Tests conditionally set the environment variable using
t.Setenv only when tt.requireScoped is true, which leaves ambient
AICR_REQUIRE_SCOPED_INFERENCE_GATEWAY values affecting the false cases; make the
setup hermetic by calling t.Setenv(requireScopedGatewayEnv,
strconv.FormatBool(tt.requireScoped)) (or equivalent) for every subtest so each
case explicitly sets the env var based on tt.requireScoped; update the subtest
setup where t.Setenv and tt.requireScoped are used to always set
requireScopedGatewayEnv rather than only on true.