@baoanaz/cviauto 0.6.5 → 0.6.8

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

@@ -1,37 +1,37 @@
-# Local Workflow System
+# 本地工作流系统
 
-`.cviauto/workflow.md` is the Cviauto workflow source of truth inside the user project. An AI does not need Cviauto source code to understand how the current project should move tasks forward; this file is enough.
+`.cviauto/workflow.md` 是用户项目内的 Cviauto 工作流权威来源。AI 不需要 Cviauto 源码就能理解当前项目应如何推进任务；有此文件足矣。
 
-## File Responsibilities
+## 文件职责
 
-`.cviauto/workflow.md` has three responsibilities:
+`.cviauto/workflow.md` 有三个职责：
 
-1. **Explain workflow phases**: Plan, Execute, Finish.
-2. **Define skill routing**: which skill or agent the AI should use when the user expresses a certain intent.
-3. **Provide workflow-state prompt blocks**: hooks can inject the prompt block for the current state into the conversation.
+1. **解释工作流阶段**：Plan、Execute、Finish。
+2. **定义 skill 路由**：当用户表达某种意图时，AI 应使用哪个 skill 或 Agent。
+3. **提供工作流状态 prompt 块**：hooks 可以将当前状态的 prompt 块注入对话。
 
-## Current Phase Model
+## 当前阶段模型
 
 ```text
-Phase 1: Plan    -> clarify what to build, produce prd.md and required research
-Phase 2: Execute -> implement against the PRD and specs, then check
-Phase 3: Finish  -> final verification, preserve lessons, and wrap up
+阶段 1：Plan    -> 明确构建内容，产出 prd.md 和所需研究
+阶段 2：Execute -> 根据 PRD 和 spec 实现，然后检查
+阶段 3：Finish  -> 最终验证，保存经验，收尾
 ```
 
-Each phase contains numbered steps, such as `1.3 Configure context`. These numbers are not runtime fields in `task.json`; they are workflow structure for AI and humans to read.
+每个阶段包含编号步骤，如 `1.3 Configure context`。这些编号不是 `task.json` 中的运行时字段；它们是供 AI 和人类阅读的工作流结构。
 
-## Skill Routing
+## Skill 路由
 
-`workflow.md` separates routing by platform capability:
+`workflow.md` 按平台能力分离路由：
 
-- Platforms with sub-agent support: dispatch `cviauto-implement` by default for implementation and `cviauto-check` for checking.
-- Platforms without sub-agent support: the main session reads skills such as `cviauto-before-dev`, then executes directly.
+- 支持 sub-agent 的平台：默认分派 `cviauto-implement` 进行实现，`cviauto-check` 进行检查。
+- 不支持 sub-agent 的平台：主会话阅读 `cviauto-before-dev` 等 skill，然后直接执行。
 
-When changing local AI behavior, update the routing descriptions in `workflow.md` first, then check whether the corresponding platform skill, command, or agent files need to stay in sync.
+当改变本地 AI 行为时，首先更新 `workflow.md` 中的路由描述，然后检查相应的平台 skill、command 或 Agent 文件是否需要保持同步。
 
-## Workflow-State Prompt Blocks
+## 工作流状态 Prompt 块
 
-The bottom of `workflow.md` can contain state blocks like this:
+`workflow.md` 底部可以包含如下状态块：
 
 ```text
 [workflow-state:no_task]
@@ -39,37 +39,37 @@ The bottom of `workflow.md` can contain state blocks like this:
 [/workflow-state:no_task]
 ```
 
-Hooks choose the right block based on current task status and inject it into the conversation. Common states include:
+Hooks 根据当前任务状态选择正确的块并注入到对话中。常见状态包括：
 
-| State | Meaning |
+| 状态 | 含义 |
 | --- | --- |
-| `no_task` | The current session has no active task. |
-| `planning` | The task is still in requirements, research, or context configuration. |
-| `in_progress` | The task has entered implementation and checking. |
-| `completed` | The task is complete and waiting for wrap-up or archive. |
+| `no_task` | 当前会话没有活动任务。 |
+| `planning` | 任务仍在需求、研究或上下文配置阶段。 |
+| `in_progress` | 任务已进入实现和检查阶段。 |
+| `completed` | 任务已完成，等待收尾或归档。 |
 
-If the user wants to change policies such as "whether to create a task when there is no task," "when task creation may be skipped," or "whether sub-agents are required," edit these state blocks and the routing table above them.
+如果用户想更改诸如"没有任务时是否创建任务"、"何时可以跳过任务创建"或"是否需要 sub-agent"等策略，编辑这些状态块及其上方的路由表。
 
