接入发布候选回执强制校验(09-06-release-gate-integrity)
这个提交包含在:
@@ -2,7 +2,7 @@
|
||||
"id": "release-gate-integrity",
|
||||
"name": "release-gate-integrity",
|
||||
"title": "部署门禁完整性与候选验收回执",
|
||||
"description": "G18在用覆盖和三处产品修复已本地验证;原四文件并发4/4、认证/OCR18/18通过。全量合同、WebKit、R1、独立及真实操作仍开放。",
|
||||
"description": "R1本地接入、125项定向测试及六项独立复核通过;生命周期52项补充通过,原3项超时保留且归因更正。按授权保存最终本地提交,等待同一clean候选一次完整门禁及独立授权后的公网义务。",
|
||||
"status": "in_progress",
|
||||
"dev_type": null,
|
||||
"scope": "release-gate",
|
||||
@@ -21,7 +21,7 @@
|
||||
"children": [],
|
||||
"parent": null,
|
||||
"relatedFiles": [],
|
||||
"notes": "2026-09-19 根据用户对重复全浏览器成本的反馈,中止budget-full-r1;后端4446与PG28通过保留,浏览器29通过/4中断/339未运行,回执FAIL/130,环境清理PASS。待Claude实际补丁复核,发布完整门禁延期,不再重跑无关测试。\n2026-09-19 预算并发修复已定向通过 PG28/单测526;待新完整候选与独立审查,旧r6为历史输入。\n2026-09-19 用户独立核实确认4437/r6时序及累计diff基线,并报告当前采购测试75 passed/EXIT=0、SHA一致;数量与证据归属争议闭合。完整独立业务review、发布边界及两条例外保持。\n2026-09-19 用户转述局部审查已核对:UTC/北京时间混用及累计diff误作运行后diff;r6实际在P10之后,4437准确,1162源码快照条目与当前一致。证据review-provenance-20260919.json,完整独立review仍PENDING,原证据不改。\n2026-09-19 g20-full-r6:4437后端通过/1原跳过,372本地浏览器全过;PARTIAL仅dirty_candidate,独立PENDING/无部署,旧registry保护例外保留且无新增漂移。当前余额见implement顶部。\n2026-09-18 G19分层验收已批准并本地实施验证,74+7合成检查和2条冻结保护通过;公网12义务/完整门禁/WebKit/R1/独立及真实事实保持开放。\n2026-09-18 G18:QA39、产品131、并发4/4、认证/OCR18/18,33路由项与R108通过;G18时点发现64/363;G19最新发现见g19-discovery/summary.json,旧完整full-r2仍失败。候选与余项见local-coverage-g18-20260918。无提交部署,独立PENDING。\n2026-09-18 G16/G17:普通 full-r2 65/359仍失败;14原失败及2串行缺失已有定向通过,1WebKit/2冻结差旅保留。当前发现64/358,有临时SHA采集告警;QA/治理/保护与增量候选见 full-gates-followup-20260918。整体in_progress、独立PENDING,六组余项见implement顶部,无提交部署/外部操作。\n2026-09-18 G12/G13本地收口,G14真实PWA通过但WebKit1条未验;原58现53重验/4排除/1未验,原历史不改。G15复核及外部事实清单与新候选在retained-gates-closeout-20260917;普通full-local/AC7完整/R1和独立PENDING,不提交部署或真实操作。\n2026-09-17 W8本地对账:四处迁移状态谓词修复已随b87cc55发布;该事实仅闭合追加预检阶段,不代表R1普通完整门禁、阶段B合同用例或58条诊断观测已通过。R1/阶段B继续原冻结,先按保留在用场景分类再另定限定批次,不盲修待精简旧测试。 原回执从主副本接回,见implement顶部;本轮无新的远端/提交发布,原验收未补勾。\n2026-09-07 §10已实施并完成一次环境有效的全套诊断,增量待用户独立复核。原21文件加6个QA环境/测试文件,共27文件;本轮产品源码和业务spec零改动,51项针对性验证通过。前三次启动在环境前置拒绝,资源已核对清理;修复跨user namespace读取父namespace的EACCES,改由父runner经本轮Unix IPC即时实测,不降级。第四次环境PASS、源码前后不变:65文件275项,199 passed/54 failed/4 timedOut/18 skipped,58条观测涉及36文件,不是独立产品缺陷计数;诊断仍PARTIAL/2。服务端193文件1692项通过,workflow场景8两个来源仍失败。R102 6/6通过;合同仍卡旧更多,续约/归档未执行;PWA在serviceWorker.ready超时且该失败无trace附件。诊断67分03秒不是普通全绿成本。旧207撤销决策资格但保留原件;阶段1、阶段B、场景8、经理缺口和R1均未扩大执行。无提交/push/归档/部署/生产操作,整体任务未完成。",
|
||||
"notes": "2026-09-19 R1定向125通过、另外两份46通过、生命周期52补充通过;原组2 exit1及3次超时保留,新增require不在其执行片段内。六项代码独立复核PASS,无理由合并保护或增预算。允许本地提交,最终完整门禁尚未执行;不具备发布资格。\n2026-09-19 根据用户对重复全浏览器成本的反馈,中止budget-full-r1;后端4446与PG28通过保留,浏览器29通过/4中断/339未运行,回执FAIL/130,环境清理PASS。待Claude实际补丁复核,发布完整门禁延期,不再重跑无关测试。\n2026-09-19 预算并发修复已定向通过 PG28/单测526;待新完整候选与独立审查,旧r6为历史输入。\n2026-09-19 用户独立核实确认4437/r6时序及累计diff基线,并报告当前采购测试75 passed/EXIT=0、SHA一致;数量与证据归属争议闭合。完整独立业务review、发布边界及两条例外保持。\n2026-09-19 用户转述局部审查已核对:UTC/北京时间混用及累计diff误作运行后diff;r6实际在P10之后,4437准确,1162源码快照条目与当前一致。证据review-provenance-20260919.json,完整独立review仍PENDING,原证据不改。\n2026-09-19 g20-full-r6:4437后端通过/1原跳过,372本地浏览器全过;PARTIAL仅dirty_candidate,独立PENDING/无部署,旧registry保护例外保留且无新增漂移。当前余额见implement顶部。\n2026-09-18 G19分层验收已批准并本地实施验证,74+7合成检查和2条冻结保护通过;公网12义务/完整门禁/WebKit/R1/独立及真实事实保持开放。\n2026-09-18 G18:QA39、产品131、并发4/4、认证/OCR18/18,33路由项与R108通过;G18时点发现64/363;G19最新发现见g19-discovery/summary.json,旧完整full-r2仍失败。候选与余项见local-coverage-g18-20260918。无提交部署,独立PENDING。\n2026-09-18 G16/G17:普通 full-r2 65/359仍失败;14原失败及2串行缺失已有定向通过,1WebKit/2冻结差旅保留。当前发现64/358,有临时SHA采集告警;QA/治理/保护与增量候选见 full-gates-followup-20260918。整体in_progress、独立PENDING,六组余项见implement顶部,无提交部署/外部操作。\n2026-09-18 G12/G13本地收口,G14真实PWA通过但WebKit1条未验;原58现53重验/4排除/1未验,原历史不改。G15复核及外部事实清单与新候选在retained-gates-closeout-20260917;普通full-local/AC7完整/R1和独立PENDING,不提交部署或真实操作。\n2026-09-17 W8本地对账:四处迁移状态谓词修复已随b87cc55发布;该事实仅闭合追加预检阶段,不代表R1普通完整门禁、阶段B合同用例或58条诊断观测已通过。R1/阶段B继续原冻结,先按保留在用场景分类再另定限定批次,不盲修待精简旧测试。 原回执从主副本接回,见implement顶部;本轮无新的远端/提交发布,原验收未补勾。\n2026-09-07 §10已实施并完成一次环境有效的全套诊断,增量待用户独立复核。原21文件加6个QA环境/测试文件,共27文件;本轮产品源码和业务spec零改动,51项针对性验证通过。前三次启动在环境前置拒绝,资源已核对清理;修复跨user namespace读取父namespace的EACCES,改由父runner经本轮Unix IPC即时实测,不降级。第四次环境PASS、源码前后不变:65文件275项,199 passed/54 failed/4 timedOut/18 skipped,58条观测涉及36文件,不是独立产品缺陷计数;诊断仍PARTIAL/2。服务端193文件1692项通过,workflow场景8两个来源仍失败。R102 6/6通过;合同仍卡旧更多,续约/归档未执行;PWA在serviceWorker.ready超时且该失败无trace附件。诊断67分03秒不是普通全绿成本。旧207撤销决策资格但保留原件;阶段1、阶段B、场景8、经理缺口和R1均未扩大执行。无提交/push/归档/部署/生产操作,整体任务未完成。",
|
||||
"meta": {
|
||||
"archiveOutputProtection": "implemented_pending_independent_review",
|
||||
"registeredLocalEvidenceVerified": 14,
|
||||
@@ -150,7 +150,7 @@
|
||||
"remediationStatus": "LOCAL_VERIFIED_INDEPENDENT_REVIEWED"
|
||||
},
|
||||
"releasePreparation": {
|
||||
"status": "LOCAL_COMMIT_AUTHORIZED_RELEASE_PENDING",
|
||||
"status": "LOCAL_COMMITS_COMPLETE_R1_PLAN_READY",
|
||||
"executor": "main Codex session",
|
||||
"request": "artifacts/qa-governance/release-preparation-claude-request-20260919.md",
|
||||
"scope": "read-only candidate inventory and actionable release preparation",
|
||||
@@ -170,6 +170,50 @@
|
||||
"commitEvidence": "artifacts/qa-governance/local-commits-20260919",
|
||||
"firstLocalCommit": "729d90576f25ba658656508af1af32a179aa7057",
|
||||
"commitResultReceipt": "artifacts/qa-governance/local-commits-20260919/result.json"
|
||||
},
|
||||
"r1IntegrationPlan": {
|
||||
"status": "LOCAL_REVIEWED_FINAL_FULL_GATE_PENDING",
|
||||
"planningApproved": true,
|
||||
"implementationApproved": true,
|
||||
"enforcementEnabled": true,
|
||||
"baselineCommit": "1f8d5b658a9fcae15be192af8c82ab557f88a046",
|
||||
"designSection": "R1 接入方案(2026-09-19,已批准本地实施)",
|
||||
"executionFiles": [
|
||||
"scripts/qa/release-gate-result.mjs",
|
||||
"scripts/qa/run-release-gate.sh",
|
||||
"deploy/trialrun/production-identity-bootstrap.mjs",
|
||||
"deploy/trialrun/deploy-existing.sh",
|
||||
"deploy/trialrun/deploy.sh"
|
||||
],
|
||||
"testExecutor": "Claude independent session",
|
||||
"testsRun": true,
|
||||
"pushAuthorized": false,
|
||||
"deploymentAuthorized": false,
|
||||
"approval": "用户确认本地R1接入与先实施再最终一次完整门禁的顺序;不含推送或部署",
|
||||
"enforcementScope": "local uncommitted code only; no real deployment executed",
|
||||
"localEnforcementImplemented": true,
|
||||
"testStatus": "SCOPED_PASS_WITH_RECORDED_PRIOR_TIMEOUT",
|
||||
"independentReview": "PASS_6_POINTS_CAUSE_CORRECTION_RECEIVED",
|
||||
"deploymentEligible": false,
|
||||
"evidenceDirectory": "artifacts/qa-governance/r1-enforcement-20260919",
|
||||
"handoff": "artifacts/qa-governance/r1-enforcement-20260919/claude-request.md",
|
||||
"reviewReception": "artifacts/qa-governance/r1-enforcement-20260919/review-reception.json",
|
||||
"nextHandoff": "artifacts/qa-governance/r1-enforcement-20260919/final-gate-claude-request.md",
|
||||
"f1": {
|
||||
"discoveryStatus": "THREE_TIMEOUTS_CONFIRMED",
|
||||
"attribution": "R1_DIRECT_CAUSE_DISPROVED",
|
||||
"remediationStatus": "NO_CODE_FIX_INDICATED_SCOPED_REVALIDATION_PASS",
|
||||
"historicalRootCause": "UNDETERMINED",
|
||||
"supplementalRun": {
|
||||
"tests": 52,
|
||||
"passed": 52,
|
||||
"exitCode": 0,
|
||||
"budgetMs": 5000
|
||||
},
|
||||
"productionChecksPreserved": true
|
||||
},
|
||||
"diagnosticReception": "artifacts/qa-governance/r1-enforcement-20260919/f1-triage-20260919/diagnostic-reception.json",
|
||||
"localCommitEvidence": "artifacts/qa-governance/r1-enforcement-20260919/local-commit/result.json"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
在新工单中引用
屏蔽一个用户