fix(agents): 修复文件重命名后遗留的断裂交叉引用 - #35
Conversation
FAQ: - 06-performance: 扩充至 7 个问题（磁盘/GPU/长时间运行/资源监控/智能体数量） - 07-delegation: 新增委派与协作 FAQ（7 个问题） - 08-automation: 新增自动化 FAQ（7 个问题，含 cron 速查） - 05-data-privacy: 补充官方云算力数据路径说明 More: - 04-supported-providers: 补充官方云算力、NewAPI 网关、创意生成厂商、选择建议 - index.md: 补充遗漏的第三方软件条目 - 02-keyboard-shortcuts: 添加快捷键分类图（drawio 源文件） - 07-data-locations: 添加数据流向图（drawio 源文件）
- capabilities: web-access 添加启用步骤、SitePattern 用例、决策流程表 - capabilities: media-generation 添加 provider 对比、参数表、使用示例 - capabilities: app-service-catalog 添加入口说明、详细安装步骤、FAQ - memory: view-manage 添加类型筛选、批量管理、Unpin 操作 - super-document: overview 替换 ASCII 流程图为正式配图 - super-document: review-changes 添加编辑后重新提交、审阅策略建议 - email: unified-inbox 添加排序筛选、搜索、批量操作 - email: labels-folders 添加同步机制对比表、自定义标签创建步骤 - 新增 3 张配图（tool-system/memory/super-doc workflow）
- delegation-model: 替换 ASCII 流程图为 Mermaid flowchart + 引用 trust-ladder.svg - agentfs: 添加数据归属关系 Mermaid 图（智能体本体/用户数据/运行态） - step-types: 添加三种步骤类型对比 Mermaid 图 - receipt-system: 添加回执工作流 Mermaid 图 - self-evolution: 添加三层进化机制 Mermaid 图 - task-orchestration: 添加编排引擎流水线 Mermaid 图 - auto-dream: 添加记忆整合过程 Mermaid 图
Interface 章节: - 添加三栏布局、导航栏结构、对话列表、聊天区域、数字人、通知面板 6 张配图 - 为 feature-entry.md 添加 YAML frontmatter Conversations 章节: - 添加消息类型对比、卡片颜色编码、模型选择器、上下文生命周期、Rewind时间线、导出流程 6 张配图 - markdown-rendering.md: 补充渲染效果示例和异常处理表格 - exporting-conversations.md: 补充详细操作步骤 - context-control.md: 补充实践建议和注意事项 - rewind-checkpoints.md: 补充分支机制说明
Phase 3 - 内容补充: - 09-clone-and-sync.md: 添加使用场景、操作步骤、同步策略、冲突解决细节、FAQ - 05-learning-feedback.md: 添加学习存储机制、多条学习、最佳实践 - 12-prompt-center.md: 添加三层实战示例、常见问题 Phase 4 - 结构优化: - 修复 09-clone-and-sync 与 09-team-version-management 编号冲突 - 重排: 09→09, 09-team→10, 10-team→11, 11-prompt→12 - 更新 04-edit-persona/05-edit-principles 中的交叉引用 - 同步重命名 i18n/en 对应文件
- 08-version-control.md: ./09-team-version-management.md → ./10-team-version-management.md - 08-version-control.md: ./clone-and-sync → ./09-clone-and-sync.md (统一为文件路径格式) - 08-version-control.md: ./team-version-control → ./10-team-version-management.md - 11-team-version-control.md: 2处 ./09-team-version-management.md → ./10-team-version-management.md - i18n/en 08-version-control.md: 同步修复 复盘确认： - 未修改任何 compute 相关文件 - 所有 24 篇子章节文件完整（agents 12 + teaching 6 + delegation 6） - 11 张 SVG 配图全部存在且内容完整 - 所有图片引用路径正确 - 所有内部和跨章节链接验证通过
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 373004744c
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| ## Next Steps | ||
|
|
||
| - [Team Version Management](./09-team-version-management.md) - Manage an entire Agent team as a single versioned unit | ||
| - [Team Version Management](./10-team-version-management.md) - Manage an entire Agent team as a single versioned unit |
There was a problem hiding this comment.
When the English locale is built, this renumbering is incomplete: 04-edit-persona.md lines 23 and 106 and 05-edit-principles.md line 98 still link to ./11-prompt-center.md, but that file is moved to 12-prompt-center.md in this commit. With onBrokenLinks: 'throw', the English documentation build fails; update these three backlinks as part of the renumbering.
Useful? React with 👍 / 👎.
|
|
||
| 导航栏从上到下分为三个区域： | ||
|
|
||
|  |
There was a problem hiding this comment.
Users relying on this new diagram are shown a UI that contradicts the page itself: the image labels the Activity entry as “脉冲线,” presents an unexplained v2.4.1, and contains specification typos such as border-rads, box-shoow, and font-fonly. Since this is presented as the navigation structure rather than as conceptual artwork, replace it with an accurate capture or diagram matching the documented controls.
Useful? React with 👍 / 👎.
|
|
||
| # 消息类型识别 | ||
|
|
||
|  |
There was a problem hiding this comment.
Loading any affected guide page now requires downloading a roughly 4–6 MiB 2048×2048 PNG through a plain static image URL; the 16 new PNGs total about 70 MiB. This is far larger than the existing documentation screenshots and creates a substantial page-load penalty, especially on mobile connections, so resize and compress these diagrams or serve optimized WebP/AVIF variants before embedding them.
Useful? React with 👍 / 👎.
修复 PR #35 审核反馈： - 删除误提交的 PLAN-interface-conversations.md - 还原 interface/conversations/super-document/memory/capabilities/email/ concepts/more/faq 章节至 origin/main（由 PR #36/#38 各自负责） - 移除 .drawio 源文件（keyboard-shortcuts-overview, data-flow-diagram） - 移除不属于本 PR 的 static/img 图片文件 - 移除 FAQ 中越界新增的 07-delegation.md、08-automation.md 本 PR 现仅包含 user-guide/06-agents/ 和 03-teaching/ 的内容增强。
There was a problem hiding this comment.
💡 Codex Review
docs/docs/02-user-guide/06-agents/10-team-version-management.md
Lines 194 to 195 in 41eb7d8
Reconnect the desktop clone before instructing it to sync
In this cross-device scenario, using “从链接安装” clears the installed team's repository URL, as the same page states at lines 157–158. The desktop copy therefore has no remote from which to pull or to which it can push, so step 4 cannot keep the two machines synchronized unless the user first reconnects the desktop team to the same repository; add that missing step or use an installation flow that preserves the remote.
Replace the stale English page with the FAQ translation
The paired Chinese 11-team-version-control.md is now a 107-line FAQ and troubleshooting page, but this renamed English locale file still contains the former 22-line capability overview. Because the localized file occupies the new FAQ's document ID, English users get stale, largely duplicate version-management content and none of the newly added troubleshooting guidance; translate the replacement page or remove this stale localization so it can fall back appropriately.
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Keep the remote for the cross-device install path
Following this cross-device scenario currently leaves the desktop unable to perform step 4: the same “Install From Link” flow above is documented as clearing the repository address after install, so the installed team has no remote to push/pull against until the user reconnects it. For the laptop/desktop sync case, either document a flow that preserves/reconnects the remote or avoid promising immediate push/pull sync.
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b60816a420
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|  | ||
|
|
||
| 完整的计划是一份结构化文档，自动保存在 **当前工作目录** 的 `plans/` 子文件夹下（文件名按任务关键词命名，例如 `plans/review-procurement-contract.md`）。即便你关掉对话，文件也会留在那里，方便后续查阅或纳入版本控制。 | ||
| 完整的计划是一份结构化 Markdown 文档，自动保存在 **当前工作目录** 的 `.desirecore/plans/<plan-id>/PLAN.md`（例如 `.desirecore/plans/plan-review-contract/PLAN.md`）。即便你关掉对话，文件也会留在那里，方便后续查阅或纳入版本控制。每次修订计划都会在 `revisions/` 子目录保存不可变历史版本。 |
There was a problem hiding this comment.
After this change, plan-confirmation says plans are stored under .desirecore/plans/<plan-id>/PLAN.md, but the adjacent execution-monitoring examples still show task entries linked to plans/review-procurement-contract.md in both the Chinese page (docs/02-user-guide/04-delegation/03-execution-monitoring.md:42) and the English locale (i18n/en/docusaurus-plugin-content-docs/current/02-user-guide/04-delegation/03-execution-monitoring.md:65). Users following the delegation flow now get conflicting locations for the same plan artifact, so update those examples when changing the storage path here.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ea0d97b116
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| | 选项 | 含义 | | ||
| |------|------| | ||
| | **批准并执行** | 按当前计划执行；强制模式自动关闭 | | ||
| | **需要修改** | 你描述修改点，智能体改完计划再让你审一次 | | ||
| | **拒绝** | 任务终止；强制模式自动关闭 | |
There was a problem hiding this comment.
In the delegation flow I checked docs/02-user-guide/04-delegation/03-execution-monitoring.md:9, which still says there is no unified “批准计划” state; these new options instead tell users to expect an approve/reject approval UI and forced-mode auto-disable behavior. Unless the product behavior was changed with the docs, users will wait for controls/states that the next page says do not exist, so keep the natural-language revision flow or update the monitoring page/feature together.
Useful? React with 👍 / 👎.
1 participant
变更内容
修复 ea95c4d 提交中文件重命名（09→10, 10→11, 11→12）后遗留的 6 处断裂交叉引用。
修改文件
docs/02-user-guide/06-agents/08-version-control.mddocs/02-user-guide/06-agents/11-team-version-control.mdi18n/en/.../06-agents/08-version-control.md复盘确认