Skip to content

feat(ISSUE-263): W4-C2 dispatch 白名单与 check run 写回 (#283) - #311

Closed
cloudbrid-agent[bot] wants to merge 1 commit into
mainfrom
feat/issue263-w4c2-dispatch-writeback
Closed

feat(ISSUE-263): W4-C2 dispatch 白名单与 check run 写回 (#283)#311
cloudbrid-agent[bot] wants to merge 1 commit into
mainfrom
feat/issue263-w4c2-dispatch-writeback

Conversation

@cloudbrid-agent

@cloudbrid-agent cloudbrid-agent Bot commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

ADR

  • ADR-0067 (spec 阶段攻击面)
  • ADR-0082 (红队守门制度)
  • ADR-0061 / ADR-0081 (g060 锁定)

W4-C2(.github#283,INV-02/AC-12/AC-14):
- .github/workflows/conductor.yml:T5/T6 前置重新断言——不信任 dispatch 载荷,
  suite-ready 谓词 + 三元组 survived 记录校验 + needs-human 不可直跳 wave-planned
  全部由 conductor 侧独立验证;T6 路由成功后经 repository_dispatch 触发 adversary
  侧 check run 写回(adversary-survived 事件)
- 注:conductor.yml 为 workflow 文件,当前 cloudbrid-agent App 无 workflows
  权限,本次以 PR 形式提交(待权限到位后合并生效);check_run_writeback.py 等
  pipeline 代码已推至 CI-Workflows PR #88Closes #283
Relates to #284
@cloudbrid-agent
cloudbrid-agent Bot enabled auto-merge (squash) August 23, 2026 10:51
auto-merge was automatically disabled August 23, 2026 12:42

Pull request was closed

@randypanding randypanding reopened this Aug 23, 2026
randypanding pushed a commit that referenced this pull request Aug 23, 2026
) (#312)

W4-C3(.github#284,AC-14/AC-19,ADR-0082):
- .github/workflows/adversary-gate.yml:specs/** 路径 PR 必须含 adversary check
  (漏配/摘除/跳过即红,负向断言);开发路径豁免谓词由 diff 路径集确定性派生
  (pipeline/adversary/expected_skip.py,禁人工打标,AC-14);App 令牌写回
  check run(checks:write,INV-02)
- docs/w4c3-adversary-gate-reference.md:adversary-gate.yml 完整实现参考副本
  (workflow 文件因当前 cloudbrid-agent App 无 workflows 权限待补推)
- 注:main-protection.json / org-required-workflows.json 的 adversary check context
  登记已在 W4-C2 PR #311 推送(adversary check 必须列入 required_status_checks
  才有意义);本 PR 聚焦 gate workflow 实现与参考。

Closes #284
Relates to #283

Co-authored-by: cloudbrid-agent[bot] <318150333+cloudbrid-agent[bot]@users.noreply.github.com>
@randypanding randypanding reopened this Aug 23, 2026
@randypanding randypanding reopened this Aug 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant