docs(ai-plan): 迁移 coroutine 早期计划#257
Conversation
- 新增 coroutine-optimization 主题并整合 legacy local-plan todo，补写缺失 trace 的恢复边界\n- 更新 ai-plan 公共索引与治理跟踪，建立 feat/coroutine-optimization 的 topic 映射\n- 删除 worktree 根目录 legacy local-plan 入口，统一从 ai-plan/public 恢复
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📜 Recent review details⏰ Context from checks skipped due to timeout of 900000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
📝 WalkthroughWalkthrough新增 ai-plan 主题目录 Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 分钟 Possibly related PRs
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
Test Results
Details
Insights
build-and-test: Run #889
🎉 All tests passed!Slowest Tests
🎉 No failed tests in this run. | 🍂 No flaky tests in this run. Github Test Reporter by CTRF 💚 |
✅MegaLinter analysis: Success
See detailed reports in MegaLinter artifacts
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md`:
- Line 92: 将重复的同级标题 "### 下一步"（触发 MD024）替换为一个带阶段或上下文限定的唯一标题，例如在原始 "### 下一步"
后添加阶段标识、时间点或模块名（如 "下一步 — 验证阶段" 或 "下一步（迭代 1）"），以确保标题唯一并消除 markdownlint 的 MD024
警告；在文档中寻找所有出现相同文本的标题并统一采用该唯一化命名约定，更新章节标题处的 "### 下一步" 即可（参考标识符: "### 下一步"）。
🪄 Autofix (Beta)
✅ Autofix completed
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: c2416faf-c709-411d-968b-02afd073554b
📒 Files selected for processing (7)
ai-plan/public/README.mdai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.mdai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.mdai-plan/public/coroutine-optimization/archive/todos/coroutine-optimization-history-pre-rp001.mdai-plan/public/coroutine-optimization/archive/traces/coroutine-optimization-history-pre-rp001.mdai-plan/public/coroutine-optimization/todos/coroutine-optimization-tracking.mdai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.md
📜 Review details
⏰ Context from checks skipped due to timeout of 900000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Analyze (C#)
- GitHub Check: Code Quality & Security
🧰 Additional context used
📓 Path-based instructions (5)
**/README.md
📄 CodeRabbit inference engine (AGENTS.md)
Every user-facing package or module directory that contains a
*.csprojintended for direct consumption MUST have a siblingREADME.mdwith canonical filenameREADME.md. A module README MUST describe the module's purpose, relationship to adjacent runtime/abstractions/generator packages, major subdirectories/subsystems, minimum adoption path, and correspondingdocs/zh-CN/entry points.
Files:
ai-plan/public/README.md
ai-plan/public/**/*
📄 CodeRabbit inference engine (AGENTS.md)
ai-plan/public/**/*: Contributors MUST keep committedai-plan/public/**content safe to publish in Git history. Never write secrets, tokens, credentials, private keys, machine usernames, home-directory paths, hostnames, IP addresses, proprietary URLs, or other sensitive environment details into anyai-plan/**file.
Never record absolute file-system paths inai-plan/**; use repository-relative paths, branch names, PR numbers, or stable document identifiers instead.
Files:
ai-plan/public/README.mdai-plan/public/coroutine-optimization/archive/todos/coroutine-optimization-history-pre-rp001.mdai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.mdai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.mdai-plan/public/coroutine-optimization/archive/traces/coroutine-optimization-history-pre-rp001.mdai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.mdai-plan/public/coroutine-optimization/todos/coroutine-optimization-tracking.md
ai-plan/public/README.md
📄 CodeRabbit inference engine (AGENTS.md)
ai-plan/public/README.mdMUST list only active topics. Do not addai-plan/public/archive/**content to the default boot index. When a worktree-to-topic mapping changes or when a topic becomes active/inactive, contributors MUST updateai-plan/public/README.mdin the same change.
Files:
ai-plan/public/README.md
ai-plan/public/*/traces/**/*
📄 CodeRabbit inference engine (AGENTS.md)
Contributors MUST maintain a matching execution trace under
ai-plan/public/<topic>/traces/for complex work. The trace should record the current date, key decisions, validation milestones, and the immediate next step. Update traces at each meaningful milestone before pausing or handing work off.
Files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.mdai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.md
ai-plan/public/*/todos/**/*
📄 CodeRabbit inference engine (AGENTS.md)
When working from a tracked implementation plan, contributors MUST update the corresponding tracking document under
ai-plan/public/<topic>/todos/in the same change. Updates MUST reflect completed work, newly discovered issues, validation results, and the next recommended recovery point. Tracking files are recovery entrypoints, not append-only changelogs, and MUST stay concise.
Files:
ai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.mdai-plan/public/coroutine-optimization/todos/coroutine-optimization-tracking.md
🧠 Learnings (14)
📓 Common learnings
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: For any multi-step refactor, migration, or cross-module task, contributors MUST create or adopt a dedicated recovery document under `ai-plan/public/<topic>/todos/` before making substantive code changes. Recovery documents MUST record the current phase, the active recovery point identifier, known risks, and the next recommended resume step so another contributor or subagent can continue the work safely.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/*/todos/**/* : When working from a tracked implementation plan, contributors MUST update the corresponding tracking document under `ai-plan/public/<topic>/todos/` in the same change. Updates MUST reflect completed work, newly discovered issues, validation results, and the next recommended recovery point. Tracking files are recovery entrypoints, not append-only changelogs, and MUST stay concise.
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/README.md : `ai-plan/public/README.md` MUST list only active topics. Do not add `ai-plan/public/archive/**` content to the default boot index. When a worktree-to-topic mapping changes or when a topic becomes active/inactive, contributors MUST update `ai-plan/public/README.md` in the same change.
Applied to files:
ai-plan/public/README.mdai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.mdai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.mdai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/*/todos/**/* : When working from a tracked implementation plan, contributors MUST update the corresponding tracking document under `ai-plan/public/<topic>/todos/` in the same change. Updates MUST reflect completed work, newly discovered issues, validation results, and the next recommended recovery point. Tracking files are recovery entrypoints, not append-only changelogs, and MUST stay concise.
Applied to files:
ai-plan/public/README.mdai-plan/public/coroutine-optimization/archive/todos/coroutine-optimization-history-pre-rp001.mdai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.mdai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.mdai-plan/public/coroutine-optimization/archive/traces/coroutine-optimization-history-pre-rp001.mdai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.mdai-plan/public/coroutine-optimization/todos/coroutine-optimization-tracking.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: When a topic is fully complete, move the entire topic directory under `ai-plan/public/archive/<topic>/` and remove it from `ai-plan/public/README.md` in the same change.
Applied to files:
ai-plan/public/README.mdai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.mdai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.mdai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: For any multi-step refactor, migration, or cross-module task, contributors MUST create or adopt a dedicated recovery document under `ai-plan/public/<topic>/todos/` before making substantive code changes. Recovery documents MUST record the current phase, the active recovery point identifier, known risks, and the next recommended resume step so another contributor or subagent can continue the work safely.
Applied to files:
ai-plan/public/README.mdai-plan/public/coroutine-optimization/archive/todos/coroutine-optimization-history-pre-rp001.mdai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.mdai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.mdai-plan/public/coroutine-optimization/archive/traces/coroutine-optimization-history-pre-rp001.mdai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.mdai-plan/public/coroutine-optimization/todos/coroutine-optimization-tracking.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/*/traces/**/* : Contributors MUST maintain a matching execution trace under `ai-plan/public/<topic>/traces/` for complex work. The trace should record the current date, key decisions, validation milestones, and the immediate next step. Update traces at each meaningful milestone before pausing or handing work off.
Applied to files:
ai-plan/public/README.mdai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.mdai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.mdai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: If a task depends on observations from `ai-libs/**`, record the referenced path and conclusion in the active plan or trace when the work is multi-step or complex, or when an active tracking document already exists, rather than editing the third-party reference copy.
Applied to files:
ai-plan/public/README.mdai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.mdai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.mdai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Use `ai-plan/public/**` only for durable, handoff-safe task state. Put temporary notes, local experiments, or worktree-specific scratch recovery data under `ai-plan/private/`.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.mdai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.mdai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/**/* : Never record absolute file-system paths in `ai-plan/**`; use repository-relative paths, branch names, PR numbers, or stable document identifiers instead.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.mdai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.mdai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: When a stage inside an active topic is fully complete, move the finished artifacts into that topic's `archive/` directory instead of leaving every completed step in the default boot path. When completed and validated stages begin to accumulate, archive their detailed history out of the active `todos/` and `traces/` entry files. Keep only the current recovery point, active facts, active risks, immediate next step, and pointers to relevant archive files in the default boot path.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.mdai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.mdai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to docs/zh-CN/**/*.md : When a feature is added, removed, renamed, or substantially refactored, contributors MUST update or create the corresponding user-facing integration documentation in `docs/zh-CN/` in the same change. For integration-oriented features, documentation MUST cover project directory layout, file conventions, required project/package wiring, minimal working usage example, and migration/compatibility notes.
Applied to files:
ai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.mdai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Before considering work complete, confirm: required comments and XML docs are present, code follows repository style and naming rules, relevant tests were added or updated, sensitive or unsafe behavior was not introduced, user-facing documentation is updated when needed, and feature adoption docs under `docs/zh-CN/` were added or updated when functionality was added, removed, or refactored.
Applied to files:
ai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to docs/zh-CN/**/*.md : Code samples, package names, and command examples in documentation MUST be aligned with the current repository state. When an existing documentation page no longer reflects the current implementation, fix the code without fixing the documentation is considered incomplete work.
Applied to files:
ai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: When a task spans multiple commits or is likely to exceed a single agent context window, update both the recovery document and the trace at each meaningful milestone before pausing or handing work off.
Applied to files:
ai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
🪛 LanguageTool
ai-plan/public/coroutine-optimization/archive/todos/coroutine-optimization-history-pre-rp001.md
[uncategorized] ~40-~40: 您的意思是“"不"更”？
Context: ...e与WaitOneFrame的命名差异是否值得保留 - 为阶段型等待补更多跨宿主说明与样例 - 审视WaitForCoroutine` 在父子调度...
(BU)
[uncategorized] ~45-~45: 您的意思是“"不"统一”？
Context: ...utine` 在父子调度器不同阶段时的语义 ### 可选增强 - 为等待指令补统一的语义类别元数据 - 支持宿主自定义阶段映射 ### 风险与验收 - 风...
(BU)
[uncategorized] ~77-~77: 您的意思是“"不"更”？
Context: ...路 ### 后续必做项 - 评估是否需要完成历史的上限或清理策略 - 为快照补更多可观测字段时保持分配与遍历成本可控 - 审查取消、终止、异常三种完成路径的外...
(BU)
[uncategorized] ~101-~101: 您的意思是“源"于"”吗？
Context: ...ration ### 已有基础 - Timing 已为各段提供缩放时间源与真实时间源 - PhysicsProcess / `DeferredProc...
(YU7_YU8)
[uncategorized] ~148-~148: 您的意思是“"不"异常”？
Context: ...odot 运行时级测试，覆盖节点归属、退树、暂停和各 segment 差异 - 补异常传播、完成历史与快照字段的更多边界测试 - 评估是否需要把 `GFramew...
(BU)
[uncategorized] ~190-~190: 您的意思是“"不"更”？
Context: ...FixedUpdate/WaitForEndOfFrame` 的宿主前提补更多页面说明 ### 可选增强 - 增加 FAQ 和排障章节 - 增加 Go...
(BU)
[uncategorized] ~205-~205: 您的意思是“"不"迁移”？
Context: ...状态 - 主文档与教程已对齐当前实现 - 下一步原计划：继续清理其他文档残留并补迁移说明 ## 历史结论 - 旧 local-plan 记录的不是“待从...
(BU)
[uncategorized] ~211-~211: 您的意思是“"不"回”？
Context: ...续推进时，应基于 active tracking 重新选择一个最小切入点，并补回当轮 trace 与验证记录
(BU)
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
[uncategorized] ~76-~76: 您的意思是“"不"齐”？
Context: ...i-plan/public/coroutine-optimization/，并补齐： - todos/ -traces/ -archi...
(BU)
[uncategorized] ~81-~81: 您的意思是“"不"写”？
Context: ... local-plan 中分散的五个阶段计划整合进主题内历史跟踪归档，并额外补写一份基于 todo 基线整理出的历史 trace， 显式记录“缺少原始 t...
(BU)
[uncategorized] ~95-~95: 您的意思是“"不"写”？
Context: ...，并明确标注推导边界 2. 保持新 topic 的 active 入口精简，不把补写 trace 变成伪造逐日执行日志
(BU)
ai-plan/public/coroutine-optimization/archive/traces/coroutine-optimization-history-pre-rp001.md
[uncategorized] ~10-~10: 您的意思是“"不"录”？
Context: ... ## 2026-04-19 ### 阶段：早期 coroutine 计划基线补录（RP-001） - 复核 `local-plan/todos/corout...
(BU)
[uncategorized] ~29-~29: 您的意思是“"不"齐”？
Context: ...free` 等行为仍需更强验证 - 更贴近运行时的集成测试与迁移对照文档仍待补齐 - 已显式记录信息缺口： - 没有原始执行 trace - 没有与每...
(BU)
[uncategorized] ~40-~40: 您的意思是“"不"证”？
Context: ...点编号 3. 如果需要更强历史精度，只能再从 Git 历史、测试记录或代码差异中补证，不能把旧 todo 当作完整 trace 使用
(BU)
ai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md
[uncategorized] ~82-~82: 您的意思是“"不"齐”？
Context: ...期、只有 todo 没有 trace 的 coroutine 计划也已按治理规则补齐 active 入口与 archive - `test ! -e local-...
(BU)
ai-plan/public/coroutine-optimization/todos/coroutine-optimization-tracking.md
[uncategorized] ~5-~5: 您的意思是“"不"宿主”？
Context: ...e Optimization 跟踪 ## 目标 继续以“先收敛语义一致性，再补宿主验证和迁移文档”为原则推进当前协程体系，避免 Core 与 Godot 两侧...
(BU)
[uncategorized] ~47-~47: 动词的修饰一般为‘形容词（副词）+地+动词’。您的意思是否是：新"地"追加
Context: ... 跟踪文件只保留当前恢复点、活跃事实、风险与下一步，避免把更早期计划直接平移成新的追加式日志 ## 下一步 1. 若继续该主题，先在 `Core Semant...
(wb4)
[uncategorized] ~52-~52: 您的意思是“"不"验证”？
Context: ...、Docs And Migration` 中只选一个切入点推进 2. 若优先补验证，先规划 Godot 集成测试宿主与节点归属/退树/暂停场景，再扩运行时诊断...
(BU)
[uncategorized] ~53-~53: 您的意思是“"不"文档”？
Context: ...t 集成测试宿主与节点归属/退树/暂停场景，再扩运行时诊断 API 3. 若优先补文档与迁移说明，先清理其余 `StartCoroutine()/StopCoro...
(BU)
[uncategorized] ~53-~53: 您的意思是“"不"统一”？
Context: ...routine()/StopCoroutine()` 残留，再为阶段等待和新入口补统一对照说明
(BU)
🪛 markdownlint-cli2 (0.22.0)
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
[warning] 92-92: Multiple headings with the same content
(MD024, no-duplicate-heading)
🔇 Additional comments (7)
ai-plan/public/coroutine-optimization/todos/coroutine-optimization-tracking.md (1)
10-53: 结构完整，符合恢复入口约束。当前 tracking 已覆盖恢复点、活跃事实、风险、验证说明与下一步，且保持为可交接的精简入口，方向正确。
As per coding guidelines
ai-plan/public/*/todos/**/*: “Updates MUST reflect completed work, newly discovered issues, validation results, and the next recommended recovery point.”ai-plan/public/coroutine-optimization/archive/todos/coroutine-optimization-history-pre-rp001.md (1)
5-211: 历史基线归档边界定义清晰。“来源—阶段—风险—验收—恢复边界”的组织方式可读性很好，便于后续在 active 文档中保持精简。
ai-plan/public/README.md (1)
28-32: 索引与分支映射更新到位。新增 active topic 与 worktree 映射同步，符合 boot 入口定位预期。
As per coding guidelines
ai-plan/public/README.md: “When a worktree-to-topic mapping changes ... contributors MUST updateai-plan/public/README.mdin the same change.”Also applies to: 54-57
ai-plan/public/coroutine-optimization/archive/traces/coroutine-optimization-history-pre-rp001.md (1)
8-40: trace 归档补录方式合理。对“可恢复结论”与“不可伪造逐日流水”的边界写得明确，能有效降低后续误用风险。
ai-plan/public/coroutine-optimization/traces/coroutine-optimization-trace.md (1)
3-34: active trace 信息完整，适合交接恢复。当前条目已覆盖关键决策、验证里程碑与立即下一步，符合复杂任务 trace 入口要求。
As per coding guidelines
ai-plan/public/*/traces/**/*: “The trace should record the current date, key decisions, validation milestones, and the immediate next step.”ai-plan/public/ai-plan-governance/todos/ai-plan-governance-tracking.md (1)
57-67: 治理 tracking 与本次迁移闭环一致。完成项、验证项、后续扫描策略三者衔接自然，作为 RP-005 的恢复入口是合格的。
Also applies to: 80-83, 97-97
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md (1)
72-90: RP-005 的 coroutine 迁移追踪记录完整。该段对“todo-only 历史”的迁移边界、验证命令与后续约束描述清楚，治理可执行性较好。
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Fixes Applied SuccessfullyFixed 1 file(s) based on 1 unresolved review comment. Files modified:
Commit: The changes have been pushed to the Time taken: |
Fixed 1 file(s) based on 1 unresolved review comment. Co-authored-by: CodeRabbit <noreply@coderabbit.ai>
Summary
Test Results
Details
Insights
build-and-test: Run #890
🎉 All tests passed!Slowest Tests
± Comparison with run #889 at 271e018 | 🎉 No failed tests detected across all runs. | 🍂 No flaky tests detected across all runs. | ⏱️ Measured over 2 runs. Github Test Reporter by CTRF 💚 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md`:
- Around line 84-90: Update the ai-plan/public/README.md to include the
mandatory worktree mapping entry for feat/coroutine-optimization ->
coroutine-optimization as described in the trace; locate the README and add a
clear mapping line or section that documents the new worktree
(feat/coroutine-optimization) pointing to the coroutine-optimization directory
so the governance requirement referenced in ai-plan-governance-trace.md is
satisfied and the repo’s worktree mappings remain consistent with the created
coroutine-optimization directory and its todos/traces/archive structure.
🪄 Autofix (Beta)
❌ Autofix failed (check again to retry)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: a2b3abf2-6500-4b4b-86b9-8992d00de727
📒 Files selected for processing (1)
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
📜 Review details
⏰ Context from checks skipped due to timeout of 900000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: Analyze (C#)
- GitHub Check: Build and Test
- GitHub Check: Code Quality & Security
🧰 Additional context used
📓 Path-based instructions (2)
ai-plan/public/**/*
📄 CodeRabbit inference engine (AGENTS.md)
ai-plan/public/**/*: Contributors MUST keep committedai-plan/public/**content safe to publish in Git history. Never write secrets, tokens, credentials, private keys, machine usernames, home-directory paths, hostnames, IP addresses, proprietary URLs, or other sensitive environment details into anyai-plan/**file.
Never record absolute file-system paths inai-plan/**; use repository-relative paths, branch names, PR numbers, or stable document identifiers instead.
Files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
ai-plan/public/*/traces/**/*
📄 CodeRabbit inference engine (AGENTS.md)
Contributors MUST maintain a matching execution trace under
ai-plan/public/<topic>/traces/for complex work. The trace should record the current date, key decisions, validation milestones, and the immediate next step. Update traces at each meaningful milestone before pausing or handing work off.
Files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
🧠 Learnings (13)
📓 Common learnings
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: For any multi-step refactor, migration, or cross-module task, contributors MUST create or adopt a dedicated recovery document under `ai-plan/public/<topic>/todos/` before making substantive code changes. Recovery documents MUST record the current phase, the active recovery point identifier, known risks, and the next recommended resume step so another contributor or subagent can continue the work safely.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Commit messages MUST use Conventional Commits format: `<type>(<scope>): <summary>`. The commit `summary` MUST use simplified Chinese and briefly describe the main change. The commit `body` MUST use unordered list items, each starting with a verb such as `新增`、`修复`、`优化`、`更新`、`补充`、`重构`. Each commit body bullet MUST describe one independent change point. Keep technical terms in English when they are established project terms, such as `API`、`Model`、`System`.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: When a topic is fully complete, move the entire topic directory under `ai-plan/public/archive/<topic>/` and remove it from `ai-plan/public/README.md` in the same change.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/*/todos/**/* : When working from a tracked implementation plan, contributors MUST update the corresponding tracking document under `ai-plan/public/<topic>/todos/` in the same change. Updates MUST reflect completed work, newly discovered issues, validation results, and the next recommended recovery point. Tracking files are recovery entrypoints, not append-only changelogs, and MUST stay concise.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/README.md : `ai-plan/public/README.md` MUST list only active topics. Do not add `ai-plan/public/archive/**` content to the default boot index. When a worktree-to-topic mapping changes or when a topic becomes active/inactive, contributors MUST update `ai-plan/public/README.md` in the same change.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Use `ai-plan/public/**` only for durable, handoff-safe task state. Put temporary notes, local experiments, or worktree-specific scratch recovery data under `ai-plan/private/`.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: When a stage inside an active topic is fully complete, move the finished artifacts into that topic's `archive/` directory instead of leaving every completed step in the default boot path. When completed and validated stages begin to accumulate, archive their detailed history out of the active `todos/` and `traces/` entry files. Keep only the current recovery point, active facts, active risks, immediate next step, and pointers to relevant archive files in the default boot path.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/*/traces/**/* : Contributors MUST maintain a matching execution trace under `ai-plan/public/<topic>/traces/` for complex work. The trace should record the current date, key decisions, validation milestones, and the immediate next step. Update traces at each meaningful milestone before pausing or handing work off.
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/*/todos/**/* : When working from a tracked implementation plan, contributors MUST update the corresponding tracking document under `ai-plan/public/<topic>/todos/` in the same change. Updates MUST reflect completed work, newly discovered issues, validation results, and the next recommended recovery point. Tracking files are recovery entrypoints, not append-only changelogs, and MUST stay concise.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/*/traces/**/* : Contributors MUST maintain a matching execution trace under `ai-plan/public/<topic>/traces/` for complex work. The trace should record the current date, key decisions, validation milestones, and the immediate next step. Update traces at each meaningful milestone before pausing or handing work off.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: For any multi-step refactor, migration, or cross-module task, contributors MUST create or adopt a dedicated recovery document under `ai-plan/public/<topic>/todos/` before making substantive code changes. Recovery documents MUST record the current phase, the active recovery point identifier, known risks, and the next recommended resume step so another contributor or subagent can continue the work safely.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: If a task depends on observations from `ai-libs/**`, record the referenced path and conclusion in the active plan or trace when the work is multi-step or complex, or when an active tracking document already exists, rather than editing the third-party reference copy.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/README.md : `ai-plan/public/README.md` MUST list only active topics. Do not add `ai-plan/public/archive/**` content to the default boot index. When a worktree-to-topic mapping changes or when a topic becomes active/inactive, contributors MUST update `ai-plan/public/README.md` in the same change.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Treat source code, `*.csproj`, tests, generated snapshots, and packaging metadata as the primary evidence for documentation updates. Treat `CoreGrid` as a secondary evidence source for real project adoption patterns, directory layouts, and end-to-end usage examples. Treat existing `README.md` files and `docs/zh-CN/` pages as editable outputs, not authoritative truth.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/**/* : Never record absolute file-system paths in `ai-plan/**`; use repository-relative paths, branch names, PR numbers, or stable document identifiers instead.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to docs/zh-CN/**/*.md : When a feature is added, removed, renamed, or substantially refactored, contributors MUST update or create the corresponding user-facing integration documentation in `docs/zh-CN/` in the same change. For integration-oriented features, documentation MUST cover project directory layout, file conventions, required project/package wiring, minimal working usage example, and migration/compatibility notes.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Before considering work complete, confirm: required comments and XML docs are present, code follows repository style and naming rules, relevant tests were added or updated, sensitive or unsafe behavior was not introduced, user-facing documentation is updated when needed, and feature adoption docs under `docs/zh-CN/` were added or updated when functionality was added, removed, or refactored.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: When a stage inside an active topic is fully complete, move the finished artifacts into that topic's `archive/` directory instead of leaving every completed step in the default boot path. When completed and validated stages begin to accumulate, archive their detailed history out of the active `todos/` and `traces/` entry files. Keep only the current recovery point, active facts, active risks, immediate next step, and pointers to relevant archive files in the default boot path.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: When a topic is fully complete, move the entire topic directory under `ai-plan/public/archive/<topic>/` and remove it from `ai-plan/public/README.md` in the same change.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Use `ai-plan/public/**` only for durable, handoff-safe task state. Put temporary notes, local experiments, or worktree-specific scratch recovery data under `ai-plan/private/`.
Applied to files:
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
🪛 LanguageTool
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md
[uncategorized] ~76-~76: 您的意思是“"不"齐”？
Context: ...i-plan/public/coroutine-optimization/，并补齐： - todos/ -traces/ -archi...
(BU)
[uncategorized] ~81-~81: 您的意思是“"不"写”？
Context: ... local-plan 中分散的五个阶段计划整合进主题内历史跟踪归档，并额外补写一份基于 todo 基线整理出的历史 trace， 显式记录"缺少原始 t...
(BU)
[uncategorized] ~95-~95: 您的意思是“"不"写”？
Context: ...，并明确标注推导边界 2. 保持新 topic 的 active 入口精简，不把补写 trace 变成伪造逐日执行日志
(BU)
🔇 Additional comments (2)
ai-plan/public/ai-plan-governance/traces/ai-plan-governance-trace.md (2)
81-82: 良好的边界标注实践。Line 81-82 明确记录"补写基于 todo 基线的历史 trace"并显式标注"缺少原始 trace，只能恢复稳定结论"的边界，这是处理遗留早期计划的最佳实践，既保证了追踪的完整性，又避免伪造详细执行历史。
92-95: "下一步"指导明确且可操作。Line 92-95 为后续遇到类似"只有 todo、没有 trace"的早期计划提供了清晰的处理模式，强调保持 active 入口精简并明确推导边界，符合治理规则对可恢复性与精简性的双重要求。
|
Note Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. The agent ran but didn't make any changes. The issues may already be fixed or require manual intervention. |
- 添加协程优化分支信息到文档 - 更新工作树提示为 GFramework 协程优化 - 添加协程优化优先级标记
Summary
Test Results
Details
Insights
build-and-test: Run #891
🎉 All tests passed!Slowest Tests
± Comparison with run #890 at 47292e2 | 🎉 No failed tests detected across all runs. | 🍂 No flaky tests detected across all runs. | ⏱️ Measured over 3 runs. Github Test Reporter by CTRF 💚 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@ai-plan/public/README.md`:
- Around line 61-64: 删除 README 中重复的映射块：移除第二处关于分支名 `feat/coroutine-optimization`
的映射定义（当前出现在行 61-64 的块），仅保留首个声明（行 54-57）并确保该保留块的缩进与周围映射一致以避免 boot
读取顺序或优先级歧义；确认最终文件只包含一处 `feat/coroutine-optimization` 映射且索引/优先级字段（如 `Worktree
hint`、`Priority`）在该唯一块中正确无误。
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: d0164e22-f72b-4625-bafe-67ab00f1ac63
📒 Files selected for processing (1)
ai-plan/public/README.md
📜 Review details
⏰ Context from checks skipped due to timeout of 900000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: Code Quality & Security
- GitHub Check: Build and Test
- GitHub Check: Analyze (C#)
🧰 Additional context used
📓 Path-based instructions (3)
**/README.md
📄 CodeRabbit inference engine (AGENTS.md)
Every user-facing package or module directory that contains a
*.csprojintended for direct consumption MUST have a siblingREADME.mdwith canonical filenameREADME.md. A module README MUST describe the module's purpose, relationship to adjacent runtime/abstractions/generator packages, major subdirectories/subsystems, minimum adoption path, and correspondingdocs/zh-CN/entry points.
Files:
ai-plan/public/README.md
ai-plan/public/**/*
📄 CodeRabbit inference engine (AGENTS.md)
ai-plan/public/**/*: Contributors MUST keep committedai-plan/public/**content safe to publish in Git history. Never write secrets, tokens, credentials, private keys, machine usernames, home-directory paths, hostnames, IP addresses, proprietary URLs, or other sensitive environment details into anyai-plan/**file.
Never record absolute file-system paths inai-plan/**; use repository-relative paths, branch names, PR numbers, or stable document identifiers instead.
Files:
ai-plan/public/README.md
ai-plan/public/README.md
📄 CodeRabbit inference engine (AGENTS.md)
ai-plan/public/README.mdMUST list only active topics. Do not addai-plan/public/archive/**content to the default boot index. When a worktree-to-topic mapping changes or when a topic becomes active/inactive, contributors MUST updateai-plan/public/README.mdin the same change.
Files:
ai-plan/public/README.md
🧠 Learnings (7)
📓 Common learnings
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to docs/zh-CN/**/*.md : When a feature is added, removed, renamed, or substantially refactored, contributors MUST update or create the corresponding user-facing integration documentation in `docs/zh-CN/` in the same change. For integration-oriented features, documentation MUST cover project directory layout, file conventions, required project/package wiring, minimal working usage example, and migration/compatibility notes.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: For any multi-step refactor, migration, or cross-module task, contributors MUST create or adopt a dedicated recovery document under `ai-plan/public/<topic>/todos/` before making substantive code changes. Recovery documents MUST record the current phase, the active recovery point identifier, known risks, and the next recommended resume step so another contributor or subagent can continue the work safely.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/*/todos/**/* : When working from a tracked implementation plan, contributors MUST update the corresponding tracking document under `ai-plan/public/<topic>/todos/` in the same change. Updates MUST reflect completed work, newly discovered issues, validation results, and the next recommended recovery point. Tracking files are recovery entrypoints, not append-only changelogs, and MUST stay concise.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Commit messages MUST use Conventional Commits format: `<type>(<scope>): <summary>`. The commit `summary` MUST use simplified Chinese and briefly describe the main change. The commit `body` MUST use unordered list items, each starting with a verb such as `新增`、`修复`、`优化`、`更新`、`补充`、`重构`. Each commit body bullet MUST describe one independent change point. Keep technical terms in English when they are established project terms, such as `API`、`Model`、`System`.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: When a topic is fully complete, move the entire topic directory under `ai-plan/public/archive/<topic>/` and remove it from `ai-plan/public/README.md` in the same change.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/README.md : `ai-plan/public/README.md` MUST list only active topics. Do not add `ai-plan/public/archive/**` content to the default boot index. When a worktree-to-topic mapping changes or when a topic becomes active/inactive, contributors MUST update `ai-plan/public/README.md` in the same change.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Use `ai-plan/public/**` only for durable, handoff-safe task state. Put temporary notes, local experiments, or worktree-specific scratch recovery data under `ai-plan/private/`.
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/*/traces/**/* : Contributors MUST maintain a matching execution trace under `ai-plan/public/<topic>/traces/` for complex work. The trace should record the current date, key decisions, validation milestones, and the immediate next step. Update traces at each meaningful milestone before pausing or handing work off.
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/README.md : `ai-plan/public/README.md` MUST list only active topics. Do not add `ai-plan/public/archive/**` content to the default boot index. When a worktree-to-topic mapping changes or when a topic becomes active/inactive, contributors MUST update `ai-plan/public/README.md` in the same change.
Applied to files:
ai-plan/public/README.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/*/todos/**/* : When working from a tracked implementation plan, contributors MUST update the corresponding tracking document under `ai-plan/public/<topic>/todos/` in the same change. Updates MUST reflect completed work, newly discovered issues, validation results, and the next recommended recovery point. Tracking files are recovery entrypoints, not append-only changelogs, and MUST stay concise.
Applied to files:
ai-plan/public/README.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: When a topic is fully complete, move the entire topic directory under `ai-plan/public/archive/<topic>/` and remove it from `ai-plan/public/README.md` in the same change.
Applied to files:
ai-plan/public/README.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: Applies to ai-plan/public/*/traces/**/* : Contributors MUST maintain a matching execution trace under `ai-plan/public/<topic>/traces/` for complex work. The trace should record the current date, key decisions, validation milestones, and the immediate next step. Update traces at each meaningful milestone before pausing or handing work off.
Applied to files:
ai-plan/public/README.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: For any multi-step refactor, migration, or cross-module task, contributors MUST create or adopt a dedicated recovery document under `ai-plan/public/<topic>/todos/` before making substantive code changes. Recovery documents MUST record the current phase, the active recovery point identifier, known risks, and the next recommended resume step so another contributor or subagent can continue the work safely.
Applied to files:
ai-plan/public/README.md
📚 Learning: 2026-04-19T07:58:40.569Z
Learnt from: CR
Repo: GeWuYou/GFramework PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-04-19T07:58:40.569Z
Learning: If a task depends on observations from `ai-libs/**`, record the referenced path and conclusion in the active plan or trace when the work is multi-step or complex, or when an active tracking document already exists, rather than editing the third-party reference copy.
Applied to files:
ai-plan/public/README.md
🔇 Additional comments (1)
ai-plan/public/README.md (1)
28-32: 这两处索引更新方向正确，和本次 topic 激活目标一致。
coroutine-optimization的 Active Topic 条目及其 Worktree 映射都已补齐，结构清晰，可作为恢复入口使用。Based on learnings:
ai-plan/public/README.md在 worktree-to-topic 映射变化时必须在同一变更内更新。Also applies to: 54-57
- 移除了关于协程优化分支的文档条目 - 清理了已归档主题的相关工作树提示信息 - 更新了 SDK 使用说明以反映当前状态
Summary
Test Results
Details
Insights
build-and-test: Run #892
🎉 All tests passed!Slowest Tests
🎉 No failed tests in this run. | 🍂 No flaky tests in this run. Github Test Reporter by CTRF 💚 |
1 participant
Summary by CodeRabbit