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/bundler/bundler_test.go`:
- Around line 2477-2544: The new tests in TestDynamicPathSetFor and
TestDynamicTolerationPathExcludedFromBakeIn use spaces instead of the file’s
tab-based Go formatting, which will fail fmt-check. Reformat the added test
blocks with gofmt (or make tidy) so the indentation matches the surrounding
code, and keep the test logic in place around dynamicPathSetFor,
computeSchedulingPathPolicy, and applyNodeSchedulingOverrides.

In `@pkg/bundler/bundler.go`:
- Around line 1143-1146: The registry-load failure in
applyNodeSchedulingOverrides is being swallowed when
GetComponentRegistryFor(provider) returns an error, which can silently disable
dynamic opt-out behavior. Update the applyNodeSchedulingOverrides path in
bundler.go to keep returning nil on error but also add a slog.Debug log,
matching the existing GetComponentRegistryFor failure handling, so the failure
is visible without changing behavior.
- Around line 1109-1132: Remove the duplicated storage-class injection block in
bundler.go within the component handling logic: the second copy of the
sc/comp.GetStorageClassPaths()/component.ApplyMapOverrides sequence is redundant
and should be deleted, leaving only the original implementation. While editing,
ensure the remaining code in that area uses the existing tab-based Go formatting
so the bundler logic around getValueOverridesForComponent and ApplyMapOverrides
still passes fmt checks.

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/bundler/bundler.go`:
- Around line 228-252: The new filtering loops in bundler.go ignore cancellation
while iterating over recipeResult.ComponentRefs and DeploymentOrder, so add
ctx.Err() checks inside these loops and return early when the context is
canceled, consistent with extractComponentValues. Update the filtering logic in
the bundle-building path to stop processing once Make’s ctx is done, using the
existing ctx passed through the bundling flow and the same cancellation pattern
used elsewhere in the bundle work.
- Around line 238-244: The re-enable path in bundler logic still carries the
recipe-level enabled override into value generation, so a component restored by
`--set <component>:enabled=true` can still render with stale disabled state.
Update the enabled-ref handling in `bundler.go` where refs are added to
`enabledRefs`/`enabledSet` so that `enabled` is stripped from any ref that was
re-enabled before later value extraction, matching the existing cleanup done for
scalar `--set` values.
- Around line 1265-1270: The source-range check in the bundler helper that
iterates over items and calls netutil.IsAnySourceCIDR is treating malformed
CIDRs as scoped, so invalid values like not-a-cidr bypass the warning. Update
that logic to validate each entry first using net.ParseCIDR (or equivalent)
before calling IsAnySourceCIDR, and return false on parse failure; add the net
import if it is not already used. Keep the behavior in the same helper so the
warning is only suppressed for valid non-any source CIDRs.