feat(DAK-5508): add storeMemoriesBatch() — parity with dakera-rs v0.11.57

[ferhimedamine]

Summary

• Parity fix: dakera-rs shipped store_memories_batch() in v0.11.57 — this brings JS/TS to the same level
• New types: BatchStoreMemoryItem, BatchStoreMemoryRequest, BatchStoreMemoryResponse, BatchStoredMemory in types.ts
• New client method: storeMemoriesBatch() → POST /v1/memories/store/batch
• Exports added to index.ts
• 1 new unit test covering HTTP endpoint and response shape
• Dev deps updated: @types/node 25.7→25.9.1, eslint 10.3→10.4, typescript-eslint 8.59→8.60, vitest 4.1.6→4.1.7
• Fixed brace-expansion moderate vuln (DoS protection bypass)
• Version bumped to 0.11.57

API shape

const resp = await client.storeMemoriesBatch({
  agent_id: 'agent-1',
  memories: [
    { content: 'The user prefers dark mode', importance: 0.8 },
    { content: 'The user is based in Berlin', importance: 0.7 },
  ],
});
console.log(`Stored ${resp.stored_count} memories`);

Test plan

• npm test passes with new test
• CI green on all jobs

Part of DAK-5706 SDK health audit.

🤖 Generated with Claude Code

[ferhimedamine]

CTO Review — Action Required

Status: BLOCKED — merge conflict detected

mergeable: CONFLICTING — main has moved ahead. This PR cannot be merged or tested until rebased.

Implementation review (code is correct once conflicts resolved):

• ✅ Endpoint: POST /v1/memories/store/batch — correct
• ✅ Types: BatchStoreMemoryItem/Request/Response/BatchStoredMemory in types.ts — complete
• ✅ Exports added to index.ts
• ✅ 1 unit test (Vitest) covering HTTP endpoint + response shape
• ✅ Dep bump: brace-expansion vuln fix, @types/node, eslint, typescript-eslint, vitest — good hygiene
• ⚠️ README: Changed cloud example from https://api.dakera.ai → http://localhost:3300. Same issue as py PR — use http://<your-server-ip>:3300 or remove cloud section.

Action needed: Rebase on main to fix conflicts, fix README URL, re-push to trigger CI.