-## Local Modification Patterns
+## 本地修改模式
 
-Common changes:
+常见变更：
 
-| Goal | Edit point |
+| 目标 | 编辑点 |
 | --- | --- |
-| Add a phase | Update the Phase Index, phase body, routing, and state blocks. |
-| Change task creation policy | Update the `no_task` state block and Phase 1 description. |
-| Change the default implementation/check path | Update Phase 2 and skill routing. |
-| Change the wrap-up flow | Update Phase 3 and `finish-work` related descriptions. Note the current split: Phase 3.3 = optional human-gated spec promotion, Phase 3.4 = AI-driven work commits (batched, user-confirmed), Phase 3.5 = `/finish-work` (local archive + session journal). `/finish-work` refuses to run if the working tree has uncommitted task code. |
-| Change platform differences | Update routing descriptions grouped by platform. |
+| 添加阶段 | 更新阶段索引、阶段正文、路由和状态块。 |
+| 更改任务创建策略 | 更新 `no_task` 状态块和阶段 1 描述。 |
+| 更改默认实现/检查路径 | 更新阶段 2 和 skill 路由。 |
+| 更改收尾流程 | 更新阶段 3 和 `finish-work` 相关描述。注意当前拆分：阶段 3.3 = 可选的人工门禁 spec 推广，阶段 3.4 = AI 驱动的工作提交（批量，用户确认），阶段 3.5 = `/finish-work`（本地归档 + 会话日志）。如果有未提交的任务代码，`/finish-work` 拒绝运行。 |
+| 更改平台差异 | 更新按平台分组的路由描述。 |
 
-After editing, make the AI reread `.cviauto/workflow.md`; do not assume the flow from the old conversation is still valid.
+编辑后，让 AI 重新读取 `.cviauto/workflow.md`；不要假设旧对话中的流程仍然有效。
 
-## Relationship To Platform Files
+## 与平台文件的关系
 
-`workflow.md` is the semantic center of the local workflow, but each platform can also have its own entry files:
+`workflow.md` 是本地工作流的语义中心，但每个平台也可以有自己的入口文件：
 
-- skills, such as `cviauto-brainstorm` and `cviauto-check`.
-- commands/prompts/workflows, such as continue and finish-work.
-- hooks, such as session-start or workflow-state injection.
+- skills，如 `cviauto-brainstorm` 和 `cviauto-check`。
+- commands/prompts/workflows，如 continue 和 finish-work。
+- hooks，如 session-start 或 workflow-state 注入。
 
-If only `workflow.md` changes, platform entry files may still contain old language. When the user wants to change "what the AI actually does," also inspect the relevant platform directory.
+如果只改了 `workflow.md`，平台入口文件可能仍然包含旧的语言。当用户想要改变"AI 实际做什么"时，也要检查相关平台目录。

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

@@ -1,8 +1,8 @@
-# Local Workspace Memory System
+# 本地工作区记忆系统（Local Workspace Memory System）
 
-`.cviauto/workspace/` stores cross-session memory. Its purpose is to let AI and humans understand what happened before across different windows and different days.
+`.cviauto/workspace/` 存储跨会话记忆。其目的是让 AI 和人类能够在不同窗口、不同日期之间了解之前发生过什么。
 
-## Directory Structure
+## 目录结构
 
 ```text
 .cviauto/workspace/
@@ -13,28 +13,28 @@
     └── journal-2.md
 ```
 
-| File | Purpose |
+| 文件 | 用途 |
 | --- | --- |
-| `.cviauto/.developer` | Current developer identity. |
-| `.cviauto/workspace/index.md` | Global workspace overview. |
-| `.cviauto/workspace/<developer>/index.md` | Session index for a developer. |
-| `.cviauto/workspace/<developer>/journal-N.md` | Session journal. |
+| `.cviauto/.developer` | 当前开发者身份。 |
+| `.cviauto/workspace/index.md` | 全局工作区概览。 |
+| `.cviauto/workspace/<developer>/index.md` | 某位开发者的会话索引。 |
+| `.cviauto/workspace/<developer>/journal-N.md` | 会话日志。 |
 
-## Developer Identity
+## 开发者身份（Developer Identity）
 
-Run this the first time:
+首次使用时运行：
 
 ```bash
 python3 ./.cviauto/scripts/init_developer.py <name>
 ```
 
