Prove Bounty COMMIT rollback and all honor round context boundaries - #188
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
已按 expected head 串行合并 #187、#188，当前 main 独立下载并核对最终头 Quality 36644965239：Python 3.15.0rc2、Ruff 0.16.9、uv 0.12.20；零 lint 诊断、stderr 空、588 文件 format、warnings-as-error compile 通过。 Deployment 36644965142：同一 wheel 的 server 安装检查 12 项、真实 OpenSSH/PAM/StrictModes 7 项、installed official selftest 42 项均通过；client-only 安装不含服务端实现。核心构建与部署演练的 wheel/sdist 逐字节一致，产物内全部 release-sha256.txt 已按实际文件校验：
候选交付产物。真实 PG+Git/CAS 全表 values/sequence、SIGKILL 重启、备份到空 PG 恢复、删除 marker 后仍持久隔离均已在演练核对；promotion=false。CI 环境 4 CPU 的测量仅属有界隔离演练：启动1.4292s，32次写入6.5149s/4.9118req/s，32次读取19.2719s/1.6604req/s，RSS/HWM81292KiB，重启1.3049s，备份1.6874s，恢复3.1091s。不是生产容量或现场恢复证据。 独立 main push 当前 4 项已 success，Rewrite 仍排队；最终主线门槛尚待该运行完成及产物核对。#72/#77 这里只增加明确事务/上下文负例，完整条款还须逐项审计；现场材料见 #84，未执行生产部署、资金、Root、真实外发或恢复放行。 |
|
合并后独立 main 验收现已完成：source 已独立核对质量36683776303和部署36683776308 ZIP摘要/source/实际报告；588文件格式、零Ruff诊断/stderr，Python3.15.0rc2。核心构建wheel/sdist与部署产物一致；所有release摘要正确，wheel/sdist/server/client锁四文件与已验#188逐字节一致。主线交付包。 独立主线安装演练：server12项、真实OpenSSH7项、official selftest42项全部通过；client-only无服务端实现。4CPU临时CI环境测量：启动1.1885s；32写入6.5881s/4.8572req/s；32读取15.1822s/2.1077req/s；RSS/HWM81180KiB；SIGKILL重启1.0437s；备份1.5109s、空PG恢复3.1388s。全表values/sequence守恒，删marker仍持久quarantine，promotion=false。这些是该run的有界隔离结果，不是目标机容量或已部署。 新增#189/#190已进入审查；#191是后续#72具体断言收口，#192是对#189的独立当前授权/只读回归。各自最终组合须重验。 |
Refs #72, #77. Depends on #187; merge serially after that installed-package restore fix passes.
Inject a real deferred PostgreSQL constraint trigger at Bounty COMMIT after the claim/transfer/receipt/Event/Inbox/result facts are prepared. Compare values in every public business table after rejection, retry the exact request, and prove one payment/notice with an unchanged committed replay.
Exercise each honor round R1–R5 with a wrong nonce, question digest and inclusive deadline, then verify durable failure, evidence removal and explicit restart. Verify a foreign subject cannot consume the owner's final challenge, and two concurrent final requests produce exactly one grant/audit with an unchanged winning request replay. Independent nonces are checked at every transition.
These are disposable real-PostgreSQL application/signature tests; no production money/Root or honor claim is made. Final full node-ID gate, quality and installed package checks must pass before merge. The umbrella issues retain their remaining design/field acceptance scope.