feat(api): namespace management — move, rename/merge, delete with strategy (#1181)

[ajianaz]

What

Namespace management across all surfaces (#1181) — namespaces are a derived view over the memories.namespace column, and this adds the sanctioned operations the issue proposed (additive, non-breaking):

• Core: Uteke::move_memory(id, ns) (plain column update, no re-embed — embeddings are content-based), Uteke::rename_namespace(from, to) (single atomic UPDATE; existing target = merge, returns {from, to, moved, target_existed}), Uteke::delete_namespace(name, strategy, target) with explicit memory-fate strategies: refuse (default — validation error while any memory incl. deprecated references the name), merge (move all memories to target, the name vanishes naturally), deprecate (soft-delete via the feat: deprecate_with_reason() + promote() + Store undeprecate #929 lifecycle — restorable via promote, never hard-deleted). Shared name validation (non-empty, ≤128 chars), recall-cache invalidation for old+new namespaces, vector-index removal on deprecate.
• Server: PUT /memory accepts optional namespace; new POST /namespaces/rename and POST /namespaces/delete (refuse → 409 Conflict, other validation → 400); GET /namespaces?with_counts=true now returns additive active/deprecated fields while count stays the total (deprecated-only ghost namespaces become visible for what they are).
• CLI: uteke namespace move|rename|delete — delete requires --confirm (same guard as the destructive-command convention).
• MCP: uteke_namespace_rename, uteke_namespace_delete, and a namespace field on uteke_update.
• Docs: docs/api-reference.md regenerated via docgen; docs/cli-reference.md namespace section updated; CHANGELOG under [Unreleased] → Added.

Why

#1181: agents (or humans) writing to a typo'd namespace had no sanctioned fix path — the name only disappeared when its last memory was manually moved, and listings could not distinguish active from deprecated-only namespaces. The design keeps the derived-view model (no new tables, no schema change) and follows the soft-delete lifecycle philosophy: there is deliberately no hard-delete path.

Testing

• Core (3 new tests, operations.rs): move updates namespace + old name vanishes from listings + unknown ID → Ok(false); rename moves all memories, merge reports target_existed, same-name/unknown-source rejected; all three delete strategies — refuse blocks non-empty, merge relocates and removes the name, deprecate soft-deletes without data loss (memory stays stored, deprecated = true, lifecycle counts show 0 active / N deprecated), unknown strategy rejected.
• Server (5 new tests, router-level with tiny_http::TestRequest, embedder-free): PUT /memory namespace move verified via GET /memory + listings; rename/merge endpoint contract (moved, target_existed); refuse → 409 with "refus*" message; merge delete removes namespace from listings; with_counts=true lifecycle split (0 active / 1 deprecated / count 1).
• cargo fmt --all ✓ · cargo clippy --workspace --all-targets -- -D warnings ✓ · cargo test --workspace ✓ (0 failures) · cora review --staged ✓ (No issues found) · docgen regenerated (freshness check will verify).

[github-actions]

🔍 Cora AI Code Review

✅ No issues found. Code looks good!

---

Review powered by cora-code · BYOK · MIT