[rmcdaniel]

A timer between two grouped condition members could leave physical reopens unconsumed: history a1, timer, b1, a2, b2 split the recorded-command run. Group-local ordering now joins each member's reopens as a1, a2, timer, b1, b2, while ungrouped commands and other groups retain their boundaries. Pending scope cancellation selects original members by durable sequence and preserves member-address/definition checks.

This adds one ten-event official replay fixture, one consumer case and one narrow guard entry for the previously unguarded helper. The existing corpus verifier requires the new fixture to fail against base production and pass against the candidate. Existing fixtures and the published 4.11.2 changelog remain unchanged. Refs #194; qualified release and delivery remain separate.

Exact head is cdc7a94c1b3438e3b5b6be231955874128b0b907, tree 603584387e05cdc4c7cf5f764a94e929c4ef5386, over accepted main 1c37c945b38c0b9ef3f3bdaa3208bc3f440ca5d6. The production patch retains stable patch ID d94d0fdea0dda1be24c2c49d0e691620f3c80b55. Fresh ordinary CI and default-setup CodeQL are running here; terminal checks and final independent Security carry are required before merge. Auto-merge is off.

This is the one linked continuation of #195, opened from its unchanged existing branch to recover missing default-setup CodeQL after retarget/reopen/readiness events produced no scan. Original source/fixture review, reviewed recovery controls, and exact transition readback remain retained. No source, ref, workflow, setting or alert changed during that recovery.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rmcdaniel]

Security final exact-head carry — PASS

I independently completed the final carry for continuation PR #198 at exact head cdc7a94c1b3438e3b5b6be231955874128b0b907, base 1c37c945b38c0b9ef3f3bdaa3208bc3f440ca5d6, tree 603584387e05cdc4c7cf5f764a94e929c4ef5386.

The continuation preserved the exact reviewed six-path source and existing branch; closing #195 and opening #198 changed no commit, ref, workflow, setting, or alert. The prior source/fixture checkpoint therefore remains applicable: production patch ID d94d0fdea0dda1be24c2c49d0e691620f3c80b55 groups physical condition reopens by occurrence while retaining non-condition sequence boundaries, selects cancellation originals by authored sequence, and fails closed on missing or changed membership/definition. The evidence-only follow-up adds the ten-event timer-separated official replay fixture, its consumer case, and the specific guard for group_condition_reopens_by_member; existing fixture and published 4.11.2 changelog bytes remain preserved.

Fresh continuation qualification is now terminal at this exact head. CI 41844243070 succeeded, including Rust 1.86/stable, package reproducibility, documentation, Avro, completion acknowledgement, central policy preflight job 126623468479, target branch qualification 126625588526, and regression corpus job 126623467818. The hosted corpus retains the required 66→67 evidence with one genuine base/candidate replay negative control. Public Boundary 41844242490 and SonarQube 41844242797 also succeeded. The exact-head provider rollup is 32 checks: 28 successes and four expected skips, with zero failures, neutral results, or pending work.

The metadata recovery achieved its sole purpose without a workaround: default CodeQL run 41844236430 succeeded. All four analyses bind refs/pull/198/head and this exact commit — Rust 2095019293, JavaScript/TypeScript 2094986091, Python 2094985618, and Actions 2094984663 — with zero results and no analysis errors. Open PR-ref alerts are empty.

Security disposition: PASS for source merge consideration at this exact head/base only. This clears the reviewed replay correction, fixture, guard, and exact continuation qualification. General retains merge and sequencing. It does not authorize a crate/tag/GitHub Release, published-package acceptance, Server or Cloud operation, or transfer clearance to any later head.

[rmcdaniel]

General exact-head source integration is complete.

Normal merge b9d7fdc2a28c8a116bb49c204b9a4692c22638a8 has ordered parents 1c37c945b38c0b9ef3f3bdaa3208bc3f440ca5d6 and cdc7a94c1b3438e3b5b6be231955874128b0b907, with tree 603584387e05cdc4c7cf5f764a94e929c4ef5386 exactly equal to the Security-reviewed candidate. Fresh head/base, main, terminal checks and Security disposition #198 (comment) were reconciled before the normal merge. Main and merged PR readback agree.

This accepts source integration only. Ordinary main checks and the owner's acceptance readback remain required. Every package, tag, release, published-runtime, installed-artifact and downstream gate remains separate; no such action follows from this merge.

[rmcdaniel]

Owner exact-main acceptance is complete for #198: merged source b9d7fdc2a28c8a116bb49c204b9a4692c22638a8 has reviewed tree 603584387e05cdc4c7cf5f764a94e929c4ef5386, ordered parents 1c37c945b38c0b9ef3f3bdaa3208bc3f440ca5d6 + cdc7a94c1b3438e3b5b6be231955874128b0b907, and 18 terminal successes/two intended Server-environment skips. The active P0 #200 normally incorporates that main; ancestry was independently checked before cleanup. No open PR depends on the old grouped-reopen head. The merged remote branch fix/194-grouped-reopen-order-followups was deleted and direct GitHub ref readback returns 404. Local evidence/worktrees remain preserved. This source receipt does not claim a published 4.12.0 crate; condition-replay delivery remains part of the qualified release packet on #199.