Repository navigation
test: independent coverage floors for publication and rollback boundaries - #284
Conversation
|
Confirmed blocker at head The test-system work stays separate. A newly authorized minimal runtime follow-up will close the descriptor before failure cleanup, retain safe-path/device/inode verification before unlink, refuse to delete a substituted path, and preserve the original error. This PR remains blocked until that separate repair and complete combined CI pass. PR283 has now merged; no parser-v3/product decision is included. Minimal reproduction on a provisioned Windows checkout: |
|
Pre-validating the planned combined tree at All original #284 files/strong safety assertions are preserved byte-for-byte, including |
|
The original Windows safety regression now has direct passing evidence on combined head |
Refs #277. Keep the separately authorized minimal runtime repair distinct from the coverage tests: close the owned descriptor before failure cleanup, retain original errors, and never delete an unverified or replaced checkpoint. Independent review and all 12 applicable checks passed at 33c9f00. Original #284 Windows safety regression also passed on its intermediate combined tree; #277 remains open for the final isolated tests-only PR and post-merge checks.
|
Final isolated head After latest main/head/reviews/checks and the exact 13-path no-runtime delta were reverified, normal squash merge is |
|
最终合后验收已完成。main Python 3.13 合后证据:3478 passed,总体覆盖 94.51%,原总体90及三个90/88/84门槛保持,新增七项独立门槛全部通过(10项总计);真实构建 wheel、来源审计和离线安装 CLI/skills 双格式验收均成功。Windows 原始零写入安全断言 Python 3.11 最后于 17:54 UTC 成功(3462 passed);此前较慢不据此宣称设备故障。nightly/manual job 按普通 push 事件策略 skipped,不冒充已执行;本项按已确认的 focus/覆盖门禁范围验收;#286 输入解析变更另需该补充验收。相关 issue 将在本回执后显式完成。#280 仍开放,#286 的精确最终 head 仍需独立 manual dataset/200-seed 验收及后续合后检查。 |
Dependency and scope
Refs #277. This final candidate is tests-only against actual main
e786bfc0395a035670cfa12d568022c758ec848a: exactly the original 13 test/checker/CI/documentation/development-dependency paths. Semantic foundation #283 and the separately authorized Windows checkpoint repair #285 are merged. There is no functional dependency on #286.Earlier head
14404c7ab2364c8798a22c44c1510c7bbb587035temporarily included unmerged #286 input validation for pre-validation. Normal two-parent commita35dfb47edee3fb29cb607c6c8e3007cce02ccc6removes exactly that nine-file input delta (seven paths restored to actual main, two #286-only new test files removed) without rewriting history. No production file is deleted; merged provenance history is unchanged. All 13 #277-owned blobs/strong assertions are preserved, including focus test blob35a1bc4a61e9b4ec57590394a2bd88cca98a7733. The independent full-tree isolation review and publication checks verified final treeb2891922f9b67cafb1f8432cec879625488e32b8.No runtime/product code, parser-v3/frame-tree decision, credential/network/runner-permission change, fixture weakening or release action is included in the final delta.
#277 implementation
coverage[toml]>=7.10.3development dependencies.Evidence and final gates
Independent source, wiring and isolation reviews found no blockers. Authored commit identities, ordered parents, all tree entries and the exact 13-path diff against actual main were verified before normal fast-forward publication. No local project unit tests/builds were duplicated.
The intermediate combined head passed all 12 applicable checks in Test 41320127308 / Platform 41320127240, earned 94.56% overall and all ten independent floors, and the unchanged original Windows
test_zero_checkpoint_write_fails_before_any_focus_mutationpassed in job 124888366129. That is intermediate evidence only, not acceptance of this final isolated tree. The new exact head must pass the complete matrix, required browser, installed-wheel acceptance and every coverage floor; #285 post-merge checks must also succeed before merge.The final latest-main/head/review/check state will be rechecked before merging. #277 will be closed only after this PR and its post-merge CI succeed. Nightly/manual dataset acceptance is not claimed by an event-skipped PR job; the separate input-boundary #286 retains its stricter final manual acceptance plan.
Snapshot provenance
Snapshot provenance decision: no-update
Snapshot provenance no-update reason: The final diff against actual main contains only tests, CI/checker documentation and a development dependency; no snapshot runtime, attribution/source mapping or provenance history changes. The unmerged #286 record was removed solely with that out-of-scope pre-validation delta, leaving the actual-main provenance blob unchanged.