@geminilight/mindos 0.6.29 → 0.6.31

package/app/lib/settings.ts

@@ -1,6 +1,7 @@
 import fs from 'fs';
 import path from 'path';
 import os from 'os';
+import { parseAcpAgentOverrides } from './acp/agent-descriptors';
 
 const SETTINGS_PATH = path.join(os.homedir(), '.mindos', 'config.json');
 
@@ -49,6 +50,8 @@ export interface ServerSettings {
   setupPending?: boolean;  // true → / redirects to /setup
   disabledSkills?: string[];
   guideState?: GuideState;
+  /** Per-agent ACP overrides (command, args, env, enabled). Keyed by agent ID. */
+  acpAgents?: Record<string, import('./acp/agent-descriptors').AcpAgentOverride>;
 }
 
 const DEFAULTS: ServerSettings = {
@@ -133,6 +136,11 @@ function parseAgent(raw: unknown): AgentConfig | undefined {
   return Object.keys(result).length > 0 ? result : undefined;
 }
 
+/** Parse acpAgents config field, delegates to agent-descriptors.ts */
+function parseAcpAgentsField(raw: unknown): Record<string, import('./acp/agent-descriptors').AcpAgentOverride> | undefined {
+  return parseAcpAgentOverrides(raw);
+}
+
 /** Parse guideState from unknown input */
 function parseGuideState(raw: unknown): GuideState | undefined {
   if (!raw || typeof raw !== 'object') return undefined;
@@ -159,6 +167,7 @@ export function readSettings(): ServerSettings {
     return {
       ai: migrateAi(parsed),
       agent: parseAgent(parsed.agent),
+      acpAgents: parseAcpAgentsField(parsed.acpAgents),
       mindRoot: (parsed.mindRoot ?? parsed.sopRoot ?? DEFAULTS.mindRoot) as string,
       webPassword: typeof parsed.webPassword === 'string' ? parsed.webPassword : undefined,
       authToken:   typeof parsed.authToken   === 'string' ? parsed.authToken   : undefined,
@@ -189,6 +198,7 @@ export function writeSettings(settings: ServerSettings): void {
   if (settings.startMode   !== undefined) merged.startMode   = settings.startMode;
   if (settings.disabledSkills !== undefined) merged.disabledSkills = settings.disabledSkills;
   if (settings.guideState !== undefined) merged.guideState = settings.guideState;
+  if (settings.acpAgents !== undefined) merged.acpAgents = settings.acpAgents;
   // setupPending: false/undefined → remove the field (cleanup); true → set it
   if ('setupPending' in settings) {
     if (settings.setupPending) merged.setupPending = true;

package/app/lib/types.ts

@@ -32,7 +32,16 @@ export interface ReasoningPart {
   text: string;
 }
 
-export type MessagePart = TextPart | ToolCallPart | ReasoningPart;
+export type ImageMimeType = 'image/png' | 'image/jpeg' | 'image/gif' | 'image/webp';
+
+export interface ImagePart {
+  type: 'image';
+  /** Base64-encoded image data (no data: prefix) */
+  data: string;
+  mimeType: ImageMimeType;
+}
+
+export type MessagePart = TextPart | ToolCallPart | ReasoningPart | ImagePart;
 
 export interface Message {
   role: 'user' | 'assistant';
@@ -41,6 +50,8 @@ export interface Message {
   timestamp?: number;
   /** Structured parts for assistant messages (tool calls + text segments) */
   parts?: MessagePart[];
+  /** Images attached to this message (user messages only) */
+  images?: ImagePart[];
   /** Skill name used for this user message (rendered as a capsule in the UI) */
   skillName?: string;
 }

package/app/next-env.d.ts

@@ -1,6 +1,6 @@
 /// <reference types="next" />
 /// <reference types="next/image-types/global" />
-import "./.next/types/routes.d.ts";
+import "./.next/dev/types/routes.d.ts";
 
 // NOTE: This file should not be edited
 // see https://nextjs.org/docs/app/api-reference/config/typescript for more information.

package/app/package.json

@@ -3,8 +3,9 @@
   "version": "0.1.0",
   "private": true,
   "scripts": {
-    "dev": "next dev -p ${MINDOS_WEB_PORT:-3456}",
-    "prebuild": "node ../scripts/gen-renderer-index.js",
+    "generate": "npx tsx scripts/generate-explore.ts",
+    "dev": "npx tsx scripts/generate-explore.ts && next dev -p ${MINDOS_WEB_PORT:-3456}",
+    "prebuild": "npx tsx scripts/generate-explore.ts && node ../scripts/gen-renderer-index.js",
     "build": "next build --webpack",
     "start": "next start -p ${MINDOS_WEB_PORT:-3456}",
     "lint": "eslint",
@@ -32,16 +33,20 @@
     "@tiptap/extension-task-list": "^3.20.1",
     "@tiptap/react": "^3.20.1",
     "@tiptap/starter-kit": "^3.20.1",
+    "@types/archiver": "^7.0.0",
     "@xyflow/react": "^12.10.1",
+    "archiver": "^7.0.1",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
     "codemirror": "^6.0.2",
     "extend": "^3.0.2",
     "fuse.js": "^7.1.0",
     "github-slugger": "^2.0.0",
+    "js-yaml": "^4.1.1",
     "lucide-react": "^0.577.0",
-    "nanoid": "^5.1.0",
+    "marked": "^17.0.5",
     "mcporter": "^0.7.3",
+    "nanoid": "^5.1.0",
     "next": "16.1.6",
     "papaparse": "^5.5.3",
     "pdfjs-dist": "^4.10.38",
@@ -52,7 +57,9 @@
     "rehype-highlight": "^7.0.2",
     "rehype-raw": "^7.0.0",
     "rehype-slug": "^6.0.0",
+    "remark": "^15.0.1",
     "remark-gfm": "^4.0.1",
+    "remark-html": "^16.0.1",
     "source-map-js": "^1.2.1",
     "tailwind-merge": "^3.5.0",
     "tiptap-markdown": "^0.9.0",
@@ -61,6 +68,7 @@
   },
   "devDependencies": {
     "@tailwindcss/postcss": "^4",
+    "@types/js-yaml": "^4.0.9",
     "@types/node": "^20",
     "@types/papaparse": "^5.5.2",
     "@types/react": "^19",

package/app/scripts/generate-explore.ts

@@ -0,0 +1,145 @@
+#!/usr/bin/env node
+/**
+ * generate-explore.ts — YAML → TypeScript code generator for Explore use cases.
+ *
+ * Reads: components/explore/use-cases.yaml (single source of truth)
+ * Generates:
+ *   1. components/explore/use-cases.generated.ts  (UseCase[] array + types)
+ *   2. lib/i18n/generated/explore-i18n.generated.ts  (zh + en translation objects)
+ *
+ * Run: npx tsx scripts/generate-explore.ts
+ * Or:  npm run generate  (via package.json hook)
+ */
+import { readFileSync, writeFileSync, mkdirSync } from 'fs';
+import { resolve, dirname } from 'path';
+import yaml from 'js-yaml';
+
+const BANNER = '// ⚠️ AUTO-GENERATED — DO NOT EDIT. Source: components/explore/use-cases.yaml\n// Run `npm run generate` to regenerate.\n';
+
+interface YamlText { title: string; desc: string; prompt: string }
+interface YamlCase {
+  id: string;
+  icon: string;
+  image?: string;
+  category: string;
+  scenario: string;
+  zh: YamlText;
+  en: YamlText;
+}
+interface YamlMeta {
+  categories: Record<string, { en: string; zh: string }>;
+  scenarios: Record<string, { en: string; zh: string }>;
+  ui: Record<string, { en: string; zh: string }>;
+}
+interface YamlRoot { meta: YamlMeta; cases: YamlCase[] }
+
+// ── Load YAML ──
+const appDir = resolve(__dirname, '..');
+const yamlPath = resolve(appDir, 'components/explore/use-cases.yaml');
+const raw = readFileSync(yamlPath, 'utf-8');
+const data = yaml.load(raw) as YamlRoot;
+
+if (!data?.cases?.length) {
+  console.error('[generate-explore] No cases found in YAML');
+  process.exit(1);
+}
+if (!data?.meta) {
+  console.error('[generate-explore] No meta section found in YAML');
+  process.exit(1);
+}
+
+// ── Validate ──
+const validCategories = new Set(Object.keys(data.meta.categories));
+const validScenarios = new Set(Object.keys(data.meta.scenarios));
+for (const c of data.cases) {
+  if (!c.id || !c.icon || !c.category || !c.scenario || !c.zh || !c.en) {
+    console.error(`[generate-explore] Invalid case: ${JSON.stringify(c)}`);
+    process.exit(1);
+  }
+  if (!validCategories.has(c.category)) {
+    console.error(`[generate-explore] Unknown category "${c.category}" in case ${c.id}`);
+    process.exit(1);
+  }
+  if (!validScenarios.has(c.scenario)) {
+    console.error(`[generate-explore] Unknown scenario "${c.scenario}" in case ${c.id}`);
+    process.exit(1);
+  }
+}
+
+// ── Generate use-cases.generated.ts ──
+const categoryUnion = Object.keys(data.meta.categories).map(k => `'${k}'`).join(' | ');
+const scenarioUnion = Object.keys(data.meta.scenarios).map(k => `'${k}'`).join(' | ');
+
+const useCasesTs = `${BANNER}
+/** Capability axis — maps to product pillars */
+export type UseCaseCategory = ${categoryUnion};
+
+/** Scenario axis — maps to user journey phase */
+export type UseCaseScenario = ${scenarioUnion};
+
+export interface UseCase {
+  id: string;
+  icon: string;
+  image?: string;
+  category: UseCaseCategory;
+  scenario: UseCaseScenario;
+}
+
+export const useCases: UseCase[] = ${JSON.stringify(
+  data.cases.map(c => ({
+    id: c.id,
+    icon: c.icon,
+    ...(c.image ? { image: c.image } : {}),
+    category: c.category,
+    scenario: c.scenario,
+  })),
+  null,
+  2,
+)};
+
+export const categories: UseCaseCategory[] = ${JSON.stringify(Object.keys(data.meta.categories))};
+export const scenarios: UseCaseScenario[] = ${JSON.stringify(Object.keys(data.meta.scenarios))};
+`;
+
+const useCasesPath = resolve(appDir, 'components/explore/use-cases.generated.ts');
+writeFileSync(useCasesPath, useCasesTs, 'utf-8');
+console.log(`[generate-explore] ✓ ${useCasesPath}`);
+
+// ── Generate explore-i18n.generated.ts ──
+function buildI18n(lang: 'en' | 'zh') {
+  const ui: Record<string, string> = {};
+  for (const [key, val] of Object.entries(data.meta.ui)) {
+    ui[key] = val[lang];
+  }
+
+  const categories: Record<string, string> = {};
+  for (const [key, val] of Object.entries(data.meta.categories)) {
+    categories[key] = val[lang];
+  }
+
+  const scenarios: Record<string, string> = {};
+  for (const [key, val] of Object.entries(data.meta.scenarios)) {
+    scenarios[key] = val[lang];
+  }
+
+  const cases: Record<string, { title: string; desc: string; prompt: string }> = {};
+  for (const c of data.cases) {
+    cases[c.id] = c[lang];
+  }
+
+  return { ...ui, categories, scenarios, ...cases };
+}
+
+const i18nTs = `${BANNER}
+export const exploreEn = ${JSON.stringify(buildI18n('en'), null, 2)} as const;
+
+export const exploreZh = ${JSON.stringify(buildI18n('zh'), null, 2)} as const;
+`;
+
+const i18nDir = resolve(appDir, 'lib/i18n/generated');
+mkdirSync(i18nDir, { recursive: true });
+const i18nPath = resolve(i18nDir, 'explore-i18n.generated.ts');
+writeFileSync(i18nPath, i18nTs, 'utf-8');
+console.log(`[generate-explore] ✓ ${i18nPath}`);
+
+console.log(`[generate-explore] Done — ${data.cases.length} use cases generated.`);

package/package.json

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

package/templates/en/.mindos/workflows/Sprint Release.flow.yaml

@@ -0,0 +1,130 @@
+title: Sprint Release Workflow
+description: Weekly sprint release process with multi-agent collaboration and comprehensive QA
+
+# Global configuration - skills available across all steps
+skills:
+  - software-architecture
+  - code-review-quality
+  - document-release
+
+# Global tools guidance (advisory - LLM auto-selects based on context)
+tools:
+  - git
+  - npm
+  - github
+
+# Workflow steps - executed sequentially
+steps:
+  # Step 1: Run comprehensive test suite
+  - id: run_tests
+    name: Run tests
+    description: Execute full test suite and report results with coverage metrics
+    agent: cursor
+    prompt: |
+      Execute the full test suite for this project.
+      
+      Provide:
+      1. Total tests run, passed, failed
+      2. Coverage report (lines/branches/functions)
+      3. Any critical failures with recommendations
+      4. Time taken
+      
+      If failures exist, list the top 3 most critical with suggested fixes.
+    timeout: 120
+
+  # Step 2: Code review with dedicated AI agent
+  - id: code_review
+    name: Code review
+    description: Comprehensive code review using software architecture principles
+    agent: claude-code
+    skill: code-review-quality
+    prompt: |
+      Review the recent code changes using the code-review-quality standard.
+      
+      Evaluate:
+      1. Correctness - error handling, edge cases
+      2. Security - authentication, input validation, secrets
+      3. Performance - N+1 queries, caching, complexity
+      4. Maintainability - naming, tests, documentation
+      5. Architecture - follows project patterns, no anti-patterns
+      
+      Provide a rating (e.g., 8.5/10) and key recommendations.
+    timeout: 120
+
+  # Step 3: Automated security scan (no agent - use LLM with tools)
+  - id: security_check
+    name: Security scan
+    description: Run security analysis and dependency checks
+    tools:
+      - npm
+      - github
+    prompt: |
+      Perform security checks on this project:
+      
+      1. Check for known vulnerabilities in npm dependencies
+      2. Review recent dependency changes
+      3. Check for hardcoded secrets or credentials
+      4. Evaluate access control and authentication mechanisms
+      5. Assess error handling for information leaks
+      
+      Report severity and recommended fixes.
+    timeout: 60
+
+  # Step 4: Update documentation using document-release skill
+  - id: update_docs
+    name: Update documentation
+    description: Sync CHANGELOG, README, and API docs with shipped changes
+    skill: document-release
+    prompt: |
+      Update project documentation based on the shipped changes:
+      
+      1. Update CHANGELOG.md following semantic versioning
+      2. Update README.md if features or APIs changed
+      3. Update API documentation if endpoints changed
+      4. Verify all documentation links are valid
+      5. Check code examples match current implementation
+      
+      Provide a summary of all documentation updates made.
+    timeout: 60
+
+  # Step 5: Final checklist before release
+  - id: pre_release_check
+    name: Pre-release verification
+    description: Final comprehensive verification before shipping
+    agent: mindos
+    prompt: |
+      Perform final pre-release verification:
+      
+      Checklist:
+      ☐ All tests passing
+      ☐ Code review completed and issues resolved
+      ☐ Security scan passed or risks accepted
+      ☐ Documentation updated and links valid
+      ☐ Version bumped correctly (semver)
+      ☐ Git tags and commits clean
+      ☐ No uncommitted changes
+      ☐ Changelog entry present
+      ☐ Dependencies updated and locked
+      ☐ Performance benchmarks acceptable
+      
+      Confirm release readiness or list any blockers.
+    timeout: 60
+
+  # Step 6: Create release tag and prepare release notes
+  - id: create_release
+    name: Create release
+    description: Tag release and prepare release notes for publishing
+    tools:
+      - git
+      - npm
+    prompt: |
+      Prepare the project for release:
+      
+      1. Confirm version in package.json matches intended release
+      2. Create git tag for this version (vX.Y.Z)
+      3. Generate release notes from CHANGELOG.md
+      4. Prepare npm release command (do not execute yet)
+      5. List all deliverables included in this release
+      
+      Provide step-by-step commands for final publishing.
+    timeout: 60

package/templates/zh/.mindos/workflows//345/221/250/350/277/255/344/273/243/346/243/200/346/237/245.flow.yaml

@@ -0,0 +1,84 @@
+title: 周迭代检查工作流
+description: 每周进行代码审查、测试运行和文档更新的标准工作流
+
+# 全局配置 - 此工作流可用的技能
+skills:
+  - software-architecture
+  - code-review-quality
+
+# 工作流步骤 - 按顺序执行
+steps:
+  # 第 1 步：运行测试套件
+  - id: run_tests
+    name: 运行测试
+    description: 执行完整测试套件并报告覆盖率
+    agent: cursor
+    prompt: |
+      执行此项目的完整测试套件。
+      
+      提供以下信息：
+      1. 运行的总测试数、通过数、失败数
+      2. 覆盖率报告（行/分支/函数）
+      3. 任何严重失败及修复建议
+      4. 耗时
+      
+      如果有失败，列出前 3 个最严重的失败及建议的修复方案。
+    timeout: 120
+
+  # 第 2 步：代码审查
+  - id: code_review
+    name: 代码审查
+    description: 使用标准进行代码审查
+    agent: claude-code
+    skill: code-review-quality
+    prompt: |
+      使用代码审查标准对最近的代码变更进行审查。
+      
+      评估以下方面：
+      1. 正确性 - 错误处理、边界情况
+      2. 安全性 - 认证、输入验证、密钥管理
+      3. 性能 - 查询优化、缓存策略、复杂度
+      4. 可维护性 - 命名规范、测试覆盖、文档完整性
+      5. 架构 - 是否遵循项目模式，有无反模式
+      
+      给出评分（如 8.5/10）和主要建议。
+    timeout: 120
+
+  # 第 3 步：更新文档
+  - id: update_docs
+    name: 更新文档
+    description: 同步 CHANGELOG 和 README
+    skill: document-release
+    prompt: |
+      根据本次发布的变更更新项目文档：
+      
+      1. 更新 CHANGELOG.md，遵循语义化版本规范
+      2. 如果功能或 API 变更，更新 README.md
+      3. 如果端点变更，更新 API 文档
+      4. 验证所有文档链接有效
+      5. 检查代码示例是否匹配当前实现
+      
+      提供所有文档变更的摘要。
+    timeout: 60
+
+  # 第 4 步：发布前最终检查
+  - id: final_check
+    name: 发布前验证
+    description: 最终确认一切就绪
+    agent: mindos
+    prompt: |
+      进行最终的发布前验证检查：
+      
+      清单：
+      ☐ 所有测试通过
+      ☐ 代码审查完成并问题已解决
+      ☐ 文档已更新并链接有效
+      ☐ 版本号正确升级（语义化版本）
+      ☐ Git 标签和提交干净
+      ☐ 无未提交的更改
+      ☐ CHANGELOG 条目存在
+      ☐ 依赖项已更新并锁定
+      ☐ 性能基准可接受
+      
+      确认发布就绪或列出任何阻碍因素。
+    timeout: 60

package/app/components/explore/use-cases.ts

@@ -1,58 +0,0 @@
-/** Capability axis — maps to product pillars */
-export type UseCaseCategory = 'knowledge-management' | 'memory-sync' | 'auto-execute' | 'experience-evolution' | 'human-insights' | 'audit-control';
-
-/** Scenario axis — maps to user journey phase */
-export type UseCaseScenario = 'first-day' | 'daily' | 'project' | 'advanced';
-
-export interface UseCase {
-  id: string;
-  icon: string;
-  category: UseCaseCategory;
-  scenario: UseCaseScenario;
-}
-
-/**
- * C1-C9 use case definitions.
- * All display text (title, description, prompt) comes from i18n — this file is structure only.
- *
- * Category (capability axis):
- *   knowledge-management — Inject, organize, and maintain knowledge
- *   memory-sync         — Record once, all Agents know
- *   auto-execute        — One sentence, auto-execute
- *   experience-evolution — Gets smarter with use
- *   human-insights      — Understand and manage relationships
- *   audit-control       — You have final say
- *
- * Scenario (journey axis):
- *   first-day — Onboarding / first-time tasks
- *   daily     — Everyday workflows
- *   project   — Project-scoped work
- *   advanced  — Power-user patterns
- */
-export const useCases: UseCase[] = [
-  { id: 'c1', icon: '👤', category: 'memory-sync',           scenario: 'first-day' },
-  { id: 'c2', icon: '📥', category: 'knowledge-management',  scenario: 'daily' },
-  { id: 'c3', icon: '🔄', category: 'memory-sync',           scenario: 'project' },
-  { id: 'c4', icon: '🔁', category: 'experience-evolution',  scenario: 'daily' },
-  { id: 'c5', icon: '💡', category: 'auto-execute',          scenario: 'daily' },
-  { id: 'c6', icon: '🚀', category: 'auto-execute',          scenario: 'project' },
-  { id: 'c7', icon: '🔍', category: 'knowledge-management',  scenario: 'project' },
-  { id: 'c8', icon: '🤝', category: 'human-insights',        scenario: 'daily' },
-  { id: 'c9', icon: '🛡️', category: 'audit-control',        scenario: 'advanced' },
-];
-
-export const categories: UseCaseCategory[] = [
-  'knowledge-management',
-  'memory-sync',
-  'auto-execute',
-  'experience-evolution',
-  'human-insights',
-  'audit-control',
-];
-
-export const scenarios: UseCaseScenario[] = [
-  'first-day',
-  'daily',
-  'project',
-  'advanced',
-];