Require durable writes and verified release qualification - #217
Merged
Conversation
This was referenced Sep 12, 2026
Coding-Dev-Tools
marked this pull request as ready for review
September 12, 2026 20:25
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. |
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
1 participant
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.
Writable file-backed memory now defaults to verified WAL/FULL durability, with an explicit balanced option and effective diagnostics. Consolidation evidence lookups respect the Store's 500-ID bound and preserve scope, temporal visibility and canonical evidence when a batch fails. Pi resolves patched Hono, while Python 3.9, the NumPy-only core and MCP <2 remain supported.
The previously separate Galaxy work is now integrated. Carrier seeds and live gravity use the same clock; coarse helper steps preserve bounded orbits; drag and contact corrections account for motion already spent. Faster local presentation remains independent from capped emitted velocity, and live sliders retain every authored orbit. Tests cover all 3,335 moving bodies through their actual parent frames and retain speed, radius, clearance and lifecycle limits.
Compatible Playwright 1.63.0, language-pack 1.16.2 and Impeccable 4.0.4 updates are consolidated from #213, #214 and #215. The proposed MCP major upgrade in #216 is replaced by the current compatible constraint and an explicit major-upgrade ignore. The original source and stashes remain preserved;
docs/REWORK_EXECUTION.mdrecords the integration and remaining work.Performance and capacity tools support real files, pinned semantic models, exact vector backends and rerankers. Capacity validation enforces the declared hosts, queueing, latency, memory and scheduled outcomes. Installed MCP/dashboard journeys bind their artifacts and dependency identities. Publication requires owner-signed qualification for the complete product ledger; reporting-command success cannot replace failed evaluation booleans.
Validation at
aee6879e38d7762b164c0c20cff54c6a4ce66240: 5,322 offline tests passed, with 53 platform or optional-dependency skips. Ruff, Pyright and commercial/asset checks passed. All 158 browser tests passed on the integrated source with Playwright 1.63.0. All 30 current GitHub checks passed, including Python 3.9 through 3.14, encryption, coverage, Docker, CodeQL and installed MCP/dashboard journeys on Windows, macOS and Linux. Four bounded internal reviews returned. GitHub PR CI used merge commit240eb59855c2b02578440a79146fd7d1424f9aa4; its complete Git tree0050301023508b5c007357e3a12b2f200b726d85matches the submitted branch. The six installed journeys retain their individual test-wheel hashes; final qualification must use one selected release wheel. Earlier release dry-run artifacts remain historical and do not qualify this new commit.This is a draft qualification candidate. Capacity on both reference hosts, independent coding comparisons, authenticated hosted journeys, operational restore, first-time developer acceptance and the bounded pilot remain mandatory. Retrieval defaults and competitive-leadership claims are not promoted by this PR.