The audit skill's copyable checklist promised '+ managed settings if present' while check-structure.sh never reads a managed-settings path — the clause was removed in #2018 to stop the false coverage claim, but the coverage gap remains. Managed settings are the highest-precedence layer (validation-categories.md), so omitting them can produce wrong verdicts. Adding coverage needs per-OS managed-settings paths verified against current official docs (fresh-docs mandate).
From the prompting-guide alignment audit (PR #2018, finding V-structural-015).
The audit skill's copyable checklist promised '+ managed settings if present' while check-structure.sh never reads a managed-settings path — the clause was removed in #2018 to stop the false coverage claim, but the coverage gap remains. Managed settings are the highest-precedence layer (validation-categories.md), so omitting them can produce wrong verdicts. Adding coverage needs per-OS managed-settings paths verified against current official docs (fresh-docs mandate).
From the prompting-guide alignment audit (PR #2018, finding V-structural-015).