From lion's #5361 review: formatMemoriesForPrime called
ensureStoreActiveForPrime with no proxied gate — the bd-m7zzd direct-store
seam class, in a read-only limb. prime sits in noDbCommands, so no UOW
provider was ever opened; the lazy direct open then hit the store factory's
proxied refusal and the silent-skip contract swallowed it, meaning proxied
prime never carried memories at all.
The memory read now routes through the proxied plane (routing chosen over
skipping — the surface exists: ConfigUseCase().GetAllConfig on one
read-only UOW, same verb as the bd memories proxied dual), via a provider
opened scoped to the read and closed after. Prime's contracts are
preserved: silent skip when the plane is unavailable, the timeout banner on
a deadline, and memories rendered through a tail now shared with the
classic path (renderPrimeMemoriesFromAllConfig) so the two cannot drift.
Tests: TestProxiedServerPrime journey suite on the shared testcontainers
harness — memories-only and full prime carry the remembered key/content
(red before this fix: proxied prime printed 'No memories stored'), the read
lands zero Dolt commits, no embedded store dir materializes, and a corrupt
sidecar degrades to exit-0 silent skip. Shard manifest entry added at the
hash-fallback shard (6).
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>