XingfenD
9061c39ef3
A1 - the four-gate line said `internal/api ~11.0s 含真库集成`. It does not include the real-database integration tests: without TEST_DATABASE_URL they skip silently, and the 11s is the mock path. The wording mattered because it hid the fact that every run in this batch - implementer, task reviewer, fix-forward and controller alike - skipped them, including the two concurrency/TOCTOU guards that §1.6 names as the behavioural evidence for phase six. Replaced with the measured picture: 4 skips in internal/api, 26 `--- SKIP` lines repo-wide, and the full list of the 11 Test functions gated on that variable (cmd 2, api 4, repository 2, service 3). Also recorded the branch review's DB-parity run - base fe810dd 194 PASS/0 FAIL versus HEAD b15c2a8 199 PASS/0 FAIL, +5 being exactly this batch's new guards, state multisets identical - which is the first runtime proof of zero behaviour change on the postgres path; everything before it was static. The pre-merge checklist now has to include a DB-enabled comparison or the next batch skips them again. A3 - fix-evidence/rv-t3-v2-filtered.py prints 6 ORDER VIOLATIONS while the fix report's prose says both trees have 0. The prose is right and the script is the artefact: it assigns repeated text lines to destinations with a greedy pop(0), so identically-named lines land in the wrong bucket. The branch review redid the check with an unambiguous-unique-text method and got pre=0, post=0. Annotated the archived script in place (it lives in the gitignored evidence area, kept for auditability) so nobody cites its violation count as evidence again, and pointed at the review's §12 reproduction method. Post-write checks: 20/20 assertions, 12 table blocks with 0 column anomalies, 8 code fences paired, 28 headings with no duplicates, and the annotated script still passes py_compile.