@baoanaz/cviauto 0.6.6 → 0.6.8

package/dist/templates/common/bundled-skills/trellis-meta/SKILL.md

@@ -5,81 +5,81 @@ description: "Understand and customize the local Cviauto architecture inside a u
 
 # Cviauto Meta
 
-This skill is for local Cviauto users who have already run `cviauto init` in a project. After reading it, an AI should understand the Cviauto architecture, operating model, and customization entry points inside that user project, then modify the generated `.cviauto/` and platform directory files according to the user's request.
-
-Cviauto v0.6 adds three architectural surfaces on top of the pre-v0.6 workflow / persistence / platform model. First, a multi-agent collaboration runtime: `cviauto channel` coordinates multiple AI worker processes through project-scoped JSONL event logs at `~/.cviauto/channels/<project>/<channel>/events.jsonl`, with worker OOM guard, forum/thread channels, durable idempotency keys, and bundled `.cviauto/agents/{check,implement}.md` runtime definitions. Second, cross-session memory: `cviauto mem list | search | context | extract | projects` reads raw Claude Code, Codex, and Pi Agent JSONL already on disk, slices by `--phase brainstorm|implement|all`, and never uploads anything. Third, a dual-package npm release: `@baoanaz/cviauto` (CLI) and `@baoanaz/cviauto-core` (SDK with `/channel`, `/task`, `/mem`, `/testing` subpaths) ship in lockstep on one version. Treat these as first-class customization surfaces alongside the per-platform integration files.
-
-The default operating scope is local files in the user project:
-
-- `.cviauto/`: workflow, config, tasks, spec, workspace, scripts, bundled runtime agents, and runtime state.
-- Platform directories: `.claude/`, `.codex/`, `.cursor/`, `.opencode/`, `.kiro/`, `.gemini/`, `.qoder/`, `.codebuddy/`, `.github/`, `.factory/`, `.pi/`, `.reasonix/`, `.kilocode/`, `.agent/`, `.devin/`, and similar directories. Pi additionally exposes a native `trellis_subagent` tool with `single` / `parallel` / `chain` dispatch modes, throttled progress cards, and `isTrellisAgent()` validation on top of the file layout. Reasonix stores both workflow skills and subagent skills as `.reasonix/skills/<name>/SKILL.md`; subagent skills carry `runAs: subagent` frontmatter.
-- Shared skill layer: `.agents/skills/`.
-- User-owned channel store outside the project tree: `~/.cviauto/channels/<project>/<channel>/events.jsonl`.
-- Raw platform conversation logs queryable via `cviauto mem`: `~/.claude/projects/`, `~/.codex/sessions/`, and `~/.pi/agent/sessions/` (OpenCode adapter degraded for the v0.6 line).
-
-Do not assume the user has the Cviauto source repository. Do not default to modifying the global npm install directory or `node_modules` — both `@baoanaz/cviauto` and `@baoanaz/cviauto-core` ship as published packages sharing one version and one git tag per release.
-
-## How To Use
-
-1. Read `references/local-architecture/overview.md` first to establish the local Cviauto system model.
-2. If the request involves a specific AI tool, read `references/platform-files/platform-map.md` and the relevant platform file notes.
-3. If the request involves multi-agent dispatch or channel workers, read `references/local-architecture/multi-agent-channel.md` and the bundled `.cviauto/agents/` files.
-4. If the user wants to change behavior, read `references/customize-local/overview.md`, then open the specific customization topic.
-5. Before editing, read the actual files in the user project and treat local content as authoritative.
-
-## References
-
-### Local Architecture
-
-- `references/local-architecture/overview.md`: The layered local Cviauto architecture (workflow / persistence / platform / channel runtime) and customization principles.
-- `references/local-architecture/generated-files.md`: Files generated by `cviauto init` and their customization boundaries, including `.cviauto/agents/`.
-- `references/local-architecture/workflow.md`: Phases, routing, workflow-state blocks, and selectable workflow templates (`native`, `tdd`, `channel-driven-subagent-dispatch`, marketplace) in `.cviauto/workflow.md`.
-- `references/local-architecture/task-system.md`: Task directories, active task, JSONL context, parent/child task trees, and task runtime.
-- `references/local-architecture/spec-system.md`: How `.cviauto/spec/` is organized, injected, and refreshed from a `registry.spec` source.
-- `references/local-architecture/workspace-memory.md`: `.cviauto/workspace/` journals plus `cviauto mem` cross-session recall and the `@baoanaz/cviauto-core/mem` SDK.
-- `references/local-architecture/context-injection.md`: Hooks, sub-agent preludes, and channel-runtime worker inbox routing.
-- `references/local-architecture/multi-agent-channel.md`: `cviauto channel` subcommands, project-scoped event store, forum/thread channels, worker OOM guard, durable idempotency, and bundled `.cviauto/agents/` runtime agents.
-- `references/local-architecture/bundled-skills.md`: Auto-dispatched bundled skills (`cviauto-meta`, `cviauto-spec-bootstrap`, `cviauto-session-insight`) and how `getBundledSkillTemplates()` ships them to every platform skill root.
-
-### Platform Files
-
-- `references/platform-files/overview.md`: How shared `.cviauto/` files relate to platform directories and the four platform integration modes (hook-driven, agent prelude, main-session workflow, channel runtime).
-- `references/platform-files/platform-map.md`: Platform directories and paths for skills, agents, hooks, and extensions across all 15 supported platforms including Reasonix and Pi's native `trellis_subagent` extension.
-- `references/platform-files/hooks-and-settings.md`: How settings/config files, hooks, plugins, and extensions connect to Cviauto; covers `channel.worker_guard.*` and `codex.dispatch_mode`.
-- `references/platform-files/agents.md`: Per-platform `cviauto-research` / `cviauto-implement` / `cviauto-check` sub-agent files plus bundled `.cviauto/agents/{check,implement}.md` for the channel runtime.
-- `references/platform-files/skills-and-commands.md`: Differences between skills, commands, prompts, and workflows, plus how to change them.
-
-### Local Customization
-
-- `references/customize-local/overview.md`: Choose the right local customization entry point for the user's request.
-- `references/customize-local/change-workflow.md`: Change phases, routing, next actions, workflow-state, and the selected workflow template.
-- `references/customize-local/change-task-lifecycle.md`: Change task creation, status, archive behavior, parent/child links, archive slug collision handling, and lifecycle hooks.
-- `references/customize-local/change-context-loading.md`: Change how tasks, specs, journals, hook context, channel inbox messages, and `cviauto mem` recall are loaded.
-- `references/customize-local/change-hooks.md`: Change platform hooks, settings, task lifecycle hooks (`hooks.after_*`), and shell session bridges.
-- `references/customize-local/change-agents.md`: Change research, implement, and check agent behavior across platform sub-agents, bundled channel runtime agents, and the Codex `dispatch_mode` toggle.
-- `references/customize-local/change-skills-or-commands.md`: Add or modify local skills, commands, prompts, and workflows; covers upstream bundled-skill auto-dispatch.
-- `references/customize-local/change-spec-structure.md`: Adjust the project spec structure under `.cviauto/spec/`, including registry-backed sources.
-- `references/customize-local/add-project-local-conventions.md`: Put team rules into project-local specs or local skills.
-
-## Current Rules
-
-- `.cviauto/workflow.md` is the local workflow source of truth; its initial content was selected from a workflow template (built-in `native`, `tdd`, `channel-driven-subagent-dispatch`, or a marketplace template) at `cviauto init` time and can be re-selected via `cviauto workflow --template <id>`. Missing `.cviauto/agents/<name>.md` files referenced by the active template trigger a non-blocking stderr warning pointing at `cviauto update`.
-- `.cviauto/config.yaml` is the project-level Cviauto configuration entry point. It hosts task lifecycle hooks (`hooks.after_create` / `after_start` / `after_finish` / `after_archive`), journal shape (`session_commit_message` / `max_journal_lines` / `session_auto_commit`), channel worker guard (`channel.worker_guard.idle_timeout` / `max_live_workers`), Codex dispatch mode (`codex.dispatch_mode: inline | sub-agent`), and the spec registry block (`registry.spec.source` + `registry.spec.template`).
-- `.cviauto/spec/` stores the user's project-specific coding conventions and design constraints. When `registry.spec` is set, files are refreshed by `cviauto update`; local edits surface as "modified by user" conflicts in `.cviauto/.template-hashes.json`.
-- `.cviauto/tasks/` stores task PRDs, design notes, implement plans, research files, and JSONL context. Tasks form parent/child trees: `task.py create --parent <slug>`, `task.py add-subtask <parent> <child>`, `task.py remove-subtask <parent> <child>`, and `task.py list-context <task>`. `task.py create` rejects a slug already present in `.cviauto/tasks/archive/**`.
-- `.cviauto/workspace/` stores **deliberately written** developer journals. Raw cross-session dialogue is **not** stored here — it lives on disk under `~/.claude/projects/`, `~/.codex/sessions/`, and `~/.pi/agent/sessions/` and is recovered via `cviauto mem search|extract|context`. The bundled `cviauto-session-insight` skill teaches when to reach for `mem`.
-- `.cviauto/agents/{check,implement}.md` are bundled, platform-agnostic channel runtime agent definitions loaded by `cviauto channel spawn --agent <name>`. Editable; `cviauto update` backfills missing ones. Editing the per-platform `cviauto-implement.md` / `cviauto-check.md` does **not** change channel-runtime worker behavior.
-- `~/.cviauto/channels/<project>/<channel>/events.jsonl` is the channel runtime event log per project per channel. User-owned, file-locked sequence numbering, durable `idempotencyKey` support; never under `.cviauto/`.
-- Bundled multi-file skills (`cviauto-meta`, `cviauto-spec-bootstrap`, `cviauto-session-insight`, `cviauto-channel`) are auto-dispatched to every platform skill root by `getBundledSkillTemplates()` in `packages/cli/src/templates/common/index.ts`. Dropping a new directory under `packages/cli/src/templates/common/bundled-skills/` (upstream) ships it to every platform on the next `cviauto update`.
-- Platform settings/config files decide which hooks, agents, skills, commands, prompts, and workflows actually run. Reasonix has no settings file — behavior is encoded inside skill frontmatter.
-- `.cviauto/.template-hashes.json` and `.cviauto/.runtime/` are management/runtime state files. Confirm necessity before editing them.
-
-## Do Not
-
-- Do not treat Cviauto upstream source code as the default target for local customization.
-- Do not modify the global npm install directory or `node_modules/@baoanaz/cviauto` or `node_modules/@baoanaz/cviauto-core` to implement project needs; both packages ship in lockstep.
-- Do not overwrite user-modified local files with default templates; check `.cviauto/.template-hashes.json` first and prefer `.new` sidecar files over destructive overwrites.
-- Do not put team-private project rules into any public bundled skill (`cviauto-meta`, `cviauto-spec-bootstrap`, `cviauto-session-insight`, `cviauto-channel`); put project rules in `.cviauto/spec/`, a project-local skill, the current task, or the workspace journal — `cviauto update` will overwrite anything inside a bundled skill directory.
-- Do not hand-edit `~/.cviauto/channels/<project>/<channel>/events.jsonl`; sequence numbers are assigned under a file lock and replay-safe writes go through the `cviauto channel` CLI or the `@baoanaz/cviauto-core/channel` SDK.
-- Do not edit `.claude/agents/cviauto-implement.md` (or any other per-platform sub-agent file) when the goal is to change channel runtime worker behavior — edit `.cviauto/agents/<name>.md` instead.
-- Do not describe removed or never-shipped mechanisms as current Cviauto behavior; cross-check against the local `.cviauto/config.yaml` and the installed CLI's `trellis --help` before claiming a knob exists.
+此技能面向已运行过 `cviauto init` 的本地 Cviauto 用户。阅读后，AI 应理解用户项目内的 Cviauto 架构、运行模型和自定义入口点，然后根据用户请求修改生成的 `.cviauto/` 和平台目录文件。
+
+Cviauto v0.6 在 v0.6 之前的工作流/持久化/平台模型之上增加了三个架构层面。第一，多 Agent 协作运行时：`cviauto channel` 通过项目范围的 JSONL 事件日志（位于 `~/.cviauto/channels/<project>/<channel>/events.jsonl`）协调多个 AI worker 进程，具有 worker OOM 守护、forum/thread 频道、持久幂等 key 和打包的 `.cviauto/agents/{check,implement}.md` 运行时定义。第二，跨会话记忆：`cviauto mem list | search | context | extract | projects` 读取已存在于磁盘上的 Claude Code、Codex 和 Pi Agent JSONL，按 `--phase brainstorm|implement|all` 切片，且绝不上传任何内容。第三，双包 npm 发布：`@mindfoldhq/cviauto`（CLI）和 `@mindfoldhq/cviauto-core`（SDK，提供 `/channel`、`/task`、`/mem`、`/testing` 子路径）在同一版本上同步发布。将这些视为与各平台集成文件并列的一等自定义层面。
+
+默认操作范围是用户项目中的本地文件：
+
+- `.cviauto/`：工作流、配置、任务、spec、工作区、脚本、打包的运行时 Agent 和运行时状态。
+- 平台目录：`.claude/`、`.codex/`、`.cursor/`、`.opencode/`、`.kiro/`、`.gemini/`、`.qoder/`、`.codebuddy/`、`.github/`、`.factory/`、`.pi/`、`.reasonix/`、`.kilocode/`、`.agent/`、`.devin/` 和类似目录。Pi 还暴露了原生 `trellis_subagent` 工具，支持 `single` / `parallel` / `chain` 分发模式、节流进度卡和基于文件布局的 `isTrellisAgent()` 验证。Reasonix 将工作流技能和 sub-agent 技能存储为 `.reasonix/skills/<name>/SKILL.md`；sub-agent 技能具有 `runAs: subagent` frontmatter。
+- 共享技能层：`.agents/skills/`。
+- 项目树之外的用户自有频道存储：`~/.cviauto/channels/<project>/<channel>/events.jsonl`。
+- 可通过 `cviauto mem` 查询的原始平台对话日志：`~/.claude/projects/`、`~/.codex/sessions/` 和 `~/.pi/agent/sessions/`（OpenCode 适配器在 v0.6 系列中降级）。
+
+不要假设用户有 Cviauto 源码仓库。不要默认修改全局 npm 安装目录或 `node_modules`——`@mindfoldhq/cviauto` 和 `@mindfoldhq/cviauto-core` 作为已发布包交付，共享一个版本和每个发布的一个 git tag。
+
+## 如何使用
+
+1. 首先阅读 `references/local-architecture/overview.md` 建立本地 Cviauto 系统模型。
+2. 如果请求涉及特定 AI 工具，阅读 `references/platform-files/platform-map.md` 和相关平台文件说明。
+3. 如果请求涉及多 Agent 分发或 channel worker，阅读 `references/local-architecture/multi-agent-channel.md` 和打包的 `.cviauto/agents/` 文件。
+4. 如果用户想改变行为，阅读 `references/customize-local/overview.md`，然后打开具体的自定义主题。
+5. 编辑前，阅读用户项目中的实际文件，将本地内容视为权威来源。
+
+## 参考文件
+
+### 本地架构
+
+- `references/local-architecture/overview.md`：分层本地 Cviauto 架构（工作流 / 持久化 / 平台 / channel 运行时）和自定义原则。
+- `references/local-architecture/generated-files.md`：由 `cviauto init` 生成的文件及其自定义边界，包括 `.cviauto/agents/`。
+- `references/local-architecture/workflow.md`：阶段、路由、工作流状态块和可选工作流模板（`native`、`tdd`、`channel-driven-subagent-dispatch`、marketplace），位于 `.cviauto/workflow.md`。
+- `references/local-architecture/task-system.md`：任务目录、活动任务、JSONL 上下文、父子任务树和任务运行时。
+- `references/local-architecture/spec-system.md`：`.cviauto/spec/` 的组织、注入和从 `registry.spec` 源刷新。
+- `references/local-architecture/workspace-memory.md`：`.cviauto/workspace/` 日志加上 `cviauto mem` 跨会话回忆和 `@mindfoldhq/cviauto-core/mem` SDK。
+- `references/local-architecture/context-injection.md`：Hooks、sub-agent 前置和 channel 运行时 worker 收件箱路由。
+- `references/local-architecture/multi-agent-channel.md`：`cviauto channel` 子命令、项目范围事件存储、forum/thread 频道、worker OOM 守护、持久幂等和打包的 `.cviauto/agents/` 运行时 Agent。
+- `references/local-architecture/bundled-skills.md`：自动分发的打包技能（`cviauto-meta`、`cviauto-spec-bootstrap`、`cviauto-session-insight`）以及 `getBundledSkillTemplates()` 如何将它们部署到每个平台技能根目录。
+
+### 平台文件
+
+- `references/platform-files/overview.md`：共享 `.cviauto/` 文件如何与平台目录关联，以及四种平台集成模式（hook 驱动、Agent 前置、主会话工作流、channel 运行时）。
+- `references/platform-files/platform-map.md`：所有 15 个支持平台（包括 Reasonix 和 Pi 的原生 `trellis_subagent` 扩展）中技能、Agent、hooks 和扩展的平台目录和路径。
+- `references/platform-files/hooks-and-settings.md`：设置/配置文件、hooks、插件和扩展如何连接到 Cviauto；涵盖 `channel.worker_guard.*` 和 `codex.dispatch_mode`。
+- `references/platform-files/agents.md`：每个平台的 `cviauto-research` / `cviauto-implement` / `cviauto-check` sub-agent 文件，加上 channel 运行时打包的 `.cviauto/agents/{check,implement}.md`。
+- `references/platform-files/skills-and-commands.md`：技能、命令、prompt 和工作流之间的区别，以及如何修改它们。
+
+### 本地自定义
+
+- `references/customize-local/overview.md`：为用户请求选择合适的本地自定义入口点。
+- `references/customize-local/change-workflow.md`：更改阶段、路由、下一步操作、工作流状态和选定的工作流模板。
+- `references/customize-local/change-task-lifecycle.md`：更改任务创建、状态、归档行为、父子链接、归档 slug 冲突处理和生命周期 hooks。
+- `references/customize-local/change-context-loading.md`：更改任务、spec、日志、hook 上下文、channel 收件箱消息和 `cviauto mem` 回忆的加载方式。
+- `references/customize-local/change-hooks.md`：更改平台 hooks、设置、任务生命周期 hooks（`hooks.after_*`）和 shell 会话桥接。
+- `references/customize-local/change-agents.md`：更改跨平台 sub-agent、打包 channel 运行时 Agent 的 research、implement 和 check Agent 行为，以及 Codex `dispatch_mode` 开关。
+- `references/customize-local/change-skills-or-commands.md`：添加或修改本地技能、命令、prompt 和工作流；涵盖上游打包技能自动分发。
+- `references/customize-local/change-spec-structure.md`：调整 `.cviauto/spec/` 下的项目 spec 结构，包括注册表支持的源。
+- `references/customize-local/add-project-local-conventions.md`：将团队规则放入项目本地 spec 或本地技能。
+
+## 当前规则
+
+- `.cviauto/workflow.md` 是本地工作流唯一权威来源；其初始内容在 `cviauto init` 时从工作流模板（内置 `native`、`tdd`、`channel-driven-subagent-dispatch` 或 marketplace 模板）中选择，并可通过 `cviauto workflow --template <id>` 重新选择。活动模板引用但缺失的 `.cviauto/agents/<name>.md` 文件会触发非阻塞 stderr 警告，指向 `cviauto update`。
+- `.cviauto/config.yaml` 是项目级 Cviauto 配置入口点。它托管任务生命周期 hooks（`hooks.after_create` / `after_start` / `after_finish` / `after_archive`）、日志形状（`session_commit_message` / `max_journal_lines` / `session_auto_commit`）、channel worker 守护（`channel.worker_guard.idle_timeout` / `max_live_workers`）、Codex 分发模式（`codex.dispatch_mode: inline | sub-agent`）和 spec 注册表块（`registry.spec.source` + `registry.spec.template`）。
+- `.cviauto/spec/` 存储用户的项目特定编码规范和设计约束。当设置了 `registry.spec` 时，文件由 `cviauto update` 刷新；本地编辑在 `.cviauto/.template-hashes.json` 中显示为"用户已修改"冲突。
+- `.cviauto/tasks/` 存储任务 PRD、设计笔记、实现计划、研究文件和 JSONL 上下文。任务形成父子树：`task.py create --parent <slug>`、`task.py add-subtask <parent> <child>`、`task.py remove-subtask <parent> <child>` 和 `task.py list-context <task>`。`task.py create` 拒绝 `.cviauto/tasks/archive/**` 中已存在的 slug。
+- `.cviauto/workspace/` 存储**刻意编写的**开发者日志。原始跨会话对话**不**存储在此——它们存在于 `~/.claude/projects/`、`~/.codex/sessions/` 和 `~/.pi/agent/sessions/` 磁盘中，通过 `cviauto mem search|extract|context` 恢复。打包的 `cviauto-session-insight` 技能教 AI 何时使用 `mem`。
+- `.cviauto/agents/{check,implement}.md` 是打包的、平台无关的 channel 运行时 Agent 定义，由 `cviauto channel spawn --agent <name>` 加载。可编辑；`cviauto update` 回填缺失的文件。编辑每个平台的 `cviauto-implement.md` / `cviauto-check.md` **不会**改变 channel 运行时 worker 的行为。
+- `~/.cviauto/channels/<project>/<channel>/events.jsonl` 是每个项目每个频道的 channel 运行时事件日志。用户拥有，文件锁定的序列号分配，持久的 `idempotencyKey` 支持；绝不在 `.cviauto/` 下。
+- 打包的多文件技能（`cviauto-meta`、`cviauto-spec-bootstrap`、`cviauto-session-insight`、`cviauto-channel`）由 `packages/cli/src/templates/common/index.ts` 中的 `getBundledSkillTemplates()` 自动分发到每个平台的技能根目录。在 `packages/cli/src/templates/common/bundled-skills/`（上游）下放置新目录，将在下次 `cviauto update` 时将其部署到每个平台。
+- 平台设置/配置文件决定哪些 hooks、Agent、技能、命令、prompt 和工作流实际运行。Reasonix 没有设置文件——行为编码在技能 frontmatter 中。
+- `.cviauto/.template-hashes.json` 和 `.cviauto/.runtime/` 是管理/运行时状态文件。编辑前请确认必要性。
+
+## 不要
+
+- 不要将 Cviauto 上游源码视为本地自定义的默认目标。
+- 不要修改全局 npm 安装目录或 `node_modules/@mindfoldhq/cviauto` 或 `node_modules/@mindfoldhq/cviauto-core` 来实现项目需求；两个包同步发布。
+- 不要用默认模板覆盖用户已修改的本地文件；先检查 `.cviauto/.template-hashes.json`，优先使用 `.new` 侧车文件而非破坏性覆盖。
+- 不要把团队私有项目规则放入任何公共打包技能（`cviauto-meta`、`cviauto-spec-bootstrap`、`cviauto-session-insight`、`cviauto-channel`）；将项目规则放入 `.cviauto/spec/`、项目本地技能、当前任务或工作区日志——`cviauto update` 会覆盖打包技能目录中的所有内容。
+- 不要手动编辑 `~/.cviauto/channels/<project>/<channel>/events.jsonl`；序列号在文件锁下分配，可安全重放的写入通过 `cviauto channel` CLI 或 `@mindfoldhq/cviauto-core/channel` SDK 进行。
+- 当目标是改变 channel 运行时 worker 行为时，不要编辑 `.claude/agents/cviauto-implement.md`（或任何其他每个平台的 sub-agent 文件）——改为编辑 `.cviauto/agents/<name>.md`。
+- 不要将被移除或从未发布的机制描述为当前 Cviauto 行为；在声称某个配置项存在之前，交叉核对本地 `.cviauto/config.yaml` 和已安装 CLI 的 `cviauto --help`。

