Repository navigation
Conversation
- 复用既有索引与 Resolver 名称，保留引用和分模式证据 - 名称不可用时保留候选，不新增工具或读取协议 - 通过官方 SDK 往返覆盖名称、去重证据与失败降级
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
目的与范围
让 MCP 调用者识别 recall 候选，只添加可读的 label：lexical 沿用既有名称，semantic Block 复用 Resolver，Relation 展示关系内容与端点。名称读取失败仍保留引用和各模式证据。
仅包含 cf73552。继续使用既有 Tool、Resource、参数与检索能力；不增加筛选、来源投影、迁移、v2 协议或窗口读取，不承担外部 MCP 消费端验收。
验证
pdm run pytest tests/test_mcp_recall.py -q：1 项 SDK 往返通过，覆盖可读名称、跨模式证据、不可读候选与 Relation。pdm run check:foundation通过。交付影响与回滚
无数据库、配置、凭据或部署变更。新增 label 为兼容字段；主要风险是 Resolver 名称读取带来额外延迟，读取异常不会丢弃候选。回滚本提交即可恢复原输出。
父 PR：无。子 PR：无。可独立合并，与 Web 语义入口没有发布顺序依赖。