mirror of
https://github.com/agentscope-ai/ReMe.git
synced 2026-09-22 00:32:49 +00:00
dd2de16481
feat(file_watcher): add directory deletion support with descendant indexing Add support for deleting entire directories and their indexed descendants in the file watcher. Previously only individual file deletions were handled properly. Now when a directory is deleted, the system finds all indexed files beneath that directory path and removes them along with their metadata and chunks. The implementation includes: - New `_descendant_indexed_paths` method to find all indexed files under a given directory path - Updated `_on_deleted` method to process both the target path and all its indexed descendants - Proper handling of symlinks and path resolution differences - Enhanced logging to show directory deletion with child count Also adds necessary os import for path operations. refactor(config): restructure configuration profiles for clarity Rename curated.yaml to remove outdated configuration file and rename full.yaml to expert.yaml with updated documentation. Add new service.yaml configuration profile that provides a service-aligned MCP surface with three main tools: - retrieve: graph-aware hybrid retrieval - remember: single write entry point with log/distill modes - maintain: vault hygiene sweep The expert configuration now excludes the ingest tool since cold-path operations are handled by external agents, and adds memory_lint tool for structural issue detection. Updated documentation to clarify the different configuration profiles and their intended usage patterns. ```
20 lines
846 B
Python
20 lines
846 B
Python
"""reme2.mcp — MCP interface layer.
|
|
|
|
The Agent-facing surface: server entrypoint + step shells that wrap
|
|
the three services in `reme2.memory` (Retriever, Ingestor, Maintainer)
|
|
plus the hot-write primitive (`sync`) and the raw `memory_*` write/read
|
|
tools that bypass services and land directly on the Memory File System.
|
|
|
|
This package depends on `reme2.memory`, `reme2.utils`, `reme2.component`
|
|
— never the reverse. The Memory schema (the typed shape of every
|
|
frontmatter) lives under `reme2.memory.schema/` so the services that
|
|
own validation can use it without an import cycle through this
|
|
transport layer.
|
|
|
|
Sub-packages:
|
|
steps/ - all @R.register MCP step shells (memory_toolkit,
|
|
memory_retriever, memory_lint, sync).
|
|
server.py - MCP server bootstrap (defaults to ../config/service.yaml).
|
|
"""
|
|
|
|
__version__ = "0.1.0"
|