package/dist/templates/common/bundled-skills/trellis-meta/references/customize-local/add-project-local-conventions.md

@@ -1,31 +1,31 @@
-# Add Project-Local Conventions
+# 添加项目本地约定
 
-Often the user does not need to change Cviauto mechanics; they need local AI to understand their team's conventions. In that case, prefer `.cviauto/spec/` or a project-local skill instead of editing `cviauto-meta`.
+用户通常不需要更改 Cviauto 机制本身；他们需要让本地 AI 理解其团队的约定。在这种情况下，优先使用 `.cviauto/spec/` 或项目本地 skill，而非编辑 `cviauto-meta`。
 
-## Where To Put Things
+## 各类内容放置位置
 
-| Content type | Location |
+| 内容类型 | 位置 |
 | --- | --- |
-| Rules code must follow | `.cviauto/spec/<layer>/` |
-| Cross-layer thinking methods | `.cviauto/spec/guides/` |
-| AI capability for a project-specific flow | Platform-local skill |
-| One-off task material | `.cviauto/tasks/<task>/` |
-| Session summary | `.cviauto/workspace/<developer>/journal-N.md` |
+| 代码必须遵循的规则 | `.cviauto/spec/<layer>/` |
+| 跨层思维方法 | `.cviauto/spec/guides/` |
+| 项目特定流程的 AI 能力 | 平台本地 skill |
+| 一次性任务材料 | `.cviauto/tasks/<task>/` |
+| 会话摘要 | `.cviauto/workspace/<developer>/journal-N.md` |
 
