sync-horizon

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Sync Horizon

同步Horizon

Synchronize eve-skillpacks with the latest state of the eve-horizon repository.

将eve-skillpacks与eve-horizon仓库的最新状态保持同步。

Core Insight

核心洞察

System docs often lag behind implementation. Features ship via feat commits with plans marked "Implemented" — but

docs/system/

may not update for weeks. This sync goes to the source: plans, code changes, and commit messages tell us what actually shipped. System docs are one signal among many, not the primary driver.

系统文档常常滞后于实现进度。功能通过feat类型的提交上线，计划标记为“已实现”——但

docs/system/

目录可能数周都不会更新。本次同步直接从源头获取信息：计划、代码变更和提交信息能告诉我们实际上线了哪些内容。系统文档只是众多信号之一，而非主要依据。

Prerequisites

前置条件

```
.sync-state.json
```
must exist in the repo root (create from template if missing)
```
.sync-state.json#eve_horizon_path
```
must point to a readable eve-horizon Git checkout
```
.sync-map.json
```
must exist in the repo root

仓库根目录必须存在
```
.sync-state.json
```
文件（若缺失可从模板创建）
```
.sync-state.json#eve_horizon_path
```
必须指向可读取的eve-horizon Git本地仓库
仓库根目录必须存在
```
.sync-map.json
```
文件

Architecture: Orchestrator + Parallel Workers

架构：编排器 + 并行工作器

You (the orchestrator) discover what shipped and dispatch focused workers. Each worker handles one update in isolation with its own context budget.

The orchestrator reads lightweight signals (commit log, plan headers, file stats, CLI module list). Workers read the heavy content (plan bodies, code diffs, source docs, target files).

你作为编排器，负责发现已上线的内容并分配任务给专注的工作器。每个工作器独立处理一项更新，拥有自己的上下文资源。

编排器读取轻量级信号（提交日志、计划标题、文件统计、CLI模块列表）。工作器读取重量级内容（计划正文、代码差异、源文档、目标文件）。

Output Standards

输出标准

Distill only shipped platform behavior. Plans marked Implemented/Complete describe shipped features.
Do not carry roadmap content into skillpacks. Ignore plans marked Proposed/Draft and sections like
```
Planned (Not Implemented)
```
,
```
What's next
```
, or "current vs planned" framing.
Keep
```
eve-work/eve-read-eve-docs/SKILL.md
```
task-first: route by intent, load only the minimal reference files needed.
Keep reference docs scoped and actionable — curated distillations, not copies.

仅提炼已上线的平台行为。标记为“已实现/完成”的计划描述的是已上线的功能。
不要将路线图内容带入技能包。忽略标记为“提议/草稿”的计划，以及诸如“计划中（未实现）”、“下一步计划”或“当前 vs 计划”的章节。
保持
```
eve-work/eve-read-eve-docs/SKILL.md
```
以任务为核心：按意图路由，仅加载所需的最小参考文件。
参考文档需保持范围明确且可操作——是经过筛选的提炼内容，而非直接复制。

Workflow

工作流程

Phase 1: Deep Discovery (orchestrator)

阶段1：深度发现（编排器）

Read lightweight signals from multiple dimensions to understand what actually shipped.

Resolve the source path once and use it for every source command:

bash

HORIZON_PATH="$(jq -r '.eve_horizon_path' .sync-state.json)"
LAST_SYNCED_COMMIT="$(jq -r '.last_synced_commit' .sync-state.json)"
test -n "$HORIZON_PATH" && test "$HORIZON_PATH" != "null"
git -C "$HORIZON_PATH" rev-parse --is-inside-work-tree

从多个维度读取轻量级信号，以了解实际上线的内容。

仅解析一次源路径，并将其用于所有源命令：

bash

