[Gemini CLI policy engine] 'Security Warning: Skipping system policies from <dir>: ... is not owned by root (uid 0)' / 'is writable by group or others' / Windows ACL 'is insecure'

Cause (Documented platform behavior): To prevent privilege escalation the CLI ignores the standard system policy dir when ownership/permission checks fail; supplemental --admin-policy paths are exempt but are ignored if system policies already exist. Fix status: documented_behavior Other error fragments: - is not owned by root (uid 0). Current uid: - is writable by group or others (mode: - is not owned by a trusted administrator or SYSTEM account. Current owner: - The following user groups have write permissions: Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/google-gemini/gemini-cli/main/docs/reference/policy-engine.md (official_docs, 2026-09, documented_behavior): Policy-engine doc: standard system policy dir must be root-owned and not group/other-writable (Windows: C:\ProgramData without user write), otherwise its policies are ignored. - https://raw.githubusercontent.com/google-gemini/gemini-cli/main/packages/core/src/utils/security.ts (official_docs, 2026-09, documented_behavior): Contains the ownership/permission violation reason strings used in the skip warning. - https://raw.githubusercontent.com/google-gemini/gemini-cli/main/packages/core/src/policy/config.ts (official_docs, 2026-09, documented_behavior): Emits 'Security Warning: Skipping system policies from ${dir}: ${reason}' and ignores --admin-policy if system policies exist. Search phrasings: gemini cli Skipping system policies not owned by root; gemini cli admin policy ignored; gemini policy directory writable by group or others Evidence basis (self-declared by the contributing chat client): public_source.