-## Create A Project-Local Skill
+## 创建项目本地 Skill
 
-If the user wants AI to know "how this project customizes Cviauto," create a local skill:
+如果用户希望 AI 了解「本项目如何自定义 Cviauto」，创建一个本地 skill：
 
 ```text
 .claude/skills/cviauto-local/
 └── SKILL.md
 ```
 
-Example:
+示例：
 
 ```md
 ---
-name: trellis-local
+name: cviauto-local
 description: "Project-local Cviauto customizations for this repository. Use when changing this project's Cviauto workflow, hooks, local agents, or team-specific conventions."
 ---
 
@@ -48,11 +48,11 @@ This skill documents this repository's Cviauto customizations only.
 - ...
 ```
 
-For multi-platform projects, place equivalent versions in other platform skill directories, or use `.agents/skills/` for platforms that support the shared layer.
+对于多平台项目，在其他平台 skill 目录中放置等效版本，或在支持共享层的平台上使用 `.agents/skills/`。
 
-## Write To `.cviauto/spec/`
+## 写入 `.cviauto/spec/`
 
-If the content is a coding convention, write it to spec. Examples:
+如果内容是编码约定，将其写入 spec。示例：
 
 ```text
 .cviauto/spec/backend/error-handling.md
@@ -60,24 +60,24 @@ If the content is a coding convention, write it to spec. Examples:
 .cviauto/spec/guides/cross-platform-thinking-guide.md
 ```
 
