Memory never writes the wiki or the diary on a fresh install #148

Summary

On a first ./stack up memory the brain projection is never cloned, and the curator waits for it forever. No wiki page is regenerated and no diary is compiled. The step reports success.

Steps to reproduce

1. Fresh install, then ./stack up docs, ./stack up code, ./stack up memory.
2. Read the up memory output.
3. docker logs stack-memory-curator.

Expected behaviour

Memory: cloned brain projection to ~/famstack-data/memory/brain, and a curator that keeps the vault in sync (admin guide § Memory).

Actual behaviour

✓ Memory brain projection clone failed at /Users/<you>/famstack-data/memory/brain (a failure with a success mark), then the curator logs waiting for brain projection at /data/memory/brain indefinitely. brain/ holds media/ and family/diary/about.md but no .git.

Environment

./stack version 0.3.0-beta.3-150-g1678e2f (main), macOS 15.5, M4 16 GB, OrbStack, port mode. AI via ./stack ai connect to an OpenAI-compatible server on the LAN.

Cause

stacklets/memory/hooks/on_start.py creates <brain>/media (the wiki's media mountpoint, added in #92, 03e1708) before on_start_ready clones family/brain, and family/diary/about.md is also written there first. git clone refuses a non-empty directory. Not in v0.3.0-beta.3. The install e2e lane never brings up memory, so CI does not cover it.

Definition of done

• A test brings up memory from nothing and finds a git working copy of family/brain with media/ excluded, and a curator past "waiting for brain projection".
• A failed clone is reported as a failure, not with ✓.
• An install that already hit this recovers on the next ./stack up memory without manual steps.