ReMe/reme2/component/file_graph/__init__.py
huangsen 6a5561f86a feat: add file_graph component and integrate with LinkedFileParser
- Add file_graph import to component registry
- Register FILE_GRAPH enum in ComponentEnum
- Implement BaseFileGraph integration in LinkedFileParser
- Replace FileEdge with FileLink for better semantic clarity
- Add lazy resolution of file_graph from app_context
- Update file watcher logging to reflect links instead of edges

refactor: streamline MCP transport layer architecture

- Remove redundant step shells from reme2/mcp/steps/
- Consolidate all @R.register components to reme2.memory package
- Update server.py to import reme2.memory directly
- Revise README.md to document new architecture
- Simplify module dependencies and import structure
2026-05-14 11:35:02 +08:00

22 lines
688 B
Python

"""File graph module.
Backend-agnostic graph engine that owns the wikilink graph (nodes +
typed edges + traversal queries). Sister to ``file_store``, which owns
chunks and projections (vector / FTS).
Two backends ship today:
- ``LocalFileGraph`` (``@R.register("local")``) — networkx
``MultiDiGraph`` + JSONL persistence. Default.
- ``Neo4jFileGraph`` (``@R.register("neo4j")``) — property-graph
backed by Neo4j. Requires the ``neo4j`` driver.
"""
from .base_file_graph import BaseFileGraph
from .local_file_graph import LocalFileGraph
from .neo4j_file_graph import Neo4jFileGraph
__all__ = [
"BaseFileGraph",
"LocalFileGraph",
"Neo4jFileGraph",
]