Can I vibecode Mem0?

Extend the memory service in this folder with entity links. Requirements:

- On add, have the LLM also return entities (name, type) for each stored fact; keep an entities
  table and a link table to memories, normalising names to lower case with aliases.
- In search, add an entity score: memories sharing an entity with the query get a boost, merged
  into the existing rank fusion with a configurable weight.
- GET /entities lists entities with memory counts; deleting a memory removes orphaned links.
- Extend the eval script with 10 cases that only the entity boost can answer, and print recall
  with and without it.
- Update the README.

Add a consolidation job to the memory service in this folder. Requirements:

- A command `python -m memsvc.consolidate` that, per user, finds memory pairs with cosine
  similarity above 0.92, asks the LLM whether they say the same thing, and merges them into one
  memory while keeping both in the history table.
- Mark memories not returned by any search for 180 days as archived, not deleted, and exclude
  archived ones from search unless asked.
- Print a report of merged, archived and unchanged counts, and support --dry-run.
- Update the README with a cron line and how to restore an archived memory.

Add an importer to the memory service in this folder. Requirements:

- `python -m memsvc.import_json <file>` reads a JSON file that is a list of objects with a
  `memory` or `text` field and optional user_id, agent_id, created_at and metadata.
- Store each item as a memory without calling the extraction LLM, embed it with EMBED_MODEL,
  and keep the original created_at when present.
- Skip exact duplicates, print counts of imported, skipped and failed items, and write failures
  to ./data/import_errors.json.
- Update the README with the expected fields and how to map a custom export schema to them.

Add a dashboard to the memory service in this folder. Requirements:

- A server-rendered page at /admin behind the same bearer token or a password in .env, listing
  memories per user with search, edit and delete.
- Each memory shows its history (adds, updates, deletes with old and new text) and which request
  created it.
- A request log page with the last 500 calls: route, status, duration, and no message bodies.
- Update the README.