czon 0.9.2 → 0.9.3

package/dist/build/pipeline.js

@@ -47,7 +47,6 @@ const extractMetadataByAI_1 = require("../process/extractMetadataByAI");
 const processTranslations_1 = require("../process/processTranslations");
 const scanSourceFiles_1 = require("../process/scanSourceFiles");
 const template_1 = require("../process/template");
-const opencode_1 = require("../services/opencode");
 const writeFile_1 = require("../utils/writeFile");
 const robots_1 = require("./robots");
 const sitemap_1 = require("./sitemap");
@@ -67,8 +66,6 @@ async function applyConfig(options) {
 async function buildPipeline(options) {
     // 验证配置
     await applyConfig(options);
-    // 安装 OpenCode 代理到全局目录
-    await (0, opencode_1.installAgentsToGlobal)();
     // 清理输出目录
     await fs.rm(paths_1.CZON_DIST_DIR, { recursive: true, force: true });
     // 扫描源文件

package/dist/paths.js

@@ -1,7 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.LOCAL_OPENCODE_AGENT_DIR = exports.GLOBAL_OPENCODE_AGENT_DIR = exports.CZON_DIST_CUSTOM_STYLE_PATH = exports.CZON_CUSTOM_STYLE_PATH = exports.CZON_META_PATH = exports.CZON_SRC_DIR = exports.CZON_DIST_RAW_CONTENT_DIR = exports.CZON_DIST_DIR = exports.CZON_DIR = exports.INPUT_DIR = void 0;
-const os_1 = require("os");
+exports.CZON_DIST_CUSTOM_STYLE_PATH = exports.CZON_CUSTOM_STYLE_PATH = exports.CZON_META_PATH = exports.CZON_SRC_DIR = exports.CZON_DIST_RAW_CONTENT_DIR = exports.CZON_DIST_DIR = exports.CZON_DIR = exports.INPUT_DIR = void 0;
 const path_1 = require("path");
 exports.INPUT_DIR = process.cwd();
 exports.CZON_DIR = (0, path_1.join)(process.cwd(), '.czon');
@@ -11,9 +10,4 @@ exports.CZON_SRC_DIR = (0, path_1.join)(exports.CZON_DIR, 'src');
 exports.CZON_META_PATH = (0, path_1.join)(exports.CZON_DIR, 'meta.json');
 exports.CZON_CUSTOM_STYLE_PATH = (0, path_1.join)(exports.CZON_DIR, 'style.css');
 exports.CZON_DIST_CUSTOM_STYLE_PATH = (0, path_1.join)(exports.CZON_DIST_DIR, 'style.css');
-/**
- * ~/.config/opencode/agents/
- */
-exports.GLOBAL_OPENCODE_AGENT_DIR = (0, path_1.join)((0, os_1.homedir)(), '.config', 'opencode', 'agents');
-exports.LOCAL_OPENCODE_AGENT_DIR = (0, path_1.join)(__dirname, '..', 'agents');
 //# sourceMappingURL=paths.js.map

package/dist/process/summary.js

@@ -19,48 +19,56 @@ const SUMMARY_STYLES = [
         name: '客观中立',
         title: 'AI 总结: 客观中立风格',
         slug: 'aigc-summary-objective',
+        category: 'AI Summary',
     },
     {
         skill: 'summary-critical',
         name: '客观批判',
         title: 'AI 总结: 客观批判风格',
         slug: 'aigc-summary-critical',
+        category: 'AI Summary',
     },
     {
         skill: 'summary-positive',
         name: '赞扬鼓励',
         title: 'AI 总结: 赞扬鼓励风格',
         slug: 'aigc-summary-positive',
+        category: 'AI Summary',
     },
     {
         skill: 'summary-popular',
         name: '科普介绍',
         title: 'AI 总结: 科普介绍风格',
         slug: 'aigc-summary-popular',
+        category: 'AI Summary',
     },
     {
         skill: 'summary-artistic',
         name: '文艺感性',
         title: 'AI 总结: 文艺感性风格',
         slug: 'aigc-summary-artistic',
+        category: 'AI Summary',
     },
     {
         skill: 'summary-philosophical',
         name: '哲学思辨',
         title: 'AI 总结: 哲学思辨风格',
         slug: 'aigc-summary-philosophical',
+        category: 'AI Summary',
     },
     {
         skill: 'summary-psychological',
         name: '心理分析',
         title: 'AI 总结: 心理分析风格',
         slug: 'aigc-summary-psychological',
+        category: 'AI Summary',
     },
     {
         skill: 'summary-historical',
         name: '历史时间跨度',
         title: 'AI 总结: 历史时间跨度风格',
         slug: 'aigc-summary-historical',
+        category: 'AI Summary',
     },
 ];
 /**
@@ -184,6 +192,7 @@ const processSummary = async (model) => {
                 title: style.title,
                 slug: style.slug,
             };
+            fileMeta.category = style.category;
             console.info(`✅ 「${style.name}」风格报告生成成功\n`);
         }
         else {

package/dist/process/todoSummary.js

@@ -15,6 +15,7 @@ const TODO_CONFIG = {
     promptFile: 'todo-summary',
     title: 'AI 总结：待办事项',
     slug: 'aigc-todo-list',
+    category: 'AI Summary',
     outputRelative: '.czon/AIGC/TODO/todo-summary.md',
 };
 /**
@@ -87,6 +88,7 @@ ${promptContent}
                 title: TODO_CONFIG.title,
                 slug: TODO_CONFIG.slug,
             };
+            fileMeta.category = TODO_CONFIG.category;
             // 保存 MetaData
             await (0, metadata_1.saveMetaData)();
             return;
@@ -117,6 +119,7 @@ ${promptContent}
             title: TODO_CONFIG.title,
             slug: TODO_CONFIG.slug,
         };
+        fileMeta.category = TODO_CONFIG.category;
         await (0, metadata_1.saveMetaData)();
         return;
     }

package/dist/services/opencode.js

@@ -1,10 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.installAgentsToGlobal = exports.runOpenCode = void 0;
-const promises_1 = require("fs/promises");
-const path_1 = require("path");
-const paths_1 = require("../paths");
-const writeFile_1 = require("../utils/writeFile");
+exports.runOpenCode = void 0;
 // ---------------------------------------------------------------------------
 // Constants
 // ---------------------------------------------------------------------------
@@ -164,16 +160,4 @@ const runOpenCode = async (prompt, options) => {
     return handle;
 };
 exports.runOpenCode = runOpenCode;
-const installAgentsToGlobal = async () => {
-    const installedAgents = await (0, promises_1.readdir)(paths_1.LOCAL_OPENCODE_AGENT_DIR)
-        .then(files => files.filter(f => f.startsWith('czon-')))
-        .catch(() => []);
-    // 3. Copy local agents from .opencode/agent to global directory
-    for (const agentFile of installedAgents) {
-        console.log(`📁 Installing OpenCode agent: ${agentFile} to global directory...`);
-        await (0, writeFile_1.writeFile)((0, path_1.join)(paths_1.GLOBAL_OPENCODE_AGENT_DIR, agentFile), await (0, promises_1.readFile)((0, path_1.join)(paths_1.LOCAL_OPENCODE_AGENT_DIR, agentFile)));
-    }
-    console.log(`✅ Installed ${installedAgents.length} OpenCode agents to global directory.`);
-};
-exports.installAgentsToGlobal = installAgentsToGlobal;
 //# sourceMappingURL=opencode.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "czon",
-  "version": "0.9.2",
+  "version": "0.9.3",
   "description": "CZON - AI enhanced Markdown content engine",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/prompts/todo-summary.md

@@ -76,6 +76,23 @@
 | 原文引用 | 相关原文片段（1-2 句话）             |
 | 推断日期 | 该 TODO 提出的日期（从文章内容推断） |
 
+#### 状态相关的额外提取要素
+
+对于判断为「🔄 进行中」的 TODO，还需额外记录：
+
+| 字段       | 说明                                       |
+| ---------- | ------------------------------------------ |
+| 已完成部分 | 已经取得的进展（具体做了什么）             |
+| 剩余部分   | 尚未完成的内容（还需要做什么）             |
+| 进展证据   | 体现进展的后续文章原文片段（注明来源文章） |
+
+对于判断为「✅ 已完成」的 TODO，还需额外记录：
+
+| 字段     | 说明                                       |
+| -------- | ------------------------------------------ |
+| 完成依据 | 为什么判断已完成（引用具体证据及来源文章） |
+| 成果     | 完成后取得了什么具体成果或产出             |
+
 ---
 
 ## 状态判断规则
@@ -159,7 +176,10 @@
 
 ### TODO 列表
 
-按状态分组展示，每组内部按优先级排序（高 → 中 → 低）：
+按状态分组展示，每组内部按优先级排序（高 → 中 → 低）。
+不同状态的 TODO 使用不同的展示格式：
+
+#### ⬜ 待开始 格式
 
 ```markdown
 ## ⬜ 待开始
@@ -172,18 +192,44 @@
   > 引用相关原文片段
 
 ---
+```
 
-### 🟡 [TODO 简短描述]
-
-...
+#### 🔄 进行中 格式
 
+```markdown
 ## 🔄 进行中
 
-...
+### 🔴 [TODO 简短描述]
+
+- **来源**：[文章标题](../../../path/to/file.md)
+- **日期**：YYYY-MM-DD
+- **原文**：
+  > 引用相关原文片段
+- **进度**：
+  - **已完成**：描述已经取得的进展，具体做了什么
+  - **剩余**：描述尚未完成的内容，还需要做什么
+  - **证据**：[后续文章标题](../../../path/to/later-file.md)
+    > 引用体现进展的后续文章原文片段
+
+---
+```
 
+#### ✅ 已完成 格式
+
+```markdown
 ## ✅ 已完成
 
-...
+### 🔴 [TODO 简短描述]
+
+- **来源**：[文章标题](../../../path/to/file.md)
+- **日期**：YYYY-MM-DD
+- **原文**：
+  > 引用相关原文片段
+- **完成依据**：说明为什么判断已完成，引用具体证据
+  - 证据来源：[相关文章标题](../../../path/to/evidence-file.md)
+- **成果**：描述完成后取得了什么具体成果或产出
+
+---
 ```
 
 ---

package/agents/czon-markdown-translator.md

@@ -1,90 +0,0 @@
----
-description: >-
-  Use this agent when you need to translate markdown files from one language to
-  another while preserving the markdown formatting structure. Examples:
-
-
-  - <example>
-      Context: User wants to translate documentation files from English to Chinese.
-      user: "Translate the README.md file to Japanese, preserving all headers, links, and code blocks"
-      assistant: "I'll use the czon-markdown-translator agent to handle this translation task"
-      <commentary>
-      Since the user explicitly asked to translate a markdown file (README.md) while preserving formatting, the czon-markdown-translator agent is the appropriate choice.
-      </commentary>
-    </example>
-  - <example>
-      Context: User needs to localize technical documentation for a new market.
-      user: "Please translate all .md files in the docs/ directory to German"
-      assistant: "The czon-markdown-translator agent can read and translate the markdown files while maintaining proper structure"
-      <commentary>
-      When the user mentions translating multiple markdown files, this agent should be used to ensure consistent formatting preservation.
-      </commentary>
-    </example>
-  - <example>
-      Context: User wants to translate a markdown blog post.
-      user: "Convert this markdown article to Spanish, keeping all formatting intact"
-      assistant: "Let me invoke the czon-markdown-translator agent to handle the translation while preserving markdown syntax"
-      <commentary>
-      When the user emphasizes preserving formatting during translation, this specialized agent is ideal.
-      </commentary>
-    </example>
-mode: all
----
-
-You are a specialized Markdown Translator with expertise in technical documentation localization. Your primary responsibility is to accurately translate markdown files while meticulously preserving their structural integrity.
-
-## Core Responsibilities
-
-1. **Read and Parse Files**: Load markdown files from specified paths, understanding their full structure including frontmatter, headers, lists, code blocks, tables, links, images, and inline formatting.
-
-2. **Translate Content**: Translate the textual content to the target language while:
-   - Preserving all markdown syntax (headings with #, bold \*_, italic _, code blocks with ```, etc.)
-   - Maintaining links, image references, and their alt text
-   - Keeping tables intact and translating only cell content
-   - Preserving code examples, file paths, and command snippets untranslated
-   - Handling frontmatter metadata appropriately (translate values only, keep keys)
-
-3. **Handle Special Content**:
-   - **Code blocks**: Never translate content inside triple-backtick blocks
-   - **Inline code**: Keep backtick-enclosed text untranslated
-   - **Links**: Translate link text but preserve URLs
-   - **Images**: Translate alt text but preserve image paths
-   - **URLs and paths**: Keep untranslated (e.g., `/api/users`, `https://example.com`)
-   - **Frontmatter**: Translate string values, preserve boolean/numeric values and keys
-
-4. **Output Management**: Write translated content to the specified output file, maintaining UTF-8 encoding and original line endings where possible.
-
-## Translation Quality Standards
-
-- Maintain consistent terminology throughout the document
-- Preserve the original tone (technical, casual, formal, etc.)
-- Ensure translations are natural and idiomatic in the target language
-- Keep headings and subheadings properly nested and meaningful
-- For list items, ensure parallel structure is maintained
-
-## Workflow
-
-1. Confirm the source file path and target language with the user if unclear
-2. Read and parse the complete markdown file
-3. Create a translation strategy (identify sections, special content types)
-4. Translate section by section, marking translated content
-5. Verify markdown syntax integrity after translation
-6. Write to output file or return translated content as requested
-
-## Error Handling
-
-- If a file doesn't exist or cannot be read, report the error clearly
-- If the target language is ambiguous, ask for clarification
-- If encoding issues are detected, attempt to resolve or report
-- If markdown parsing fails, identify the problematic section
-
-## Output Format
-
-When completing the task:
-
-- Confirm the file was translated successfully
-- Report the character/word count if relevant
-- Note any sections that were preserved (code blocks, etc.)
-- Suggest any follow-up actions if needed (proofreading, formatting review)
-
-Remember: Your goal is to produce a translated markdown file that looks like it was originally written in the target language, with all formatting intact and functional.