HORIZON_PATH="$(jq -r '.eve_horizon_path' .sync-state.json)"
LAST_SYNCED_COMMIT="$(jq -r '.last_synced_commit' .sync-state.json)"
test -n "$HORIZON_PATH" && test "$HORIZON_PATH" != "null"
git -C "$HORIZON_PATH" rev-parse --is-inside-work-tree

1a. Commit log

1a. 提交日志

bash

git -C "$HORIZON_PATH" log --oneline "$LAST_SYNCED_COMMIT"..HEAD

Categorize commits:

```
feat:
```
— new capabilities (primary interest)
```
fix:
```
— bugfixes that may affect documented behavior
```
docs:
```
— documentation changes (check if they describe already-shipped features)
```
chore:
```
/
```
refactor:
```
— usually no skillpack impact, but note removals

bash

git -C "$HORIZON_PATH" log --oneline "$LAST_SYNCED_COMMIT"..HEAD

对提交进行分类：

```
feat:
```
—— 新功能（重点关注）
```
fix:
```
—— 可能影响文档描述行为的Bug修复
```
docs:
```
—— 文档变更（检查是否描述了已上线的功能）
```
chore:
```
/
```
refactor:
```
—— 通常不影响技能包，但需注意内容移除情况

1b. Plan intelligence

1b. 计划情报

This is the richest signal. Plans describe what shipped, why, and how.

bash

git -C "$HORIZON_PATH" diff --stat "$LAST_SYNCED_COMMIT"..HEAD -- docs/plans/

For each changed plan, read its header only (first 15-20 lines) to extract status:

bash

sed -n '1,20p' "$HORIZON_PATH/docs/plans/<plan-file>.md"

Categorize:

Shipped: Status contains
```
Implemented
```
,
```
Complete
```
, or
```
Done
```
— these are the primary source of truth for new capabilities
In progress: Status contains
```
In Progress
```
,
```
Partially Implemented
```
— note for awareness but don't distill unfinished work
Proposed/Draft: Status contains
```
Proposed
```
,
```
Plan
```
,
```
Draft
```
,
```
Ready to build
```
— skip entirely
Removed: Plan files deleted in this range — something was deprecated or abandoned

IMPORTANT: Do not read full plan bodies. Just headers. Workers will read the plans they need.

这是最丰富的信号源。计划描述了上线内容、原因及实现方式。

bash

git -C "$HORIZON_PATH" diff --stat "$LAST_SYNCED_COMMIT"..HEAD -- docs/plans/

对于每个变更的计划，仅读取其标题部分（前15-20行）以提取状态：

bash

sed -n '1,20p' "$HORIZON_PATH/docs/plans/<plan-file>.md"

分类：

已上线：状态包含
```
Implemented
```
、
```
Complete
```
或
```
Done
```
——这些是新功能的主要事实来源
进行中：状态包含
```
In Progress
```
、
```
Partially Implemented
```
——仅作记录，不提炼未完成的工作
提议/草稿：状态包含
```
Proposed
```
、
```
Plan
```
、
```
Draft
```
、
```
Ready to build
```
——完全跳过
已移除：此范围内被删除的计划文件——说明某项功能已被弃用或放弃

重要提示：不要读取完整的计划正文，仅读取标题。工作器会按需读取完整计划。

1c. Code signal

1c. 代码信号

New CLI commands, DB migrations, and package changes confirm what shipped and reveal capabilities that plans may not fully describe.

bash

undefined

新的CLI命令、数据库迁移和包变更可确认已上线内容，并揭示计划可能未充分描述的功能。

bash

undefined

New/changed/removed CLI commands

新增/变更/移除的CLI命令

git -C "$HORIZON_PATH" diff --stat "$LAST_SYNCED_COMMIT"..HEAD -- packages/cli/src/commands/

New DB migrations (table/column names reveal capability shape)

新数据库迁移（表/列名称可揭示功能形态）

git -C "$HORIZON_PATH" diff --stat "$LAST_SYNCED_COMMIT"..HEAD -- packages/db/migrations/

Key package changes (new modules, removed modules)

