Repository navigation
说话人风险横幅按原因拆分,命名失败不再误报区分不准 - #283
Merged
Merged
Conversation
added 2 commits
October 30, 2026 17:24
Agent-Executor: codex-pi Agent-Model: gpt-6-luna Agent-Effort: xhigh Dispatch-Id: dlg-20261030-090333-c7c0cb Task-Id: VideoTranscriptAPI-20261030-02
Agent-Executor: codex-pi Agent-Model: gpt-6-luna Agent-Effort: xhigh Dispatch-Id: dlg-20261030-090333-c7c0cb Task-Id: VideoTranscriptAPI-20261030-02
Required Gate v2 — 状态面板当前状态:pass · 可合并 当前裁决: PR 累计主审轮(影子):
Gate 历史(v1;来源为持久化
|
| Run | Attempt | Head | 状态 | PR 累计主审轮(影子) | 收件人动作 |
|---|---|---|---|---|---|
| 41034666906 | 1 | 1147fcc |
pass |
1/5 · collecting |
可合并 |
历史行按 run_id + run_attempt 去重并只增不删;删除本评论后可由 gate_terminal 制品重建。
Advisory 未复核 · ocr-minimax这次没扫:评审额度已耗尽。这不是「扫过且干净」——本 PR 少了一层 advisory 扫描。 要不要管:不阻塞合并,无需处理。下个 run 会自动重跑。 查原因:→ job 日志 失败证据
status=budget_exhausted · verdict=unknown · reviewer=ocr-minimax · adapter_rc=20 · sig=OCR 失败链未走完,评审预算耗尽,未启动后续腿 |
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
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.
背景
生产推特任务 2115809881399922849(John Collison 与 @Sama 的两人对谈)的两个声音分组完全正确,但因为名字没被采用,页面显示「本集说话人区分可能不准」。现在只要
speaker_risk_flags非空,就会显示这一句横幅,把「命名失败」说成了「分组可能有问题」。改动
按 flag 的含义分别提示:
semantic_contradiction_detected/semantic_scan_unreliable/ 未知 flag:仍显示「本集说话人区分可能不准」(data-speaker-risk="segmentation")。low_confidence_cluster_dropped:改为显示「部分说话人姓名未识别」,英文为 "Some speaker names could not be identified"(data-speaker-risk="names_unresolved")。low_average_mapping_confidence:不显示横幅,因为它来自 LLM 自报的置信度,未经校准。flag 名称不变,API 字段保持兼容。浏览器夹具改为调用真实的
DialogRenderer;新增两条真实 Chromium 用例。AGENTS.md增加一行录屏层豁免,原因是录屏发布链路尚未接通(Refs #282)。验证
npm run test:browser:36 passed(执行器报告)。make test:退出码 0(执行器报告)。设计文档:分支
feat/vta-speaker-naming-261030下的docs/sessions/vta-speaker-naming-261030/design.md(卡 B)。🤖 Generated with Claude Code