-After writing it, update the corresponding `index.md` so AI can find the new rule from the entry point.
+写入后，更新对应的 `index.md`，以便 AI 能从入口点找到新规则。
 
-## Make The Current Task Use New Conventions
+## 让当前 Task 使用新约定
 
-After writing a spec, add it to the current task context:
+写入 spec 后，将其添加到当前 task 上下文中：
 
 ```bash
 python3 ./.cviauto/scripts/task.py add-context <task> implement ".cviauto/spec/backend/error-handling.md" "Error handling conventions"
 python3 ./.cviauto/scripts/task.py add-context <task> check ".cviauto/spec/backend/error-handling.md" "Review error handling"
 ```
 
-## Do Not Store Project-Private Rules In `cviauto-meta`
+## 不要将项目私有规则存储在 `cviauto-meta` 中
 
-`cviauto-meta` is a public skill for understanding Cviauto architecture and local customization entry points. Put project-private content in:
+`cviauto-meta` 是一个用于理解 Cviauto 架构和本地自定义入口点的公共 skill。将项目私有内容放在：
 
 - `.cviauto/spec/`
-- a project-local skill
-- the current task
+- 项目本地 skill
+- 当前 task
 - workspace journal
 
-This prevents future updates to Cviauto's built-in `cviauto-meta` from overwriting the team's own conventions.
+这可以防止未来 Cviauto 内置的 `cviauto-meta` 更新覆盖团队自己的约定。

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