关键包变更（新增模块、移除模块）

git -C "$HORIZON_PATH" diff --stat "$LAST_SYNCED_COMMIT"..HEAD -- packages/shared/src/ packages/api/src/ packages/worker/src/ packages/gateway/src/ --stat-name-width=120 | head -50

undefined

git -C "$HORIZON_PATH" diff --stat "$LAST_SYNCED_COMMIT"..HEAD -- packages/shared/src/ packages/api/src/ packages/worker/src/ packages/gateway/src/ --stat-name-width=120 | head -50

undefined

1d. System doc changes

1d. 系统文档变更

Still a useful signal — especially for removals and corrections.

bash

git -C "$HORIZON_PATH" diff --stat "$LAST_SYNCED_COMMIT"..HEAD -- docs/system/ AGENTS.md

仍是有用的信号——尤其对于内容移除和修正。

bash

git -C "$HORIZON_PATH" diff --stat "$LAST_SYNCED_COMMIT"..HEAD -- docs/system/ AGENTS.md

1e. Current CLI surface

1e. 当前CLI界面

Snapshot the current CLI command modules. This is the ground truth for what agents can invoke.

bash

find "$HORIZON_PATH/packages/cli/src/commands" -maxdepth 1 -name '*.ts' -print | sort

快照当前CLI命令模块。这是Agent可调用内容的真实依据。

bash

find "$HORIZON_PATH/packages/cli/src/commands" -maxdepth 1 -name '*.ts' -print | sort

Phase 2: Capability Synthesis (orchestrator)

阶段2：功能合成（编排器）

STOP and think. This is the critical step. Cross-reference all signals to build a capability map.

For each shipped plan (Implemented/Complete), create a capability entry:

Capability: <name>
  Plan: docs/plans/<file>.md (status: Implemented)
  Feat commits: <matching commit hashes>
  Code signal: <new CLI commands, new migrations, new/removed modules>
  System doc: <updated/created/unchanged>
  Scope: <which platform areas this touches>
  One-line summary: <what this capability does, from the plan header>

Also create entries for capabilities evidenced by feat commits that have no corresponding plan — these are smaller features or fixes that shipped directly.

Also note removals: plans deleted, CLI commands removed, modules deleted. These need to be cleaned from our skills too.

暂停并思考。这是关键步骤。交叉引用所有信号以构建功能映射表。

对于每个已上线计划（已实现/完成），创建一个功能条目：

功能：<名称>
  计划：docs/plans/<文件>.md（状态：已实现）
  Feat提交：<匹配的提交哈希>
  代码信号：<新CLI命令、新迁移、新增/移除模块>
  系统文档：<已更新/已创建/未变更>
  范围：<涉及哪些平台领域>
  一行摘要：<该功能的作用，来自计划标题>

同时为那些无对应计划但由feat提交证明存在的功能创建条目——这些是直接上线的小型功能或修复。

还要记录移除内容：已删除的计划、已移除的CLI命令、已删除的模块。这些需要从技能包中清理。

Phase 3: Cascade Analysis (orchestrator)

阶段3：级联分析（编排器）

For each capability in the map, determine its impact on

eve-read-eve-docs

对于映射表中的每个功能，确定其对

eve-read-eve-docs

的影响：

3a. Reference doc impact

3a. 参考文档影响

For each capability, ask:

Does an existing reference already cover this area? → Worker updates it
Is this a new primitive that needs its own reference? → Worker creates it
Was something removed? → Worker cleans stale content from affected references

Cross-reference against the current reference index in

eve-work/eve-read-eve-docs/SKILL.md

and the

reference_docs

section of

.sync-map.json

对于每个功能，询问：

是否已有参考文档覆盖此领域？→ 工作器更新该文档
这是否是需要独立参考文档的新基础功能？→ 工作器创建新文档
是否有内容被移除？→ 工作器从受影响的参考文档中清理过时内容

对照

