@baoanaz/cviauto 0.6.5 → 0.6.8

package/dist/templates/common/bundled-skills/trellis-meta/references/local-architecture/multi-agent-channel.md

@@ -1,69 +1,69 @@
-# Local Multi-Agent Channel Runtime
+# 本地多代理通道运行时（Local Multi-Agent Channel Runtime）
 
-`cviauto channel` is the local multi-agent collaboration runtime shipped with the Cviauto CLI. It lets the main AI session spawn peer workers (Claude Code, Codex, or any agent definition under `.cviauto/agents/`), exchange durable messages through an event log, and coordinate review or brainstorm loops without hand-stitching shell pipelines.
+`cviauto channel` 是 Cviauto CLI 随附的本地多代理协作运行时。它让主 AI 会话可以派生出对等的工作者（peer workers）——Claude Code、Codex 或 `.cviauto/agents/` 下的任何代理定义——通过事件日志交换持久化消息，并协调审查或头脑风暴循环，无需手动拼接 shell 管道。
 
-This reference covers how channels are wired into the user project so an AI customizing the project knows what to edit. For runtime usage (commands, forum/thread patterns, worker spawn flags), defer to the bundled `cviauto-channel` capability skill.
+本文档涵盖通道如何在用户项目中接入，以便自定义项目的 AI 知道该编辑什么。关于运行时用法（命令、论坛/帖子模式、工作者派生标志），请参考随附的 `cviauto-channel` 能力技能（capability skill）。
 
-## Local System Model
+## 本地系统模型（Local System Model）
 
-The channel runtime spans three local surfaces:
+通道运行时横跨三个本地层面：
 
-1. **Storage layer** in the user's home directory: durable event logs and worker state files.
-2. **Agent definitions** inside the project at `.cviauto/agents/`: platform-agnostic role cards consumed by `cviauto channel spawn --agent <name>`.
-3. **Project configuration** in `.cviauto/config.yaml`: worker guard thresholds and other channel knobs.
+1. **存储层**位于用户主目录：持久化事件日志和工作者状态文件。
+2. **代理定义**位于项目内的 `.cviauto/agents/`：平台无关的角色卡，由 `cviauto channel spawn --agent <name>` 消费。
+3. **项目配置**位于 `.cviauto/config.yaml`：工作者守护阈值和其他通道参数。
 
-## Core Paths
+## 核心路径（Core Paths）
 
-| Path | Purpose |
+| 路径 | 用途 |
 | --- | --- |
-| `~/.cviauto/channels/<project>/<channel>/events.jsonl` | Per-channel append-only event log. Sequence-locked, replay-safe. |
-| `~/.cviauto/channels/<project>/<channel>/<channel>.lock` | Channel-level write lock. |
-| `~/.cviauto/channels/<project>/<channel>/<worker>.spawnlock` | Per-worker spawn lock used by the OOM guard. |
-| `~/.cviauto/channels/<project>/<channel>/.seq` | Sequence sidecar for ordered event assignment. |
-| `~/.cviauto/channels/_global/<channel>/...` | Channels created with `--scope global`. The project bucket is replaced by a shared key. |
-| `.cviauto/agents/check.md` | Default Check Agent role definition consumed by `--agent check`. |
-| `.cviauto/agents/implement.md` | Default Implement Agent role definition consumed by `--agent implement`. |
-| `.cviauto/config.yaml` (`channel.*` block) | Worker guard thresholds and channel defaults. |
+| `~/.cviauto/channels/<project>/<channel>/events.jsonl` | 每个通道的只追加事件日志。序列锁定，可安全重放。 |
+| `~/.cviauto/channels/<project>/<channel>/<channel>.lock` | 通道级写锁。 |
+| `~/.cviauto/channels/<project>/<channel>/<worker>.spawnlock` | 每个工作者的派生锁，供 OOM 守护使用。 |
+| `~/.cviauto/channels/<project>/<channel>/.seq` | 序列辅助文件，用于有序事件分配。 |
+| `~/.cviauto/channels/_global/<channel>/...` | 通过 `--scope global` 创建的通道。项目桶（project bucket）被共享键替换。 |
+| `.cviauto/agents/check.md` | 默认 Check Agent 角色定义，由 `--agent check` 消费。 |
+| `.cviauto/agents/implement.md` | 默认 Implement Agent 角色定义，由 `--agent implement` 消费。 |
+| `.cviauto/config.yaml`（`channel.*` 块） | 工作者守护阈值和通道默认值。 |
 
-The project bucket name is derived from the absolute project path (slashes flattened, non-alphanumerics replaced with `-`), matching Claude Code's `~/.claude/projects/<sanitized-cwd>/` convention. Override with `TRELLIS_CHANNEL_ROOT` (root directory) or `TRELLIS_CHANNEL_PROJECT` (bucket name) for testing or sandboxing.
+项目桶名称由绝对项目路径派生（斜杠展平，非字母数字字符替换为 `-`），与 Claude Code 的 `~/.claude/projects/<sanitized-cwd>/` 约定一致。可通过 `TRELLIS_CHANNEL_ROOT`（根目录）或 `TRELLIS_CHANNEL_PROJECT`（桶名称）覆盖，用于测试或沙箱环境。
 
-## When To Reach For The Channel Runtime
+## 何时使用通道运行时（When To Reach For The Channel Runtime）
 
-Channels are heavier than a single Bash call or a one-shot sub-agent dispatch. Use them only when at least one of these conditions holds:
+通道比单次 Bash 调用或一次性子代理派发更重。仅在满足以下至少一个条件时使用：
 
-- The work needs **two or more agents to converse** through more than one turn (cross-AI brainstorm, peer review, dispatcher + worker).
-- A worker should run as a **peer process** that the main session can interrupt, watch progress on, or wait for asynchronously.
-- The conversation must be **durable and inspectable** later (forum/thread channels, issue boards, decision trails).
-- Multiple workers must **share an event log** so each can see what the others reported.
+- 工作需要**两个或以上代理进行多轮对话**（跨 AI 头脑风暴、同行审查、调度器 + 工作者）。
+- 工作者应作为**对等进程**运行，主会话可以中断、观察进度或异步等待。
+- 对话必须是**持久化且事后可检查的**（论坛/帖子通道、问题看板、决策记录）。
+- 多个工作者必须**共享一个事件日志**，以便每个工作者都能看到其他工作者的报告。
 
-Prefer cheaper primitives when:
+在以下情况优先使用更轻量的原语：
 
-- A single-shot Bash command or single Agent tool call is enough -> do that directly.
-- The user just needs a static review against a file -> read the file and reply inline.
-- The need is "remember what we discussed last week" -> use `cviauto mem` instead of a channel.
+- 单次 Bash 命令或单次 Agent 工具调用就够用 -> 直接执行即可。
+- 用户只需要对文件进行静态审查 -> 读取文件并直接回复。
+- 需求是「记住我们上周讨论的内容」-> 使用 `cviauto mem` 而非通道。
 
-## Customization Points
+## 自定义点（Customization Points）
 
-| Need | Edit location |
+| 需求 | 编辑位置 |
 | --- | --- |
-| Change default channel worker idle timeout | `channel.worker_guard.idle_timeout` in `.cviauto/config.yaml`. Accepts `5m`, `30s`, etc. Set `0` to disable idle cleanup. |
-| Change live worker budget | `channel.worker_guard.max_live_workers` in `.cviauto/config.yaml`. Set `0` to disable the spawn-time budget check. |
-| Override worker guard per spawn | Pass `--idle-timeout` / `--max-live-workers` on `cviauto channel spawn`, or set `TRELLIS_CHANNEL_WORKER_IDLE_TIMEOUT` / `TRELLIS_CHANNEL_MAX_LIVE_WORKERS` in the environment. |
-| Change what the default Check or Implement worker does | Edit `.cviauto/agents/check.md` or `.cviauto/agents/implement.md`. These are platform-agnostic role cards; the channel runtime injects them when `--agent check|implement` is passed. |
-| Add a new role card | Drop `<name>.md` into `.cviauto/agents/`. `cviauto channel spawn --agent <name>` will pick it up. |
-| Relocate channel storage (CI sandbox, ephemeral runs) | Set `TRELLIS_CHANNEL_ROOT=/path/to/dir`. Channel events move with it; existing channels stay at the old root. |
-| Switch storage scope | Pass `--scope project` (default) or `--scope global` on every channel subcommand. The bucket directory changes; nothing else does. |
+| 更改默认通道工作者空闲超时 | `.cviauto/config.yaml` 中的 `channel.worker_guard.idle_timeout`。支持 `5m`、`30s` 等格式。设为 `0` 可禁用空闲清理。 |
+| 更改活跃工作者预算 | `.cviauto/config.yaml` 中的 `channel.worker_guard.max_live_workers`。设为 `0` 可禁用派生时的预算检查。 |
+| 单次派生时覆盖工作者守护参数 | 在 `cviauto channel spawn` 时传入 `--idle-timeout` / `--max-live-workers`，或设置环境变量 `TRELLIS_CHANNEL_WORKER_IDLE_TIMEOUT` / `TRELLIS_CHANNEL_MAX_LIVE_WORKERS`。 |
+| 更改默认 Check 或 Implement 工作者的行为 | 编辑 `.cviauto/agents/check.md` 或 `.cviauto/agents/implement.md`。这些是平台无关的角色卡；通道运行时在传入 `--agent check|implement` 时将其注入。 |
+| 添加新的角色卡 | 将 `<name>.md` 放入 `.cviauto/agents/`。`cviauto channel spawn --agent <name>` 会自动识别。 |
+| 迁移通道存储位置（CI 沙箱、临时运行） | 设置 `TRELLIS_CHANNEL_ROOT=/path/to/dir`。通道事件随之迁移；现有通道保留在原位置。 |
+| 切换存储作用域 | 在每个通道子命令中传入 `--scope project`（默认）或 `--scope global`。仅桶目录变化，其余不变。 |
 
-Precedence for the worker guard is: CLI flag > environment variable > `.cviauto/config.yaml` > built-in default. Built-in defaults are `idle_timeout: 5m` and `max_live_workers: 6`.
+工作者守护参数的优先级为：CLI 标志 > 环境变量 > `.cviauto/config.yaml` > 内置默认值。内置默认值为 `idle_timeout: 5m` 和 `max_live_workers: 6`。
 
-## Relationship To Other Local Layers
+## 与其他本地层的关系（Relationship To Other Local Layers）
 
-- **Workflow layer**: workflows that use channel dispatch (such as `channel-driven-subagent-dispatch`) instruct the main agent to call `cviauto channel spawn --agent check` or `--agent implement` instead of a platform sub-agent. If `.cviauto/agents/check.md` or `implement.md` is missing, `cviauto workflow --template <id>` prints a non-blocking warning at install time. Restore them with `cviauto update` if they are deleted by accident.
-- **Task layer**: channel workers do not own task state. The supervising main session passes the active task path through the worker inbox; the worker resolves task artifacts from disk.
-- **Spec layer**: workers read `.cviauto/spec/` the same way the main session does. Channel runtime does not bypass spec context loading.
-- **Platform integration layer**: channel runtime is platform-neutral. It does not depend on `.claude/`, `.codex/`, or any other platform directory. The adapters that normalize provider output (Claude `stream-json`, Codex `app-server`) live inside the Cviauto CLI binary, not in the project.
-- **Platform sub-agent files vs. channel workers**: editing `.claude/agents/cviauto-implement.md` (and its peers in other platform `.X/agents/` directories) does NOT change channel-runtime worker behavior — channel workers load `.cviauto/agents/<name>.md`. The platform-specific agent files are for direct sub-agent dispatch from the main AI session, not for channel-spawned workers. See `platform-files/agents.md` for the per-platform agent surface, and the `cviauto-meta/SKILL.md` rule that codifies this split.
+- **工作流层（Workflow layer）**：使用通道派发的工作流（如 `channel-driven-subagent-dispatch`）指示主代理调用 `cviauto channel spawn --agent check` 或 `--agent implement`，而非使用平台子代理。如果 `.cviauto/agents/check.md` 或 `implement.md` 缺失，`cviauto workflow --template <id>` 会在安装时打印非阻塞警告。如果意外删除，可通过 `cviauto update` 恢复。
+- **任务层（Task layer）**：通道工作者不拥有任务状态。监督主会话通过工作者收件箱传递活跃任务路径；工作者从磁盘解析任务产物。
+- **规范层（Spec layer）**：工作者与主会话以相同方式读取 `.cviauto/spec/`。通道运行时不绕过 spec 上下文加载。
+- **平台集成层（Platform integration layer）**：通道运行时是平台中立的。它不依赖 `.claude/`、`.codex/` 或任何其他平台目录。标准化不同提供商输出（Claude `stream-json`、Codex `app-server`）的适配器位于 Cviauto CLI 二进制文件内部，不在项目中。
+- **平台子代理文件 vs. 通道工作者**：编辑 `.claude/agents/cviauto-implement.md`（以及其他平台 `.X/agents/` 目录中的对应文件）**不会**改变通道运行时工作者的行为——通道工作者加载 `.cviauto/agents/<name>.md`。平台特定的代理文件用于主 AI 会话的直接子代理派发，而非通道派生的工作者。请参阅 `platform-files/agents.md` 了解各平台的代理表面，以及 `cviauto-meta/SKILL.md` 中编码此分离的规则。
 
-## Runtime Usage
+## 运行时用法（Runtime Usage）
 
