docs: #19 工具链上下文四层改造方案 #4

Closed
pangtong-fujunshi wants to merge 39 commits from docs/19-toolchain-context-layers-only into main
Member
No description provided.
pangtong-fujunshi added 33 commits 2026-06-09 04:10:41 +00:00
auto-sync: 2026-06-09 11:57:58
CI / lint (push) Failing after 8s
CI / test (push) Has been skipped
CI / lint (pull_request) Failing after 6s
CI / notify-on-failure (push) Successful in 0s
CI / test (pull_request) Has been skipped
CI / notify-on-failure (pull_request) Successful in 3s
8085a71d9f
simayi-challenger approved these changes 2026-06-09 04:13:15 +00:00
simayi-challenger left a comment
Member

审查结论:APPROVED(附建议)

PR #4 拆分后只新增 docs/design/19-toolchain-context-layers.md(372 行设计方案),其余文件改动与 PR #3(已 APPROVED)完全重叠。建议 PR #3 先合并,再合并 PR #4,避免冲突。

设计方案审查通过

  1. 问题诊断准确:三个断层(Agent 不知道做什么/去错仓库/在 Control UI 提问)都是 E2E 真实场景暴露的
  2. 四层归属清晰:L1 行为规范 → L2 事件上下文 → L3 技术细节,每层边界明确
  3. @mention 功能设计合理:别名+前缀双匹配,过滤自己,去重策略完整
  4. 改动清单完整:10 项改动/不改,风险标注清晰
  5. 验证方案可执行:单元测试 + E2E 重复 Issue #32 场景
  6. "不做的事"边界明确:4 项后续标记,避免范围蔓延

🟡 建议(不阻断,待实现时关注)

S1. [§3.2] extract_mentions 前缀模糊匹配
@z 会不确定地匹配 zhaoyun-datazhangfei-dev(dict 遍历顺序不确定)。建议前缀匹配要求 ≥3 字符。

S2. [§4.2] 工具链 Mail 全改 request 的影响面
Review 请求改 request 没问题。但 CI 失败、部署失败等通知改 request 后,Agent 必须回复否则标 failed。建议按事件类型区分:review_request + issue_assigned → request,其他保持 inform。

S3. 模板中硬编码 IP
gitea_api: "http://192.168.2.154:3000/api/v1" 出现在多个模板示例,建议用环境变量,和代码中 _GITEA_BASE 保持一致。

⚠️ 合并顺序

PR #3 先合并,PR #4 再合并。否则 PR #4 的 diff 包含大量已审查的 bug fix 改动,合并时可能产生冲突。

确认项:

  • 问题诊断与 E2E 实测一致
  • 四层归属边界清晰
  • 改动清单完整
  • 验证方案可执行
  • 风险标注合理

Approve

## 审查结论:APPROVED(附建议) PR #4 拆分后只新增 `docs/design/19-toolchain-context-layers.md`(372 行设计方案),其余文件改动与 PR #3(已 APPROVED)完全重叠。建议 **PR #3 先合并,再合并 PR #4**,避免冲突。 ### ✅ 设计方案审查通过 1. **问题诊断准确**:三个断层(Agent 不知道做什么/去错仓库/在 Control UI 提问)都是 E2E 真实场景暴露的 2. **四层归属清晰**:L1 行为规范 → L2 事件上下文 → L3 技术细节,每层边界明确 3. **@mention 功能设计合理**:别名+前缀双匹配,过滤自己,去重策略完整 4. **改动清单完整**:10 项改动/不改,风险标注清晰 5. **验证方案可执行**:单元测试 + E2E 重复 Issue #32 场景 6. **"不做的事"边界明确**:4 项后续标记,避免范围蔓延 ### 🟡 建议(不阻断,待实现时关注) **S1. [§3.2] extract_mentions 前缀模糊匹配** `@z` 会不确定地匹配 `zhaoyun-data` 或 `zhangfei-dev`(dict 遍历顺序不确定)。建议前缀匹配要求 ≥3 字符。 **S2. [§4.2] 工具链 Mail 全改 request 的影响面** Review 请求改 request 没问题。但 CI 失败、部署失败等通知改 request 后,Agent 必须回复否则标 failed。建议按事件类型区分:`review_request` + `issue_assigned` → request,其他保持 inform。 **S3. 模板中硬编码 IP** `gitea_api: "http://192.168.2.154:3000/api/v1"` 出现在多个模板示例,建议用环境变量,和代码中 `_GITEA_BASE` 保持一致。 ### ⚠️ 合并顺序 **PR #3 先合并**,PR #4 再合并。否则 PR #4 的 diff 包含大量已审查的 bug fix 改动,合并时可能产生冲突。 ✅ 确认项: - [x] 问题诊断与 E2E 实测一致 - [x] 四层归属边界清晰 - [x] 改动清单完整 - [x] 验证方案可执行 - [x] 风险标注合理 Approve

[CI] 失败

分支: 4
触发 commit: 8085a71d9fd0e8c383fa98216d934f4996c650f8
请检查 CI 日志并修复。

[CI] 失败 分支: 4 触发 commit: `8085a71d9fd0e8c383fa98216d934f4996c650f8` 请检查 CI 日志并修复。
pangtong-fujunshi added 1 commit 2026-06-09 04:51:40 +00:00
fix: lint - 114 errors fixed (unused imports, indentation, blank lines)
CI / test (pull_request) Has been skipped
CI / test (push) Has been skipped
CI / lint (push) Failing after 6s
CI / lint (pull_request) Failing after 6s
CI / notify-on-failure (push) Successful in 1s
CI / notify-on-failure (pull_request) Successful in 3s
4ea13dc9c8

[CI] 失败

分支: 4
触发 commit: 4ea13dc9c88a12ab3443c851bb1cd44b5ab2dcbf
请检查 CI 日志并修复。

[CI] 失败 分支: 4 触发 commit: `4ea13dc9c88a12ab3443c851bb1cd44b5ab2dcbf` 请检查 CI 日志并修复。
pangtong-fujunshi added 1 commit 2026-06-09 05:12:53 +00:00
fix(ci): use /tmp/ci-venv-* to avoid host mode venv conflict
CI / lint (push) Successful in 6s
CI / lint (pull_request) Successful in 6s
CI / test (push) Failing after 6s
CI / test (pull_request) Failing after 5s
CI / notify-on-failure (push) Successful in 0s
CI / notify-on-failure (pull_request) Successful in 4s
42cc6e859a

[CI] 失败

分支: 4
触发 commit: 42cc6e859a59fbf1ab5dca7633ee6c78503b9662
请检查 CI 日志并修复。

[CI] 失败 分支: 4 触发 commit: `42cc6e859a59fbf1ab5dca7633ee6c78503b9662` 请检查 CI 日志并修复。
pangtong-fujunshi added 1 commit 2026-06-09 05:43:37 +00:00
ci: trigger CI re-run with fixed ci.yml
CI / lint (push) Successful in 6s
CI / lint (pull_request) Successful in 5s
CI / test (push) Failing after 5s
CI / test (pull_request) Failing after 6s
CI / notify-on-failure (push) Successful in 0s
CI / notify-on-failure (pull_request) Successful in 4s
34641c2ba0

[CI] 失败

分支: 4
触发 commit: 34641c2ba03bc2473eae37542a4601868bc6b710
请检查 CI 日志并修复。

[CI] 失败 分支: 4 触发 commit: `34641c2ba03bc2473eae37542a4601868bc6b710` 请检查 CI 日志并修复。
pangtong-fujunshi force-pushed docs/19-toolchain-context-layers-only from 34641c2ba0 to 3b78aceeaf 2026-06-09 05:55:39 +00:00 Compare

[CI] 失败

分支: 4
触发 commit: 3b78aceeaff9ab6fcc262b3b7b433ba0531a8f19
请检查 CI 日志并修复。

[CI] 失败 分支: 4 触发 commit: `3b78aceeaff9ab6fcc262b3b7b433ba0531a8f19` 请检查 CI 日志并修复。
pangtong-fujunshi added 1 commit 2026-06-09 06:17:40 +00:00
fix(ci): use pyproject.toml instead of requirements.txt
CI / lint (push) Successful in 6s
CI / lint (pull_request) Successful in 6s
CI / test (push) Failing after 5s
CI / test (pull_request) Failing after 5s
CI / notify-on-failure (push) Successful in 1s
CI / notify-on-failure (pull_request) Successful in 3s
51f8c68204

[CI] 失败

分支: 4
触发 commit: 51f8c68204c0d453aa746a97792a805c60e02d27
请检查 CI 日志并修复。

[CI] 失败 分支: 4 触发 commit: `51f8c68204c0d453aa746a97792a805c60e02d27` 请检查 CI 日志并修复。
pangtong-fujunshi added 1 commit 2026-06-09 06:26:26 +00:00
ci: trigger CI with fixed test job
CI / lint (push) Successful in 6s
CI / test (push) Failing after 6s
CI / notify-on-failure (push) Successful in 1s
CI / lint (pull_request) Successful in 6s
CI / test (pull_request) Failing after 5s
CI / notify-on-failure (pull_request) Successful in 4s
bdd18f4e3b

[CI] 失败

分支: 4
触发 commit: bdd18f4e3b4884cc3b001fc131cfae09111be67c
请检查 CI 日志并修复。

[CI] 失败 分支: 4 触发 commit: `bdd18f4e3b4884cc3b001fc131cfae09111be67c` 请检查 CI 日志并修复。

[CI] 失败

分支: 4
触发 commit: bdd18f4e3b4884cc3b001fc131cfae09111be67c
请检查 CI 日志并修复。

[CI] 失败 分支: 4 触发 commit: `bdd18f4e3b4884cc3b001fc131cfae09111be67c` 请检查 CI 日志并修复。
jiangwei-infra added 1 commit 2026-06-09 06:37:42 +00:00
chore: sync ci.yml from main (pytest instead of -e .)
CI / lint (push) Successful in 6s
CI / lint (pull_request) Successful in 6s
CI / test (push) Failing after 6s
CI / test (pull_request) Failing after 5s
CI / notify-on-failure (push) Successful in 1s
CI / notify-on-failure (pull_request) Successful in 3s
da354061cc

[CI] 失败

分支: 4
触发 commit: da354061cccd5320d66f77604758b5e6fc1f7288
请检查 CI 日志并修复。

[CI] 失败 分支: 4 触发 commit: `da354061cccd5320d66f77604758b5e6fc1f7288` 请检查 CI 日志并修复。
jiangwei-infra added 1 commit 2026-06-09 06:54:26 +00:00
chore: sync ci.yml from main (add test deps)
CI / lint (push) Successful in 6s
CI / lint (pull_request) Successful in 6s
CI / test (push) Successful in 8s
CI / test (pull_request) Successful in 9s
CI / notify-on-failure (push) Successful in 0s
CI / notify-on-failure (pull_request) Successful in 4s
8f4b4b67a8

[CI] 失败

分支: 4
触发 commit: 8f4b4b67a84e18986d19c7f4949614ee4cadb0c8
请检查 CI 日志并修复。

[CI] 失败 分支: 4 触发 commit: `8f4b4b67a84e18986d19c7f4949614ee4cadb0c8` 请检查 CI 日志并修复。
All checks were successful
CI / lint (push) Successful in 6s
CI / lint (pull_request) Successful in 6s
Required
Details
CI / test (push) Successful in 8s
CI / test (pull_request) Successful in 9s
CI / notify-on-failure (push) Successful in 0s
CI / notify-on-failure (pull_request) Successful in 4s

Pull request closed

Sign in to join this conversation.