feat(release): qualify the omp 18.2.3 two-gpu composition

[alphastorm]

Qualified candidate — publication held

• RTX5090 and RTX4090 only; RTX3090 is deferred until its physical host returns.
• OMP18.2.3 live acceptance passed on macOS arm64, Windows x64 and Linux x64 (UbuntuWSL2).
• All24 documented blocks passed; no executable block changed afterward. Both hosts restored.
• Ready contract and immutable Git pins pass; six public evidence URLs returned200 with matching SHA256.
• Required CI passed161tests on the unchanged candidate tree: https://github.com/alphastorm/omp-ninfer/actions/runs/35297003295
• Launch-only corrections are independently published on main at aff4653; their CI and Pages deployment passed. Public Latest remains v0.7.2.

The resolver-selected cross-family reviewer returned HTTP429 before producing a verdict. This is not review approval. v0.7.3 is not tagged or published; retry the frozen review after provider availability returns, then disposition and cut the release. No further GPU window is required for an unchanged subject.

[alphastorm]

Fresh-session checkpoint

All repository work is committed and pushed on release/v0.7.3-client at 25191e07efa62c4affb153de1108f41eb62ba542 (tree ee6c9193f6875f01a8d5e234dbc931476b57596f).

• Required CI35297003295 passed161tests. Ready contract, immutable pins, and six public evidence URL hashes passed.
• RTX5090/RTX4090 only;24documented steps and all3client architectures accepted. Both hosts restored. Runtime bytes/settings unchanged. RTX3090 deferred; legacyv0.7.2 remains separate.
• Launch-only corrections are published on main at aff4653; main CI and Pages passed. Public Latest remainsv0.7.2.
• v0.7.3 publication is held only for the missing focused cross-family verdict. The sole attempt returnedHTTP429 before review; retry after the reported Claude reset, not before the conservative04:22UTC September18 boundary. No approval or reviewer findings exist.
• Private resume instructions and a byte-verified backup of the frozen review inputs are preserved in the local launch packet. Revalidate the current envelope and submit its exact generated Task payload; do not use the older34f8f75 envelope or substitute reviewers.

After review disposition, finish the normal checked product tag/release/Latest cut, actual-date changelog, public-link verification and founder-packet hold removal. Reuse unchanged hardware proof; no fresh GPU window or client-component publication is needed. Do not modify the separately owned18.2.5 reroll or gateway work.