@baoanaz/cviauto 0.6.5 → 0.6.8

package/dist/templates/common/bundled-skills/trellis-meta/references/customize-local/change-skills-or-commands.md

@@ -1,36 +1,36 @@
-# Change Local Skills, Commands, Prompts, And Workflows
+# 修改本地 Skills、Commands、Prompts 和 Workflows
 
-When the user wants to change AI entry points, auto-trigger rules, or explicit command behavior, edit skills, commands, prompts, or workflows in local platform directories.
+当用户想更改 AI 入口点、自动触发规则或显式命令行为时，编辑本地平台目录中的 skills、commands、prompts 或 workflows。
 
-Before editing, classify the skill you are about to touch:
+在编辑之前，先对你即将操作的 skill 进行分类：
 
-- **Bundled upstream skill** — `cviauto-meta`, `cviauto-spec-bootstrap`, `cviauto-session-insight`, `cviauto-channel`. Source of truth lives in the Cviauto CLI repo under `packages/cli/src/templates/common/bundled-skills/<name>/`; auto-dispatched to every platform's skill root by `getBundledSkillTemplates()` on `cviauto init` / `cviauto update`. Local edits here are tracked by `.cviauto/.template-hashes.json` and will be flagged on the next update.
-- **Project-local skill** — anything else under `.{platform}/skills/`. Owned by the user; not refreshed by `cviauto update`.
+- **捆绑的上游 skill** — `cviauto-meta`、`cviauto-spec-bootstrap`、`cviauto-session-insight`、`cviauto-channel`。其事实来源位于 Cviauto CLI 仓库的 `packages/cli/src/templates/common/bundled-skills/<name>/` 中；在 `cviauto init` / `cviauto update` 时由 `getBundledSkillTemplates()` 自动分发到每个平台的 skill 根目录。此处的本地编辑会被 `.cviauto/.template-hashes.json` 追踪，并在下次更新时被标记。
+- **项目本地 skill** — 位于 `.{platform}/skills/` 下的其他所有内容。归用户所有，不会被 `cviauto update` 刷新。
 
-The remainder of this file uses "skill" for the local file; the override and conflict rules differ between the two cases.
+本文余下部分使用"skill"代指本地文件；两种情况下覆盖和冲突规则不同。
 
-## Read These Files First
+## 先阅读这些文件
 
 1. `.cviauto/workflow.md`
-2. Target platform skill/command/prompt/workflow directory
-3. Related agent or hook files
-4. Whether project rules already exist in `.cviauto/spec/`
-5. `.cviauto/.template-hashes.json` — confirms whether the skill you are about to edit is upstream-owned (entry present) or project-local (entry absent)
+2. 目标平台的 skill/command/prompt/workflow 目录
+3. 相关的 agent 或 hook 文件
+4. 确认 `.cviauto/spec/` 中是否已有项目规则
+5. `.cviauto/.template-hashes.json` — 确认你要编辑的 skill 是上游所有的（有对应条目）还是项目本地的（无对应条目）
 
-## Which Entry Type To Choose
+## 选择哪种入口类型
 
-| Goal | Recommendation |
+| 目标 | 推荐做法 |
 | --- | --- |
-| AI should automatically know a capability | Add or modify a skill. |
-| User wants to trigger manually with a command | Add or modify a command/prompt/workflow. |
-| Team project conventions | Prefer `.cviauto/spec/` or a project-local skill — never a bundled skill directory. |
-| Tweak a bundled skill (`cviauto-meta` et al.) for the user's own project | Create a project-local sibling skill (different name) that overrides intent, or edit `.cviauto/spec/`. Edits inside the bundled skill directory survive only until the next `cviauto update` and will need a "keep" choice each time. |
-| Contribute the change back upstream | Edit `packages/cli/src/templates/common/bundled-skills/<name>/` in the Cviauto CLI repo, not the deployed copy. |
-| Change Cviauto flow semantics | Synchronize `.cviauto/workflow.md`. |
+| AI 应自动知晓某项能力 | 添加或修改 skill。 |
+| 用户希望通过命令手动触发 | 添加或修改 command/prompt/workflow。 |
+| 团队项目约定 | 优先使用 `.cviauto/spec/` 或项目本地 skill——切勿使用捆绑的 skill 目录。 |
+| 为用户自己的项目微调捆绑 skill（`cviauto-meta` 等） | 创建一个名称不同的项目本地兄弟 skill 来覆盖意图，或编辑 `.cviauto/spec/`。在捆绑 skill 目录内的编辑仅在下一次 `cviauto update` 之前有效，且每次都需要选择"保留"。 |
+| 将更改回馈给上游 | 在 Cviauto CLI 仓库中编辑 `packages/cli/src/templates/common/bundled-skills/<name>/`，而非部署后的副本。 |
+| 更改 Cviauto 流程语义 | 同步 `.cviauto/workflow.md`。 |
 
