[BUG] Gemini CLI: no GEMINI.md created after sync — memory path may be wrong

[FZ2000]

Tool Affected

gemini-cli

What Happened

After apc sync --all --yes with 203 memory entries in cache:

• ~/.gemini/ contains only settings.json
• No GEMINI.md or memory file was created
• apc status shows ● synced

$ find ~/.gemini -type f
/Users/frank/.gemini/settings.json

What Was Expected

The GEMINI_MEMORY_SCHEMA in gemini.py describes writing to a GEMINI.md path. After sync, this file should exist with transformed memory entries.

Root Cause

Memory sync was skipped due to LLM 401 auth error in this test. However, even with a valid LLM, the path needs verification.

Looking at the schema comment: "## Gemini Added Memories" — Gemini CLI's save_memory tool appends facts here. This implies Gemini CLI stores memories in a specific Markdown file — likely ~/.gemini/GEMINI.md or similar.

Concerns

1. Gemini CLI's memory file location may vary by version or OS — hardcoding ~/.gemini/GEMINI.md could be wrong
2. The settings.json format at ~/.gemini/settings.json may be the actual memory location for newer Gemini CLI versions

To Reproduce

1. Install gemini-cli and run gemini to initialize config
2. apc configure with valid Gemini API key
3. apc memory sync --tools gemini-cli --yes
4. Check ls ~/.gemini/ — confirm GEMINI.md was created with correct format

[FZ2000]

📋 Plan (flagged for Ace — needs Gemini CLI research)

Need to verify the actual Gemini CLI memory file path before writing code. The current hardcoded ~/.gemini/GEMINI.md may be wrong for newer versions that use settings.json instead.

Next steps:

1. Inspect actual Gemini CLI source / docs for the memory storage path
2. Confirm whether it's ~/.gemini/GEMINI.md or embedded in settings.json
3. Update gemini.py applier + extractor accordingly
4. Test end-to-end with a valid Gemini API key

Estimated ~2-3hr including research. Flagging for prioritization.

[FZ2000]

Fixed in 7d930c0 (branch fix/bug-patrol-38-39-40-41-43-44-47). See PR for full diff.