Settings validation now warns when policy helper keys are nested where nothing reads them.
What's wrong with this entry?
Settings validation now flags helper-shaped and payload-shaped keys that were put in a slot that does not read them, and each warning says the nested config will not apply from there.
- Covers cases like
defaultSettingsplaced on the singularpolicyHelperkey, per-OS keys placed inside a single entry, andclaudeMdplaced on the helper key. - These are status warnings only; they do not block startup.
"policyHelper" and "policyHelpers" are TOP-LEVEL settings keys; nothing nests inside the singular entry. The nested config will NOT apply from here.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.228
Managed settings accept per-OS
policyHelpersBoth mention policy helper managed
-
v2.1.228
New
policyHelpersmanaged-settings key for per-OS policy helper executablesBoth mention policy helper managed
-
v2.1.235
Policy helpers can be delivered by remote managed settings, after explicit approval
Both mention policy helper managed