eve-work/eve-read-eve-docs/SKILL.md

中的当前参考索引，以及

.sync-map.json

的

reference_docs

部分进行交叉引用。

3b. SKILL.md routing impact

3b. SKILL.md路由影响

Check if

eve-work/eve-read-eve-docs/SKILL.md

needs:

New entries in the Task Router
New entries in the Index
New rows in the Intent Coverage Matrix
New trigger keywords in the frontmatter
Removal of stale entries for deprecated capabilities

检查

eve-work/eve-read-eve-docs/SKILL.md

是否需要：

任务路由中的新条目
索引中的新条目
意图覆盖矩阵中的新行
前置元数据中的新触发关键词
移除已弃用功能的过时条目

3c. Other skill impact

3c. 其他技能影响

Check

.sync-map.json

skill_triggers

and

composite_triggers

for other skills affected. Also consider:

```
eve-se/eve-manifest-authoring
```
— if manifest shape changed
```
eve-se/eve-deploy-debugging
```
— if deploy/infra behavior changed
```
eve-se/eve-auth-and-secrets
```
— if auth model changed
```
eve-work/eve-agent-memory
```
— if storage primitives changed
```
eve-design/eve-fullstack-app-design
```
— if app patterns changed

检查

.sync-map.json

的

skill_triggers

和

composite_triggers

，查看是否有其他受影响的技能。同时考虑：

```
eve-se/eve-manifest-authoring
```
—— 若清单格式变更
```
eve-se/eve-deploy-debugging
```
—— 若部署/基础设施行为变更
```
eve-se/eve-auth-and-secrets
```
—— 若认证模型变更
```
eve-work/eve-agent-memory
```
—— 若存储基础功能变更
```
eve-design/eve-fullstack-app-design
```
—— 若应用模式变更

Phase 4: Plan Work Items (orchestrator)

阶段4：规划工作项（编排器）

For each update identified in Phase 3, create a work item:

Title:
```
Update <target-file>: <capability name>
```
Description — everything a worker needs to operate independently:
- The eve-horizon repo path resolved from
```
.sync-state.json#eve_horizon_path
```
- The commit range:
```
<last_synced_commit>..HEAD
```
- Which plan(s) to read (the shipped plans relevant to this update)
- Which source files to diff or read (code, system docs)
- The target file path to update or create
- Whether this is a reference doc update, skill update, new reference, or removal
- The appropriate worker instructions from below

Add a final work item:

Update sync state and produce report

— blocked until all updates finish.

If any work item touches

eve-work/eve-read-eve-docs

, also add:

Run state-today compliance scan for eve-read-eve-docs

Validate progressive-access routing in eve-read-eve-docs/SKILL.md

Update .sync-map.json with any new reference doc mappings

针对阶段3中识别的每项更新，创建一个工作项：

标题：
```
更新 <目标文件>: <功能名称>
```
描述 —— 工作器独立操作所需的所有信息：
- 从
```
.sync-state.json#eve_horizon_path
```
  解析得到的eve-horizon仓库路径
- 提交范围：
```
<last_synced_commit>..HEAD
```
- 需读取的计划（与本次更新相关的已上线计划）
- 需对比或读取的源文件（代码、系统文档）
- 需更新或创建的目标文件路径
- 本次更新属于参考文档更新、技能包更新、新参考文档创建还是内容移除
- 以下对应的工作器指令

添加最后一个工作项：

更新同步状态并生成报告

—— 需等待所有更新完成后执行。

若任何工作项涉及

eve-work/eve-read-eve-docs

，还需添加：

为eve-read-eve-docs运行state-today合规扫描

验证eve-read-eve-docs/SKILL.md中的渐进式访问路由

更新.sync-map.json中的新参考文档映射

Phase 5: Dispatch Workers (parallel)

阶段5：调度工作器（并行）

Spawn one background worker per work item. Launch them all at once.

Each worker prompt must be self-contained. The worker has no access to the orchestrator's conversation. Include:

The plan file(s) to read — these are the primary source of truth
The git diff command for relevant code/doc changes
The target file to read and modify
The capability summary from Phase 2
The appropriate worker instructions from below

为每个工作项启动一个后台工作器。同时启动所有工作器。

每个工作器提示必须独立完整。工作器无法访问编排器的对话内容。需包含：

需读取的计划文件——这些是主要事实来源
相关代码/文档变更的git diff命令
需读取和修改的目标文件
阶段2中的功能摘要
以下对应的工作器指令

Worker Instructions: Reference Doc Update

工作器指令：参考文档更新

Your primary sources are shipped plans (marked Implemented/Complete) and code changes. System docs are secondary — they may lag behind or be absent.
Read the plan(s) listed in your task — understand what shipped and why.

Read the current reference doc you're updating.

Run the git diff for relevant source files (code, system docs).
If the plan references specific CLI commands or APIs, verify they exist:
bash
test -f "$HORIZON_PATH/packages/cli/src/commands/<name>.ts"
Distill the shipped capability into the reference doc:

What it does (from plan + code)

How to use it (CLI commands, manifest config, API calls)

Key constraints or requirements

Exclude roadmap content. Only document what is implemented.

Edit the existing file; do not rewrite from scratch.

Preserve existing structure, voice, and formatting.

你的主要来源是已上线计划（标记为已实现/完成）和代码变更。系统文档是次要来源——它们可能滞后或缺失。
读取任务中列出的计划——理解已上线内容及原因。

读取你要更新的当前参考文档。

运行相关源文件（代码、系统文档）的git diff命令。
若计划提及特定CLI命令或API，验证它们是否存在：
bash
test -f "$HORIZON_PATH/packages/cli/src/commands/<name>.ts"
将已上线功能提炼到参考文档中：

功能作用（来自计划+代码）

使用方法（CLI命令、清单配置、API调用）

关键约束或要求

排除路线图内容。仅记录已实现的功能。

编辑现有文件；不要从头重写。

保留现有结构、语气和格式。

Worker Instructions: New Reference Doc

工作器指令：新参考文档创建

Read the plan(s) that describe this capability.
Check for any system doc coverage at
$HORIZON_PATH/docs/system/<name>.md
(may not exist).
Read the CLI command source at
$HORIZON_PATH/packages/cli/src/commands/<name>.ts
if relevant.
Create a reference doc that follows the conventions of existing references in
eve-work/eve-read-eve-docs/references/
.
Include: purpose, CLI commands/flags, manifest config if relevant, key behaviors, constraints.

Keep it concise and agent-actionable. These are distillations, not documentation copies.

State-today only — no planned/roadmap content.

读取描述此功能的计划。
检查
$HORIZON_PATH/docs/system/<name>.md
是否有系统文档覆盖（可能不存在）。
若相关，读取CLI命令源码
$HORIZON_PATH/packages/cli/src/commands/<name>.ts
。
创建符合
eve-work/eve-read-eve-docs/references/
中现有参考文档规范的新参考文档。
包含：用途、CLI命令/参数、相关清单配置、关键行为、约束条件。

保持简洁且适合Agent操作。这些是提炼内容，而非文档副本。

仅记录当前状态——不包含计划/路线图内容。

Worker Instructions: Skill Update

工作器指令：技能包更新

Your primary sources are shipped plans and code changes.

Read the plan(s) listed in your task.

Read the current SKILL.md you're updating.

Update with new commands, changed workflows, or new capabilities.

Remove stale content that references deprecated features.

Keep state-today only. Ensure progressive disclosure.

Maintain imperative voice and conciseness.

Edit the existing file; do not rewrite from scratch.

你的主要来源是已上线计划和代码变更。

读取任务中列出的计划。

读取你要更新的当前SKILL.md文件。

更新新增命令、变更工作流或新功能。

移除引用已弃用功能的过时内容。