@@ -1,18 +1,18 @@
-# Change Local Agents
+# 修改本地 Agents
 
-When the user wants to change `cviauto-research`, `cviauto-implement`, or `cviauto-check` behavior, edit platform agent files in the user project.
+当用户想更改 `cviauto-research`、`cviauto-implement` 或 `cviauto-check` 的行为时，编辑用户项目中的平台 agent 文件。
 
-## Read These Files First
+## 先阅读这些文件
 
-1. Target platform agent directory
-2. `.cviauto/workflow.md` Phase 2 / research routing
-3. Current task `prd.md`
-4. Current task `implement.jsonl` / `check.jsonl`
-5. Relevant hook or agent prelude
+1. 目标平台的 agent 目录
+2. `.cviauto/workflow.md` Phase 2 / research 路由
+3. 当前 task 的 `prd.md`
+4. 当前 task 的 `implement.jsonl` / `check.jsonl`
+5. 相关的 hook 或 agent 前置部分
 
-## Common Paths
+## 常见路径
 
-| Platform | Path |
+| 平台 | 路径 |
 | --- | --- |
 | Claude Code | `.claude/agents/cviauto-*.md` |
 | Cursor | `.cursor/agents/cviauto-*.md` |
@@ -24,33 +24,33 @@ When the user wants to change `cviauto-research`, `cviauto-implement`, or `cviau
 | 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` |
 
