@geminilight/mindos 0.6.58 → 0.6.60

package/app/lib/types.ts

@@ -52,6 +52,8 @@ export interface ImagePart {
   /** Base64-encoded image data (no data: prefix) */
   data: string;
   mimeType: ImageMimeType;
+  /** Original file name, if available */
+  fileName?: string;
 }
 
 export type MessagePart = TextPart | ToolCallPart | ReasoningPart | ImagePart;
@@ -72,6 +74,16 @@ export interface Message {
 export interface LocalAttachment {
   name: string;
   content: string;
+  /** Extraction status for PDF uploads. Absent / undefined = legacy (treated as success). */
+  status?: 'loading' | 'success' | 'error';
+  /** Human-readable error message (only when status = 'error'). */
+  error?: string;
+  /** Present when the full text was too long and had to be truncated. */
+  truncatedInfo?: {
+    totalChars: number;
+    includedChars: number;
+    totalPages: number;
+  };
 }
 
 /** User-facing Ask modes. 'organize' is internal-only (not selectable by users). */
@@ -87,4 +99,5 @@ export interface ChatSession {
   createdAt: number;
   updatedAt: number;
   messages: Message[];
+  pinned?: boolean;
 }

package/app/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wiki-app",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "private": true,
   "scripts": {
     "generate": "npx tsx scripts/generate-explore.ts",

package/app/scripts/extract-pdf.cjs

@@ -13,7 +13,6 @@
 'use strict';
 
 const fs = require('fs');
-const path = require('path');
 
 // Suppress pdfjs-dist warnings (loadFont etc.) that go to stdout/stderr
 // and would corrupt our JSON output.
@@ -22,6 +21,115 @@ const _log = console.log;
 console.warn = () => {};
 console.log = () => {};
 
+// ---------------------------------------------------------------------------
+// CJK-aware smart text joining
+// ---------------------------------------------------------------------------
+
+/**
+ * Detect whether a character falls in CJK / fullwidth ranges where
+ * inter-item spaces are NOT desired.
+ */
+function isCJK(ch) {
+  const c = ch.codePointAt(0);
+  return (
+    (c >= 0x2E80 && c <= 0x2FDF) ||   // CJK Radicals Supplement, Kangxi Radicals
+    (c >= 0x4E00 && c <= 0x9FFF) ||   // CJK Unified Ideographs
+    (c >= 0x3400 && c <= 0x4DBF) ||   // CJK Extension A
+    (c >= 0xF900 && c <= 0xFAFF) ||   // CJK Compatibility Ideographs
+    (c >= 0x3040 && c <= 0x309F) ||   // Hiragana
+    (c >= 0x30A0 && c <= 0x30FF) ||   // Katakana
+    (c >= 0xAC00 && c <= 0xD7AF) ||   // Hangul Syllables
+    (c >= 0x20000 && c <= 0x2FA1F)    // CJK Extensions B-F + Supplement
+  );
+}
+
+/** True for CJK fullwidth punctuation that already occupies its own space. */
+function isCJKPunct(ch) {
+  const c = ch.codePointAt(0);
+  return (
+    (c >= 0x3000 && c <= 0x303F) ||    // 。、「」【】
+    (c >= 0xFF01 && c <= 0xFF0F) ||    // ！＂＃＄
+    (c >= 0xFF1A && c <= 0xFF20) ||    // ：；＜＝＞
+    (c >= 0xFF3B && c <= 0xFF40) ||    // ［＼］
+    (c >= 0xFF5B && c <= 0xFF65) ||    // ｛｜｝～
+    (c >= 0xFE50 && c <= 0xFE6B)      // Small Form Variants
+  );
+}
+
+/**
+ * Decide whether a space should be inserted between two adjacent characters
+ * that come from separate pdfjs-dist TextItem objects.
+ *
+ * Rules:
+ *   CJK + CJK  → no space  (中文相邻不加)
+ *   CJK + Punct → no space  (标点紧跟)
+ *   Punct + CJK → no space
+ *   CJK + Latin → space     (中英之间加)
+ *   Latin + CJK → space
+ *   Latin + Latin → space    (英文单词间加)
+ *   Punct + Latin → no space (e.g. `(hello`)
+ *   Latin + Punct → no space (e.g. `hello.`)
+ */
+function shouldAddSpace(left, right) {
+  if (!left || !right) return false;
+
+  const lCJK = isCJK(left);
+  const rCJK = isCJK(right);
+  const lPunct = isCJKPunct(left) || /^[^\w\s]$/.test(left);
+  const rPunct = isCJKPunct(right) || /^[^\w\s]$/.test(right);
+
+  // Any side is punctuation → no space
+  if (lPunct || rPunct) return false;
+  // Both CJK → no space
+  if (lCJK && rCJK) return false;
+  // Mixed CJK/Latin → space
+  if (lCJK !== rCJK) return true;
+  // Both non-CJK (Latin/digit) → space between words
+  return true;
+}
+
+/**
+ * Join pdfjs-dist TextItem[] into clean text, respecting CJK spacing
+ * rules and `hasEOL` line-break markers.
+ */
+function smartJoinTextItems(items) {
+  const lines = [];
+  let cur = '';
+
+  for (const item of items) {
+    const str = item.str ?? '';
+
+    if (str === '') {
+      // Empty str with hasEOL → line break
+      if (item.hasEOL && cur.trim()) {
+        lines.push(cur.trim());
+        cur = '';
+      }
+      continue;
+    }
+
+    if (cur === '') {
+      cur = str;
+    } else {
+      const left = cur[cur.length - 1];
+      const right = str[0];
+      cur += shouldAddSpace(left, right) ? ' ' + str : str;
+    }
+
+    if (item.hasEOL) {
+      if (cur.trim()) lines.push(cur.trim());
+      cur = '';
+    }
+  }
+
+  if (cur.trim()) lines.push(cur.trim());
+  return lines.join('\n');
+}
+
+// ---------------------------------------------------------------------------
+// Main
+// ---------------------------------------------------------------------------
+
 async function main() {
   const pdfPath = process.argv[2];
   if (!pdfPath || !fs.existsSync(pdfPath)) {
@@ -43,8 +151,7 @@ async function main() {
   for (let i = 1; i <= numPages; i++) {
     const page = await doc.getPage(i);
     const content = await page.getTextContent();
-    const line = content.items.map((item) => item.str ?? '').join(' ');
-    pageTexts.push(line);
+    pageTexts.push(smartJoinTextItems(content.items));
   }
 
   process.stdout.write(JSON.stringify({ text: pageTexts.join('\n\n'), pages: numPages }));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@geminilight/mindos",
-  "version": "0.6.58",
+  "version": "0.6.60",
   "description": "MindOS — Human-Agent Collaborative Mind System. Local-first knowledge base that syncs your mind to all AI Agents via MCP.",
   "keywords": [
     "mindos",

package/skills/mindos/SKILL.md

@@ -1,26 +1,33 @@
 ---
 name: mindos
 description: >
-  Operate a MindOS knowledge base: update notes, search, organize files, execute SOPs/workflows,
-  retrospective, append CSV, cross-agent handoff, route unstructured input to the right files,
-  distill experience, sync related docs.
+  The user's shared knowledge base — persistent across sessions and agents. MindOS stores decisions,
+  meeting notes, SOPs, debugging lessons, architecture choices, research findings, and preferences.
   更新笔记, 搜索知识库, 整理文件, 执行SOP/工作流, 复盘, 追加CSV, 跨Agent交接,
   路由非结构化输入到对应文件, 提炼经验, 同步关联文档.
   NOT for editing app source, project docs, or paths outside the KB.
   Core concepts: Space, Instruction (INSTRUCTION.md), Skill (SKILL.md); notes can embody both.
-  Trigger when user asks to: save or record anything, search for prior notes or context, update or
-  edit a file, organize notes, run a workflow or SOP, capture decisions from a session, append rows
-  to a table or CSV, hand off context to another agent, check if something was discussed before,
-  look up a past decision, distill lessons learned, prepare context for a meeting.
-  Also trigger on Chinese: 帮我记下来, 搜一下笔记, 更新知识库, 整理文件, 复盘, 提炼经验,
-  保存, 记录, 交接, 查一下之前的, 有没有相关笔记, 把这个存起来.
-  When the user's question implies stored context may exist (past decisions, previous discussions,
-  meeting records), consider searching MindOS even if they don't explicitly mention it.
+
+  Trigger on: save or record anything, search for prior notes or context, update or edit a file,
+  organize notes, run a workflow or SOP, capture decisions, append rows to a table or CSV,
+  hand off context to another agent, check if something was discussed before, look up a past
+  decision, distill lessons learned, prepare context for a meeting, quick-capture to staging area,
+  organize inbox, check knowledge health, detect conflicts or contradictions, find stale content.
+  Chinese triggers: 帮我记下来, 搜一下笔记, 更新知识库, 整理文件, 复盘, 提炼经验,
+  保存, 记录, 交接, 查一下之前的, 有没有相关笔记, 把这个存起来, 放到暂存台,
+  整理暂存台, 知识健康检查, 检测知识冲突.
+
+  Proactive behavior — do not wait for the user to mention MindOS:
+  (1) When user's question implies stored context may exist (past decisions, previous discussions,
+  meeting records) → search MindOS first, even if they don't explicitly mention it.
+  (2) After completing valuable work (bug fixed, decision made, lesson learned, architecture chosen,
+  meeting summarized) → offer to save it to MindOS for future reference.
+  (3) After a long or multi-topic conversation → suggest persisting key decisions and context.
 ---
 
 # MindOS Skill
 
-<!-- version: 3.0.0 — CLI-first, MCP optional -->
+<!-- version: 3.2.0 — CLI-first, MCP optional -->
 
 ## CLI commands
 
@@ -85,6 +92,7 @@ npm install -g @geminilight/mindos
 - **Space** — Knowledge partitions organized the way you think. Agents follow the same structure.
 - **Instruction** — A rules file (`INSTRUCTION.md`) all connected agents obey.
 - **Skill** — Teaches agents how to read, write, and organize the KB.
+- **Inbox** — The `Inbox/` directory is a staging area for quick capture. Files land here when there's no obvious home yet. They get organized later — by the user manually or via AI-assisted batch organization.
 
 Notes can embody both Instruction and Skill — they're just Markdown files in the tree.
 
@@ -99,9 +107,13 @@ User request
   │   └─ [Read-only]: search → read → answer with citations. No writes.
   │
   ├─ Save / record / update / organize specific content?
-  │   ├─ Single file → [Single-file edit]
+  │   ├─ Know where it goes → [Single-file edit]
+  │   ├─ Don't know where it goes → [Inbox path] — save to Inbox/, classify later
   │   └─ Multiple files or unclear → [Multi-file routing] — plan first
   │
+  ├─ Organize inbox / classify staged files?
+  │   └─ [Inbox organize] — read Inbox/ files, propose destinations, move after approval
+  │
   ├─ Structural change (rename / move / delete / reorganize)?
   │   └─ [Structural path] — check backlinks before and after
   │
@@ -111,6 +123,9 @@ User request
   ├─ Retrospective / distill / handoff?
   │   └─ [Retrospective path]
   │
+  ├─ Knowledge health check / detect conflicts?
+  │   └─ [Health check path] — read references/knowledge-health.md
+  │
   └─ Ambiguous?
       └─ ASK. Propose 2-3 specific options based on KB state.
 ```
@@ -125,8 +140,9 @@ User request
 - "organize" → ask: display only, or write back?
 
 **File location uncertainty:**
-- Can't decide in 5 seconds → use nearest existing directory, inform user
-- "Just put it somewhere" → inbox, propose classification after
+- Can't decide in 5 seconds → save to `Inbox/`, inform user, propose classification later
+- "Just put it somewhere" / "先放着" → save to `Inbox/`
+- User drags files or pastes unstructured content without specifying location → `Inbox/`
 
 **Scope creep:**
 - Input routes to >5 files → pause, confirm scope
@@ -159,6 +175,42 @@ When user expresses a standing preference → read [references/preference-captur
 
 When creating/rewriting an SOP → read [references/sop-template.md](./references/sop-template.md).
 
+## Inbox (staging area)
+
+The `Inbox/` directory is the KB's quick-capture zone. It has its own `INSTRUCTION.md` that governs behavior.
+
+**When to use Inbox:**
+- User says "just save it" / "先放着" / "放到暂存台" without specifying a location
+- Content doesn't clearly fit any existing Space or directory
+- Batch import of multiple files that need individual classification
+
+**How to save to Inbox:**
+```bash
+mindos file create "Inbox/<filename>.md" --content "..."
+```
+
+**How to organize Inbox:**
+1. List Inbox files: `mindos file list Inbox/`
+2. Read each file to understand its content
+3. For each file, propose the best destination directory based on KB structure
+4. Present the full routing plan to user for approval
+5. Move files: `mindos file rename "Inbox/<file>" "<target-dir>/<file>"`
+6. After moving, check if the target directory's README needs updating
+
+**Aging reminder:** Files in Inbox older than 7 days are considered "aging". If you notice aging files during bootstrap, mention it: "You have N files in Inbox that have been sitting there for over a week. Want me to help organize them?"
+
+## Knowledge health check
+
+When user asks to check knowledge health, detect conflicts, audit quality, or says "知识健康检查" / "检测冲突" → read [references/knowledge-health.md](./references/knowledge-health.md) for the full procedure.
+
+Quick summary of what gets checked:
+- **Contradictions**: conflicting facts across files on the same topic
+- **Broken links**: references to files that no longer exist
+- **Stale content**: files with outdated date markers or untouched for >6 months
+- **Duplicates**: two files covering the same ground without cross-referencing
+- **Orphan files**: files with zero backlinks, hard to discover
+- **Structural issues**: wrong directory, missing READMEs, aging Inbox files
+
 ---
 
 ## Error handling (CLI)

package/skills/mindos/references/knowledge-health.md

@@ -0,0 +1,120 @@
+# Knowledge Health Check
+
+When the user asks to check KB health, detect conflicts, or audit knowledge quality, follow this guide.
+
+## Dimensions
+
+### 1. Contradictions / Conflicts
+
+Two or more files state conflicting facts about the same topic (e.g., one says "rate limit = 100/min", another says "rate limit = 200/min" without distinguishing context).
+
+**Detection procedure:**
+1. Identify the topic scope (user may specify, or scan recent edits)
+2. Search for all files related to the topic (2-4 keyword variants)
+3. Read each hit and extract key claims/decisions
+4. Compare claims across files — flag any pair that contradicts
+5. Present conflicts to user with file paths and quotes
+
+**Resolution:** Ask user which version is authoritative. Update or annotate the non-authoritative file to reference the correct source. Never silently overwrite.
+
+### 2. Orphan References
+
+A file links to another file that no longer exists (broken `[[link]]` or markdown link).
+
+**Detection procedure:**
+1. List all files in KB
+2. For each file, extract all internal links (markdown links, wiki-links)
+3. Check if each link target exists
+4. Report broken links with source file path and line
+
+**Resolution:** Either remove the dead link, or recreate the missing file if the content is recoverable from git history.
+
+### 3. Stale / Outdated Content
+
+Files with explicit date markers (e.g., "Last verified: 2025-01-15") that are significantly old, or files whose topic has clearly evolved but the file hasn't been updated.
+
+**Detection procedure:**
+1. Search for date markers: "Last verified", "Last updated", "截止日期", "更新时间"
+2. Flag any file where the marker date is >90 days old
+3. Also check `mindos file history <path>` — files untouched for >6 months with active topics are suspects
+
+**Resolution:** Present the list to user. For each stale file, ask: still accurate? update? archive?
+
+### 4. Duplicate Content
+
+Two files covering the same topic with substantial overlap, neither referencing the other.
+
+**Detection procedure:**
+1. Search for the topic from multiple angles
+2. If two files return as top results for the same query, read both
+3. Compare: are they covering the same ground? Is one a superset of the other?
+4. Flag duplicates with a similarity summary
+
+**Resolution:** Merge into one authoritative file. Convert the other into a redirect/link. Never delete without confirmation.
+
+### 5. Orphan Files
+
+Files that no other file references — isolated knowledge that may be hard to discover.
+
+**Detection procedure:**
+1. For each file, run `mindos file backlinks <path>`
+2. Files with zero backlinks AND not in a well-indexed directory (no README listing them) are orphan candidates
+3. Exclude governance files (INSTRUCTION.md, README.md) and root-level files
+
+**Resolution:** Suggest adding links from relevant parent documents or READMEs.
+
+### 6. Structural Issues
+
+- Files in wrong directories (content doesn't match the directory's topic)
+- Inbox files that have been sitting >7 days (aging)
+- Missing READMEs in directories with >3 files
+- Inconsistent naming conventions within a directory
+
+**Detection procedure:**
+1. Bootstrap the KB tree
+2. For each directory: check if README exists, read a sample of files to verify topic consistency
+3. Check Inbox for aging files (>7 days)
+4. Spot-check naming patterns per directory
+
+## Health Report Format
+
+Present findings as a structured report:
+
+```markdown
+# Knowledge Health Report — {date}
+
+## Summary
+- Contradictions found: N
+- Broken links: N
+- Stale files (>90 days): N
+- Duplicates suspected: N
+- Orphan files: N
+- Structural issues: N
+- **Overall health: {Good / Needs Attention / Critical}**
+
+## Contradictions
+1. `file-a.md` vs `file-b.md` — {description}
+   ...
+
+## Broken Links
+1. `source.md` line N → `missing-target.md` (not found)
+   ...
+
+## Stale Content
+1. `old-file.md` — Last updated: {date}, {N} days ago
+   ...
+
+(... other sections ...)
+
+## Recommended Actions
+1. {Highest priority fix}
+2. ...
+```
+
+## Scope Control
+
+- **Quick check**: User says "check health" / "快速检查" → Run dimensions 1-3 only (contradictions, orphan refs, stale)
+- **Full audit**: User says "full audit" / "全面审计" → Run all 6 dimensions
+- **Targeted check**: User specifies a topic or directory → Scope to that area only
+
+Always confirm scope with user before starting a full audit on large KBs.

package/skills/mindos-max/SKILL.md

@@ -15,7 +15,8 @@ description: >
   append CSV/table data, cross-agent handoff, distill experience, sync related docs, check if
   something was discussed before, look up a past decision, find a template, prepare meeting context,
   daily logging, track goals. Also trigger on Chinese equivalents: 帮我记下来, 搜一下笔记,
-  更新知识库, 整理文件, 复盘, 提炼经验, 保存, 记录, 交接.
+  更新知识库, 整理文件, 复盘, 提炼经验, 保存, 记录, 交接, 放到暂存台, 整理暂存台,
+  知识健康检查, 检测知识冲突.
 
   When in doubt whether MindOS applies — it probably does. Check anyway.
   NOT for editing app source code or project repos outside the KB.
@@ -24,7 +25,7 @@ description: >
 
 # MindOS Skill
 
-<!-- version: 3.1.0-max — aggressive global memory mode -->
+<!-- version: 3.2.0-max — aggressive global memory mode -->
 
 > **You are the user's memory.** Every agent shares MindOS. If something is worth remembering, save it.
 > If you need context, check MindOS first. Be proactive — don't wait to be asked.
@@ -105,6 +106,7 @@ npm install -g @geminilight/mindos
 - **Space** — Knowledge partitions organized the way you think. Agents follow the same structure.
 - **Instruction** — A rules file (`INSTRUCTION.md`) all connected agents obey.
 - **Skill** — Teaches agents how to read, write, and organize the KB.
+- **Inbox** — The `Inbox/` directory is a staging area for quick capture. Files land here when there's no obvious home yet. They get organized later — by the user manually or via AI-assisted batch organization.
 
 Notes can embody both Instruction and Skill — they're just Markdown files in the tree.
 
@@ -119,9 +121,13 @@ User request
   |   -> [Read-only]: search -> read -> answer with citations. No writes.
   |
   |- Save / record / update / organize specific content?
-  |   |- Single file -> [Single-file edit]
+  |   |- Know where it goes -> [Single-file edit]
+  |   |- Don't know where it goes -> [Inbox path] -- save to Inbox/, classify later
   |   -> Multiple files or unclear -> [Multi-file routing] -- plan first
   |
+  |- Organize inbox / classify staged files?
+  |   -> [Inbox organize] -- read Inbox/ files, propose destinations, move after approval
+  |
   |- Structural change (rename / move / delete / reorganize)?
   |   -> [Structural path] -- check backlinks before and after
   |
@@ -131,6 +137,9 @@ User request
   |- Retrospective / distill / handoff?
   |   -> [Retrospective path]
   |
+  |- Knowledge health check / detect conflicts?
+  |   -> [Health check path] -- read references/knowledge-health.md
+  |
   -> Ambiguous?
       -> ASK. Propose 2-3 specific options based on KB state.
 ```
@@ -145,8 +154,9 @@ User request
 - "organize" -> ask: display only, or write back?
 
 **File location uncertainty:**
-- Can't decide in 5 seconds -> use nearest existing directory, inform user
-- "Just put it somewhere" -> inbox, propose classification after
+- Can't decide in 5 seconds -> save to `Inbox/`, inform user, propose classification later
+- "Just put it somewhere" / "先放着" -> save to `Inbox/`
+- User drags files or pastes unstructured content without specifying location -> `Inbox/`
 
 **Scope creep:**
 - Input routes to >5 files -> pause, confirm scope
@@ -179,6 +189,43 @@ When user expresses a standing preference -> read [references/preference-capture
 
 When creating/rewriting an SOP -> read [references/sop-template.md](../mindos/references/sop-template.md).
 
+## Inbox (staging area)
+
+The `Inbox/` directory is the KB's quick-capture zone. It has its own `INSTRUCTION.md` that governs behavior.
+
+**When to use Inbox:**
+- User says "just save it" / "先放着" / "放到暂存台" without specifying a location
+- Content doesn't clearly fit any existing Space or directory
+- Batch import of multiple files that need individual classification
+
+**How to save to Inbox:**
+```bash
+mindos file create "Inbox/<filename>.md" --content "..."
+```
+
+**How to organize Inbox:**
+1. List Inbox files: `mindos file list Inbox/`
+2. Read each file to understand its content
+3. For each file, propose the best destination directory based on KB structure
+4. Present the full routing plan to user for approval
+5. Move files: `mindos file rename "Inbox/<file>" "<target-dir>/<file>"`
+6. After moving, check if the target directory's README needs updating
+
+**Aging reminder:** Files in Inbox older than 7 days are considered "aging". If you notice aging files during bootstrap, mention it: "You have N files in Inbox that have been sitting there for over a week. Want me to help organize them?"
+
+## Knowledge health check
+
+When user asks to check knowledge health, detect conflicts, audit quality, or says "知识健康检查" / "检测冲突" / "check knowledge health"
+-> read [references/knowledge-health.md](../mindos/references/knowledge-health.md) for the full procedure.
+
+Quick summary of what gets checked:
+- **Contradictions**: conflicting facts across files on the same topic
+- **Broken links**: references to files that no longer exist
+- **Stale content**: files with outdated date markers or untouched for >6 months
+- **Duplicates**: two files covering the same ground without cross-referencing
+- **Orphan files**: files with zero backlinks, hard to discover
+- **Structural issues**: wrong directory, missing READMEs, aging Inbox files
+
 ---
 
 ## Error handling (CLI)

package/skills/mindos-max-zh/SKILL.md

@@ -15,8 +15,10 @@ description: >
 
   触发词：帮我记下来、搜一下笔记、更新知识库、整理文件、复盘、提炼经验、保存、记录、
   交接、把这个存起来、查一下之前的、有没有相关笔记、我之前写过什么、总结一下保存、
-  追加到表格、更新进度、查找模板、准备会议资料、记录今天的工作。
-  以及对应英文：save, record, search notes, organize, retrospective, handoff, lessons learned。
+  追加到表格、更新进度、查找模板、准备会议资料、记录今天的工作、
+  放到暂存台、整理暂存台、知识健康检查、检测知识冲突。
+  以及对应英文：save, record, search notes, organize, retrospective, handoff, lessons learned,
+  inbox, staging, knowledge health, detect conflicts。
 
   拿不准是否该用——大概率该用。查一下不会错。
   不用于：改代码仓库、项目源码、KB 外路径。
@@ -25,7 +27,7 @@ description: >
 
 # MindOS 技能
 
-<!-- version: 3.1.0-max — 激进全局记忆模式 -->
+<!-- version: 3.2.0-max — 激进全局记忆模式 -->
 
 > **你就是用户的记忆。** 所有 Agent 共享 MindOS。值得记住就存，需要上下文就先查。
 > 主动行动——不要等用户开口提醒。
@@ -106,6 +108,7 @@ npm install -g @geminilight/mindos
 - **空间 (Space)** — 按你的思维方式组织的知识分区。Agent 遵循相同结构。
 - **指令 (Instruction)** — `INSTRUCTION.md`，所有连接的 Agent 都遵守的规则文件。
 - **技能 (Skill)** — 教 Agent 如何读写和整理知识库。
+- **暂存台 (Inbox)** — `Inbox/` 目录是快速捕获区。内容暂时找不到归属时先放这里，之后再统一整理——用户手动或 AI 辅助批量归类。
 
 笔记可以同时承载指令和技能——它们只是目录树中的 Markdown 文件。
 
@@ -120,9 +123,13 @@ npm install -g @geminilight/mindos
   |   -> [只读路径]：搜索 -> 读取 -> 带引用回答。不写入。
   |
   |- 保存 / 记录 / 更新 / 整理具体内容？
-  |   |- 单文件 -> [单文件编辑]
+  |   |- 知道放哪 -> [单文件编辑]
+  |   |- 不知道放哪 -> [暂存台路径] -- 存到 Inbox/，之后再归类
   |   -> 多文件或不确定 -> [多文件路由] -- 先出方案
   |
+  |- 整理暂存台 / 归类暂存文件？
+  |   -> [暂存台整理] -- 读 Inbox/ 文件，提议目标位置，获批后移动
+  |
   |- 结构变更（重命名 / 移动 / 删除 / 重组）？
   |   -> [结构路径] -- 变更前后检查反向链接
   |
@@ -132,6 +139,9 @@ npm install -g @geminilight/mindos
   |- 复盘 / 提炼 / 交接？
   |   -> [复盘路径]
   |
+  |- 知识健康检查 / 检测冲突？
+  |   -> [健康检查路径] -- 读取 references/knowledge-health.md
+  |
   -> 模糊？
       -> 提问。基于知识库状态提出 2-3 个具体选项。
 ```
@@ -146,8 +156,9 @@ npm install -g @geminilight/mindos
 - "整理一下" -> 先问：仅展示，还是写回知识库？
 
 **文件位置不确定：**
-- 5 秒内定不了 -> 用最近的现有目录，告知用户
-- "随便放哪" -> 收件箱，之后提议分类
+- 5 秒内定不了 -> 存到 `Inbox/`，告知用户，之后提议归类
+- "随便放哪" / "先放着" -> 存到 `Inbox/`
+- 用户拖拽文件或粘贴非结构化内容但没指定位置 -> `Inbox/`
 
 **范围蔓延：**
 - 输入路由到 >5 个文件 -> 暂停确认
@@ -180,6 +191,44 @@ npm install -g @geminilight/mindos
 
 创建/重写工作流 SOP 时 -> 读取 [references/sop-template.md](../mindos/references/sop-template.md)。
 
+## 暂存台 (Inbox)
+
+`Inbox/` 目录是知识库的快速捕获区，有自己的 `INSTRUCTION.md` 约束行为。
+
+**何时使用暂存台：**
+- 用户说"先存着" / "放到暂存台" / "随便放哪"，没指定具体位置
+- 内容明显不属于任何现有空间或目录
+- 批量导入多个文件，需要逐个归类
+
+**如何存到暂存台：**
+```bash
+mindos file create "Inbox/<文件名>.md" --content "..."
+```
+
+**如何整理暂存台：**
+1. 列出暂存文件：`mindos file list Inbox/`
+2. 读取每个文件，理解其内容
+3. 根据知识库结构，为每个文件提议最佳目标目录
+4. 向用户展示完整路由方案，获批后执行
+5. 移动文件：`mindos file rename "Inbox/<文件>" "<目标目录>/<文件>"`
+6. 移动后检查目标目录的 README 是否需要更新
+
+**老化提醒：** Inbox 中超过 7 天的文件视为"老化"。如果在 bootstrap 时发现老化文件，主动提醒：
+"暂存台有 N 个文件已经放了一周以上了，要我帮你整理一下吗？"
+
+## 知识健康检查
+
+用户要求检查知识库健康度、检测冲突、审计质量，或说"知识健康检查" / "检测冲突" / "check knowledge health" 时
+-> 读取 [references/knowledge-health.md](../mindos/references/knowledge-health.md) 获取完整流程。
+
+检查维度速览：
+- **矛盾/冲突**：同一主题的不同文件说法互相矛盾
+- **断裂链接**：引用了不存在的文件
+- **过期内容**：带有过期日期标记的文件，或超过 6 个月未更新的活跃主题
+- **重复内容**：两个文件覆盖同一主题且没有互相引用
+- **孤立文件**：零反向链接，难以被发现
+- **结构问题**：文件放错目录、缺少 README、暂存台老化文件
+
 ---
 
 ## 错误处理（CLI）