-This creates `.cviauto/.developer` and the corresponding workspace directory. The AI should not change developer identity casually; if the identity is wrong, first confirm who is using the current project.
+此命令会创建 `.cviauto/.developer` 和对应的工作区目录。AI 不应随意更改开发者身份；如果身份有误，请先确认当前项目的使用者是谁。
 
-## Journal
+## 日志（Journal）
 
-`journal-N.md` records completed or partially completed work from each session. By default, each journal holds about 2000 lines; after that it rotates to the next file.
+`journal-N.md` 记录每个会话中已完成或部分完成的工作。默认情况下，每个日志文件容纳约 2000 行；超出后自动轮转到下一个文件。
 
-Common command for recording a session:
+记录会话的常用命令：
 
 ```bash
 python3 ./.cviauto/scripts/add_session.py \
@@ -43,29 +43,29 @@ python3 ./.cviauto/scripts/add_session.py \
   --commit "abc1234"
 ```
 
-Planning or review work without a commit can also be recorded by using `--no-commit` or an empty commit value.
+没有 commit 的计划或审查工作也可以通过 `--no-commit` 或空 commit 值来记录。
 
-## Relationship Between Workspace Memory And Tasks
+## 工作区记忆与任务的关系（Relationship Between Workspace Memory And Tasks）
 
-| System | What it stores |
+| 系统 | 存储内容 |
 | --- | --- |
-| `.cviauto/tasks/` | Requirements, design, research, and state for a specific task. |
-| `.cviauto/workspace/` | Work records across tasks and sessions. |
-| `.cviauto/spec/` | Engineering knowledge preserved as long-term conventions. |
+| `.cviauto/tasks/` | 特定任务的需求、设计、研究和状态。 |
+| `.cviauto/workspace/` | 跨任务、跨会话的工作记录。 |
+| `.cviauto/spec/` | 作为长期约定保存的工程知识。 |
 
-If information is only useful for the current task, put it in the task directory.  
-If information describes what happened in the current session, put it in the workspace journal.  
-If information should be followed every time code is written in the future, put it in spec.
+如果信息仅对当前任务有用，请放入任务目录。  
+如果信息描述了当前会话中发生的事，请放入工作区日志。  
+如果信息应在未来每次编写代码时都遵循，请放入 spec。
 
-## Local Customization Points
+## 本地自定义点（Local Customization Points）
 
-| Need | Edit location |
+| 需求 | 编辑位置 |
 | --- | --- |
-| Change maximum journal lines | `max_journal_lines` in `.cviauto/config.yaml`. |
-| Change session auto-commit message | `session_commit_message` in `.cviauto/config.yaml`. |
-| Change session content format | `.cviauto/scripts/add_session.py`. |
-| Change how workspace is displayed in context | `.cviauto/scripts/common/session_context.py`. |
+| 更改日志最大行数 | `.cviauto/config.yaml` 中的 `max_journal_lines`。 |
+| 更改会话自动 commit 消息 | `.cviauto/config.yaml` 中的 `session_commit_message`。 |
+| 更改会话内容格式 | `.cviauto/scripts/add_session.py`。 |
+| 更改工作区在上下文中的展示方式 | `.cviauto/scripts/common/session_context.py`。 |
 
-## AI Usage Rules
+## AI 使用规则（AI Usage Rules）
 
-The AI should not treat workspace as the only source of truth. When resuming a task, read the current task first, then use workspace for background. After a task is complete, record important process notes in workspace; if long-term rules emerged, update spec.
+AI 不应将工作区视为唯一的事实来源。恢复任务时，请先阅读当前任务，然后将工作区用作背景信息。任务完成后，在工作区中记录重要的过程笔记；如果产生了长期规则，请更新 spec。

package/dist/templates/common/bundled-skills/trellis-meta/references/platform-files/agents.md

@@ -1,26 +1,26 @@
-# Agents
+# Agents（代理）
 
-Cviauto agent files define specialized roles. Common Cviauto agents in a user project are:
+Cviauto Agent 文件定义专门的角色。用户项目中常见的 Cviauto Agent 有：
 
 - `cviauto-research`
 - `cviauto-implement`
 - `cviauto-check`
 
-File locations and formats differ by platform, but responsibility boundaries should stay consistent.
+文件位置和格式因平台而异，但职责边界应保持一致。
 
-## Agent Responsibilities
+## Agent Responsibilities（Agent 职责）
 
-| Agent | Responsibility |
+| Agent（代理） | Responsibility（职责） |
 | --- | --- |
-| `cviauto-research` | Investigate the question and write findings into the current task's `research/`. |
-| `cviauto-implement` | Implement against `prd.md`, optional `design.md` / `implement.md`, `implement.jsonl`, and related spec/research. |
-| `cviauto-check` | Review changes, fix discovered issues, and run necessary checks. |
+| `cviauto-research` | 调查问题并将发现写入当前任务的 `research/`。 |
+| `cviauto-implement` | 根据 `prd.md`、可选的 `design.md` / `implement.md`、`implement.jsonl` 及相关 spec/research 进行实现。 |
+| `cviauto-check` | 审查变更、修复发现的问题，并运行必要的检查。 |
 
-Agent files should not become generic chat prompts. They should define input sources, write boundaries, whether code may be changed, and how results are reported.
+Agent 文件不应变成通用的聊天提示。它们应定义输入来源、写入边界、是否可以修改代码，以及如何报告结果。
 
-## Common Paths
+## Common Paths（常见路径）
 
-| Platform | Agent path |
+| Platform（平台） | Agent path（代理路径） |
 | --- | --- |
 | Claude Code | `.claude/agents/cviauto-*.md` |
 | Cursor | `.cursor/agents/cviauto-*.md` |
@@ -32,51 +32,51 @@ Agent files should not become generic chat prompts. They should define input sou
 | CodeBuddy | `.codebuddy/agents/cviauto-*.md` |
 | Factory Droid | `.factory/droids/cviauto-*.md` |
 | Pi Agent | `.pi/agents/cviauto-*.md` |
-| Reasonix | `.reasonix/skills/cviauto-*/SKILL.md` (subagent frontmatter) |
+| Reasonix | `.reasonix/skills/cviauto-*/SKILL.md`（subagent frontmatter） |
 | ZCode | `.zcode/cli/agents/cviauto-*.md` |
 
-GitHub Copilot agent/prompt support is provided by a combination of directories such as `.github/agents/`, `.github/prompts/`, and `.github/skills/`; inspect the files actually generated in the user project.
+GitHub Copilot 的 agent/prompt 支持由 `.github/agents/`、`.github/prompts/` 和 `.github/skills/` 等目录组合提供；请检查用户项目中实际生成的文件。
 
-Main-session workflow platforms such as Kilo, Antigravity, and Devin may not have Cviauto sub-agent files. They usually rely on workflows/skills to guide the main session.
+主会话工作流平台如 Kilo、Antigravity 和 Devin 可能没有 Cviauto sub-agent 文件。它们通常依赖 workflows/skills 来引导主会话。
 
-## Two Context Loading Modes
+## Two Context Loading Modes（两种上下文加载模式）
 
-### hook push
+### hook push（钩子推送）
 
-The platform hook injects task context before the agent starts. The agent file itself can focus more on responsibilities and boundaries.
+平台 hook 在 agent 启动前注入任务上下文。agent 文件本身可以更专注于职责和边界。
 
-Common on platforms that support agent hooks.
+常见于支持 agent hooks 的平台。
 
-### agent pull
+### agent pull（agent 拉取）
 
-The agent file instructs the agent to read after startup:
+agent 文件指示 agent 在启动后读取：
 
 - `python3 ./.cviauto/scripts/task.py current --source`
-- `implement.jsonl` or `check.jsonl`
-- spec/research files referenced by JSONL
-- current task `prd.md`
-- `design.md` if present
-- `implement.md` if present
+- `implement.jsonl` 或 `check.jsonl`
+- JSONL 引用的 spec/research 文件
+- 当前任务的 `prd.md`
+- `design.md`（如有）
+- `implement.md`（如有）
 
-This mode fits platforms whose hooks cannot reliably rewrite sub-agent prompts.
+此模式适用于 hooks 无法可靠地重写 sub-agent prompt 的平台。
 
-## Local Change Scenarios
+## Local Change Scenarios（本地修改场景）
 
-| User need | Edit location |
+| User need（用户需求） | Edit location（编辑位置） |
 | --- | --- |
-| Implement agent must follow extra restrictions | The platform's `cviauto-implement` agent file. |
-| Check agent must run project-specific commands | `cviauto-check` agent file, and `.cviauto/spec/` if needed. |
-| Research agent must output a fixed format | `cviauto-research` agent file. |
-| Agent cannot read task context | Agent prelude or `inject-subagent-context` hook. |
-| Add a project-specific agent | Platform agent directory + related workflow/command/skill entry point. |
+| Implement agent 必须遵循额外限制 | 平台的 `cviauto-implement` agent 文件。 |
+| Check agent 必须运行项目特定命令 | `cviauto-check` agent 文件，以及 `.cviauto/spec/`（如需要）。 |
+| Research agent 必须输出固定格式 | `cviauto-research` agent 文件。 |
+| Agent 无法读取任务上下文 | Agent 序言或 `inject-subagent-context` hook。 |
+| 添加项目特定 agent | 平台 agent 目录 + 相关 workflow/command/skill 入口点。 |
 