-## Modify A Skill
+## 修改 Skill
 
-A skill is usually:
+一个 skill 通常结构如下：
 
 ```text
 <skill-name>/
@@ -38,86 +38,86 @@ A skill is usually:
 └── references/
 ```
 
-`SKILL.md` should be short and responsible for triggering/routing. Put long content in `references/` so AI can read it on demand.
+`SKILL.md` 应简短，负责触发/路由。将长内容放入 `references/`，以便 AI 按需读取。
 
-The frontmatter description should specify when to use the skill. Example:
+frontmatter 中的 description 应说明何时使用该 skill。示例：
 
 ```yaml
 description: "Use when customizing this project's deployment workflow and release checklist."
 ```
 
-Do not write vague descriptions such as "helpful project skill"; they can trigger incorrectly.
+不要编写模糊的 description，如 "helpful project skill"；它们可能会错误触发。
 
-### Bundled vs. Project-Local
+### 捆绑 vs. 项目本地
 
-The same directory shape is used by two very different ownership models:
+相同的目录结构由两种截然不同的所有权模型使用：
 
-| Aspect | Bundled (`cviauto-meta`, `cviauto-spec-bootstrap`, `cviauto-session-insight`, `cviauto-channel`) | Project-local |
+| 方面 | 捆绑（`cviauto-meta`、`cviauto-spec-bootstrap`、`cviauto-session-insight`、`cviauto-channel`） | 项目本地 |
 | --- | --- | --- |
-| Source of truth | `packages/cli/src/templates/common/bundled-skills/<name>/` in Cviauto CLI repo | Inside the user project itself |
-| Dispatch | Auto-dispatched to every platform skill root by `getBundledSkillTemplates()` (`packages/cli/src/templates/common/index.ts`) on `cviauto init` / `cviauto update` | Created by the user (or another skill) and never moved |
-| Hash tracking | Every file recorded in `.cviauto/.template-hashes.json`; conflict prompt on update | Not tracked |
-| Editing locally | Allowed but will be marked "modified by user" on next update | Free editing |
-| The right way to customize | Add a *new* project-local skill with a *different* name that supplements (or supersedes) the bundled one | Edit the file directly |
+| 事实来源 | Cviauto CLI 仓库中的 `packages/cli/src/templates/common/bundled-skills/<name>/` | 用户项目自身内部 |
+| 分发方式 | 在 `cviauto init` / `cviauto update` 时由 `getBundledSkillTemplates()`（`packages/cli/src/templates/common/index.ts`）自动分发到每个平台 skill 根目录 | 由用户（或其他 skill）创建，永不移动 |
+| Hash 追踪 | 每个文件记录在 `.cviauto/.template-hashes.json` 中；更新时提示冲突 | 不追踪 |
+| 本地编辑 | 允许，但在下次更新时会被标记为"用户已修改" | 自由编辑 |
+| 正确的自定义方式 | 添加一个**新的**、**名称不同**的项目本地 skill 来补充（或替代）捆绑的 skill | 直接编辑文件 |
 
-If the goal is "make my project's AI behave differently when discussing release notes," the answer is almost always a project-local skill, not surgery on `cviauto-meta/`.
+如果目标是"让我的项目 AI 在讨论发布说明时行为不同"，答案几乎始终是创建一个项目本地 skill，而不是对 `cviauto-meta/` 动手术。
 
-## Modify A Command/Prompt/Workflow
+## 修改 Command/Prompt/Workflow
 
-Explicit entry points should state:
+显式入口点应说明：
 
-- How the user triggers it.
-- Which `.cviauto/` files to read.
-- Which scripts to run.
-- How to report after completion.
+- 用户如何触发它。
+- 需要读取哪些 `.cviauto/` 文件。
+- 需要运行哪些脚本。
+- 完成后如何报告。
 
-If a command only repeats workflow rules, prefer making it reference/read `.cviauto/workflow.md` instead of maintaining a second copy of the flow.
+如果一个 command 仅是重复工作流规则，优先让它引用/读取 `.cviauto/workflow.md`，而不是维护流程的第二份副本。
 
-## Common Paths
+## 常见路径
 
-| Platform | Entry directories |
+| 平台 | 入口目录 |
 | --- | --- |