-For command syntax, forum/thread patterns, worker handles, progress inspection, and the `--kind done` / `--kind turn_finished` dispatcher wait pattern, load the bundled `cviauto-channel` skill (auto-installed under each platform's skills directory after `cviauto init` / `cviauto update`). This reference only covers the local file layout and customization knobs; it does not duplicate command syntax that may change between releases.
+关于命令语法、论坛/帖子模式、工作者句柄、进度检查以及 `--kind done` / `--kind turn_finished` 调度器等待模式，请加载随附的 `cviauto-channel` 技能（在 `cviauto init` / `cviauto update` 后自动安装到各平台的技能目录下）。本文档仅涵盖本地文件布局和自定义参数；不重复可能在不同版本间变化的命令语法。

package/dist/templates/common/bundled-skills/trellis-meta/references/local-architecture/overview.md

@@ -1,51 +1,51 @@
-# Local Cviauto Architecture Overview
+# 本地 Cviauto 架构概述
 
-`cviauto-meta` is for user projects that have already run `cviauto init`. The user's machine usually has only the npm-installed `cviauto` command plus the Cviauto files generated inside the project; it may not have the Cviauto CLI source code.
+`cviauto-meta` 面向已运行过 `cviauto init` 的用户项目。用户机器通常只有通过 npm 安装的 `cviauto` 命令以及项目中生成的 Cviauto 文件；可能没有 Cviauto CLI 源码。
 
-Therefore, when an AI uses this skill, the default customization target is local files inside the user project:
+因此，当 AI 使用此技能时，默认的自定义目标是用户项目中的本地文件：
 
-- `.cviauto/`: workflow, tasks, specs, memory, scripts, and runtime state.
-- Platform directories: `.claude/`, `.codex/`, `.cursor/`, `.opencode/`, `.kiro/`, `.gemini/`, `.qoder/`, `.codebuddy/`, `.github/`, `.factory/`, `.pi/`, `.kilocode/`, `.agent/`, `.devin/`, `.reasonix/`, `.zcode/`, and similar directories.
-- Shared skill layer: `.agents/skills/`.
+- `.cviauto/`：工作流、任务、spec、记忆、脚本和运行时状态。
+- 平台目录：`.claude/`、`.codex/`、`.cursor/`、`.opencode/`、`.kiro/`、`.gemini/`、`.qoder/`、`.codebuddy/`、`.github/`、`.factory/`、`.pi/`、`.kilocode/`、`.agent/`、`.devin/`、`.reasonix/`、`.zcode/` 及类似目录。
+- 共享技能层：`.agents/skills/`。
 
-Do not default to guiding the user to fork the Cviauto CLI repository. Treat upstream source code as the operating target only when the user explicitly says they want to change Cviauto upstream source, publish an npm package, or contribute a PR.
+不要默认引导用户 fork Cviauto CLI 仓库。仅当用户明确说要更改 Cviauto 上游源码、发布 npm 包或提交 PR 时，才将上游源码视为操作目标。
 
-## Local System Model
+## 本地系统模型
 
-Cviauto provides three layers inside a user project:
+Cviauto 在用户项目内提供三层：
 
-1. **Workflow layer**: `.cviauto/workflow.md` defines phases, routing, next actions, and prompt blocks.
-2. **Persistence layer**: `.cviauto/tasks/`, `.cviauto/spec/`, and `.cviauto/workspace/` store tasks, specs, and session memory.
-3. **Platform integration layer**: hooks, settings, agents, skills, commands, prompts, and workflows in platform directories connect the Cviauto workflow to different AI tools.
+1. **工作流层**：`.cviauto/workflow.md` 定义阶段、路由、下一步操作和 prompt 块。
+2. **持久化层**：`.cviauto/tasks/`、`.cviauto/spec/` 和 `.cviauto/workspace/` 存储任务、spec 和会话记忆。
+3. **平台集成层**：平台目录中的 hooks、settings、agents、skills、commands、prompts 和 workflows 将 Cviauto 工作流连接到不同的 AI 工具。
 
-All three layers live inside the user project, so an AI can read and modify them directly.
+所有三层都位于用户项目内，因此 AI 可以直接读取和修改它们。
 
-## Core Paths
+## 核心路径
 
-| Path | Purpose |
+| 路径 | 用途 |
 | --- | --- |
-| `.cviauto/workflow.md` | Workflow phases, skill routing, and workflow-state prompt blocks. |
-| `.cviauto/config.yaml` | Project configuration, task lifecycle hooks, monorepo package configuration, and journal configuration. |
-| `.cviauto/spec/` | The user's project-specific coding conventions and thinking guides. |
-| `.cviauto/tasks/` | Each task's PRD, technical notes, research files, and JSONL context. |
-| `.cviauto/workspace/` | Per-developer journals and cross-session memory. |
-| `.cviauto/scripts/` | Local Python runtime used by commands, hooks, and context injection. |
-| `.cviauto/.runtime/` | Session-level runtime state, such as the current task pointer. |
-| `.cviauto/.template-hashes.json` | Template hashes for Cviauto-managed files, used by update to determine whether local files were modified by the user. |
-
-## AI Customization Principles
-
-1. **Find the local source of truth first**: Do not edit from memory. Read `.cviauto/workflow.md`, `.cviauto/config.yaml`, the relevant platform directory, and related task files first.
-2. **Edit the user project, not the npm package cache**: Modify generated files inside the project, not `node_modules` or the global npm install directory.
-3. **Keep platform files aligned with `.cviauto/`**: If workflow routing changes, also check whether platform skills or commands still describe the same flow.
-4. **Put project-specific rules in `.cviauto/spec/` or a local skill**: Do not put team conventions into `cviauto-meta`.
-5. **Preserve user changes**: If a file was already modified locally, work from the current content instead of overwriting it with a default template.
-
-## How To Use This Directory
-
-- To understand which files exist after init, read `generated-files.md`.
-- To change phases, routing, or next actions, read `workflow.md`.
-- To change the task model, JSONL context, or active task behavior, read `task-system.md`.
-- To change coding convention injection, read `spec-system.md`.
-- To understand journals and cross-session memory, read `workspace-memory.md`.
-- To change hooks or sub-agent context loading, read `context-injection.md`.
+| `.cviauto/workflow.md` | 工作流阶段、技能路由和工作流状态 prompt 块。 |
+| `.cviauto/config.yaml` | 项目配置、任务生命周期 hooks、monorepo 包配置和日志配置。 |
+| `.cviauto/spec/` | 用户的项目特定编码规范和思维指南。 |
+| `.cviauto/tasks/` | 每个任务的 PRD、技术笔记、研究文件和 JSONL 上下文。 |
+| `.cviauto/workspace/` | 每个开发者的日志和跨会话记忆。 |
+| `.cviauto/scripts/` | 由命令、hooks 和上下文注入使用的本地 Python 运行时。 |
+| `.cviauto/.runtime/` | 会话级运行时状态，如当前任务指针。 |
+| `.cviauto/.template-hashes.json` | Cviauto 管理文件的模板哈希值，由 update 用于判断本地文件是否被用户修改。 |
+
+## AI 自定义原则
+
+1. **首先找到本地唯一权威来源**：不要凭记忆编辑。先读取 `.cviauto/workflow.md`、`.cviauto/config.yaml`、相关的平台目录和相关任务文件。
+2. **编辑用户项目，而非 npm 包缓存**：修改项目内生成的文件，而非 `node_modules` 或全局 npm 安装目录。
+3. **保持平台文件与 `.cviauto/` 一致**：如果工作流路由发生变化，同时检查平台技能或命令是否仍描述相同的流程。
+4. **将项目特定规则放入 `.cviauto/spec/` 或本地技能**：不要将团队约定放入 `cviauto-meta`。
+5. **保留用户更改**：如果文件已在本地被修改，以当前内容为基准工作，而非用默认模板覆盖。
+
+## 如何使用本目录
+
+- 要了解 init 后存在哪些文件，阅读 `generated-files.md`。
+- 要更改阶段、路由或下一步操作，阅读 `workflow.md`。
+- 要更改任务模型、JSONL 上下文或活动任务行为，阅读 `task-system.md`。
+- 要更改编码规范注入，阅读 `spec-system.md`。
+- 要了解日志和跨会话记忆，阅读 `workspace-memory.md`。
+- 要更改 hooks 或 sub-agent 上下文加载，阅读 `context-injection.md`。

package/dist/templates/common/bundled-skills/trellis-meta/references/local-architecture/spec-system.md

@@ -1,10 +1,10 @@
-# Local Spec System
+# 本地 Spec 系统
 
-`.cviauto/spec/` is the user's project-specific engineering spec library. Cviauto is not about making AI memorize conventions; it injects relevant specs or requires the AI to read them at the right time.
+`.cviauto/spec/` 是用户的项目特定工程 spec 库。Cviauto 不是让 AI 记忆约定；而是在适当的时机注入相关 spec 或要求 AI 阅读它们。
 
-## Directory Model
+## 目录模型
 
-A common single-repository structure:
+常见的单仓库结构：
 
 ```text
 .cviauto/spec/
@@ -19,7 +19,7 @@ A common single-repository structure:
     └── ...
 ```
 
-A common monorepo structure:
+常见的 monorepo 结构：
 
 ```text
 .cviauto/spec/
@@ -39,11 +39,11 @@ A common monorepo structure:
     └── ...
 ```
 
-`index.md` is the entry point for each layer. It should list the Pre-Development Checklist and Quality Check. Specific guidelines live in other Markdown files in the same directory.
+`index.md` 是每层的入口点。它应列出开发前检查清单和质量检查。具体指南在同一个目录中的其他 Markdown 文件中。
 
-## Package Configuration
+## 包配置
 
-`.cviauto/config.yaml` can declare packages:
+`.cviauto/config.yaml` 可以声明包：
 
 ```yaml
 packages:
@@ -55,48 +55,48 @@ packages:
 default_package: cli
 ```
 
-The AI can run:
+AI 可以运行：
 
 ```bash
 python3 ./.cviauto/scripts/get_context.py --mode packages
 ```
 
-This command lists packages and spec layers for the current project. Use this output as the reference when configuring context JSONL.
+此命令列出当前项目的包和 spec 层。将此输出作为配置上下文 JSONL 时的参考。
 
-## How Specs Enter Tasks
+## Spec 如何进入任务
 
-Before a task enters implementation, planning may write relevant specs into `implement.jsonl` / `check.jsonl` when the task needs spec or research context beyond the task artifacts:
+在任务进入实现之前，当任务需要超出任务文档的 spec 或研究上下文时，规划可以将相关 spec 写入 `implement.jsonl` / `check.jsonl`：
 
 ```jsonl
-{"file": ".cviauto/spec/cli/backend/index.md", "reason": "CLI backend conventions"}
-{"file": ".cviauto/spec/cli/unit-test/conventions.md", "reason": "Test expectations"}
+{"file": ".cviauto/spec/cli/backend/index.md", "reason": "CLI 后端约定"}
+{"file": ".cviauto/spec/cli/unit-test/conventions.md", "reason": "测试预期"}
 ```
 
-Sub-agents or platform preludes read these JSONL files and load the referenced specs. On platforms without sub-agent support, the AI should read the relevant specs directly according to the workflow.
+Sub-agent 或平台前置指令读取这些 JSONL 文件并加载引用的 spec。在不支持 sub-agent 的平台上，AI 应根据工作流直接阅读相关 spec。
 
-## What Specs Should Contain
+## Spec 应包含什么
 
-Specs should contain executable engineering conventions for the project, not generic best practices:
+Spec 应包含项目的可执行工程约定，而非泛泛的最佳实践：
 
-- Where files should live.
-- How error handling should be expressed.
-- Input/output contracts for APIs, hooks, and commands.
-- Patterns that are forbidden.
-- Cases that require tests.
-- Project-specific pitfalls and how to avoid them.
+- 文件应放在哪里。
+- 错误处理应如何表达。
+- API、hooks 和命令的输入/输出契约。
+- 被禁止的模式。
+- 需要测试的情况。
+- 项目特定的陷阱及如何避免。
 
-When the AI learns a new rule during implementation or debugging, it should update `.cviauto/spec/` rather than only summarizing it in chat.
+当 AI 在实现或调试过程中学到新规则时，应更新 `.cviauto/spec/`，而不仅仅在聊天中总结。
 
-## Local Customization Points
+## 本地自定义点
 
-| Need | Edit location |
+| 需求 | 编辑位置 |
 | --- | --- |
-| Add a new spec layer | `.cviauto/spec/<package>/<layer>/index.md` and corresponding guideline files. |
-| Change monorepo spec mapping | `packages` / `default_package` / `spec_scope` in `.cviauto/config.yaml`. |
-| Change which specs AI reads before implementation | The task's `implement.jsonl`. |
-| Change which specs AI reads during checking | The task's `check.jsonl`. |
-| Change when specs should be updated | Phase 3.3 in `.cviauto/workflow.md` and the `cviauto-update-spec` skill. Default native workflow runs this only when the user explicitly asks to promote knowledge into spec. |
+| 添加新的 spec 层 | `.cviauto/spec/<package>/<layer>/index.md` 和相应的指南文件。 |
+| 更改 monorepo spec 映射 | `.cviauto/config.yaml` 中的 `packages` / `default_package` / `spec_scope`。 |
+| 更改 AI 在实现前阅读哪些 spec | 任务的 `implement.jsonl`。 |
+| 更改 AI 在检查期间阅读哪些 spec | 任务的 `check.jsonl`。 |
+| 更改何时应更新 spec | `.cviauto/workflow.md` 中的阶段 3.3 和 `cviauto-update-spec` skill。默认原生工作流仅在用户明确要求将知识推广到 spec 时才运行。 |
 
-## Boundaries
+## 边界
 
-`.cviauto/spec/` is the user's project specification, not a permanent copy of Cviauto built-in templates. The AI should encourage the user to update it according to the actual project code instead of treating Cviauto default templates as immutable documents.
+`.cviauto/spec/` 是用户的项目规范，不是 Cviauto 内置模板的永久副本。AI 应鼓励用户根据实际项目代码更新它，而非将 Cviauto 默认模板视为不可变文档。

package/dist/templates/common/bundled-skills/trellis-meta/references/local-architecture/task-system.md

@@ -1,8 +1,8 @@
-# Local Task System
+# 本地任务系统
 
-The Cviauto task system is stored entirely under `.cviauto/tasks/` in the user project. Each task is a directory containing requirements, context, research, state, and relationship information.
+Cviauto 任务系统完全存储在用户项目的 `.cviauto/tasks/` 下。每个任务是一个目录，包含需求、上下文、研究、状态和关系信息。
 
-## Task Directory Structure
+## 任务目录结构
 
 ```text
 .cviauto/tasks/
@@ -18,95 +18,95 @@ The Cviauto task system is stored entirely under `.cviauto/tasks/` in the user p
     └── 2026-04/
 ```
 
-| File | Purpose |
+| 文件 | 用途 |
 | --- | --- |
-| `task.json` | Task metadata: status, assignee, priority, branch, parent/child tasks, and similar fields. |
-| `prd.md` | Requirements, constraints, and acceptance criteria. Lightweight tasks may be PRD-only. |
-| `design.md` | Technical design for complex tasks: boundaries, contracts, data flow, compatibility, tradeoffs. |
-| `implement.md` | Execution plan for complex tasks: ordered checklist, validation commands, review gates, rollback points. |
-| `implement.jsonl` | List of spec/research files the implement agent must read first. |
-| `check.jsonl` | List of spec/research files the check agent must read first. |
-| `research/` | Research artifacts. Complex findings should not live only in chat. |
+| `task.json` | 任务元数据：状态、负责人、优先级、分支、父子任务及类似字段。 |
+| `prd.md` | 需求、约束和验收标准。轻量级任务可以只有 PRD。 |
+| `design.md` | 复杂任务的技术设计：边界、契约、数据流、兼容性、权衡。 |
+| `implement.md` | 复杂任务的执行计划：有序检查清单、验证命令、审查门禁、回滚点。 |
+| `implement.jsonl` | implement Agent 必须首先阅读的 spec/research 文件列表。 |
+| `check.jsonl` | check Agent 必须首先阅读的 spec/research 文件列表。 |
+| `research/` | 研究产出物。复杂发现不应只存在于聊天中。 |
 
 ## `task.json`
 
-`task.json` records task status and metadata. Common fields:
+`task.json` 记录任务状态和元数据。常见字段：
 
-| Field | Meaning |
+| 字段 | 含义 |
 | --- | --- |
-| `id` / `name` / `title` | Task identity and title. |
-| `status` | Status such as `planning`, `in_progress`, `review`, or `completed`. |
-| `priority` | `P0`, `P1`, `P2`, `P3`. |
-| `creator` / `assignee` | Creator and assignee. |
-| `package` | Target package in a monorepo; may be empty. |
-| `branch` / `base_branch` | Working branch and PR target branch. |
-| `children` / `parent` | Parent/child task relationships. |
-| `commit` / `pr_url` | Commit and PR information after completion. |
-| `meta` | Extension fields. |
+| `id` / `name` / `title` | 任务标识和标题。 |
+| `status` | 状态，如 `planning`、`in_progress`、`review` 或 `completed`。 |
+| `priority` | `P0`、`P1`、`P2`、`P3`。 |
+| `creator` / `assignee` | 创建者和负责人。 |
+| `package` | monorepo 中的目标包；可为空。 |
+| `branch` / `base_branch` | 工作分支和 PR 目标分支。 |
+| `children` / `parent` | 父子任务关系。 |
+| `commit` / `pr_url` | 完成后的提交和 PR 信息。 |
+| `meta` | 扩展字段。 |
 
-## Parent / Child Task Trees
+## 父子任务树
 
-Parent/child task relationships are for work structure. A parent task groups related deliverables under one source requirement set; it is not a dependency scheduler and does not replace the child task's own planning artifacts.
+父子任务关系用于工作结构。父任务将相关交付物分组到一个需求来源集下；它不是依赖调度器，也不替代子任务自己的规划文档。
 
-Use a parent task when a request has multiple independently verifiable deliverables. The parent owns:
+当请求有多个可独立验证的交付物时使用父任务。父任务拥有：
 
-- Source requirements and user-facing scope.
-- The map of child tasks and their responsibility boundaries.
-- Cross-child acceptance criteria and final integration review.
+- 来源需求和面向用户的范围。
+- 子任务映射及其职责边界。
+- 跨子任务验收标准和最终集成审查。
 
-Use child tasks for deliverables that can move through planning, implementation, check, and archive independently. If one child depends on another, write that dependency in the child `prd.md` / `implement.md`; do not rely on tree position to imply ordering.
+对于可以独立经历规划、实现、检查和归档的交付物使用子任务。如果一个子任务依赖另一个，将该依赖写入子任务的 `prd.md` / `implement.md`；不要依赖树的位置来暗示顺序。
 
-Create new children with:
+创建新子任务：
 
 ```bash
-python3 ./.cviauto/scripts/task.py create "<child title>" --slug <child-slug> --parent <parent-dir>
+python3 ./.cviauto/scripts/task.py create "<子任务标题>" --slug <子任务-slug> --parent <父任务-目录>
 ```
 
-Link or unlink existing tasks with:
+链接或取消链接现有任务：
 
 ```bash
-python3 ./.cviauto/scripts/task.py add-subtask <parent-dir> <child-dir>
-python3 ./.cviauto/scripts/task.py remove-subtask <parent-dir> <child-dir>
+python3 ./.cviauto/scripts/task.py add-subtask <父任务-目录> <子任务-目录>
+python3 ./.cviauto/scripts/task.py remove-subtask <父任务-目录> <子任务-目录>
 ```
 
-`children` on the parent is a historical list. When a child is archived, Cviauto keeps that child name in the parent so progress like `[2/3 done]` remains meaningful after completed children move to `archive/`.
+父任务的 `children` 是历史列表。当子任务归档时，Cviauto 保留该子任务名称在父任务中，以便在已完成的子任务移至 `archive/` 后 `[2/3 done]` 这样的进度仍然有意义。
 
-The AI should not treat phase numbers as task status. Task progress is mainly determined by `status`, artifact presence (`prd.md`, optional `design.md` / `implement.md`), whether JSONL context is configured for sub-agent mode, and the phase descriptions in `workflow.md`.
+AI 不应将阶段编号视为任务状态。任务进度主要由 `status`、文档存在情况（`prd.md`、可选的 `design.md` / `implement.md`）、JSONL 上下文是否为 sub-agent 模式配置以及 `workflow.md` 中的阶段描述决定。
 
-## Active Task
+## 活动任务
 
-The user sees a "current task," but Cviauto stores active task state per session.
+用户看到"当前任务"，但 Cviauto 按会话存储活动任务状态。
 
 ```text
 .cviauto/.runtime/sessions/<context-key>.json
 ```
 
-`task.py start` writes the task path into the runtime session file for the current session. `task.py current --source` shows the current task and where it came from. Different AI windows can point to different tasks without overwriting each other.
+`task.py start` 将任务路径写入当前会话的运行时会话文件。`task.py current --source` 显示当前任务及其来源。不同的 AI 窗口可以指向不同的任务而不会互相覆盖。
 
-If the platform or shell environment has no stable session identity, `task.py start` may be unable to set the active task. The AI should read the error, inspect the platform hook/session environment, and not fall back to a shared global pointer.
+如果平台或 shell 环境没有稳定的会话身份，`task.py start` 可能无法设置活动任务。AI 应阅读错误信息，检查平台 hook/会话环境，而非回退到共享全局指针。
 
-## JSONL Context
+## JSONL 上下文
 
-`implement.jsonl` and `check.jsonl` are context manifests for sub-agents to read first. They do not replace `implement.md`; `implement.md` is the human-readable execution plan.
+`implement.jsonl` 和 `check.jsonl` 是供 sub-agent 首先阅读的上下文清单。它们不替代 `implement.md`；`implement.md` 是人类可读的执行计划。
 
-Format:
+格式：
 
 ```jsonl
-{"file": ".cviauto/spec/cli/backend/index.md", "reason": "Backend conventions"}
-{"file": ".cviauto/tasks/04-28-example/research/api.md", "reason": "API research"}
+{"file": ".cviauto/spec/cli/backend/index.md", "reason": "后端约定"}
+{"file": ".cviauto/tasks/04-28-example/research/api.md", "reason": "API 研究"}
 ```
 
-Rules:
+规则：
 
-- Include spec and research files.
-- Do not include code files that are about to be modified.
-- Do not treat temporary conclusions in chat as the only context.
-- Seed rows have no `file` field; they only prompt the AI to fill in real entries.
+- 包含 spec 和研究文件。
+- 不要包含即将被修改的代码文件。
+- 不要将聊天中的临时结论作为唯一上下文。
+- 种子行没有 `file` 字段；它们仅提示 AI 填入真实条目。
 
-## Common Commands
+## 常用命令
 
 ```bash
-python3 ./.cviauto/scripts/task.py create "<title>" --slug <slug>
+python3 ./.cviauto/scripts/task.py create "<标题>" --slug <slug>
 python3 ./.cviauto/scripts/task.py start <task>
 python3 ./.cviauto/scripts/task.py current --source
 python3 ./.cviauto/scripts/task.py add-context <task> implement <file> <reason>
@@ -115,16 +115,16 @@ python3 ./.cviauto/scripts/task.py finish
 python3 ./.cviauto/scripts/task.py archive <task>
 ```
 
-When modifying the task system, the AI should prefer script commands to maintain structure. Edit JSON/Markdown directly only when scripts do not cover the need.
+修改任务系统时，AI 应优先使用脚本命令来维护结构。仅在脚本无法满足需求时才直接编辑 JSON/Markdown。
 
-## Local Customization Points
+## 本地自定义点
 
-| Need | Edit location |
+| 需求 | 编辑位置 |
 | --- | --- |
-| Change the default task template | `.cviauto/scripts/common/task_store.py` and task creation instructions. |
-| Change status semantics | `.cviauto/workflow.md`, workflow-state hook logic, and task usage conventions. |
-| Add task lifecycle actions | `hooks.after_*` in `.cviauto/config.yaml`. |
-| Change context rules | Planning artifact guidance in `.cviauto/workflow.md` and related platform agent/hook instructions. |
-| Change archive policy | `.cviauto/scripts/common/task_store.py` / `task_utils.py`. |
+| 更改默认任务模板 | `.cviauto/scripts/common/task_store.py` 和任务创建指令。 |
+| 更改状态语义 | `.cviauto/workflow.md`、workflow-state hook 逻辑和任务使用约定。 |
+| 添加任务生命周期操作 | `.cviauto/config.yaml` 中的 `hooks.after_*`。 |
+| 更改上下文规则 | `.cviauto/workflow.md` 中的规划文档指导和相关平台 agent/hook 指令。 |
+| 更改归档策略 | `.cviauto/scripts/common/task_store.py` / `task_utils.py`。 |
 
-These are local files in the user project. Do not default to editing Cviauto CLI source code unless the user wants to contribute upstream.
+这些是用户项目中的本地文件。除非用户想向上游贡献，否则不要默认编辑 Cviauto CLI 源码。