-## Modification Principles
+## Modification Principles（修改原则）
 
-1. **Keep responsibilities single-purpose**. Do not mix research, implement, and check responsibilities into one agent.
-2. **Specify the read order**. Agents must know to start from the active task, read jsonl/spec context, then read `prd.md`, `design.md` if present, and `implement.md` if present.
-3. **Specify write boundaries**. Research usually only writes `research/`; implement can write code; check can fix issues.
-4. **Keep semantics synchronized in multi-platform projects**. If the user configured Claude, Codex, and Cursor together, decide whether changes to one platform's agent also need to be applied to others.
+1. **Keep responsibilities single-purpose（保持职责单一）**。不要将 research、implement 和 check 职责混入一个 agent。
+2. **Specify the read order（指定读取顺序）**。Agent 必须知道从当前任务开始，读取 jsonl/spec 上下文，然后读取 `prd.md`、`design.md`（如有）和 `implement.md`（如有）。
+3. **Specify write boundaries（指定写入边界）**。Research 通常只写入 `research/`；implement 可以写代码；check 可以修复问题。
+4. **Keep semantics synchronized in multi-platform projects（多平台项目中保持语义同步）**。如果用户同时配置了 Claude、Codex 和 Cursor，请决定对某个平台 agent 的更改是否也需要应用到其他平台。
 
-## Do Not Default To Editing Upstream Templates
+## Do Not Default To Editing Upstream Templates（不要默认编辑上游模板）
 
-Local AI should default to modifying platform agent files inside the user project. Discuss upstream template source only when the user explicitly wants to contribute the change back to Cviauto.
+本地 AI 应默认修改用户项目内的平台 agent 文件。仅当用户明确希望将更改回馈给 Cviauto 时，才讨论上游模板源。

package/dist/templates/common/bundled-skills/trellis-meta/references/platform-files/hooks-and-settings.md

@@ -1,20 +1,20 @@
-# Hooks And Settings
+# Hooks And Settings（钩子与设置）
 
-Hooks/settings are the entry layer that connects a platform to Cviauto. They decide which scripts, plugins, or extensions a platform runs for which events.
+Hooks/settings 是将平台连接到 Cviauto 的入口层。它们决定平台在哪些事件上运行哪些脚本、插件或扩展。
 
-## Settings Responsibilities
+## Settings Responsibilities（Settings 的职责）
 
-settings/config files usually register:
+settings/config 文件通常注册：
 
-- session-start hook: injects a Cviauto overview when a new session starts or context resets.
-- workflow-state hook: parses `[workflow-state:STATUS]` blocks from `.cviauto/workflow.md` and emits the body matching the current task `status` on each user input. Parser-only; the script does not embed fallback content.
-- sub-agent context hook: injects task context when implementation/check/research agents start.
-- shell/session bridge: lets shell commands see the same Cviauto session identity.
-- platform plugin or extension entry points.
+- session-start hook（会话启动钩子）：在新会话启动或上下文重置时注入 Cviauto 概览。
+- workflow-state hook（工作流状态钩子）：解析 `.cviauto/workflow.md` 中的 `[workflow-state:STATUS]` 块，在每次用户输入时输出与当前任务 `status` 匹配的正文。仅做解析；脚本不嵌入回退内容。
+- sub-agent context hook（子代理上下文钩子）：在 implementation/check/research agent 启动时注入任务上下文。
+- shell/session bridge（shell/会话桥接）：让 shell 命令看到相同的 Cviauto 会话身份。
+- platform plugin or extension entry points（平台插件或扩展入口点）。
 
-Common files:
+常见文件：
 
-| Platform | settings/config |
+| Platform（平台） | settings/config（设置/配置） |
 | --- | --- |
 | Claude Code | `.claude/settings.json` |
 | Cursor | `.cursor/hooks.json` |
@@ -26,47 +26,46 @@ Common files:
 | CodeBuddy | `.codebuddy/settings.json` |
 | GitHub Copilot | `.github/copilot/hooks.json` |
 | Factory Droid | `.factory/settings.json` |
-| Pi Agent | `.pi/settings.json`, `.pi/extensions/trellis/` |
-| Trae IDE | `.trae/hooks.json` |
+| Pi Agent | `.pi/settings.json`, `.pi/extensions/cviauto/` |
 