-| Claude Code | `.claude/skills/`, `.claude/commands/` |
-| Cursor | `.cursor/skills/`, `.cursor/commands/` |
-| OpenCode | `.opencode/skills/`, `.opencode/commands/` |
-| Codex | `.agents/skills/`, `.codex/skills/` |
-| Gemini CLI | `.agents/skills/`, `.gemini/commands/` |
+| Claude Code | `.claude/skills/`、`.claude/commands/` |
+| Cursor | `.cursor/skills/`、`.cursor/commands/` |
+| OpenCode | `.opencode/skills/`、`.opencode/commands/` |
+| Codex | `.agents/skills/`、`.codex/skills/` |
+| Gemini CLI | `.agents/skills/`、`.gemini/commands/` |
 | Kiro | `.kiro/skills/` |
-| Qoder | `.qoder/skills/`, `.qoder/commands/` |
-| CodeBuddy | `.codebuddy/skills/`, `.codebuddy/commands/` |
-| GitHub Copilot | `.github/skills/`, `.github/prompts/` |
-| Factory Droid | `.factory/skills/`, `.factory/commands/` |
+| Qoder | `.qoder/skills/`、`.qoder/commands/` |
+| CodeBuddy | `.codebuddy/skills/`、`.codebuddy/commands/` |
+| GitHub Copilot | `.github/skills/`、`.github/prompts/` |
+| Factory Droid | `.factory/skills/`、`.factory/commands/` |
 | Pi Agent | `.pi/skills/` |
-| Reasonix | `.reasonix/skills/` (no separate commands dir; slash commands built into the platform) |
-| ZCode | `.agents/skills/`, `.zcode/commands/` |
+| Reasonix | `.reasonix/skills/`（无独立 commands 目录；斜杠命令由平台内置） |
+| ZCode | `.agents/skills/`、`.zcode/commands/` |
 | Kilo / Antigravity / Devin | workflows + skills |
 
-Every directory above is a deploy target for the four bundled skills. Each platform receives a full copy on `cviauto init` and refresh on `cviauto update`; nothing has to be wired by hand.
+以上每个目录都是四个捆绑 skill 的部署目标。每个平台在 `cviauto init` 时获得完整副本，并在 `cviauto update` 时刷新；无需手动配置。
 
-## Add A Project-Local Skill
+## 添加项目本地 Skill
 
-If the user wants to document team-private customizations, create a project-local skill — never put project-private content into a bundled skill directory, since `cviauto update` will overwrite it.
+如果用户想记录团队私有的自定义内容，创建项目本地 skill——切勿将项目私有内容放入捆绑 skill 目录，因为 `cviauto update` 会覆盖它。
 
 ```text
-.claude/skills/project-trellis-local/
+.claude/skills/project-cviauto-local/
 └── SKILL.md
 ```
 
-For multi-platform projects, add equivalent versions in each platform skill directory, or use `.agents/skills/` on platforms that support the shared layer (Codex, Gemini CLI).
+对于多平台项目，在每个平台 skill 目录中添加等效版本，或在支持共享层的平台（Codex、Gemini CLI）上使用 `.agents/skills/`。
 
-Pick a name that does **not** collide with the bundled set:
+选择一个**不**与捆绑集合冲突的名称：
 
 - `cviauto-meta`
 - `cviauto-spec-bootstrap`
 - `cviauto-session-insight`
 - `cviauto-channel`
 
-A reused name causes `getBundledSkillTemplates()` to overwrite the project-local copy on the next update. A common convention is to prefix the project name: `acme-trellis-deploy`, `acme-trellis-onboarding`.
+重名会导致 `getBundledSkillTemplates()` 在下一次更新时覆盖项目本地副本。常见的约定是使用项目名称作为前缀：`acme-cviauto-deploy`、`acme-cviauto-onboarding`。
 
-## Notes
+## 注意事项
 
-- Do not mix every platform's syntax into one file.
-- Do not change only one platform entry point while claiming all platforms are supported.
-- Do not hide long-term engineering conventions inside a command; write them to `.cviauto/spec/`.
-- Do not hand-edit files inside `cviauto-meta/`, `cviauto-spec-bootstrap/`, `cviauto-session-insight/`, or `cviauto-channel/` under any `.{platform}/skills/` directory expecting the change to persist — they are bundled and refreshed by `cviauto update`. Either contribute upstream or add a project-local skill that complements them.
-- After `cviauto update` reports a "modified by you" conflict on a bundled skill file, choose **keep** only if you accept maintaining the divergence by hand; otherwise accept the overwrite and re-apply the intent as a project-local skill.
+- 不要将每个平台的语法混入一个文件中。
+- 不要仅修改一个平台的入口点却声称支持所有平台。
+- 不要将长期工程约定隐藏在 command 中；将其写入 `.cviauto/spec/`。
+- 不要手动编辑任何 `.{platform}/skills/` 目录下的 `cviauto-meta/`、`cviauto-spec-bootstrap/`、`cviauto-session-insight/` 或 `cviauto-channel/` 中的文件并期望修改能持久——它们是捆绑的，会被 `cviauto update` 刷新。要么贡献给上游，要么添加一个补充它们的项目本地 skill。
+- 当 `cviauto update` 报告捆绑 skill 文件存在"已被您修改"的冲突时，仅当你接受手动维护差异时才选择**保留**；否则接受覆盖并将意图作为项目本地 skill 重新实现。