仅记录当前状态。确保渐进式披露。

保持命令式语气和简洁性。

编辑现有文件；不要从头重写。

Worker Instructions: SKILL.md Routing Update

工作器指令：SKILL.md路由更新

This worker updates the eve-read-eve-docs SKILL.md routing, index, and coverage matrix.
Read the current
eve-work/eve-read-eve-docs/SKILL.md
.
For each new reference doc created by other workers, add:

A Task Router entry describing when to load it

An Index entry with the file path and one-line description

An Intent Coverage Matrix row if it serves a distinct user intent

For each removed capability, clean up stale routing entries.

Add any new trigger keywords to the YAML frontmatter.

Maintain alphabetical or logical ordering within sections.

此工作器负责更新eve-read-eve-docs SKILL.md的路由、索引和覆盖矩阵。
读取当前的
eve-work/eve-read-eve-docs/SKILL.md
。
对于其他工作器创建的每个新参考文档，添加：

任务路由条目，描述何时加载该文档

索引条目，包含文件路径和一行描述

若服务于独特用户意图，则添加意图覆盖矩阵行

对于每个已移除的功能，清理过时的路由条目。

向前置YAML元数据添加新的触发关键词。

保持各章节内的字母顺序或逻辑顺序。

Worker Instructions: Staleness Check

工作器指令：过时内容检查

This is a cross-cutting skill that spans multiple platform primitives. Your job is to validate that the skill's claims match current platform reality.
Read the SKILL.md and all files in its
references/
directory.
Read the shipped plan(s) listed in your task for context on what changed.
List current CLI command modules:
bash
find "$HORIZON_PATH/packages/cli/src/commands" -maxdepth 1 -name '*.ts' -print | sort
Scan the skill for stale claims:

"No dedicated X" / "X not available" / "not yet supported" — check if X now exists.

"Current Gaps" or "Workarounds" sections — verify each gap is still a gap.

Decision tables or comparison matrices — check for missing rows.

References to removed features (e.g., inference/ollama/managed-models).

If stale claims are found, update the skill. Add new primitives. Remove false gaps.

Keep state-today only. Maintain imperative voice and conciseness.

Edit existing files; do not rewrite from scratch.
Report what was stale and what you corrected.

这是一项跨多个平台基础功能的技能。你的任务是验证技能包中的描述是否与当前平台实际情况匹配。
读取SKILL.md及其
references/
目录下的所有文件。
读取任务中列出的已上线计划，了解变更背景。
列出当前CLI命令模块：
bash
find "$HORIZON_PATH/packages/cli/src/commands" -maxdepth 1 -name '*.ts' -print | sort
扫描技能包中的过时描述：

“无专用X”/“X不可用”/“暂不支持”——检查X是否现已存在。

“当前差距”或“变通方案”章节——验证每个差距是否仍然存在。

决策表或对比矩阵——检查是否缺少行。

引用已移除功能的内容（如inference/ollama/managed-models）。

若发现过时描述，更新技能包。添加新基础功能。移除错误的差距描述。

仅记录当前状态。保持命令式语气和简洁性。

编辑现有文件；不要从头重写。
报告哪些内容过时以及你进行了哪些修正。

Worker Instructions: Sync Map Update

工作器指令：同步映射更新

Update
.sync-map.json
to reflect new mappings discovered during this sync.
Read the current
.sync-map.json
.
For each new reference doc created, add a
reference_docs
entry mapping the source files to the target.
For each new skill trigger relationship discovered, add a
skill_triggers
entry.
For removed source docs, clean up stale mappings.
Ensure
watch_paths
covers any new directories that should be monitored.

更新
.sync-map.json
以反映本次同步中发现的新映射关系。
读取当前的
.sync-map.json
。
对于每个创建的新参考文档，添加
reference_docs
条目，映射源文件到目标文件。
对于每个发现的新技能触发关系，添加
skill_triggers
条目。
对于已移除的源文档，清理过时的映射。
确保
watch_paths
覆盖所有需要监控的新目录。