-Use the actual paths in the user project as authoritative.
+以用户项目中的实际路径为准。
 
-## Common Needs
+## 常见需求
 
-| Need | Which agent to edit |
+| 需求 | 应编辑哪个 agent |
 | --- | --- |
-| Research must write files, not only reply in chat | `cviauto-research` |
-| Certain local specs must be read before implementation | `cviauto-implement` + `implement.jsonl` configuration rules |
-| Specific commands must run during checking | `cviauto-check` |
-| Agent must not modify certain directories | The corresponding agent's write boundary instructions |
-| Agent output format must be fixed | The corresponding agent's final/reporting instructions |
+| Research 必须写入文件，而不能仅在聊天中回复 | `cviauto-research` |
+| 实现前必须读取某些本地 spec | `cviauto-implement` + `implement.jsonl` 配置规则 |
+| 检查阶段必须运行特定命令 | `cviauto-check` |
+| Agent 不得修改某些目录 | 对应 agent 的写入边界指令 |
+| Agent 输出格式必须固定 | 对应 agent 的最终/报告指令 |
 
-## Modification Principles
+## 修改原则
 
-1. **Preserve role boundaries**: research investigates and persists; implement writes implementation; check reviews and fixes.
-2. **Do not hard-code project specs into agents**: long-term specs belong in `.cviauto/spec/`; agents are responsible for reading them.
-3. **Make read order explicit**: active task -> PRD -> info -> JSONL -> spec/research.
-4. **Make write boundaries explicit**: which directories may be written and which may not.
-5. **Synchronize across platforms**: when the user configured multiple platforms, decide whether to change only the current platform or all platform agents.
+1. **保持角色边界**：research 负责调研并持久化；implement 负责编写实现；check 负责审查和修复。
+2. **不要在 agent 中硬编码项目 spec**：长期 spec 应放在 `.cviauto/spec/` 中；agent 负责读取它们。
+3. **明确读取顺序**：active task -> PRD -> info -> JSONL -> spec/research。
+4. **明确写入边界**：哪些目录可写、哪些不可写。
+5. **跨平台同步**：当用户配置了多个平台时，决定是仅修改当前平台还是修改所有平台的 agent。
 
-## Agent Pull Platforms
+## Agent Pull（拉取）平台
 
-If an agent file contains a prelude for "read task/context after startup," do not remove those steps when editing. Otherwise the agent will work only from chat context and bypass Cviauto's core mechanism.
+如果 agent 文件中包含「启动后读取 task/context」的前置步骤，编辑时不要删除这些步骤。否则 agent 将仅依赖聊天上下文工作，绕过 Cviauto 的核心机制。
 
-## Hook Push Platforms
+## Hook Push（推送）平台
 
-If context is injected by a hook, the agent file should still retain responsibility boundaries. Do not remove PRD/spec requirements from the agent just because a hook injects context.
+如果上下文由 hook 注入，agent 文件仍应保留职责边界。不要因为 hook 注入了上下文就从 agent 中移除 PRD/spec 要求。

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

@@ -1,78 +1,78 @@
-# Change Local Context Loading
+# 修改本地上下文加载
 