-Reasonix and ZCode are pull-based platforms that do not use hooks or settings files; their agent files contain prelude instructions to read context after startup.
+Reasonix 和 ZCode 是拉取模式平台，不使用 hooks 或 settings 文件；它们的 agent 文件包含启动后读取上下文的序言指令。
 
-Whether these files exist in a project depends on which `cviauto init --<platform>` flags the user ran.
+这些文件是否存在于项目中，取决于用户运行了哪些 `cviauto init --<platform>` 标志。
 
-## Hook Script Types
+## Hook Script Types（Hook 脚本类型）
 
-| Script | Purpose |
+| Script（脚本） | Purpose（用途） |
 | --- | --- |
-| `session-start.py` | Generates session-start context. |
-| `inject-workflow-state.py` | Parses `[workflow-state:STATUS]` blocks in `.cviauto/workflow.md` and emits the body matching the current task status. Falls back to `Refer to workflow.md for current step.` when no matching block exists. |
-| `inject-subagent-context.py` | Injects PRD, JSONL context, and related spec/research into sub-agents. |
-| `inject-shell-session-context.py` | Lets shell commands inherit Cviauto session identity. |
+| `session-start.py` | 生成会话启动上下文。 |
+| `inject-workflow-state.py` | 解析 `.cviauto/workflow.md` 中的 `[workflow-state:STATUS]` 块，输出与当前任务状态匹配的正文。当没有匹配块时，回退到 `Refer to workflow.md for current step.`。 |
+| `inject-subagent-context.py` | 将 PRD、JSONL 上下文及相关 spec/research 注入 sub-agent。 |
+| `inject-shell-session-context.py` | 让 shell 命令继承 Cviauto 会话身份。 |
 
-Not every platform has every hook. Do not copy files from another platform just because a platform lacks a hook; first confirm whether that platform supports the corresponding event.
+并非每个平台都有所有 hook。不要因为某个平台缺少 hook 就从其他平台复制文件；先确认该平台是否支持相应的事件。
 
-## Local Change Scenarios
+## Local Change Scenarios（本地修改场景）
 
-| User need | Edit location |
+| User need（用户需求） | Edit location（编辑位置） |
 | --- | --- |
-| AI should see more/less context in a new session | Platform `session-start` hook. |
-| Per-turn hint policy should change | `[workflow-state:STATUS]` block in `.cviauto/workflow.md`. The hook parses workflow.md verbatim — no script edit required. |
-| Sub-agent cannot read PRD/spec | `inject-subagent-context` hook or agent prelude. |
-| `task.py current` in shell has no active task | Shell/session bridge hook or platform environment variable configuration. |
-| Disable an automatic injection | The corresponding hook registration in settings/config. |
+| AI 在新会话中应看到更多/更少上下文 | 平台 `session-start` hook。 |
+| 每轮提示策略应更改 | `.cviauto/workflow.md` 中的 `[workflow-state:STATUS]` 块。hook 逐字解析 workflow.md — 无需编辑脚本。 |
+| Sub-agent 无法读取 PRD/spec | `inject-subagent-context` hook 或 agent 序言。 |
+| shell 中 `task.py current` 无当前任务 | Shell/session bridge hook 或平台环境变量配置。 |
+| 禁用自动注入 | settings/config 中对应的 hook 注册。 |
 
-## Modification Principles
+## Modification Principles（修改原则）
 
-1. **Settings wire things up; hooks define behavior**. If only the hook changes, the platform may never call it. If only settings change, behavior may not change.
-2. **Confirm platform event names first**. Different platforms use different names for SessionStart, UserPromptSubmit, AgentSpawn, shell execution, and similar events.
-3. **Hooks read local `.cviauto/`, not upstream source**. `.cviauto/scripts/` and `.cviauto/workflow.md` in the user project are the default targets.
-4. **Errors must be visible**. Hook failures should tell the user what was not injected instead of silently leaving the AI without context.
+1. **Settings wire things up; hooks define behavior（Settings 负责接线；hooks 定义行为）**。如果只改了 hook，平台可能根本不会调用它。如果只改了 settings，行为可能不会改变。
+2. **Confirm platform event names first（先确认平台事件名称）**。不同平台对 SessionStart、UserPromptSubmit、AgentSpawn、shell 执行及类似事件使用不同的名称。
+3. **Hooks read local `.cviauto/`, not upstream source（Hooks 读取本地 `.cviauto/`，而非上游源）**。用户项目中的 `.cviauto/scripts/` 和 `.cviauto/workflow.md` 是默认目标。
+4. **Errors must be visible（错误必须可见）**。Hook 失败时应告知用户什么没有被注入，而不是静默地让 AI 缺少上下文。
 