Example Worker Prompt

工作器提示示例

You are updating a reference doc in the eve-skillpacks repository.

你正在更新eve-skillpacks仓库中的参考文档。

Your Task

你的任务

Update the file: eve-work/eve-read-eve-docs/references/agents-teams.md Add coverage for agent aliases (short names for chat addressing).

更新文件：eve-work/eve-read-eve-docs/references/agents-teams.md 添加Agent别名（聊天寻址的短名称）的相关内容。

Capability Summary

功能摘要

Agent aliases let users declare short names for agents instead of using full project-slug-agent-name. Declared in manifest under

agents[].alias

. Resolved at chat dispatch time. Status: Implemented.

Agent别名允许用户为Agent声明短名称，而非使用完整的project-slug-agent-name。在清单的

agents[].alias

下声明。在聊天调度时解析。状态：已实现。

Primary Source

主要来源

Read the plan:

$HORIZON_PATH/docs/plans/agent-aliases-plan.md

读取计划：

$HORIZON_PATH/docs/plans/agent-aliases-plan.md

Code Confirmation

代码确认

The agents CLI was updated:

git -C "$HORIZON_PATH" diff <commit>..HEAD -- packages/cli/src/commands/agents.ts

New migration: packages/db/migrations/00076_add_agent_alias.sql

Agents CLI已更新：

git -C "$HORIZON_PATH" diff <commit>..HEAD -- packages/cli/src/commands/agents.ts

新迁移文件：packages/db/migrations/00076_add_agent_alias.sql

Target

目标

Read and edit: eve-work/eve-read-eve-docs/references/agents-teams.md

读取并编辑：eve-work/eve-read-eve-docs/references/agents-teams.md

Rules

规则

Distill only shipped behavior from the plan and code
Edit the existing file; do not rewrite from scratch
These are curated distillations for agents, not copies
Keep it concise and actionable

undefined

仅从计划和代码中提炼已上线的行为
编辑现有文件；不要从头重写
这些是为Agent准备的精选提炼内容，而非副本
保持简洁且可操作

undefined

Phase 6: Collect Results and Finalize (orchestrator)

阶段6：收集结果并完成（编排器）

Wait for all workers to complete.

Once all update work items are done:

Get current HEAD:
bash
```
git -C "$HORIZON_PATH" rev-parse HEAD
```
Run the state-today check before recording the cascade:
bash
```
./private-skills/sync-horizon/scripts/check-state-today.sh
```
Update
```
.sync-state.json
```
:
- Set
```
last_synced_commit
```
  to the HEAD hash
- Set
```
last_synced_at
```
  to current ISO timestamp
- Prepend a sync-log entry, sort entries newest-first, and keep the latest 10

Run the complete deterministic checks twice after the state update. The second pass must be a no-op and produce the same successful result:

bash

./private-skills/sync-horizon/scripts/check-state-today.sh
python3 scripts/check-repository.py
python3 scripts/check-source-sync.py --source "$HORIZON_PATH"

./private-skills/sync-horizon/scripts/check-state-today.sh
python3 scripts/check-repository.py
python3 scripts/check-source-sync.py --source "$HORIZON_PATH"

等待所有工作器完成。

所有更新工作项完成后：

获取当前HEAD：
bash
```
git -C "$HORIZON_PATH" rev-parse HEAD
```

在记录级联更新前运行state-today检查：

bash

./private-skills/sync-horizon/scripts/check-state-today.sh

更新
```
.sync-state.json
```
：
- 将
```
last_synced_commit
```
  设置为HEAD哈希值
- 将
```
last_synced_at
```
  设置为当前ISO时间戳
- 添加一条同步日志条目，按最新到最旧排序日志条目，并保留最近10条

状态更新后运行完整的确定性检查两次。第二次检查必须无操作并产生相同的成功结果：

bash

