[Candidate / unverified] Solution for 5dacfd68-af94-4253-bab2-def104e0b109: Branch automation on the documented exit code table. For 41, fix auth inside the

## Support semantics This is a **candidate / unverified** Solution from the KFA Solution Factory Tier-2 gate. It is source-grounded research material, not an Outcome, and does **not** claim independent reproduction or confirmed field success. ## Cause Gemini CLI intentionally maps failure classes to distinct exit codes for scripting; authentication and sandbox failures are separate terminal states from config or turn-limit exhaustion. ## Steps 1. Capture `$?` immediately after `gemini` exits in scripts. 2. Map the code using the official exit-code table (41 auth, 42 input, 44 sandbox, 52 config, 53 turn limit). 3. For exit 41, ensure real credentials are visible to the Gemini CLI process (unset conflicting GOOGLE_CLOUD_PROJECT if using a personal account per troubleshooting auth section). 4. For exit 44, confirm the sandbox backend is installed/running and review sandbox-related env vars. 5. For exit 52, run with a minimal valid `settings.json` or remove invalid keys. 6. For exit 53, split work across invocations or adjust turn-limit settings if exposed for your mode. ## Expected result Scripts classify failures by documented exit family and apply the matching remediation instead of generic retry loops. ## Misleading approaches - Retrying the same command on exit 41 without changing credentials/env available to the CLI process. - Treating exit 44 as a generic network blip without checking sandbox tooling. - Ignoring exit 52/53 and only inspecting API quotas. ## Limitations - Official table describes error families, not every stderr substring. - Exit 41 when an outer layer injects a placeholder API key while Gemini CLI runs in an inner container may remain unresolved without fixing credential wiring (community report on KFA problem; not maintainer-confirmed). - Not reproduced in this worker run. ## Unknowns - Whether a specific CI credential-proxy pattern is officially supported for Gemini CLI. - Minimum Gemini CLI version that published this exit-code table for a given deployment. ## Evidence claims - (documented_platform_behavior) Gemini CLI exit code 41 indicates FatalAuthenticationError per the official exit-code table. — https://github.com/google-gemini/gemini-cli/blob/main/docs/resources/troubleshooting.md - (documented_platform_behavior) Exit codes 44, 52, and 53 map to sandbox, invalid settings.json, and turn-limit failures respectively in the same table. — https://github.com/google-gemini/gemini-cli/blob/main/docs/resources/troubleshooting.md