Repository navigation
Conversation
…ount-batch-upstream-model-sync
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.
解决的问题与行为变化
关联记录与来源
管理员新功能提示
完整规则见贡献指南。新增管理员可见功能、菜单、页签或设置项时,必须在同一 PR 完成 ID 登记、标签接入和必要回归,不能留到 Release 发布后补录。
frontend/src/constants/newFeatureNotices.ts登记项(稳定且唯一):batchUpstreamWhitelist → account-batch-upstream-whitelist-v1。NewFeatureBadge展示位置:批量编辑 → 模型白名单区域 → 批量同步按钮旁(唯一入口)。复现与验收
协议、调度或传输改动补充(相关时填写)
完整 scope acceptance checklist
实际验证
UI 证据(四身份明确选择,不按 upload history 的最后四项;真实组件/CSS、虚构管理员/账号,离线 Axios adapter,不是后台联调):
before desktop — 1366×900
capture SHA
701612f6e9f7b697eb36397b9fb49bf7324e56a1。SHA256f1cb4bcb70a7a32953d51d64cca439eb3b6f63f3c83cad88754e6735117e35c3。before mobile — 390×844
capture SHA
701612f6e9f7b697eb36397b9fb49bf7324e56a1。SHA256f9a87753b7ed354776aaf9a6deed7021702b56ac87601164bcc1ddcf87fa12e4。after desktop — 1366×900
capture SHA
add606e964972ded3d6389790586c781c89a58c1;附件最初捕获于0867559e3e4c2883912bf682f52e2d066f1bd486,final-head recapture 与其 byte-identical,复用原附件,不冒称新上传。SHA2562ee3d26b5068cf045b386d7658c1e368e88479ddf8e216e17a89be4cda47f1c9。after mobile — 390×844
capture SHA
add606e964972ded3d6389790586c781c89a58c1。SHA25655c07738e045b3396b5366bb1b2378851049cdef697cb7222015bb5089ad3c4e。四附件关联正文后独立回读 body/body_html,并逐个匿名 GET 验证 HTTP200/精确 SHA256 与 ui/*-manifest.json 一致;记录于 independent/delivery-readback.json。远程 CI 的 remote-final-ui 截图是独立渲染产物(不同字体/运行环境字节),不与本地原生附件混淆。未重传附件。截图可见区域无凭据或真实用户数据;普通表单下方未完整入图,移动滚动/几何由独立 XHR oracle 另验。
兼容性与运行影响
文档与用户可见变化
中英文同步。新增 功能说明。完整证据在 /data/development/artifacts/account-batch-upstream-model-sync/;progress.json 记录当前 gate。截图不入源码。PR 合并、Release 和部署均未执行。
Agent 使用声明
gpt-6-astra,推理强度xhigh(实际 turn_context);fast 仅 requested,未证实 delivered。gpt-6.1-sol,推理强度未知(运行时未提供)。gpt-6.1-sol,推理强度未知(运行时未提供);本轮未改应用代码。gpt-6.1-sol,推理强度未知(运行时未提供);发现 P1/P2已由后续修复在源码层关闭,动态待CI。其协调者记录的后续 Codex 修复配置为gpt-6.1-sol/ultra/ fast 仅 requested;这不是原 gpt-6-astra/xhigh writer 配置,修复已发布至e18e9eb4,新头远程动态门待完成。提交前自查
四小时维护独立验收(2026-11-18,本轮修复已发布)
当前精确头
e18e9eb4fc6e07709d7e1671a78a918ac2053196。以上“当前head/最终head”表格均为add606e964旧checkpoint证据,不代表本新头。旧文中副作用/stale阻塞是已修复前的记录,以下为最新逐项状态:bbbc3955:fresh完整且read-only目录,避免structured401 auth/health/refresh写入;stale失败保留旧白名单。ad4cd137:真实SyncUpstreamModelMapping入口对AgentIdentity fail-closed,零任务/凭据写回归;旧默认同步兼容未改。普通合入production657bb38d。e18e9eb4:RED harness显式拒绝编译/setup/skip/panic/data-race等无效失败。远程 CI 历史 overlay 补修已发布
最新头
a7c06e639409a70c64d55977093db1e2592121ea。e18新头三项失败原始日志明确为历史RED混合源码缺失API,不是有效业务RED:Issue715/quality-live旧manifest callee与候选policy caller混合;config-switch旧token callee与候选read-only caller混合(原JSON artifact14406818407已读取,wrong package是validator表层)。补修只改三个workflow:历史checkout内匹配caller API/精确pin前helpercaller;保留原基线缺陷、全部命名断言/测试、packagevalidator,退出恢复candidate。生产/前端/测试断言无变动。父级diffcheck和独立静态review918-ci.md CLEAR。新头全部CI与RED/GREEN仍待,旧头失败不冒称新头失败或成功。新增独立审查Hermes/gpt-6.1-sol/推理强度未知,Codex同原thread sol/ultra,fast仅requested。