@geminilight/mindos 0.6.58 → 0.6.59

package/app/hooks/useAskSession.ts

@@ -227,6 +227,20 @@ export function useAskSession(currentFile?: string) {
     });
   }, []);
 
+  /** Toggle pin/unpin a session. Pinned sessions sort to top. */
+  const togglePinSession = useCallback((id: string) => {
+    setSessions((prev) => {
+      const idx = prev.findIndex((s) => s.id === id);
+      if (idx < 0) return prev;
+      const updated = { ...prev[idx], pinned: !prev[idx].pinned };
+      const next = [...prev];
+      next[idx] = updated;
+      // Only persist if session has messages
+      if (updated.messages.length > 0) void upsertSession(updated);
+      return next;
+    });
+  }, []);
+
   const clearAllSessions = useCallback(() => {
     // Only delete sessions that have messages (were persisted)
     const persistedIds = sessions.filter(s => s.messages.length > 0).map(s => s.id);
@@ -239,10 +253,17 @@ export function useAskSession(currentFile?: string) {
     // No upsertSession — memory only
   }, [currentFile, sessions]);
 
+  /** Sessions sorted: pinned first, then by updatedAt desc */
+  const sortedSessions = [...sessions].sort((a, b) => {
+    if (a.pinned && !b.pinned) return -1;
+    if (!a.pinned && b.pinned) return 1;
+    return b.updatedAt - a.updatedAt;
+  });
+
   return {
     messages,
     setMessages,
-    sessions,
+    sessions: sortedSessions,
     activeSessionId,
     initSessions,
     persistSession,
@@ -251,6 +272,7 @@ export function useAskSession(currentFile?: string) {
     loadSession,
     deleteSession,
     renameSession,
+    togglePinSession,
     clearAllSessions,
   };
 }

package/app/lib/i18n/modules/ai-chat.ts

@@ -6,7 +6,12 @@ export const aiChatEn = {
     fabLabel: 'Ask AI',
     placeholder: 'Ask a question... @ files, / skills',
     emptyPrompt: 'How can I help?',
-    emptyHint: 'Type @ to reference files · / to use skills',
+    emptyHint: 'Type @ to reference files · / to use skills · drag images',
+    executingTool: 'Executing tool…',
+    toolRunning: 'Running...',
+    copyMessage: 'Copy',
+    toolInput: 'Input',
+    toolOutput: 'Output',
     send: 'send',
     newlineHint: 'new line',
     panelComposerResize: 'Drag up to enlarge the input area',
@@ -36,10 +41,49 @@ export const aiChatEn = {
     proxyCompatAlsoFailed: (err: string) => `Compatibility mode also failed: ${err}. Please check your Base URL, API key, and model name.`,
     retry: 'Retry',
     suggestions: [
-      'Summarize this document',
-      'Organize my recent notes',
-      'Find related notes',
-      'Draft a new note',
+      { label: 'Organize inbox', prompt: 'Organize my inbox files into the right spaces' },
+      { label: 'Research a topic', prompt: 'Research the latest trends in AI agents' },
+      { label: 'Draft weekly review', prompt: 'Draft a weekly review based on my recent notes' },
+      { label: 'Brainstorm ideas', prompt: 'Brainstorm 3 creative ideas for my next project' },
+    ],
+    /** Categorized prompts for homepage explore section */
+    homeCategories: [
+      {
+        label: 'Knowledge',
+        items: [
+          { label: 'Organize into Spaces', desc: 'Sort scattered notes by topic', prompt: 'Help me organize my recent unstructured notes into appropriate spaces with proper tags' },
+          { label: 'Sync & Deduplicate', desc: 'Clean up cross-platform overlap', prompt: 'Find duplicate or overlapping content across my spaces and help me consolidate them' },
+          { label: 'Auto-tag & Categorize', desc: 'Add structure to raw notes', prompt: 'Review my untagged notes and suggest categories and tags for each' },
+          { label: 'Weekly Digest', desc: 'Summarize this week\'s changes', prompt: 'Summarize everything I added or changed this week across all spaces' },
+        ],
+      },
+      {
+        label: 'Writing',
+        items: [
+          { label: 'Blog from Notes', desc: 'Turn drafts into polished posts', prompt: 'Turn my draft notes into a polished blog post with clear structure' },
+          { label: 'Product Copy', desc: 'Landing page & descriptions', prompt: 'Write compelling product description and landing page copy based on my notes' },
+          { label: 'Polish & Refine', desc: 'Improve clarity and tone', prompt: 'Review this document for clarity, tone, and structure, then rewrite the weak parts' },
+          { label: 'Slide Deck Outline', desc: 'Presentation structure from notes', prompt: 'Create a slide deck outline from my notes on this topic' },
+        ],
+      },
+      {
+        label: 'Analysis',
+        items: [
+          { label: 'Competitive Overview', desc: 'Compare products & differentiators', prompt: 'Compare the products in my research notes and identify key differentiators' },
+          { label: 'Extract Insights', desc: 'Patterns across reading notes', prompt: 'What are the most important insights and patterns across my reading notes?' },
+          { label: 'Decision Framework', desc: 'Pros, cons, recommendation', prompt: 'Help me structure this decision with pros, cons, risks, and a recommendation' },
+          { label: 'GTM Strategy', desc: 'Go-to-market from research', prompt: 'Help me build a go-to-market plan based on my product and market research notes' },
+        ],
+      },
+      {
+        label: 'Innovation',
+        items: [
+          { label: 'Challenge My Assumptions', desc: 'Find blind spots in my thinking', prompt: 'Review my notes and challenge the key assumptions I\'m making. What am I missing?' },
+          { label: 'What If Scenarios', desc: 'Explore alternative futures', prompt: 'Based on my research, generate 3 contrarian "what if" scenarios I haven\'t considered' },
+          { label: 'Combine & Remix Ideas', desc: 'Cross-pollinate across domains', prompt: 'Find unexpected connections between ideas in different spaces and suggest novel combinations' },
+          { label: 'Spot the Opportunity', desc: 'Gaps others are missing', prompt: 'Analyze my market research notes and identify underserved niches or emerging opportunities' },
+        ],
+      },
     ],
     modeChat: 'Chat',
     modeAgent: 'Agent',
@@ -145,7 +189,12 @@ export const aiChatZh = {
     fabLabel: 'AI 助手',
     placeholder: '输入问题… @ 附加文件，/ 技能',
     emptyPrompt: '有什么可以帮你？',
-    emptyHint: '输入 @ 引用文件 · / 使用技能',
+    emptyHint: '输入 @ 引用文件 · / 使用技能 · 拖拽图片',
+    executingTool: '正在执行工具…',
+    toolRunning: '运行中...',
+    copyMessage: '复制',
+    toolInput: '输入',
+    toolOutput: '输出',
     send: '发送',
     newlineHint: '换行',
     panelComposerResize: '向上拖拽以拉高输入区',
@@ -175,10 +224,48 @@ export const aiChatZh = {
     proxyCompatAlsoFailed: (err: string) => `兼容模式也失败了：${err}。请检查 Base URL、API Key 和模型名称。`,
     retry: '重试',
     suggestions: [
-      '总结这篇文档',
-      '整理最近的笔记',
-      '查找相关笔记',
-      '起草一篇新笔记',
+      { label: '整理收件箱', prompt: '把收件箱的文件整理到对应空间' },
+      { label: '调研一个话题', prompt: '调研一下 AI Agent 的最新趋势' },
+      { label: '起草周报', prompt: '根据最近的笔记起草一份周报' },
+      { label: '想新 idea', prompt: '为我的下一个项目想 3 个新 idea' },
+    ],
+    homeCategories: [
+      {
+        label: '知识管理',
+        items: [
+          { label: '整理到 Space', desc: '按主题归类零散笔记', prompt: '帮我把最近的零散笔记整理到合适的 Space，并打好标签' },
+          { label: '同步去重', desc: '清理跨平台重复内容', prompt: '找出我各个 Space 中重复或重叠的内容，帮我合并整理' },
+          { label: '自动打标签', desc: '给未分类笔记加结构', prompt: '检查我未标记的笔记，建议合适的分类和标签' },
+          { label: '每周摘要', desc: '汇总本周变更', prompt: '总结我这周在所有 Space 中新增和修改的内容' },
+        ],
+      },
+      {
+        label: '内容创作',
+        items: [
+          { label: '笔记变博客', desc: '草稿变成精修文章', prompt: '把我的草稿笔记改写成一篇结构清晰的博客文章' },
+          { label: '产品文案', desc: '落地页与产品描述', prompt: '根据我的笔记写一段有吸引力的产品描述和落地页文案' },
+          { label: '润色优化', desc: '提升清晰度和语气', prompt: '审阅这篇文档的清晰度、语气和结构，重写不好的部分' },
+          { label: '演示大纲', desc: '从笔记生成演讲结构', prompt: '根据我关于这个主题的笔记，创建一个演示文稿大纲' },
+        ],
+      },
+      {
+        label: '分析洞察',
+        items: [
+          { label: '竞品对比', desc: '比较产品差异化', prompt: '对比我调研笔记中的产品，找出关键差异点' },
+          { label: '提炼洞察', desc: '发现阅读笔记中的规律', prompt: '我的阅读笔记中有哪些最重要的见解和规律？' },
+          { label: '决策框架', desc: '利弊分析与建议', prompt: '帮我用利弊、风险和建议来结构化这个决策' },
+          { label: 'GTM 策略', desc: '从调研到上市方案', prompt: '根据我的产品和市场调研笔记，帮我制定一份上市计划' },
+        ],
+      },
+      {
+        label: '启发创新',
+        items: [
+          { label: '挑战假设', desc: '找出思维盲点', prompt: '审视我的笔记，挑战我正在做的关键假设。我遗漏了什么？' },
+          { label: '反常识探索', desc: '探索替代可能性', prompt: '根据我的调研，生成 3 个我没考虑过的反常识场景' },
+          { label: '跨域融合', desc: '不同领域的创意碰撞', prompt: '在我不同 Space 的想法中找到意想不到的联系，并建议新颖的组合' },
+          { label: '发现机会', desc: '别人没看到的空白', prompt: '分析我的市场调研笔记，找出未被充分服务的小众市场或新兴机会' },
+        ],
+      },
     ],
     modeChat: '对话',
     modeAgent: 'Agent',

package/app/lib/i18n/modules/onboarding.ts

@@ -174,17 +174,17 @@ export const onboardingEn = {
       button: 'Import Files',
     },
     ai: {
-      title: 'See AI read your content',
+      title: 'Save with AI',
       cta: 'Try it',
-      desc: 'Your files are in the knowledge base. Ask MindOS Agent what it learned:',
-      prompt: 'Introduce me based on my knowledge base — who am I and what am I working on?',
+      desc: 'Ask MindOS Agent to capture knowledge from this conversation into your KB:',
+      prompt: 'Help me distill the key takeaways from our conversation into a reusable SOP in my knowledge base.',
       promptEmpty: 'Help me design a knowledge base folder structure that fits my needs',
     },
     agent: {
-      title: 'Try in another Agent',
+      title: 'Connect other Agents',
       cta: 'Copy prompt',
-      desc: 'Open Cursor, Claude Code, or any MCP-connected Agent and paste this:',
-      copyPrompt: 'Read my MindOS knowledge base and summarize my background, then suggest what I should focus on next.',
+      desc: 'Open Cursor, Claude Code, or any Agent with MindOS CLI and paste:',
+      copyPrompt: 'Summarize what we discussed and save it to my MindOS knowledge base as a reusable SOP.',
       copy: 'Copy',
       copied: 'Copied!',
     },
@@ -396,17 +396,17 @@ export const onboardingZh = {
       button: '导入文件',
     },
     ai: {
-      title: '感受 AI 读取内容',
+      title: 'AI 帮你沉淀',
       cta: '试试',
-      desc: '你的文件已在知识库中。问问 MindOS Agent 它了解了什么：',
-      prompt: '根据我的知识库介绍一下我——我是谁、在做什么？',
+      desc: '让 MindOS Agent 把对话中的经验沉淀到知识库：',
+      prompt: '帮我把这次对话的关键收获整理成一份可复用的 SOP，存到我的知识库里。',
       promptEmpty: '帮我设计一个适合我的知识库目录结构',
     },
     agent: {
-      title: '在其他 Agent 验证',
+      title: '连接其他 Agent',
       cta: '复制提示词',
-      desc: '打开 Cursor、Claude Code 或任意连接了 MCP 的 Agent，粘贴以下提示词：',
-      copyPrompt: '读取我的 MindOS 知识库，概括我的背景，然后建议我接下来该做什么。',
+      desc: '打开 Cursor、Claude Code 或任意 MCP Agent，粘贴以下提示词，让知识流入 MindOS：',
+      copyPrompt: '把我们刚才讨论的内容总结一下，存到我的 MindOS 知识库里，形成可复用的 SOP。',
       copy: '复制',
       copied: '已复制！',
     },

package/app/lib/stores/LocaleStoreInit.tsx

@@ -1,14 +1,37 @@
 'use client';
 
-import { useEffect } from 'react';
+import { useEffect, useRef } from 'react';
 import { useLocaleStore } from '@/lib/stores/locale-store';
 import type { Locale } from '@/lib/i18n';
+import { messages } from '@/lib/i18n';
 
 /**
  * Initializes locale store with SSR value and attaches event listeners.
  * Renders nothing. Place once near the root.
+ *
+ * During the first client render, synchronously updates the Zustand store
+ * to match ssrLocale (from server cookie). This ensures the first client
+ * render produces identical HTML to the server, preventing hydration mismatch.
+ * After hydration, _init() reconciles with localStorage/navigator for
+ * the true client preference.
  */
 export default function LocaleStoreInit({ ssrLocale }: { ssrLocale: Locale }) {
+  const didSync = useRef(false);
+
+  // Synchronous store update during first render — before React commits.
+  // The store defaults to 'en'; if ssrLocale is 'zh' (from cookie), update
+  // immediately so all sibling/child components read 'zh' in the same pass.
+  if (!didSync.current) {
+    didSync.current = true;
+    const state = useLocaleStore.getState();
+    if (state.locale !== ssrLocale) {
+      useLocaleStore.setState({
+        locale: ssrLocale,
+        t: messages[ssrLocale] as unknown as typeof state.t,
+      });
+    }
+  }
+
   useEffect(() => {
     const cleanup = useLocaleStore.getState()._init(ssrLocale);
     return cleanup;

package/app/lib/stores/locale-store.ts

@@ -22,23 +22,37 @@ function getLocaleSnapshot(): Locale {
   return navigator.language.startsWith('zh') ? 'zh' : 'en';
 }
 
+/**
+ * Read the locale that the inline <script> in layout.tsx already resolved.
+ * Returns 'en' to match SSR default — the LocaleStoreInit component
+ * reconciles to the real locale synchronously before first commit.
+ */
+function getPreHydrateLocale(): Locale {
+  return 'en';
+}
+
+const initialLocale = getPreHydrateLocale();
+
 export const useLocaleStore = create<LocaleStoreState>((set) => ({
-  locale: 'en',
-  t: messages['en'] as unknown as Messages,
+  locale: initialLocale,
+  t: messages[initialLocale] as unknown as Messages,
 
   setLocale: (l: Locale) => {
     document.cookie = `locale=${l};path=/;max-age=31536000;SameSite=Lax`;
     document.documentElement.lang = l === 'zh' ? 'zh' : 'en';
+    (window as any).__mindos_locale__ = l;
     set({ locale: l, t: messages[l] as unknown as Messages });
     window.dispatchEvent(new Event('mindos-locale-change'));
   },
 
   _init: (ssrLocale: Locale) => {
-    // Hydrate with client value (or SSR fallback)
-    const clientLocale = typeof window !== 'undefined' ? getLocaleSnapshot() : ssrLocale;
-    set({ locale: clientLocale, t: messages[clientLocale] as unknown as Messages });
+    // Reconcile: if client localStorage disagrees with current store, update once
+    const clientLocale = getLocaleSnapshot();
+    const current = useLocaleStore.getState().locale;
+    if (clientLocale !== current) {
+      set({ locale: clientLocale, t: messages[clientLocale] as unknown as Messages });
+    }
 
-    // Listen for external changes (e.g. localStorage change in another tab, or pre-hydration script)
     const handler = () => {
       const l = getLocaleSnapshot();
       set({ locale: l, t: messages[l] as unknown as Messages });

package/app/lib/types.ts

@@ -87,4 +87,5 @@ export interface ChatSession {
   createdAt: number;
   updatedAt: number;
   messages: Message[];
+  pinned?: boolean;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@geminilight/mindos",
-  "version": "0.6.58",
+  "version": "0.6.59",
   "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.