feature(UI): Delete memories from Cloud UI dashboard #681

[Dharmikas]

🔗 Linked Issue

Closes #681

---

🏷️ PR Type

• type:bug — Bug fix
• type:feature — New feature
• type:docs — Documentation only
• type:refactor — Code refactoring
• type:chore — Maintenance, dependencies, tooling
• type:breaking-change — Breaking change

---

📝 Summary

• Adds the ability to delete memories directly from the Cloud UI dashboard.
• Makes memory cleanup faster and avoids requiring CLI commands.

📂 Changes

Area	Change
Cloud UI dashboard	Added a delete action for memories
Memory management	Connected the dashboard action to memory deletion

🧪 Test Plan

• Unit tests pass locally: go test ./...
• E2E tests pass locally: go test -tags e2e ./internal/server/...
• Manually verified deleting a memory from the Cloud UI dashboard

🤖 Automated Checks

All repository checks must pass before merge.

✅ Contributor Checklist

• I linked issue 681 with Closes #681
• I added the type:feature label to this PR
• I ran unit tests locally
• I ran E2E tests locally
• Docs updated if needed
• Commits follow conventional commit format
• No Co-Authored-By trailers in commits

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[dnlrsls]

Closing this PR because #681 is still awaiting design approval, and the maintainer discussion correctly identified this implementation as premature while deletion, authorization, and sync semantics remain unsettled. The current head is also a large conflicting draft.

Please keep the product and safety contract on #681. If that design is approved later, the implementation should restart as a focused change against current main.