feat(mem0-agent): read path, hooks, maintenance, CLI and skills

- pack.py: single-call context pack, budgeted, sanitized, cached, with
  served-id tracking that turns a citation into POSITIVE feedback
- assist.py: error-signature lookup (never raw stdout, which returned 0 results in v1)
- maintain.py: transactional consolidation (add merged -> verify -> delete sources)
- transcript.py: JSONL parsing into non-overlapping windows via a cursor
- cli.py: the twelve commands the hooks invoke; detached assist queues a block
  that the next prompt hook drains, keeping the hot path network-free
- hooks generated from one spec; plugin manifest, MCP wiring, five skills

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

integrations/mem0-agent/skills/remember/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: remember
+description: Store something the user explicitly asked to be remembered, verbatim and immediately. Use when the user says remember this, save this, note that, don't forget, or otherwise asks for a fact to be recorded.
+---
+
+# Remember
+
+The user asked for something to be kept. Store it exactly as they said it — this path
+bypasses the extraction gate on purpose, because an explicit request is already a decision
+that the fact matters.
+
+## How
+
+Run:
+
+```bash
+mem0-agent remember --type <type> --text "<the fact, in one self-contained sentence>"
+```
+
+Pick `--type` from the six, by what the fact *is*:
+
+| Type | Use when the fact is |
+|---|---|
+| `preference` | how they want work done (stored at user scope — it follows them across repos) |
+| `decision` | a resolved choice, ideally with the reasoning |
+| `convention` | a project rule not written in the repo |
+| `insight` | a gotcha, constraint, or non-obvious behavior |
+| `runbook` | a procedure verified to work |
+
+## Rules
+
+- **One fact per memory.** Two facts means two calls.
+- **Self-contained.** "Use pnpm here" is useless later; "This repo uses pnpm, never npm"
+  survives on its own.
+- **Say it back.** Confirm what was stored in one short line, with the type.
+- Don't paraphrase away their meaning. Tighten wording, keep intent.
+- If the user's phrasing is a one-off instruction for the current task rather than a
+  standing rule, say so and don't store it.