docs: 跟踪 Artificer Git identity 修复
This commit is contained in:
@@ -26,3 +26,19 @@
|
||||
## R2 [in_progress]
|
||||
|
||||
解决 [AgentRun #335](https://github.com/pikasTech/agentrun/issues/335):修复 Artificer 同 session follow-up 丢失 AipodSpec primary workspace、resource bundle 和 GitHub tool credential 的退化;只修既有继承路径,不新增合同、租约、围栏、fallback 或第二 credential authority,恢复后由 Artificer 接回原业务任务,完成任务后将详细报告写入[任务报告](./details/artificer-runtime-capabilities/R2_Task_Report.md)。
|
||||
|
||||
## R3 [in_progress]
|
||||
|
||||
解决 [AgentRun #337](https://github.com/pikasTech/agentrun/issues/337):由 Artificer owning YAML 的既有 Aipod/runner 启动装配统一提供 Git author/committer identity,使全新 task 与同 session resume/new-turn 均无需任务内 git config 即可提交;只做最小必要修复,不新增第二 authority、合同、租约、安全机制、围栏或 monitor 支线,完成任务后将详细报告写入[任务报告](./details/artificer-runtime-capabilities/R3_Task_Report.md)。
|
||||
|
||||
### R3.1 [in_progress]
|
||||
|
||||
调查 config/aipods/artificer.yaml、Aipod render 与 runner 启动路径,确认单一 identity owner,并用两个既有失败 task 和 #335 resume canary 建立初始/续跑复现证据,完成任务后将详细报告写入[任务报告](./details/artificer-runtime-capabilities/R3.1_Task_Report.md)。
|
||||
|
||||
### R3.2
|
||||
|
||||
由原生子代理在独立 AgentRun v0.2 worktree 实现最小 YAML-first identity 装配与定向测试,覆盖初始 runner 和同 session 新 turn;Artificer 不递归修自己,完成任务后将详细报告写入[任务报告](./details/artificer-runtime-capabilities/R3.2_Task_Report.md)。
|
||||
|
||||
### R3.3
|
||||
|
||||
主代理 review/合并后只观察自动 CI/CD;以新 task 直接 commit、同 session send 直接 commit 两个 canary 验收,不使用 task-local git config 或人工发布,完成任务后将详细报告写入[任务报告](./details/artificer-runtime-capabilities/R3.3_Task_Report.md)。
|
||||
|
||||
Reference in New Issue
Block a user