recallnest 2.3.0 → 2.6.0

package/docs/architecture.md

@@ -0,0 +1,168 @@
+# Architecture
+
+> 架构总览：RecallNest 的分层设计，从接入层到存储层。
+
+边界说明：
+
+- structured capture 写 durable memory
+- checkpoint store 写 session state
+- raw ingest 写 evidence
+
+See [memory-boundary-contract.md](./memory-boundary-contract.md).
+
+## System Architecture
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                       Client Layer                           │
+├──────────┬──────────┬──────────┬──────────┬─────────────────┤
+│ Claude   │ Gemini   │ Codex    │ Custom   │ curl / any      │
+│ Code     │ CLI      │          │ Agents   │ HTTP client     │
+└────┬─────┴────┬─────┴────┬─────┴────┬─────┴────┬────────────┘
+     │          │          │          │          │
+     └──── MCP (stdio) ───┘          └── HTTP ──┘
+                │                        │
+                ▼                        ▼
+┌─────────────────────────────────────────────────────────────┐
+│                     Integration Layer                        │
+├────────────────────────┬────────────────────────────────────┤
+│    MCP Server          │       HTTP API Server               │
+│    (mcp-server.ts)     │       (api-server.ts)               │
+│                        │       port 4318                     │
+│  Tools:                │                                     │
+│  - search_memory       │  Endpoints:                         │
+│  - memory_stats        │  - POST /v1/recall                  │
+│  - brief_memory        │  - POST /v1/store                   │
+│  - distill_memory      │  - POST /v1/search                  │
+│  - pin_memory          │  - GET  /v1/stats                   │
+│  - explain_memory      │  - GET  /v1/health                  │
+│  - export_memory       │  - POST /v1/consolidate             │
+│                        │  - GET  /v1/gaps                    │
+└────────────┬───────────┴──────────────┬─────────────────────┘
+             │                          │
+             ▼                          ▼
+┌─────────────────────────────────────────────────────────────┐
+│                      Core Engine                             │
+├─────────────────────────────────────────────────────────────┤
+│                                                              │
+│  ┌─────────────┐  ┌──────────────┐  ┌────────────────────┐  │
+│  │  Retriever   │  │  Classifier  │  │  Query Expander    │  │
+│  │ (hybrid:     │  │ (6 categories│  │  (synonym +        │  │
+│  │  vector +    │  │  auto-assign)│  │   semantic expand) │  │
+│  │  BM25 + RRF) │  │              │  │                    │  │
+│  └──────┬───────┘  └──────────────┘  └────────────────────┘  │
+│         │                                                    │
+│  ┌──────┴───────┐  ┌──────────────┐  ┌────────────────────┐  │
+│  │  Decay       │  │  Access      │  │  Noise Filter      │  │
+│  │  Engine      │  │  Tracker     │  │  (relevance        │  │
+│  │  (Weibull)   │  │  (use it or  │  │   threshold)       │  │
+│  │              │  │   lose it)   │  │                    │  │
+│  └──────────────┘  └──────────────┘  └────────────────────┘  │
+│                                                              │
+│  ┌──────────────┐  ┌──────────────┐                          │
+│  │ Consolidator │  │ Gap Detector │   ← Self-Evolution       │
+│  │ (merge/dedup)│  │ (find blind  │                          │
+│  │              │  │  spots)      │                          │
+│  └──────────────┘  └──────────────┘                          │
+│                                                              │
+└──────────────────────────┬──────────────────────────────────┘
+                           │
+                           ▼
+┌─────────────────────────────────────────────────────────────┐
+│                     Storage Layer                            │
+├─────────────────────────┬───────────────────────────────────┤
+│  LanceDB               │  Jina Embeddings                   │
+│  (vector + columnar)    │  (v5, 1024-dim)                    │
+│                         │                                    │
+│  Tables:                │  Task-aware:                       │
+│  - memories (main)      │  - retrieval.query (for searches)  │
+│  - access_log           │  - retrieval.passage (for docs)    │
+│  - search_log           │                                    │
+└─────────────────────────┴───────────────────────────────────┘
+```
+
+## Data Flow
+
+### Ingestion Pipeline
+
+```
+Source Files                    Processing                  Storage
+─────────────                  ──────────                  ───────
+
+CC transcripts ─┐
+                │   ┌──────────────────┐   ┌───────────┐
+Codex sessions ─┼──►│  Chunker         │──►│ Embedder  │──► LanceDB
+                │   │  (split by turn, │   │ (Jina v5) │
+Gemini chats ───┤   │   noise filter)  │   └───────────┘
+                │   └──────────────────┘
+Memory .md ─────┘         │
+                          ▼
+                   ┌──────────────┐
+                   │ Classifier   │
+                   │ (6 categories│
+                   │  + tier)     │
+                   └──────────────┘
+```
+
+> 入库流程：多源文件 → 分块 → 过滤噪音 → 分类 → 嵌入向量 → 存入 LanceDB
+
+### Search Pipeline
+
+```
+Query                                               Results
+─────                                               ───────
+
+"Docker debugging"
+    │
+    ▼
+┌──────────────┐    ┌──────────────┐    ┌───────────────┐
+│ Query        │───►│ Hybrid       │───►│ Post-process  │──► Top-K
+│ Expander     │    │ Retrieval    │    │               │   Results
+│ (synonyms)   │    │              │    │ - Decay       │
+└──────────────┘    │ Vector: 0.7  │    │ - Access boost│
+                    │ BM25:   0.3  │    │ - Score floor │
+                    │ RRF merge    │    │ - Dedup       │
+                    └──────────────┘    └───────────────┘
+```
+
+## Key Design Decisions
+
+| Decision | Rationale |
+|----------|-----------|
+| **LanceDB** (not SQLite/Postgres) | Native vector search, columnar storage, zero-config, single-file DB |
+| **Jina v5** (not OpenAI embeddings) | Task-aware embeddings (query vs passage), better multilingual, 1024-dim sweet spot |
+| **Hybrid retrieval** (vector + BM25) | Vector alone misses keyword matches; BM25 alone misses semantic similarity |
+| **RRF fusion** | Reciprocal Rank Fusion is parameter-free and robust across score distributions |
+| **Weibull decay** (not exponential) | Better models human forgetting: slow start, accelerating fade |
+| **6 categories** (not free-form tags) | Structured enough for filtering and lifecycle rules, simple enough to auto-classify |
+| **HTTP API + MCP** (not just MCP) | MCP is great for CLI tools, but HTTP API works with any language/framework |
+| **Bun runtime** | Fast startup, native TypeScript, good for CLI tools and local servers |
+
+## File Map
+
+```
+src/
+├── api-server.ts          # HTTP API server (port 4318)
+├── mcp-server.ts          # MCP server (stdio transport)
+├── cli.ts                 # CLI entry point (lm command)
+├── store.ts               # LanceDB storage layer
+├── retriever.ts           # Hybrid retrieval (vector + BM25 + RRF)
+├── embedder.ts            # Jina embedding client
+├── ingest.ts              # Multi-source ingestion pipeline
+├── chunker.ts             # Text chunking with noise filtering
+├── decay-engine.ts        # Weibull time decay
+├── access-tracker.ts      # "Use it or lose it" tracking
+├── noise-filter.ts        # Low-quality content filter
+├── query-expander.ts      # Query expansion (synonyms)
+├── retrieval-profiles.ts  # 4 search profiles (precision/balanced/exploratory/recent)
+├── memory-output.ts       # Output formatting
+├── memory-assets.ts       # Brief/pin/export asset management
+├── asset-sync.ts          # Asset indexing
+├── runtime-config.ts      # Config loading
+├── llm-client.ts          # LLM client for smart extraction
+├── doctor.ts              # Health check diagnostics
+├── adaptive-retrieval.ts  # Adaptive retrieval strategies
+├── stderr-log.ts          # Logging
+├── tracker.ts             # Ingestion tracker (incremental)
+└── __tests__/             # Test suite
+```

package/docs/connector-spec.md

@@ -0,0 +1,126 @@
+# RecallNest Connector Specification (connector-v1)
+
+## Overview
+
+The connector-v1 format is the standard interface for feeding external data into RecallNest. Any external script, service, or integration can produce a JSON file in this format, and RecallNest will consume it through its existing ingest pipeline (dedup, embedding, smart extraction, tiered storage).
+
+**Design philosophy**: RecallNest's core engine stays lean. External connectors handle data fetching and normalization; RecallNest handles memory quality (dedup, decay, governance, retrieval).
+
+## JSON Schema
+
+```json
+{
+  "version": "connector-v1",
+  "source": "obsidian",
+  "scope": "vault:my-notes",
+  "batchId": "batch-2026-04-13-001",
+  "producedAt": "2026-04-13T12:00:00Z",
+  "records": [
+    {
+      "id": "obsidian:notes/meeting-2026-04-13.md",
+      "text": "Meeting with team about Q2 goals...",
+      "title": "Q2 Planning Meeting",
+      "categoryHint": "events",
+      "importanceHint": 0.8,
+      "tags": ["meeting", "q2", "link:Team-Goals"],
+      "timestamp": "2026-04-13T10:00:00Z",
+      "contentHash": "a1b2c3d4e5f67890",
+      "sourceMetadata": {
+        "filePath": "notes/meeting-2026-04-13.md",
+        "frontmatter": { "tags": ["meeting"] }
+      }
+    }
+  ]
+}
+```
+
+## Field Reference
+
+### Top-level
+
+| Field | Type | Required | Description |
+|-------|------|----------|-------------|
+| `version` | `"connector-v1"` | Yes | Fixed version string for format detection |
+| `source` | string | Yes | Data source identifier (e.g. `"obsidian"`, `"email"`, `"rss"`) |
+| `scope` | string | Yes | Target scope for all records (e.g. `"vault:my-notes"`, `"project:research"`) |
+| `batchId` | string | No | Batch identifier for idempotent retry |
+| `producedAt` | string (ISO 8601) | Yes | When this payload was generated |
+| `records` | ConnectorRecord[] | Yes | Array of records to ingest |
+
+### ConnectorRecord
+
+| Field | Type | Required | Description |
+|-------|------|----------|-------------|
+| `id` | string | Yes | Unique ID within the source (used for incremental tracking) |
+| `text` | string | Yes | Main content to be stored and embedded |
+| `title` | string | No | Title or heading (prepended as `[title]` in stored text) |
+| `categoryHint` | string | No | Suggested category: `preferences`, `events`, `knowledge`, `facts`, `decisions` |
+| `importanceHint` | number (0-1) | No | Suggested importance score (default: extracted by LLM or 0.7) |
+| `tags` | string[] | No | Tags stored in metadata as `connectorTags` |
+| `timestamp` | string (ISO 8601) | No | Original creation/modification time |
+| `contentHash` | string | No | Content hash for incremental sync (skip if unchanged) |
+| `sourceMetadata` | object | No | Arbitrary metadata from the source (stored as-is in entry metadata) |
+
+## Ingest Behavior
+
+1. **Format detection**: `detectFormat()` identifies connector-v1 by checking `version === "connector-v1"` and `Array.isArray(records)`. Takes highest priority among object-type formats.
+
+2. **Incremental sync**: If `contentHash` is present, RecallNest stores it in entry metadata. Future versions may use this for pre-embedding dedup.
+
+3. **Dedup**: Each record goes through the standard two-stage dedup pipeline (vector pre-filter + optional LLM semantic decision).
+
+4. **Category/importance**: If `categoryHint` or `importanceHint` are provided, they override the LLM-extracted values. Otherwise, smart extraction determines them.
+
+5. **Tags**: `tags` are stored in `metadata.connectorTags` (separate from RecallNest's internal tags to avoid namespace collision).
+
+6. **Scope**: All records share the top-level `scope`. To ingest records into different scopes, produce separate connector-v1 payloads.
+
+## Writing a Connector
+
+A connector is any script that produces a connector-v1 JSON file. Minimal example in TypeScript:
+
+```typescript
+import { writeFileSync } from "node:fs";
+
+const output = {
+  version: "connector-v1",
+  source: "my-app",
+  scope: "project:my-app",
+  producedAt: new Date().toISOString(),
+  records: [
+    {
+      id: "note-001",
+      text: "User prefers dark mode and compact layout",
+      title: "UI Preferences",
+      categoryHint: "preferences",
+      importanceHint: 0.9,
+      tags: ["ui", "preferences"],
+    },
+  ],
+};
+
+writeFileSync("my-connector-output.json", JSON.stringify(output, null, 2));
+```
+
+Then feed it to RecallNest:
+
+```bash
+# Via CLI
+recallnest ingest --connector my-connector-output.json
+
+# Via MCP tool
+# Use import_conversations with format="connector-v1" and content=<file contents>
+```
+
+## Built-in Connectors
+
+| Connector | Source | Description |
+|-----------|--------|-------------|
+| `obsidian-connector` | `obsidian` | Scans an Obsidian vault, extracts frontmatter + wikilinks, maps folder structure to tags |
+
+## Versioning
+
+The `version` field enables future format evolution. RecallNest will:
+- Accept `"connector-v1"` indefinitely (no breaking changes within v1)
+- Future v2 will be a separate format, not a replacement
+- Unknown versions are rejected with a clear error message

package/eval/cases-canary.json

@@ -0,0 +1,58 @@
+[
+  {
+    "name": "canary-A-mem0-borrow",
+    "query": "mem0 对 recallnest 有没有借鉴作用",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": ["a2fe9b62"],
+    "expectTopK": 3,
+    "notes": "A 单目标：mem0→recallnest 借鉴审计结论该被召回。"
+  },
+  {
+    "name": "canary-A-dual-dir-fix",
+    "query": "recallnest 本地两个目录反复踩坑是怎么解决的",
+    "profile": "debug",
+    "limit": 8,
+    "targets": ["dbcb317a"],
+    "expectTopK": 3,
+    "notes": "A 单目标：dual-dir 符号链接统一 case（dbcb317a, cases, imp 0.9, baseline rank1）。原 target e40ab64b 系标注错——e40ab64b 实为『RecallNest 演进优先 workflow pattern』，与本 query 无关；dbcb317a 才是『~/recallnest→~/Projects/recallnest symlink 统一』。"
+  },
+  {
+    "name": "canary-B-capture-heuristic-evolution",
+    "query": "recallnest 的 capture 是纯 heuristic 吗，提取到底用不用 LLM",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": ["727da608"],
+    "expectOrder": ["727da608", "a2fe9b62"],
+    "expectTopK": 3,
+    "notes": "B 新旧对：727da608(cases,imp0.8) 正文明确『修正 a2fe9b62 中 capture 纯heuristic/zero-LLM 的不准确表述』，是本 query 准确答案；a2fe9b62(events,imp0.72,mem0借鉴审计) 含被纠正的旧表述。expectOrder 测『两者同时召回时准确版 727 须排在旧版 a2 前』——纯排名对比(rank 唯一，<与≤等价)，不靠结构化 supersede。校准修正：原 notes『验 confidence/recency/decay』机制声称不成立(二者无 evolution 链/降权链，靠内容质量排序)；且主话题不重合(727=ingest去重史 / a2=mem0审计)，实测 a2 常落选(baseline rank=null)，故本 case 当前主要测 727 召回质量+弱新旧序保护，非真正新旧竞争。理想 B 类应换一对同话题、会同时召回的新旧记忆(P1 后续)。"
+  },
+  {
+    "name": "canary-C-scope-isolation-noise",
+    "query": "工作记忆要不要做 scope 隔离",
+    "profile": "default",
+    "limit": 8,
+    "targets": ["491c8b30"],
+    "hardNegatives": ["b59e86b2"],
+    "expectTopK": 2,
+    "notes": "C 干扰项：491c8b30(元决策『工作记忆不做 scope 隔离』,baseline rank1) 应召回。hardNegative b59e86b2(entities,imp0.65,scope=codex:019cfba5) 是 codex 端关于 scope 模型/associative access/隔离的设计讨论片段——词面同话题、别处语境(非 Alice 元决策)，baseline rank2 进了 top。补此 hardNeg 后本 case 在当前裸 retrieve 下会 fail，暴露『跨-scope 旁支讨论被召回进 top』的真问题(契合 P0 scope 主题)。"
+  },
+  {
+    "name": "canary-D-writing-style",
+    "query": "Alice 的写作风格偏好是什么",
+    "profile": "writing",
+    "limit": 6,
+    "expectContentAny": ["口语化", "不端着", "剧评腔", "书面非口语", "可自嘲"],
+    "expectTopK": 3,
+    "notes": "D 稳定偏好：不钉 id，召回文本命中要点即算对。"
+  },
+  {
+    "name": "canary-D-visual-style",
+    "query": "Alice 的配图审美偏好",
+    "profile": "default",
+    "limit": 6,
+    "expectContentAny": ["手绘", "撞色", "高对比", "静物无人物", "涂鸦"],
+    "expectTopK": 3,
+    "notes": "D 稳定偏好：同上。"
+  }
+]

package/eval/cases-scope-robustness.json

@@ -0,0 +1,278 @@
+[
+  {
+    "name": "scope-727da608-v1-WITH",
+    "query": "recallnest 的 capture 用不用 LLM，是不是纯 heuristic",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": [
+      "727da608"
+    ],
+    "expectTopK": 3,
+    "scope": "project:recallnest",
+    "notes": "P1.1 scope 影响 — 目标 727da608 变体1 带 scope=project:recallnest"
+  },
+  {
+    "name": "scope-727da608-v1-WITHOUT",
+    "query": "recallnest 的 capture 用不用 LLM，是不是纯 heuristic",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": [
+      "727da608"
+    ],
+    "expectTopK": 3,
+    "notes": "P1.1 scope 影响 — 目标 727da608 变体1 不带 scope(裸 retrieve)"
+  },
+  {
+    "name": "scope-727da608-v2-WITH",
+    "query": "ingest 去重为什么会把携带新信息的内容误删",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": [
+      "727da608"
+    ],
+    "expectTopK": 3,
+    "scope": "project:recallnest",
+    "notes": "P1.1 scope 影响 — 目标 727da608 变体2 带 scope=project:recallnest"
+  },
+  {
+    "name": "scope-727da608-v2-WITHOUT",
+    "query": "ingest 去重为什么会把携带新信息的内容误删",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": [
+      "727da608"
+    ],
+    "expectTopK": 3,
+    "notes": "P1.1 scope 影响 — 目标 727da608 变体2 不带 scope(裸 retrieve)"
+  },
+  {
+    "name": "scope-727da608-v3-WITH",
+    "query": "recallnest 早期 ingest 排除太厉害是什么原因、后来怎么修的",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": [
+      "727da608"
+    ],
+    "expectTopK": 3,
+    "scope": "project:recallnest",
+    "notes": "P1.1 scope 影响 — 目标 727da608 变体3 带 scope=project:recallnest"
+  },
+  {
+    "name": "scope-727da608-v3-WITHOUT",
+    "query": "recallnest 早期 ingest 排除太厉害是什么原因、后来怎么修的",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": [
+      "727da608"
+    ],
+    "expectTopK": 3,
+    "notes": "P1.1 scope 影响 — 目标 727da608 变体3 不带 scope(裸 retrieve)"
+  },
+  {
+    "name": "scope-a2fe9b62-v1-WITH",
+    "query": "mem0 对 recallnest 有没有借鉴价值",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": [
+      "a2fe9b62"
+    ],
+    "expectTopK": 3,
+    "scope": "project:recallnest",
+    "notes": "P1.1 scope 影响 — 目标 a2fe9b62 变体1 带 scope=project:recallnest"
+  },
+  {
+    "name": "scope-a2fe9b62-v1-WITHOUT",
+    "query": "mem0 对 recallnest 有没有借鉴价值",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": [
+      "a2fe9b62"
+    ],
+    "expectTopK": 3,
+    "notes": "P1.1 scope 影响 — 目标 a2fe9b62 变体1 不带 scope(裸 retrieve)"
+  },
+  {
+    "name": "scope-a2fe9b62-v2-WITH",
+    "query": "mem0 的招牌设计 recallnest 有没有独立实现",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": [
+      "a2fe9b62"
+    ],
+    "expectTopK": 3,
+    "scope": "project:recallnest",
+    "notes": "P1.1 scope 影响 — 目标 a2fe9b62 变体2 带 scope=project:recallnest"
+  },
+  {
+    "name": "scope-a2fe9b62-v2-WITHOUT",
+    "query": "mem0 的招牌设计 recallnest 有没有独立实现",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": [
+      "a2fe9b62"
+    ],
+    "expectTopK": 3,
+    "notes": "P1.1 scope 影响 — 目标 a2fe9b62 变体2 不带 scope(裸 retrieve)"
+  },
+  {
+    "name": "scope-a2fe9b62-v3-WITH",
+    "query": "mem0 借鉴审计的核心结论是什么",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": [
+      "a2fe9b62"
+    ],
+    "expectTopK": 3,
+    "scope": "project:recallnest",
+    "notes": "P1.1 scope 影响 — 目标 a2fe9b62 变体3 带 scope=project:recallnest"
+  },
+  {
+    "name": "scope-a2fe9b62-v3-WITHOUT",
+    "query": "mem0 借鉴审计的核心结论是什么",
+    "profile": "fact-check",
+    "limit": 8,
+    "targets": [
+      "a2fe9b62"
+    ],
+    "expectTopK": 3,
+    "notes": "P1.1 scope 影响 — 目标 a2fe9b62 变体3 不带 scope(裸 retrieve)"
+  },
+  {
+    "name": "scope-491c8b30-v1-WITH",
+    "query": "工作记忆要不要做 scope 隔离",
+    "profile": "default",
+    "limit": 8,
+    "targets": [
+      "491c8b30"
+    ],
+    "expectTopK": 3,
+    "scope": "project:recallnest",
+    "notes": "P1.1 scope 影响 — 目标 491c8b30 变体1 带 scope=project:recallnest"
+  },
+  {
+    "name": "scope-491c8b30-v1-WITHOUT",
+    "query": "工作记忆要不要做 scope 隔离",
+    "profile": "default",
+    "limit": 8,
+    "targets": [
+      "491c8b30"
+    ],
+    "expectTopK": 3,
+    "notes": "P1.1 scope 影响 — 目标 491c8b30 变体1 不带 scope(裸 retrieve)"
+  },
+  {
+    "name": "scope-491c8b30-v2-WITH",
+    "query": "单位/工作记忆该不该 forget 清理",
+    "profile": "default",
+    "limit": 8,
+    "targets": [
+      "491c8b30"
+    ],
+    "expectTopK": 3,
+    "scope": "project:recallnest",
+    "notes": "P1.1 scope 影响 — 目标 491c8b30 变体2 带 scope=project:recallnest"
+  },
+  {
+    "name": "scope-491c8b30-v2-WITHOUT",
+    "query": "单位/工作记忆该不该 forget 清理",
+    "profile": "default",
+    "limit": 8,
+    "targets": [
+      "491c8b30"
+    ],
+    "expectTopK": 3,
+    "notes": "P1.1 scope 影响 — 目标 491c8b30 变体2 不带 scope(裸 retrieve)"
+  },
+  {
+    "name": "scope-491c8b30-v3-WITH",
+    "query": "Alice 对工作记忆隔离是怎么决定的",
+    "profile": "default",
+    "limit": 8,
+    "targets": [
+      "491c8b30"
+    ],
+    "expectTopK": 3,
+    "scope": "project:recallnest",
+    "notes": "P1.1 scope 影响 — 目标 491c8b30 变体3 带 scope=project:recallnest"
+  },
+  {
+    "name": "scope-491c8b30-v3-WITHOUT",
+    "query": "Alice 对工作记忆隔离是怎么决定的",
+    "profile": "default",
+    "limit": 8,
+    "targets": [
+      "491c8b30"
+    ],
+    "expectTopK": 3,
+    "notes": "P1.1 scope 影响 — 目标 491c8b30 变体3 不带 scope(裸 retrieve)"
+  },
+  {
+    "name": "scope-dbcb317a-v1-WITH",
+    "query": "recallnest 本地两个目录反复踩坑怎么解决的",
+    "profile": "debug",
+    "limit": 8,
+    "targets": [
+      "dbcb317a"
+    ],
+    "expectTopK": 3,
+    "scope": "project:recallnest",
+    "notes": "P1.1 scope 影响 — 目标 dbcb317a 变体1 带 scope=project:recallnest"
+  },
+  {
+    "name": "scope-dbcb317a-v1-WITHOUT",
+    "query": "recallnest 本地两个目录反复踩坑怎么解决的",
+    "profile": "debug",
+    "limit": 8,
+    "targets": [
+      "dbcb317a"
+    ],
+    "expectTopK": 3,
+    "notes": "P1.1 scope 影响 — 目标 dbcb317a 变体1 不带 scope(裸 retrieve)"
+  },
+  {
+    "name": "scope-dbcb317a-v2-WITH",
+    "query": "~/recallnest 和 ~/Projects/recallnest 是什么关系",
+    "profile": "debug",
+    "limit": 8,
+    "targets": [
+      "dbcb317a"
+    ],
+    "expectTopK": 3,
+    "scope": "project:recallnest",
+    "notes": "P1.1 scope 影响 — 目标 dbcb317a 变体2 带 scope=project:recallnest"
+  },
+  {
+    "name": "scope-dbcb317a-v2-WITHOUT",
+    "query": "~/recallnest 和 ~/Projects/recallnest 是什么关系",
+    "profile": "debug",
+    "limit": 8,
+    "targets": [
+      "dbcb317a"
+    ],
+    "expectTopK": 3,
+    "notes": "P1.1 scope 影响 — 目标 dbcb317a 变体2 不带 scope(裸 retrieve)"
+  },
+  {
+    "name": "scope-dbcb317a-v3-WITH",
+    "query": "recallnest 用符号链接统一目录是怎么回事",
+    "profile": "debug",
+    "limit": 8,
+    "targets": [
+      "dbcb317a"
+    ],
+    "expectTopK": 3,
+    "scope": "project:recallnest",
+    "notes": "P1.1 scope 影响 — 目标 dbcb317a 变体3 带 scope=project:recallnest"
+  },
+  {
+    "name": "scope-dbcb317a-v3-WITHOUT",
+    "query": "recallnest 用符号链接统一目录是怎么回事",
+    "profile": "debug",
+    "limit": 8,
+    "targets": [
+      "dbcb317a"
+    ],
+    "expectTopK": 3,
+    "notes": "P1.1 scope 影响 — 目标 dbcb317a 变体3 不带 scope(裸 retrieve)"
+  }
+]