package/dist/templates/common/bundled-skills/trellis-meta/references/customize-local/change-spec-structure.md

@@ -1,28 +1,28 @@
-# Change Local Spec Structure
+# 修改本地 Spec 结构
 
-When the user wants to change the engineering conventions AI follows, add new spec layers, or adjust monorepo package mapping, edit `.cviauto/spec/` and `.cviauto/config.yaml`.
+当用户想更改 AI 遵循的工程约定、添加新的 spec 层或调整 monorepo 包映射时，编辑 `.cviauto/spec/` 和 `.cviauto/config.yaml`。
 
-## Read These Files First
+## 先阅读这些文件
 
 1. `.cviauto/config.yaml`
 2. `.cviauto/spec/`
-3. `.cviauto/workflow.md` planning artifact guidance and Phase 3.3
-4. Current task `implement.jsonl` / `check.jsonl`
+3. `.cviauto/workflow.md` 中的规划产物指导和 Phase 3.3
+4. 当前 task 的 `implement.jsonl` / `check.jsonl`
 
-## Common Needs
+## 常见需求
 
-| Need | Edit location |
+| 需求 | 编辑位置 |
 | --- | --- |
-| Add backend/frontend/docs/test spec layer | `.cviauto/spec/<layer>/` or `.cviauto/spec/<package>/<layer>/` |
-| Add shared thinking guides | `.cviauto/spec/guides/` |
-| Adjust monorepo packages | `packages` in `.cviauto/config.yaml` |
-| Change default package | `default_package` in `.cviauto/config.yaml` |
-| Control spec scanning scope | `spec_scope` in `.cviauto/config.yaml` |
-| Make a task read a new spec | Task `implement.jsonl` / `check.jsonl` |
+| 添加 backend/frontend/docs/test 的 spec 层 | `.cviauto/spec/<layer>/` 或 `.cviauto/spec/<package>/<layer>/` |
+| 添加共享思维指南 | `.cviauto/spec/guides/` |
+| 调整 monorepo 包 | `.cviauto/config.yaml` 中的 `packages` |
+| 更改默认包 | `.cviauto/config.yaml` 中的 `default_package` |
+| 控制 spec 扫描范围 | `.cviauto/config.yaml` 中的 `spec_scope` |
+| 让 task 读取新的 spec | Task 的 `implement.jsonl` / `check.jsonl` |
 
-## Add A Spec Layer
+## 添加 Spec 层
 
-Single-repository example:
+单仓库示例：
 
 ```text
 .cviauto/spec/security/
@@ -30,7 +30,7 @@ Single-repository example:
 └── auth.md
 ```
 
-Monorepo example:
+Monorepo 示例：
 
 ```text
 .cviauto/spec/webapp/security/
@@ -38,25 +38,25 @@ Monorepo example:
 └── auth.md
 ```
 
-`index.md` should include:
+`index.md` 应包含：
 
-- What code this layer applies to.
-- Pre-Development Checklist.
-- Quality Check.
-- Links to specific guideline files.
+- 该层适用于哪些代码。
+- 开发前检查清单（Pre-Development Checklist）。
+- 质量检查（Quality Check）。
+- 指向具体指南文件的链接。
 
-## Update Context
+## 更新上下文
 
-Adding a spec does not mean every task automatically reads it. The current task must reference it in JSONL:
+添加 spec 并不意味着每个 task 都会自动读取它。当前 task 必须在 JSONL 中引用它：
 
 ```bash
 python3 ./.cviauto/scripts/task.py add-context <task> implement ".cviauto/spec/webapp/security/index.md" "Security conventions"
 python3 ./.cviauto/scripts/task.py add-context <task> check ".cviauto/spec/webapp/security/index.md" "Security review rules"
 ```
 
-## Change Monorepo Packages
+## 更改 Monorepo 包
 
-Example `.cviauto/config.yaml`:
+示例 `.cviauto/config.yaml`：
 
 ```yaml
 packages:
@@ -67,17 +67,17 @@ packages:
 default_package: webapp
 ```
 
-After editing, run:
+编辑后运行：
 
 ```bash
 python3 ./.cviauto/scripts/get_context.py --mode packages
 ```
 
-Use this output to confirm AI can see the correct packages and spec layers.
+使用此输出来确认 AI 能看到正确的包和 spec 层。
 
