fix: correct context_type classification for memories during reindex

[muxiaomu001]

Summary

Fixes #1060

When reindexing via /api/v1/content/reindex, all memories under viking://user/*/memories/* and viking://agent/*/memories/* are incorrectly classified as context_type="resource" instead of "memory". This causes downstream consumers (e.g. OpenClaw's auto-recall plugin) that filter by context_type == "memory" to miss all reindexed memories.

Root Cause

Two bugs in the reindex code path:

Bug 1: summarizer.py — wrong URI prefix check

# Before (never matches — no URI uses this path)
if uri.startswith("viking://memory/"):

# After (matches actual memory URIs like viking://user/default/memories/...)
if "/memories" in uri:

The fix uses the same substring matching logic as core/directories.get_context_type_for_uri().

Bug 2: semantic_dag.py — root context_type propagated to all children

SemanticDagExecutor stored the root URI's context_type as self._context_type and used it for every child node during recursive traversal. When reindexing from viking:// (root), the root has no /memories/ segment, so context_type defaults to "resource" and propagates to all descendants.

Fixed by calling get_context_type_for_uri() per node instead of inheriting from root.

Why this was hidden

Normal memory creation via auto-capture uses a completely different code path (memory_updater.py → embedding queue, which hardcodes "memory"). It never touches Summarizer or SemanticDagExecutor. This bug only manifests during reindex operations — typically after switching embedding models.

Changes

• openviking/utils/summarizer.py: Fix URI matching to use "/memories" in uri and "/skills" in uri
• openviking/storage/queuefs/semantic_dag.py: Use get_context_type_for_uri() per node instead of self._context_type

Test Plan

1. Populate memories via normal auto-capture flow
2. Run POST /api/v1/content/reindex with {"uri": "viking://", "regenerate": true}
3. Verify via GET /api/v1/debug/vector/scroll that records under /memories/ have context_type="memory"
4. Verify OpenClaw auto-recall (which filters by context_type=="memory") can find reindexed memories

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

Failed to generate code suggestions for PR