-## Troubleshooting Path
+## Troubleshooting Path（排查路径）
 
-If the user says "AI did not read Cviauto state":
+如果用户说"AI 没有读取 Cviauto 状态"：
 
-1. Check whether the platform settings register the hook.
-2. Check whether the hook file exists.
-3. Manually run the `.cviauto/scripts/get_context.py` or `task.py current --source` command that the hook depends on.
-4. Check whether active task state exists in `.cviauto/.runtime/sessions/`.
-5. Check whether the platform shell passes session identity.
+1. 检查平台 settings 是否注册了该 hook。
+2. 检查 hook 文件是否存在。
+3. 手动运行该 hook 依赖的 `.cviauto/scripts/get_context.py` 或 `task.py current --source` 命令。
+4. 检查 `.cviauto/.runtime/sessions/` 中是否存在当前任务状态。
+5. 检查平台 shell 是否传递了会话身份。

package/dist/templates/common/bundled-skills/trellis-meta/references/platform-files/overview.md

@@ -1,59 +1,59 @@
-# Platform Files Overview
+# Platform Files Overview（平台文件概览）
 
-Cviauto connects the same local architecture to different AI tools. `.cviauto/` stores the shared runtime; platform directories store adapter files that define how each AI tool enters Cviauto.
+Cviauto 将同一套本地架构连接到不同的 AI 工具。`.cviauto/` 存放共享运行时；platform 目录存放适配器文件，定义每个 AI 工具如何进入 Cviauto。
 
-When a local AI modifies Cviauto, it should distinguish two file categories first:
+当本地 AI 修改 Cviauto 时，应首先区分两类文件：
 
-- **Shared files**: `.cviauto/workflow.md`, `.cviauto/tasks/`, `.cviauto/spec/`, `.cviauto/scripts/`.
-- **Platform files**: `.claude/`, `.codex/`, `.cursor/`, `.opencode/`, `.kiro/`, `.gemini/`, `.qoder/`, `.codebuddy/`, `.github/`, `.factory/`, `.pi/`, `.trae/`, `.kilocode/`, `.agent/`, `.devin/`, `.reasonix/`, `.zcode/`, and similar directories.
+- **Shared files（共享文件）**：`.cviauto/workflow.md`、`.cviauto/tasks/`、`.cviauto/spec/`、`.cviauto/scripts/`。
+- **Platform files（平台文件）**：`.claude/`、`.codex/`、`.cursor/`、`.opencode/`、`.kiro/`、`.gemini/`、`.qoder/`、`.codebuddy/`、`.github/`、`.factory/`、`.pi/`、`.kilocode/`、`.agent/`、`.devin/`、`.reasonix/`、`.zcode/` 以及类似目录。
 
-Platform files do not store business state. They let the corresponding AI tool read Cviauto state, call Cviauto scripts, and load Cviauto skills/agents/hooks.
+平台文件不存储业务状态。它们让对应的 AI 工具能够读取 Cviauto 状态、调用 Cviauto 脚本，并加载 Cviauto skills/agents/hooks。
 
-## Platform File Categories
+## Platform File Categories（平台文件分类）
 
-| Category | Common paths | Purpose |
+| Category（类别） | Common paths（常见路径） | Purpose（用途） |
 | --- | --- | --- |
-| settings/config | `.claude/settings.json`, `.codex/hooks.json`, `.qoder/settings.json`, `.trae/hooks.json` | Register hooks, plugins, extensions, or platform behavior. |
-| hooks/plugins/extensions | `.claude/hooks/`, `.opencode/plugins/`, `.pi/extensions/` | Inject context at session start, user input, agent startup, shell execution, and similar events. |
-| agents | `.claude/agents/`, `.codex/agents/`, `.kiro/agents/` | Define `cviauto-research`, `cviauto-implement`, and `cviauto-check`. |
-| skills | `.claude/skills/`, `.agents/skills/`, `.qoder/skills/` | Capability descriptions that auto-trigger or can be read on demand. |
-| commands/prompts/workflows | `.cursor/commands/`, `.github/prompts/`, `.devin/workflows/` | Entry points explicitly invoked by the user. |
+| settings/config（设置/配置） | `.claude/settings.json`、`.codex/hooks.json`、`.qoder/settings.json` | 注册 hooks、plugins、extensions 或平台行为。 |
+| hooks/plugins/extensions（钩子/插件/扩展） | `.claude/hooks/`、`.opencode/plugins/`、`.pi/extensions/` | 在会话启动、用户输入、agent 启动、shell 执行等事件时注入上下文。 |
+| agents（代理） | `.claude/agents/`、`.codex/agents/`、`.kiro/agents/` | 定义 `cviauto-research`、`cviauto-implement` 和 `cviauto-check`。 |
+| skills（技能） | `.claude/skills/`、`.agents/skills/`、`.qoder/skills/` | 能力描述，可自动触发或按需读取。 |
+| commands/prompts/workflows（命令/提示/工作流） | `.cursor/commands/`、`.github/prompts/`、`.devin/workflows/` | 用户显式调用的入口点。 |
 
