Commit Graph

11 Commits

Author SHA1 Message Date
lanrtop
1e3989d0d7 feat(delivery/mcp): get_delivery_status 支持按 pr_number/branch 查询,结论绑定 Gitea head SHA(使者回传 #203)
All checks were successful
Push & PR Check / check (push) Successful in 1m0s
Push & PR Check / check (pull_request) Successful in 1m2s
Enterprise 2026-10-03 实测:为避开主工作区里其他会话的在制品,在独立 worktree
分支上开 PR 交付时,get_delivery_status 只读主工作区当前分支,返回「当前分支没有
开放 PR」、CI 停在主工作区 HEAD,传 pr_number 也被忽略,只能用 git ls-remote 与
get_ci_status(commit_sha) 兜底。

- MCP schema 新增可选 pr_number(优先)与 branch;都不给时保持原行为
- pr_number:GET /pulls/{n} 取 head 分支与 head SHA,CI 与 review 均绑定该 PR;
  PR 不存在(404)返回 not_found,与 Gitea 不可达(unavailable)区分;
  同时传 branch 且与 PR head 分支不一致时以 pr_number 为准并在 detail 提示
- branch:匹配该分支的开放 PR 并以其 head SHA 查 CI;无开放 PR 时取 Gitea 上
  该分支 head SHA;远端分支不存在时 CI 为 unknown
- 顶层新增 target(mode/pr_number/branch/head_sha/source/detail),
  pull_request.data 增 head_sha;git 字段仍反映主工作区,既有字段兼容
- 取值校验在能力本体 DeliveryQuery 单点实现,MCP 只解析 JSON 类型;显式给出的
  非法值直接报错,不静默回退主工作区
- Gitea 读取拆为本地/PR/分支三种目标,凭证存储注入以便合成 Gitea 测试;
  merge_pull_request 门禁代码未改
- lian-jing skill 第 6 条改为 get_delivery_status(project_id, pr_number),
  base-onboarding 1.8.0→1.9.0(BASE_ONBOARDING_PACK_VERSION、模板
  capability-packs.json、TEMPLATE_FINGERPRINTS);Codex 插件 skill 同步
- 契约说明同步 docs/ai-context/project-context.yaml;蓝图 P3-F 标 ✅

Feature-Confirmed: true
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-03 06:22:09 +09:00
lanrtop
d8ba9dbf40 docs(blueprint/delivery): 立卡 P3-F get_delivery_status 按 PR/分支查询(使者回传 #203)
Enterprise 2026-10-03 实测:在独立 worktree 分支开 PR 交付时,get_delivery_status
只读主工作区当前分支,PR/CI 结论与目标 PR 脱节。本卡开始执行,标 🔵。

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-03 06:09:25 +09:00
lanrtop
f04cc8d43d docs(blueprint/project-capability): 记录 P3 验收结果
All checks were successful
Push & PR Check / check (push) Successful in 59s
记录隔离镜像切换与 production 双证据,并启动收益观测。

Rules-Applied: R13
2026-09-23 13:07:16 +09:00
lanrtop
dbc1b068ab fix(delivery): avoid false deployed timestamp
All checks were successful
Push & PR Check / check (push) Successful in 59s
Push & PR Check / check (pull_request) Successful in 1m0s
Rules-Applied: R07,R13
2026-09-23 12:09:38 +09:00
lanrtop
8bc33aaab9 fix(delivery): distinguish skipped production deploy
All checks were successful
Push & PR Check / check (push) Successful in 1m18s
Push & PR Check / check (pull_request) Successful in 58s
2026-09-23 11:08:10 +09:00
lanrtop
02b9f1ec36 feat(delivery): observe production revision with dual evidence
Read project-owned production profile, verify Gitea deploy context and public version probe, and surface explicit degraded states.

Feature-Confirmed: true
2026-09-23 10:37:07 +09:00
lanrtop
c9e92f7af4 chore(blueprint): 收口 Agent PR 合并门禁
All checks were successful
Push & PR Check / check (push) Successful in 1m20s
记录 PR #14 的真实 SHA 绑定合并与交付状态回读证据,并写入 M 级任务复盘。

Rules-Applied: R03,R13
2026-09-22 21:23:01 +09:00
lanrtop
b6d7490254 chore(onboarding): 完成炼境自身 Codex 接入
All checks were successful
Push & PR Check / check (push) Successful in 1m18s
Push & PR Check / check (pull_request) Successful in 58s
建立 canonical project context、Codex MCP 配置、项目级炼境 skill 与能力包版本记录,并补齐蓝图任务和复盘证据。

Rules-Applied: R03,R10,R13
2026-09-22 21:10:42 +09:00
lanrtop
0141b8b09a feat(delivery/gitea): 归一化 Gitea 部署状态信号
All checks were successful
Push & PR Check / check (push) Successful in 1m4s
Push & PR Check / check (pull_request) Successful in 59s
保留目标 SHA、context、时间与跳转证据,按精确 context 提取部署结果,并修正 Gitea 1.22 skipped job 被编码为 success 的误判。同步落账 production 只读双证据方案与 P3-A 完成状态。

Rules-Applied: R07,R10,R13

Feature-Confirmed: true
2026-09-22 19:54:43 +09:00
lanrtop
9ab9dc4f71 docs(blueprint): reconcile capability task status
All checks were successful
Push & PR Check / check (push) Successful in 1m21s
Mark the canonical context task complete from verified P2 evidence and retain the latest flywheel snapshot.

Rules-Applied: R09,R13
2026-09-22 10:46:03 +09:00
lanrtop
383b5b35d7 feat(delivery): add project delivery status
All checks were successful
Push & PR Check / check (push) Successful in 1m0s
Push & PR Check / check (pull_request) Successful in 58s
Feature-Confirmed: true
2026-09-21 15:16:40 +09:00