feat(sdk/go, control-plane): Add Vector Memory Ops

[SwekeR-463]

Summary

This PR implements comprehensive support for vector memory operations in the Go SDK and the Control Plane. It introduces Set, Get, Search, and Delete operations for vector embeddings, enabling agents to manage semantic memory effectively. The Control Plane API has been updated with new RESTful endpoints while maintaining backward compatibility for existing clients.

Changes

1. Go SDK (sdk/go/agent)

Interface Update

• Extended the MemoryBackend interface to include the following vector operations:
  • SetVector
  • GetVector
  • SearchVector
  • DeleteVector

Memory Client

• Updated the Memory struct to expose high-level vector methods.
• Added a chainable scoping method:
  • Scoped(scope, scopeID) for explicit and composable scoping.

Backends

• InMemoryBackend
  • Implemented vector operations for local development and testing.
• ControlPlaneMemoryBackend
  • Implemented vector operations via communication with the Control Plane API.

---

2. Control Plane (control-plane)

Storage Layer

• Added GetVector to the following interfaces:
  • StorageProvider
  • vectorStore
• Implemented vector retrieval in:
  • sqliteVectorStore
  • postgresVectorStore
• Exposed GetVector through LocalStorage.

Handlers

• Added GetVectorHandler to retrieve vector records by key.
• Updated DeleteVectorHandler to support RESTful path parameters
  (e.g. DELETE /.../:key).

---

3. Routes (internal/server/server.go)

New RESTful Endpoints

• POST /api/v1/memory/vector — Set
• GET /api/v1/memory/vector/:key — Get
• POST /api/v1/memory/vector/search — Search
• DELETE /api/v1/memory/vector/:key — Delete

Backward Compatibility

• Preserved existing POST-based endpoints
  (e.g. /memory/vector/set) to avoid breaking changes.

Testing

• ./scripts/test-all.sh
• Additional verification (please describe):

Checklist

• I updated documentation where applicable.
• I added or updated tests (or none were needed).
• I updated CHANGELOG.md (or this change does not warrant a changelog entry).

Screenshots (if UI-related)

Related issues

Fixes #94

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 3 committers have signed the CLA.

✅ SwekeR-463
✅ AbirAbbas
❌ github-actions[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[santoshkumarradha]

@AbirAbbas needs update to our doc post merge 🚀