-Context loading determines when AI reads workflow, task, spec, research, workspace, and git status. Read this page when the user says "AI does not know the current task," "the agent did not read specs," or "there is too much/too little context."
+上下文加载决定了 AI 何时读取工作流、任务、规范（spec）、调研（research）、工作区（workspace）和 git 状态。当用户说"AI 不知道当前任务"、"代理没有读取规范"或"上下文太多/太少"时，请阅读本页。
 
-## Read These Files First
+## 先阅读这些文件
 
 1. `.cviauto/workflow.md`
 2. `.cviauto/scripts/get_context.py`
 3. `.cviauto/scripts/common/session_context.py`
 4. `.cviauto/scripts/common/task_context.py`
 5. `.cviauto/scripts/common/active_task.py`
-6. Current platform hooks or agent files
-7. The current task's `implement.jsonl` / `check.jsonl`
+6. 当前平台钩子或代理文件
+7. 当前任务的 `implement.jsonl` / `check.jsonl`
 
-## Context Sources
+## 上下文来源
 
-| Source | Purpose |
+| 来源 | 用途 |
 | --- | --- |
-| `.cviauto/workflow.md` | Workflow and next-action hints. |
-| `.cviauto/tasks/<task>/prd.md` | Current task requirements. |
-| `.cviauto/tasks/<task>/design.md` | Complex task technical design. |
-| `.cviauto/tasks/<task>/implement.md` | Complex task execution plan. |
-| `.cviauto/tasks/<task>/implement.jsonl` | Spec/research to read before implementation. |
-| `.cviauto/tasks/<task>/check.jsonl` | Spec/research to read during checking. |
-| `.cviauto/spec/` | Project specs. |
-| `.cviauto/workspace/` | Session records. |
-| git status | Current working tree changes. |
-
-## Common Needs And Edit Points
-
-| Need | Edit point |
+| `.cviauto/workflow.md` | 工作流和下一步提示。 |
+| `.cviauto/tasks/<task>/prd.md` | 当前任务需求。 |
+| `.cviauto/tasks/<task>/design.md` | 复杂任务的技术设计。 |
+| `.cviauto/tasks/<task>/implement.md` | 复杂任务的执行计划。 |
+| `.cviauto/tasks/<task>/implement.jsonl` | 实现前要读取的规范/调研。 |
+| `.cviauto/tasks/<task>/check.jsonl` | 检查期间要读取的规范/调研。 |
+| `.cviauto/spec/` | 项目规范。 |
+| `.cviauto/workspace/` | 会话记录。 |
+| git status | 当前工作树变更。 |
+
+## 常见需求与编辑点
+
+| 需求 | 编辑点 |
 | --- | --- |
-| Inject more/less information in new sessions | `session_context.py` or the platform `session-start` hook. |
-| Change hints on each user input | `[workflow-state:STATUS]` block in `.cviauto/workflow.md`. The `inject-workflow-state` hook is parser-only and reads the block verbatim. |
-| Agent did not read specs | Task JSONL, agent prelude, `inject-subagent-context` hook. |
-| Active task is lost | `active_task.py` and platform session identity propagation. |
-| Change JSONL validation rules | `task_context.py`. |
+| 在新会话中注入更多/更少信息 | `session_context.py` 或平台 `session-start` 钩子。 |
+| 修改每次用户输入时的提示 | `.cviauto/workflow.md` 中的 `[workflow-state:STATUS]` 块。`inject-workflow-state` 钩子是纯解析器，会逐字读取该块内容。 |
+| 代理没有读取规范 | 任务 JSONL、代理 prelude、`inject-subagent-context` 钩子。 |
+| 活动任务丢失 | `active_task.py` 和平台会话身份传播。 |
+| 修改 JSONL 验证规则 | `task_context.py`。 |
 
-## JSONL Rules
+## JSONL 规则
 
-`implement.jsonl` / `check.jsonl` are the key context loading interface:
+`implement.jsonl` / `check.jsonl` 是关键的上下文加载接口：
 
 ```jsonl
-{"file": ".cviauto/spec/backend/index.md", "reason": "Backend conventions"}
-{"file": ".cviauto/tasks/04-28-x/research/api.md", "reason": "API research"}
+{"file": ".cviauto/spec/backend/index.md", "reason": "后端约定"}
+{"file": ".cviauto/tasks/04-28-x/research/api.md", "reason": "API 调研"}
 ```
 
-Include only spec/research files. Do not put code files that will be modified into these manifests; agents read code files themselves during implementation.
+仅包含规范/调研文件。不要将将要修改的代码文件放入这些清单中；代理在实现期间会自行读取代码文件。
 
-## Change Session Context
+## 修改会话上下文
 
-If the user wants every new session to see more project state, edit:
+如果用户希望每个新会话都能看到更多项目状态，请编辑：
 
 - `.cviauto/scripts/common/session_context.py`
-- the corresponding platform `session-start` hook
+- 相应的平台 `session-start` 钩子
 
-Context cannot grow without bound. Prefer injecting indexes and paths so the AI can read detailed files on demand.
+上下文不能无限制增长。优先注入索引和路径，使 AI 可以按需读取详细文件。
 
-## Change Sub-Agent Context
+## 修改子代理上下文
 
-First determine which mode the platform uses:
+首先确定平台使用哪种模式：
 
-- hook push: edit the `inject-subagent-context` hook.
-- agent pull: edit the read steps in the corresponding `cviauto-implement` / `cviauto-check` agent file.
+- 钩子推送（hook push）：编辑 `inject-subagent-context` 钩子。
+- 代理拉取（agent pull）：编辑对应 `cviauto-implement` / `cviauto-check` 代理文件中的读取步骤。
 