-## Three Platform Integration Modes
+## Three Platform Integration Modes（三种平台集成模式）
 
-### 1. Hook / Extension Driven
+### 1. Hook / Extension Driven（钩子/扩展驱动）
 
-These platforms can trigger scripts or plugins on specific events and actively inject Cviauto context into AI.
+这些平台可以在特定事件上触发脚本或插件，并主动将 Cviauto 上下文注入 AI。
 
-Common capabilities:
+常见能力：
 
-- session-start injection of a `.cviauto/` overview.
-- workflow-state hints for each user turn.
-- PRD/spec/research injection when sub-agents start.
-- Shell commands inheriting session identity.
+- 会话启动时注入 `.cviauto/` 概览。
+- 每次用户对话轮次的工作流状态提示。
+- sub-agent 启动时注入 PRD/spec/research。
+- Shell 命令继承会话身份。
 
-To change "when the AI knows what," inspect hooks/plugins/extensions and settings first.
+要改变"AI 何时知道什么"，请先检查 hooks/plugins/extensions 和 settings。
 
-### 2. Agent Prelude / Pull-Based
+### 2. Agent Prelude / Pull-Based（Agent 序言 / 拉取模式）
 
-Some platforms cannot reliably let hooks rewrite sub-agent prompts, so the agent file itself instructs the agent to read the active task, PRD, and JSONL context after startup.
+某些平台无法可靠地让 hooks 重写 sub-agent 的 prompt，因此 agent 文件本身会指示 agent 在启动后读取当前任务、PRD 和 JSONL 上下文。
 
-To change how sub-agents load context, inspect the agent files themselves.
+要改变 sub-agent 加载上下文的方式，请检查 agent 文件本身。
 
-### 3. Main-Session Workflow
+### 3. Main-Session Workflow（主会话工作流）
 
-Some platforms do not have Cviauto sub-agent or hook capabilities. They rely on workflows/skills/commands to guide the main-session AI to read files, run scripts, and move tasks forward.
+某些平台没有 Cviauto sub-agent 或 hook 能力。它们依赖 workflows/skills/commands 来引导主会话 AI 读取文件、运行脚本和推进任务。
 
-To change behavior, inspect platform workflows/skills/commands and `.cviauto/workflow.md`.
+要改变行为，请检查平台 workflows/skills/commands 和 `.cviauto/workflow.md`。
 
-## Local Modification Order
+## Local Modification Order（本地修改顺序）
 
-When the user asks to customize behavior for a platform, the AI should inspect files in this order:
+当用户要求为某个平台自定义行为时，AI 应按以下顺序检查文件：
 
-1. Read `.cviauto/workflow.md` to confirm the shared flow.
-2. Read the target platform's settings/config to see which hooks/agents/skills/commands are registered.
-3. Read the target platform's agents/skills/commands/hooks.
-4. Modify the local file closest to the user's need.
-5. If the change affects the shared flow, synchronize `.cviauto/workflow.md` or `.cviauto/spec/`.
+1. 读取 `.cviauto/workflow.md` 确认共享流程。
+2. 读取目标平台的 settings/config 查看注册了哪些 hooks/agents/skills/commands。
+3. 读取目标平台的 agents/skills/commands/hooks。
+4. 修改最贴近用户需求的本地文件。
+5. 如果改动影响共享流程，同步更新 `.cviauto/workflow.md` 或 `.cviauto/spec/`。
 
-Do not modify only platform files and forget the shared workflow. Do not modify only `.cviauto/workflow.md` and forget that platform entry points may still contain old descriptions.
+不要只修改平台文件而忘记共享工作流。不要只修改 `.cviauto/workflow.md` 而忘记平台入口点可能仍包含旧描述。