./private-skills/sync-horizon/scripts/check-state-today.sh
python3 scripts/check-repository.py
python3 scripts/check-source-sync.py --source "$HORIZON_PATH"

./private-skills/sync-horizon/scripts/check-state-today.sh
python3 scripts/check-repository.py
python3 scripts/check-source-sync.py --source "$HORIZON_PATH"

Phase 7: Report (orchestrator)

阶段7：报告（编排器）

undefined

undefined

Sync Report: <old_commit_short>..<new_commit_short>

同步报告：<旧提交短哈希>..<新提交短哈希>

Commits

提交记录

<count> commits synced (<feat count> features, <fix count> fixes)

同步了<数量>个提交（<feat数量>个功能，<fix数量>个修复）

Shipped Capabilities (from plans)

已上线功能（来自计划）

<capability>: <one-line summary> (plan status, feat commits)

<功能>：<一行摘要>（计划状态，feat提交）

Capability Cascade

功能级联

For each shipped capability:

<capability> → updated <reference/skill>, because <reason>

针对每个已上线功能：

<功能> → 更新了<参考文档/技能包>，原因：<理由>

Removals

移除内容

<what was removed/deprecated and cleaned from skills>

<已移除/弃用的内容及从技能包中清理的内容>

Updated Reference Docs

更新的参考文档

<file>: <what changed and why>

<文件>：<变更内容及原因>

New Reference Docs

新增的参考文档

<file>: <what it covers>

<文件>：<覆盖内容>

Updated Skills

更新的技能包

<skill>: <what changed>

<技能包>：<变更内容>

SKILL.md Routing Changes

SKILL.md路由变更

<new routes, index entries, or coverage matrix rows>

<新路由、索引条目或覆盖矩阵行>

Sync Map Changes

同步映射变更

<new mappings added>

<新增的映射关系>

State-Today Compliance

当前状态合规性

<pass/fail + scan results>

<通过/失败 + 扫描结果>

Coverage Gaps

覆盖差距

<shipped capabilities with no reference doc yet>
<plan files with no sync-map entry>
<CLI commands with no documentation coverage>

<尚无参考文档的已上线功能>
<无同步映射条目的计划文件>
<无文档覆盖的CLI命令>

Next Steps

下一步计划

<manual follow-up needed>

undefined

<需手动跟进的事项>

undefined

Key Constraints

关键约束

Plans are the primary source of truth for understanding what shipped. System docs are secondary. Code changes are confirmation.
Orchestrator reads lightweight signals only: commit log, plan headers (first 15-20 lines), file stats, CLI module list. Never full plans, full diffs, or source docs.
Workers read the heavy content: full plans, code diffs, source docs, target files.
Worker independence: Each worker prompt must be fully self-contained with plan paths, code paths, target path, capability summary, and update rules.
Parallelism: All workers launch simultaneously. No worker depends on another worker's output (except the routing update worker, which should launch after reference doc workers finish).
Edit, don't rewrite: Workers modify existing files incrementally.
State-today fidelity: Only document shipped, implemented behavior.
Progressive access: Preserve task-first routing in entry skills and keep deep detail in references.

计划是了解已上线内容的主要事实来源。系统文档是次要来源。代码变更是确认依据。
编排器仅读取轻量级信号：提交日志、计划标题（前15-20行）、文件统计、CLI模块列表。绝不读取完整计划、完整差异或源文档。
工作器读取重量级内容：完整计划、代码差异、源文档、目标文件。
工作器独立性：每个工作器提示必须完全独立，包含计划路径、代码路径、目标路径、功能摘要和更新规则。
并行性：所有工作器同时启动。除路由更新工作器需在参考文档工作器完成后启动外，其他工作器无需依赖彼此的输出。
编辑而非重写：工作器增量修改现有文件。
当前状态准确性：仅记录已上线、已实现的行为。
渐进式访问：保留入门技能包中以任务为核心的路由，将详细内容放在参考文档中。