Evidence record / gemini-cli

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the signals and issues that cite it, below.

Policy File Resilience: EBUSY Fallback and TOML Recovery

What Changed

Enhanced policy file persistence with EBUSY/EXDEV fallback mechanism and TOML parse recovery. When atomic rename fails on certain mount configs, falls back to copy-then-unlink. If policy file becomes corrupted with syntax errors, automatically backs up malformed file with .bak extension and recovers from scratch.

Operator Implication

Prevents policy update failures in cross-device mount scenarios common in containerized environments. Automatic corrupted file recovery eliminates manual intervention for syntax errors. Improves resilience of configuration persistence layer.

Receipt

Commit title: ‘fix(policy): add EBUSY fallback and TOML parse recovery (#19919) (#21541)’ with 51 additions and 8 deletions to packages/core/src/policy/config.t

Finding metadata

Confidence: high
Actionability: observe
Accessibility impact: none

Run: 2026-06-03-weekly-digest-2026-05-28_2026-06-03-frontier-v0

Finding ID: 2026-06-03-gemini-cli-policy-resilience

Accepted signals

Policy file survives cross-device mounts and corruption via EBUSY fallback and TOML recovery / 2026-06-03

Source links

Primary links, including exact changelog lines when available.

Gemini CLI
commitCommit title: 'fix(policy): add EBUSY fallback and TOML parse recovery (#19919) (#21541)' with 51 additions and 8 deletions to packages/core/src/policy/config.ts plus comprehensive test coverage in pegithub.com/google-gemini/gemini-cli/commit/dceb2ea30650c3f6742e67ec71110857904e78b3

Versioned source: run artifact