chore(deps): memory-core 0.3.2 - commit lock-retry

[vreshch]

What

Bump @agentage/memory-core ^0.3.1 -> ^0.3.2 to pick up the LocalBackend
commit lock-retry (memory-core#19/#20): a transient git commit failed under a
concurrent write + sync storm is now retried inside the engine, so the daemon's
directly-spawned sync git no longer races the engine's commit into a spurious
failure.

Scope

Targeted bump only. The lock diff touches only @agentage/memory-core:

• package.json: ^0.3.1 -> ^0.3.2
• package-lock.json root dep + node_modules/@agentage/memory-core: 0.3.1 -> 0.3.2
• nested @agentage/memory-core@0.1.3 under @agentage/server-memory (pinned ^0.1.3) is unchanged

No other packages moved; the runtime dep set is identical (package-guard green).

Verify

• npm run verify green - 337 tests pass, build clean.
• Full offline e2e set green (47 tests), including the @couch hermetic docker
  tier: daemon m1-requirements mcp-daemon mcp-stdio memory-offline sync vault-offline integrity mcp-contract account-vault couch-sync.

Note - concurrency assertion deliberately not added

Considered tightening integrity/couch to assert zero transient
git commit/sync failed errors under a write+sync storm. Skipped it: it's a
negative, timing-dependent assertion whose real risk is a false RED (the
lock-retry is bounded; contended runners could exhaust it), and transient sync
errors are "recorded, not crashed" so surfacing them deterministically at the
e2e level is indirect/vacuous. The existing integrity tests already lock the
structural invariants the fix protects (clean tree, no index.lock, fsck
clean under 10/30 concurrent ops) and couch-sync exercises concurrent
write+sync convergence - all green on 0.3.2. Kept this a clean one-line bump.

[github-actions]

🎉 PR Validation ✅ PASSED

Commit: b743a5c360e170d7edbab194a3844e28e0cdedb6
Branch: chore/bump-memory-core-0.3.2

Checks:

• ✅ Release guard (no version/changelog changes)
• ✅ Dependencies installed
• ✅ Type check passed
• ✅ Linting passed
• ✅ Format check passed
• ✅ Tests + coverage passed
• ✅ Build successful

Ready to merge! ✨

---

🔗 View workflow run
⏰ Generated at: 2026-07-06T22:15:56.076Z