-## Notes
+## 注意事项
 
-- Specs are user project conventions and can be changed according to project needs.
-- Do not put temporary task information into specs; put temporary information in the task.
-- Do not put long-term conventions only in agents or commands; preserve them in specs.
-- After changing spec structure, check whether existing task JSONL files still point to files that exist.
+- Specs 是用户项目约定，可根据项目需求更改。
+- 不要将临时任务信息放入 specs；将临时信息放入 task 中。
+- 不要将长期约定仅放在 agent 或 command 中；将其保存在 specs 中。
+- 更改 spec 结构后，检查现有 task JSONL 文件是否仍然指向存在的文件。

package/dist/templates/common/bundled-skills/trellis-meta/references/customize-local/change-task-lifecycle.md

@@ -1,31 +1,31 @@
-# Change Local Task Lifecycle
+# 修改本地任务生命周期
 
-Task lifecycle includes creation, start, context configuration, finish, archive, parent/child tasks, and lifecycle hooks. The default customization targets are `.cviauto/tasks/`, `.cviauto/config.yaml`, and `.cviauto/scripts/`.
+任务生命周期包括创建、启动、上下文配置、完成、归档、父子任务以及生命周期钩子。默认的自定义目标是 `.cviauto/tasks/`、`.cviauto/config.yaml` 和 `.cviauto/scripts/`。
 
-## Read These Files First
+## 先阅读这些文件
 
 1. `.cviauto/workflow.md`
 2. `.cviauto/config.yaml`
 3. `.cviauto/scripts/task.py`
 4. `.cviauto/scripts/common/task_store.py`
 5. `.cviauto/scripts/common/task_utils.py`
-6. The current task's `.cviauto/tasks/<task>/task.json`
+6. 当前任务的 `.cviauto/tasks/<task>/task.json`
 
-## Common Needs And Edit Points
+## 常见需求与编辑点
 
-| Need | Edit point |
+| 需求 | 编辑点 |
 | --- | --- |
-| Automatically sync an external system after task creation | `hooks.after_create` in `.cviauto/config.yaml`. |
-| Automatically update status after task start | `hooks.after_start` in `.cviauto/config.yaml`. |
-| Run a script after task finish | `hooks.after_finish` in `.cviauto/config.yaml`. |
-| Clean external resources after archive | `hooks.after_archive` in `.cviauto/config.yaml`. |
-| Change default task fields | `.cviauto/scripts/common/task_store.py`. |
-| Change task parsing/search | `.cviauto/scripts/common/task_utils.py`. |
-| Change active task behavior | `.cviauto/scripts/common/active_task.py`. |
+| 任务创建后自动同步外部系统 | `.cviauto/config.yaml` 中的 `hooks.after_create`。 |
+| 任务启动后自动更新状态 | `.cviauto/config.yaml` 中的 `hooks.after_start`。 |
+| 任务完成后运行脚本 | `.cviauto/config.yaml` 中的 `hooks.after_finish`。 |
+| 归档后清理外部资源 | `.cviauto/config.yaml` 中的 `hooks.after_archive`。 |
+| 修改默认任务字段 | `.cviauto/scripts/common/task_store.py`。 |
+| 修改任务解析/搜索 | `.cviauto/scripts/common/task_utils.py`。 |
+| 修改活动任务行为 | `.cviauto/scripts/common/active_task.py`。 |
 
-## lifecycle hooks
+## 生命周期钩子
 
-`.cviauto/config.yaml` supports:
+`.cviauto/config.yaml` 支持：
 
 ```yaml
 hooks:
@@ -39,13 +39,13 @@ hooks:
     - "python3 .cviauto/scripts/hooks/my_sync.py archive"
 ```
 
-Hook commands receive the `TASK_JSON_PATH` environment variable, pointing to the current task's `task.json`. Hook failures should usually warn, but not block the main task operation.
+钩子命令接收 `TASK_JSON_PATH` 环境变量，指向当前任务的 `task.json`。钩子失败通常应发出警告，但不应阻塞主任务操作。
 
-## Change Task Fields
+## 修改任务字段
 
-If the user wants to add project-local fields, prefer putting them under `meta` in `task.json` to avoid breaking existing scripts' assumptions about standard fields.
+如果用户想要添加项目本地字段，建议将其放在 `task.json` 的 `meta` 下，以避免破坏现有脚本对标准字段的假设。
 
-Example:
+示例：
 
 ```json
 "meta": {
@@ -54,37 +54,37 @@ Example:
 }
 ```
 
-If standard fields really need to change, inspect every local script that reads `task.json`.
+如果确实需要修改标准字段，请检查所有读取 `task.json` 的本地脚本。
 