-In both modes, make sure the agent ultimately reads:
+两种模式下，确保代理最终读取：
 
-1. active task
-2. the corresponding JSONL
-3. spec/research referenced by the JSONL
+1. 活动任务
+2. 对应的 JSONL
+3. JSONL 引用的规范/调研
 4. `prd.md`
-5. `design.md` if present
-6. `implement.md` if present
+5. `design.md`（如果存在）
+6. `implement.md`（如果存在）
 
-## Troubleshooting Order
+## 排查顺序
 
 ```bash
 python3 ./.cviauto/scripts/task.py current --source
@@ -81,4 +81,4 @@ python3 ./.cviauto/scripts/task.py validate <task>
 python3 ./.cviauto/scripts/get_context.py --mode packages
 ```
 
-Confirm the task and JSONL are correct before editing hooks/agents.
+在编辑钩子/代理之前，先确认任务和 JSONL 是正确的。

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

@@ -1,57 +1,57 @@
-# Change Local Hooks
+# 修改本地 Hooks
 
-Hooks are the automation layer that connects a platform to Cviauto. When the user wants to change "when context is injected," "how shell commands inherit a session," or "which files are read before an agent starts," hooks are usually the edit point.
+Hooks（钩子）是将平台与 Cviauto 连接起来的自动化层。当用户想更改「何时注入上下文」「shell 命令如何继承会话」「agent 启动前应读取哪些文件」时，通常需要编辑 hooks。
 
-## Read These Files First
+## 先阅读这些文件
 
-1. Target platform settings/config, such as `.claude/settings.json`, `.codex/hooks.json`, `.cursor/hooks.json`, `.trae/hooks.json`
-2. Target platform hooks directory
+1. 目标平台的 settings/config，如 `.claude/settings.json`、`.codex/hooks.json`、`.cursor/hooks.json`
+2. 目标平台的 hooks 目录
 3. `.cviauto/scripts/common/active_task.py`
 4. `.cviauto/scripts/common/session_context.py`
 5. `.cviauto/workflow.md`
 
-## Common Hook Types
+## 常见 Hook 类型
 
-| Hook | Purpose |
+| Hook | 用途 |
 | --- | --- |
-| session-start | Injects a Cviauto overview when a session starts, clears, or compacts. |
-| workflow-state | Injects a state hint on each user input. |
-| sub-agent context | Injects PRD/spec/research before an agent starts. |
-| shell session bridge | Lets `task.py` commands in shell see the same session identity. |
+| session-start | 在会话启动、清除或压缩时注入 Cviauto 概览。 |
+| workflow-state | 在每次用户输入时注入状态提示。 |
+| sub-agent context | 在 agent 启动前注入 PRD/spec/research。 |
+| shell session bridge | 让 shell 中的 `task.py` 命令能够看到相同的会话标识。 |
 
-## Modification Steps
+## 修改步骤
 
-1. Find the hook registration in settings/config.
-2. Confirm the registered script path exists.
-3. Read the hook script and identify inputs, outputs, and called `.cviauto/scripts/`.
-4. Modify hook behavior.
-5. If the hook depends on workflow content, synchronize `.cviauto/workflow.md`.
+1. 在 settings/config 中找到 hook 注册项。
+2. 确认注册的脚本路径存在。
+3. 阅读 hook 脚本，识别输入、输出以及调用的 `.cviauto/scripts/`。
+4. 修改 hook 行为。
+5. 如果 hook 依赖工作流内容，同步更新 `.cviauto/workflow.md`。
 
-## Example: Change New-Session Injection Content
+## 示例：更改新会话注入内容
 
-First find the session-start hook:
+首先找到 session-start hook：
 
 ```text
 .claude/settings.json
 .claude/hooks/session-start.py
 ```
 
-If the hook ultimately calls `.cviauto/scripts/get_context.py` or `session_context.py`, editing the local script is usually more robust than hard-coding content in the hook.
+如果该 hook 最终调用了 `.cviauto/scripts/get_context.py` 或 `session_context.py`，那么编辑本地脚本通常比在 hook 中硬编码内容更稳健。
 
-## Example: Agent Did Not Read JSONL
+## 示例：Agent 未读取 JSONL
 
-First confirm:
+首先确认：
 
 ```bash
 python3 ./.cviauto/scripts/task.py current --source
 python3 ./.cviauto/scripts/task.py validate <task>
 ```
 
-If the task and JSONL are correct, determine whether the platform uses hook push or agent pull. For hook push, edit `inject-subagent-context`; for agent pull, edit the agent file.
+如果 task 和 JSONL 正确，判断平台使用的是 hook push（推送）方式还是 agent pull（拉取）方式。对于 hook push，编辑 `inject-subagent-context`；对于 agent pull，编辑 agent 文件。
 
-## Notes
+## 注意事项
 
-- Settings handle registration, hook scripts handle behavior; inspect both together.
-- Different platforms support different hook events. Do not directly copy another platform's settings.
-- Hooks should read project-local `.cviauto/`; they should not depend on Cviauto upstream source paths.
-- Hook failures should produce visible errors so AI does not silently lose context.
+- Settings 负责注册，hook 脚本负责行为；两者需一起检查。
+- 不同平台支持不同的 hook 事件。不要直接复制其他平台的 settings。
+- Hooks 应读取项目本地的 `.cviauto/`；不应依赖 Cviauto 上游源码路径。
+- Hook 失败时应产生可见的错误，使 AI 不会静默丢失上下文。