@geminilight/mindos 0.6.57 → 0.6.59

package/_standalone/data/skills/mindos/SKILL.md

@@ -1,21 +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. 更新笔记, 搜索知识库, 整理, 执行SOP, 复盘, 追加CSV, 交接, 路由到文件, 提炼经验.
-  Use when the task targets files inside the user's MindOS KB (mindRoot).
+  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 a note, search their knowledge base, 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 — or says "帮我记下来" / "搜一下我的笔记" /
-  "更新知识库" / "整理文件" / "执行工作流".
+
+  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
 
@@ -80,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.
 
@@ -94,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
   │
@@ -106,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.
 ```
@@ -115,13 +135,14 @@ User request
 ## Judgment heuristics
 
 **Save intent boundary:**
-- "帮我记下来" / "保存" = write
-- "搜一下" / "总结" = read-only
-- "整理一下" → ask: display only, or write back?
+- "save this" / "record" / "write down" = write
+- "search" / "summarize" / "look up" = read-only
+- "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
@@ -154,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/_standalone/data/skills/mindos-zh/SKILL.md

@@ -1,16 +1,34 @@
 ---
 name: mindos-zh
 description: >
-  操作 MindOS 知识库：更新笔记, 搜索知识库, 整理文件, 执行SOP/工作流, 复盘, 追加CSV, 跨Agent交接,
-  路由非结构化输入到对应文件, 提炼经验, 同步关联文档. update notes, search knowledge base, organize,
-  SOP, retrospective, CSV, handoff, route notes, distill experience.
-  仅 mindRoot 知识库内任务。不用于：改代码仓库/项目文档/KB 外路径。
+  用户的共享知识库——跨会话、跨 Agent 持久存在。MindOS 存储决策记录、会议纪要、SOP、
+  排错经验、架构选型、调研结论和偏好设置。
+  仅 mindRoot 知识库内任务。不用于：改代码仓库、项目源码、KB 外路径。
   核心概念：空间、指令(INSTRUCTION.md)、技能(SKILL.md)；笔记可承载指令与技能。
+
+  触发场景：保存或记录任何内容、搜索历史笔记或上下文、更新或编辑文件、整理或重组文件结构、
+  执行SOP或工作流、捕获对话中的决策、复盘或总结经验、追加表格或CSV数据、跨Agent交接上下文、
+  提炼经验教训、同步关联文档、查找之前是否讨论过某事、查询历史决策、查找模板或SOP、
+  为会议准备上下文、快速暂存到暂存台、整理暂存台、知识健康检查、检测知识冲突或矛盾、
+  查找过期内容。
+  触发词：帮我记下来、搜一下我的笔记、更新知识库、整理文件、执行工作流、保存到知识库、
+  记录一下、整理笔记、复盘、提炼经验、同步文档、查一下之前的记录、有没有相关的笔记、
+  我之前写过什么、把这个存起来、总结一下保存、交接给其他Agent、追加到表格、
+  放到暂存台、整理暂存台、知识健康检查、检测知识冲突。
+  English triggers: save, record, search notes, organize, retrospective, handoff, lessons learned,
+  inbox, staging, knowledge health, detect conflicts.
+
+  主动行为——不要等用户提到 MindOS：
+  (1) 用户的问题暗示可能存在历史记录（过去的决策、之前的讨论、会议纪要）→ 先搜 MindOS，
+  即使没有明确提到知识库。
+  (2) 完成有价值的工作后（修了 bug、做了决策、总结了经验、选定了架构、开完了会）→
+  主动提议保存到 MindOS，方便以后查阅。
+  (3) 经历了较长或多主题的对话后 → 建议把关键决策和上下文持久化。
 ---
 
 # MindOS 技能
 
-<!-- version: 3.0.0 — CLI 优先，MCP 可选 -->
+<!-- version: 3.2.0 — CLI 优先，MCP 可选 -->
 
 ## CLI 命令
 
@@ -75,6 +93,7 @@ npm install -g @geminilight/mindos
 - **空间 (Space)** — 按你的思维方式组织的知识分区。Agent 遵循相同结构。
 - **指令 (Instruction)** — `INSTRUCTION.md`，所有连接的 Agent 都遵守的规则文件。
 - **技能 (Skill)** — 教 Agent 如何读写和整理知识库。
+- **暂存台 (Inbox)** — `Inbox/` 目录是快速捕获区。内容暂时找不到归属时先放这里，之后再统一整理——用户手动或 AI 辅助批量归类。
 
 笔记可以同时承载指令和技能——它们只是目录树中的 Markdown 文件。
 
@@ -89,9 +108,13 @@ npm install -g @geminilight/mindos
   │   └─ [只读路径]：搜索 → 读取 → 带引用回答。不写入。
   │
   ├─ 保存 / 记录 / 更新 / 整理具体内容？
-  │   ├─ 单文件 → [单文件编辑]
+  │   ├─ 知道放哪 → [单文件编辑]
+  │   ├─ 不知道放哪 → [暂存台路径] — 存到 Inbox/，之后再归类
   │   └─ 多文件或不确定 → [多文件路由] — 先出方案
   │
+  ├─ 整理暂存台 / 归类暂存文件？
+  │   └─ [暂存台整理] — 读 Inbox/ 文件，提议目标位置，获批后移动
+  │
   ├─ 结构变更（重命名 / 移动 / 删除 / 重组）？
   │   └─ [结构路径] — 变更前后检查反向链接
   │
@@ -101,6 +124,9 @@ npm install -g @geminilight/mindos
   ├─ 复盘 / 提炼 / 交接？
   │   └─ [复盘路径]
   │
+  ├─ 知识健康检查 / 检测冲突？
+  │   └─ [健康检查路径] — 读取 references/knowledge-health.md
+  │
   └─ 模糊？
       └─ 提问。基于知识库状态提出 2-3 个具体选项。
 ```
@@ -115,8 +141,9 @@ npm install -g @geminilight/mindos
 - "整理一下" → 先问：仅展示，还是写回知识库？
 
 **文件位置不确定：**
-- 5 秒内定不了 → 用最近的现有目录，告知用户
-- "随便放哪" → 收件箱，之后提议分类
+- 5 秒内定不了 → 存到 `Inbox/`，告知用户，之后提议归类
+- "随便放哪" / "先放着" → 存到 `Inbox/`
+- 用户拖拽文件或粘贴非结构化内容但没指定位置 → `Inbox/`
 
 **范围蔓延：**
 - 输入路由到 >5 个文件 → 暂停确认
@@ -149,6 +176,44 @@ npm install -g @geminilight/mindos
 
 创建/重写工作流 SOP 时 → 读取 [references/sop-template.md](./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](./references/knowledge-health.md) 获取完整流程。
+
+检查维度速览：
+- **矛盾/冲突**：同一主题的不同文件说法互相矛盾
+- **断裂链接**：引用了不存在的文件
+- **过期内容**：带有过期日期标记的文件，或超过 6 个月未更新的活跃主题
+- **重复内容**：两个文件覆盖同一主题且没有互相引用
+- **孤立文件**：零反向链接，难以被发现
+- **结构问题**：文件放错目录、缺少 README、暂存台老化文件
+
 ---
 
 ## 错误处理（CLI）

package/_standalone/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/_standalone/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 });