-## Change Active Task
+## 修改活动任务
 
-Active task is session-level state stored in `.cviauto/.runtime/sessions/`. Do not fall back to a global `.current-task` model. If the user wants to change active task behavior, edit:
+活动任务是存储在 `.cviauto/.runtime/sessions/` 中的会话级状态。不要回退到全局 `.current-task` 模型。如果用户想要修改活动任务行为，请编辑：
 
 - `.cviauto/scripts/common/active_task.py`
-- platform hooks or shell session bridges
-- active task descriptions in `.cviauto/workflow.md`
+- 平台钩子或 shell 会话桥接
+- `.cviauto/workflow.md` 中的活动任务描述
 
-### `task.py create` Sets the Active Pointer
+### `task.py create` 设置活动指针
 
-`cmd_create` in `.cviauto/scripts/common/task_store.py` calls `set_active_task` best-effort right after writing the new task directory. The behavior:
+`.cviauto/scripts/common/task_store.py` 中的 `cmd_create` 在写入新任务目录后立即尽最大努力（best-effort）调用 `set_active_task`。其行为如下：
 
-- When the calling shell carries session identity (`TRELLIS_CONTEXT_ID` env var, or any platform-specific session env that `resolve_context_key` recognizes — see `active_task.py:_ENV_SESSION_KEYS`), the per-session pointer at `.cviauto/.runtime/sessions/<context_key>.json` is rewritten to point at the new task. The task's `status=planning` and `[workflow-state:planning]` fires on the very next `UserPromptSubmit`.
-- When session identity is unavailable (raw CLI invocation outside an AI session, or a platform that doesn't propagate identity to shell), the task directory is still created and `status=planning` is still written, but the active pointer is left untouched. The user can attach the task later with `task.py start <dir>` once they're back in an AI session.
+- 当调用 shell 携带会话身份标识（`TRELLIS_CONTEXT_ID` 环境变量，或 `resolve_context_key` 能识别的任何平台特定会话环境变量——参见 `active_task.py:_ENV_SESSION_KEYS`）时，`.cviauto/.runtime/sessions/<context_key>.json` 中的按会话指针会被重写为指向新任务。任务 `status=planning`，且 `[workflow-state:planning]` 会在紧接着的 `UserPromptSubmit` 时触发。
+- 当会话身份不可用时（AI 会话之外的原始 CLI 调用，或不传播身份到 shell 的平台），任务目录仍会被创建，`status=planning` 仍会被写入，但活动指针保持不变。用户可以在回到 AI 会话后通过 `task.py start <dir>` 附加该任务。
 
-This makes `[workflow-state:planning]` the live breadcrumb during the brainstorm and JSONL curation work that follows `task.py create`. The pre-R7 behavior left the breadcrumb stuck on `no_task` until `task.py start`, so the planning block was effectively dead text.
+这使得 `[workflow-state:planning]` 成为 `task.py create` 之后的头脑风暴和 JSONL 整理工作中的实时面包屑导航。R7 之前的行为会将面包屑卡在 `no_task` 直到 `task.py start`，因此 planning 块实际上是一段死文本。
 
-If you fork `task.py` to add a new creation path (e.g. an external import that bypasses `cmd_create`), audit whether your path also calls `set_active_task`. Without that call, your created tasks will not surface as active. The full status writer table is in `.cviauto/spec/cli/backend/workflow-state-contract.md`.
+如果你 fork `task.py` 添加新的创建路径（例如绕过 `cmd_create` 的外部导入），请检查你的路径是否也调用了 `set_active_task`。没有该调用，你创建的任务将不会作为活动任务出现。完整的状态写入表位于 `.cviauto/spec/cli/backend/workflow-state-contract.md`。
 
-## Modification Steps
+## 修改步骤
 
-1. Confirm the current task with `python3 ./.cviauto/scripts/task.py current --source`.
-2. Read the current task's `task.json` and confirm status and fields.
-3. For configuration needs, edit `.cviauto/config.yaml` first.
-4. For script behavior needs, then edit `.cviauto/scripts/`.
-5. If the AI flow changed, synchronize `.cviauto/workflow.md`.
+1. 使用 `python3 ./.cviauto/scripts/task.py current --source` 确认当前任务。
+2. 读取当前任务的 `task.json` 并确认状态和字段。
+3. 对于配置需求，首先编辑 `.cviauto/config.yaml`。
+4. 对于脚本行为需求，然后编辑 `.cviauto/scripts/`。
+5. 如果 AI 流程发生变化，同步更新 `.cviauto/workflow.md`。
 
-## Do Not
+## 不要做的事
 
-- Do not directly edit `.cviauto/.runtime/sessions/` to "fix" business state.
-- Do not hard-code project-private fields into scripts; prefer `meta`.
-- Do not default to asking the user to fork Cviauto CLI.
+- 不要直接编辑 `.cviauto/.runtime/sessions/` 来"修复"业务状态。
+- 不要将项目私有字段硬编码到脚本中；优先使用 `meta`。
+- 不要默认让用户 fork Cviauto CLI。

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

@@ -1,66 +1,66 @@
-# Change Local Workflow
+# 修改本地工作流
 
-When the user wants to change Cviauto phases, next-action hints, whether to create tasks, whether to use sub-agents, or when to check/wrap up, edit `.cviauto/workflow.md` first.
+当用户想要修改 Cviauto 阶段、下一步提示、是否创建任务、是否使用子代理，或何时检查/收尾时，首先编辑 `.cviauto/workflow.md`。
 
-## Read These Files First
+## 先阅读这些文件
 
 1. `.cviauto/workflow.md`
-2. Entry files for the current platform, such as skills/commands/prompts/workflows
-3. The current task's `task.json` and `prd.md`
+2. 当前平台的入口文件，如 skills/commands/prompts/workflows
+3. 当前任务的 `task.json` 和 `prd.md`
 
-## Common Needs And Edit Points
+## 常见需求与编辑点
 
-| Need | Edit point |
+| 需求 | 编辑点 |
 | --- | --- |
-| Change phase names or phase order | `Phase Index` and the corresponding Phase sections. |
-| Change whether to create a task when there is no task | `[workflow-state:no_task]` state block. |
-| Change the next step during planning | Phase 1 and `[workflow-state:planning]`. |
-| Change whether an agent is required during in_progress | Phase 2 and `[workflow-state:in_progress]`. |
-| Change wrap-up after completion | Phase 3 and `[workflow-state:completed]`. |
-| Change which skill a user intent triggers | `Skill Routing` table. |
+| 修改阶段名称或阶段顺序 | `Phase Index` 及对应的 Phase 章节。 |
+| 修改无任务时是否创建任务 | `[workflow-state:no_task]` 状态块。 |
+| 修改规划期间的下一步 | Phase 1 和 `[workflow-state:planning]`。 |
+| 修改 in_progress 期间是否需要代理 | Phase 2 和 `[workflow-state:in_progress]`。 |
+| 修改完成后的收尾 | Phase 3 和 `[workflow-state:completed]`。 |
+| 修改用户意图触发哪个 skill | `Skill Routing` 表格。 |
 
-## Modification Steps
+## 修改步骤
 
-1. Find the relevant section in `.cviauto/workflow.md`.
-2. When changing rules, keep explicit trigger conditions and next actions.
-3. If adding or renaming a skill/agent, synchronize the corresponding files in platform directories.
-4. Workflow-state changes only need an edit to the `[workflow-state:STATUS]` block in `.cviauto/workflow.md`. The hook is parser-only — it reads whatever you put in the block. Keep the opening and closing tags' STATUS strings identical (`[workflow-state:foo]…[/workflow-state:foo]`); mismatched STATUS pairs are silently dropped.
-5. Make the AI reread `.cviauto/workflow.md`; do not keep using rules from the old conversation.
+1. 在 `.cviauto/workflow.md` 中找到相关章节。
+2. 修改规则时，保留明确的触发条件和下一步操作。
+3. 如果添加或重命名 skill/agent，同步更新平台目录中的对应文件。
+4. 工作流状态变更只需编辑 `.cviauto/workflow.md` 中的 `[workflow-state:STATUS]` 块。钩子是纯解析器——它会读取你在块中放入的任何内容。保持开始和结束标签的 STATUS 字符串一致（`[workflow-state:foo]…[/workflow-state:foo]`）；不匹配的 STATUS 对会被静默丢弃。
+5. 让 AI 重新读取 `.cviauto/workflow.md`；不要继续使用旧对话中的规则。
 
-## Example: Relax Task Creation Requirements
+## 示例：放宽任务创建要求
 
-To change when task creation can be skipped, usually edit `[workflow-state:no_task]`:
+要修改可以跳过任务创建的情形，通常编辑 `[workflow-state:no_task]`：
 
 ```md
 [workflow-state:no_task]
-Task is not required when the answer is a one-reply explanation, no files are changed, and no research is needed.
+当答案是单次回复说明、不涉及文件变更且无需调研时，不需要创建任务。
 [/workflow-state:no_task]
 ```
 
-If the formal Phase 1 flow also needs to change, synchronize the Phase 1 section.
+如果正式的 Phase 1 流程也需要变更，同步修改 Phase 1 章节。
 
-## Example: One Platform Does Not Use Sub-Agents
+## 示例：某个平台不使用子代理
 
-If the user wants only one platform to avoid sub-agents, first confirm whether that platform has a separate group in the workflow. Then change Phase 2 routing for that platform group instead of deleting all `cviauto-implement` / `cviauto-check` instructions across platforms.
+如果用户只想让某个平台避免使用子代理，首先确认该平台在工作流中是否有独立的分组。然后修改该平台分组的 Phase 2 路由，而不是跨平台删除所有 `cviauto-implement` / `cviauto-check` 指令。
 
-## `/cviauto:continue` Route Table
+## `/cviauto:continue` 路由表
 
-`/cviauto:continue` resumes a task by deciding which phase step to load next. The decision combines `task.json.status` with the presence of artifacts inside the task directory. The mapping is fixed in the command itself; forks that add custom statuses must extend both the workflow.md tag block and this table.
+`/cviauto:continue` 通过决定下一步加载哪个阶段步骤来恢复任务。决策结合了 `task.json.status` 与任务目录中工件（artifact）的存在情况。映射关系在命令本身中固定；添加自定义状态的 fork 必须同时扩展 workflow.md 标签块和此路由表。
 
-| `status` | Artifact state | Resume at |
+| `status` | 工件状态 | 恢复到 |
 | --- | --- | --- |
-| `planning` | `prd.md` missing | Phase 1.1 (load `cviauto-brainstorm`) |
-| `planning` | lightweight task with `prd.md` complete | ask for start review, then run `task.py start` |
-| `planning` | complex task missing `design.md` or `implement.md` | complete missing planning artifacts |
-| `planning` | complex task has `prd.md`, `design.md`, and `implement.md` | ask for start review, then run `task.py start` |
-| `in_progress` | no implementation in conversation history | Phase 2.1 (`cviauto-implement`) |
-| `in_progress` | implementation done, no `cviauto-check` run | Phase 2.2 (`cviauto-check`) |
-| `in_progress` | check passed, no explicit spec-promotion request | Phase 3.4 (commit) |
-| `in_progress` | check passed, user explicitly asks to promote knowledge into spec | Phase 3.3 (spec update proposal) → 3.4 (commit) |
-| `completed` | task is still in active tree | Phase 3.5 (run `/cviauto:finish-work` to archive) |
+| `planning` | `prd.md` 缺失 | Phase 1.1（加载 `cviauto-brainstorm`） |
+| `planning` | 轻量任务且 `prd.md` 已完成 | 询问开始审查，然后运行 `task.py start` |
+| `planning` | 复杂任务缺少 `design.md` 或 `implement.md` | 补全缺失的规划工件 |
+| `planning` | 复杂任务包含 `prd.md`、`design.md` 和 `implement.md` | 询问开始审查，然后运行 `task.py start` |
+| `in_progress` | 对话历史中无实现记录 | Phase 2.1（`cviauto-implement`） |
+| `in_progress` | 实现已完成，未运行 `cviauto-check` | Phase 2.2（`cviauto-check`） |
+| `in_progress` | 检查已通过，无显式的 spec 提升请求 | Phase 3.4（commit） |
+| `in_progress` | 检查已通过，用户显式要求将知识提升到 spec | Phase 3.3（spec 更新提案）→ 3.4（commit） |
+| `completed` | 任务仍在活动树中 | Phase 3.5（运行 `/cviauto:finish-work` 进行归档） |
 
-When you add a custom status (e.g. `in-review`), add a `[workflow-state:in-review]` block in `.cviauto/workflow.md` for the per-turn breadcrumb AND extend this route table — usually by editing the `/cviauto:continue` command file (`.{platform}/commands/cviauto/continue.md` or equivalent) to add a row that decides where to resume from. Without the route entry, `/cviauto:continue` will fall through to a default branch and the user will not land on the step you intended.
+当你添加自定义状态（如 `in-review`）时，在 `.cviauto/workflow.md` 中为每轮面包屑导航添加 `[workflow-state:in-review]` 块，并扩展此路由表——通常通过编辑 `/cviauto:continue` 命令文件（`{platform}/commands/cviauto/continue.md` 或等效文件）来添加一行，决定从何处恢复。没有路由条目时，`/cviauto:continue` 会落入默认分支，用户将无法到达你预期的步骤。
 
-## Notes
+## 注意事项
 
-`.cviauto/workflow.md` is the local project workflow, not an immutable template. The user can adapt it to team habits. After editing it, platform entry files may still contain old descriptions, so inspect them too.
+`.cviauto/workflow.md` 是本地项目工作流，而非不可变的模板。用户可以根据团队习惯进行调整。编辑后，平台入口文件可能仍包含旧描述，因此也需要检查它们。