Repository navigation
同步 gate-disposition caller 到 gate v2 模板八输入 (#167) - #182
Merged
Merged
Conversation
Agent-Executor: ocgo-bunny-pi Agent-Model: space-bunny-free Agent-Effort: high Dispatch-Id: dlg-20261006-042550-d50791 Task-Id: VideoTranscriptAPI-20261006-02
zj1123581321
marked this pull request as ready for review
October 6, 2026 04:29
Required Gate v2 — 状态面板当前状态：pass · 可合并 当前裁决： Gate 历史（v1；来源为持久化
|
| Run | Attempt | Head | 状态 | 收件人动作 |
|---|---|---|---|---|
| 37413851376 | 1 | 1e6e148 |
fail |
要修代码 |
| 37413966705 | 1 | 1e6e148 |
pass |
可合并 |
历史行按 run_id + run_attempt 去重并只增不删；删除本评论后可由 gate_terminal 制品重建。
This was referenced Oct 6, 2026
zj1123581321
added a commit
that referenced
this pull request
Oct 6, 2026
10/03-10/04 的证据类卡走了「直推分支存档、不开 PR」模式，内容从未落主干， 远端分支因 not_terminal 被回收器无限期跳过。按「有价值落主干、无价值清理」原则， 把其中仍有价值的证据文档 cherry-pick 落主干（docs/sessions/ 本就是主干惯例）。 来源分支（tip sha）： - 6fde3713 docs: SDK65 上线独立只读复核报告（Refs #166） - d3d08f37 docs: 脱敏私网地址与服务端绝对路径以过公开仓出站扫描（Refs #166） - 1b2db358 docs: SDK65 镜像上线与真实 CapsWriter 验收报告（Refs #166） - 3ef45588 docs: SDK65 部署前生产取证与无D3自动部署确认（Refs #166） - 772ed140 补SDK65下游独立审查结论 - 9aeb99c3 记录 CapsWriter wire 诊断结果 - 92ae9c9e 校准 #166 健康探针命令记录 - 9a3eadbb 更正 #166 样本与关联诊断证据 - 03aeb206 记录 #166 真实探针前提阻塞 - d8c6fe36 修订 #166 诊断：收窄归因至客户端已证边界、分段/时限降为未证实、探针契约入档并纠正墙钟 - 448533a0 诊断报告脱敏：内网 ASR 端点改用占位符（公开仓 pre-push 扫描） - b0317ebb 诊断 #166：CapsWriter 短音频 121 秒失败边界（只读报告+进度存档） - ce05349e 删除 AGENTS.md 中指向不存在的 docs/project-memory.md 的失效指针 - df958ec3 补 n305 生产只读复核结论 - e02e971d 记录 n305 部署 ff92a17 的生产验收证据（#147/#156/#159） - 22f0d819 记录音轨最终增量审查结论 - c1e1111c 记录音轨增量独立复验结论 - f0543cfe docs(review): 记录 PR164 音轨准入验收 - cc047b84 记录 PR 163 独立审查结论 - ef57bce5 记录 PR #162 配置诊断验收 压成单提交的原因：来源分支存在「先推原文、后补脱敏」的中间提交， cherry-pick 保真历史会把脱敏前的私网端点（内网 ASR 端点）重放进推送历史， 被 pre-push public-scan 正确拦截；压平后只推最终已脱敏状态。 vta-181-idle-timeout-261006 不落：诊断文档已随 #182 进主干，代码方案被 #192 取代。 落主干后对 13 个来源分支与 vta-181 走 abandon 归档，远端分支交回收器清理。 Agent-Executor: pi-lead Agent-Session: pi-lead-1791289146893-1158775 Co-authored-by: zj1123581321 <zj1123581321@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #167
范围
仅
.github/workflows/gate-disposition.yml一个文件（+8/-2）：on.workflow_dispatch.inputs补齐三个可选输入disposition/counterevidence_json/tracking_issue（required: false,type: string，描述照抄模板）。with:块新增三行${{ inputs.* }}转发。@__PINNED_GATE_SHA__占位说明）。非目标（有意保留差异）
uses: ...gate-v2-disposition.yml@v2不改（不引入 40-hex pin）。secrets: inherit不改（模板的 Silo 显式映射不在本卡范围）。gate_ref。验证
python3 -c "import yaml; yaml.safe_load(open('.github/workflows/gate-disposition.yml'))"通过。zlxlabs/gate@v2:templates/caller-gate-disposition.yml用 python yaml 解析后比较workflow_dispatch.inputs与with键集合，均一致（差集双向为空）。真实
workflow_dispatch调用留待合并后由主脑执行。