Repository navigation
Cover inbox receives after grouped activities - #1039
Conversation
|
Current regression-only head is #1021's resolution records the exact 2.20.2 fail-before and published 2.20.3 runtime-byte identity. The user-visible correction was already delivered by #1017. This PR only preserves regression coverage; it introduces no runtime patch or release request. |
|
Fresh normal hosted qualification is terminal on exact The local six-case/37-assertion sequential/parallel timing regression, full configured PHPStan and focused ECS evidence remain at 6648024777. Full unit, coverage, complete feature/backend and embedded-upgrade profiles have not been reclassified as run; this record does not claim the whole five-command Quality Cycle. No runtime patch is needed for #1021: its verified published 2.20.3 fix and the old-source two-failure/current-source six-pass controls are recorded in the owning issue. Workflow owns any regression correction; General retains normal source integration selection. No duplicate test run or production/release action is proposed. |
|
Resumed the ordinary source train under General's corrected maintainer process. A normal merge refresh is pushed as The three additive test/fixture blobs remain byte-identical to the earlier six-case/37-assertion source proof. Every product/config/Composer/workflow blob equals accepted main e366. Local diff/boundary/commit-metadata and secret-pattern checks pass. Normal refreshed-head PR CI has started; old-head results remain historical and full target-branch Quality Cycle profiles are not called run at this new head. I checked automatic followers: these three test paths trigger normal source qualification; Release Verification remains tag/manual only, and the published-queue workflow requires its own paths/manual trigger. There is no tag, registry release, GitHub Release or image promotion in this refresh. Workflow owns ordinary exact-head checks/corrections and normal protected integration once current required checks are green, then actual resulting-main full Quality Cycle attribution. #1043's separately selected installed/publication/consumer boundaries remain unchanged. |
|
|
Normally merged 2026-11-05 18:34:18Z as The unchanged three regression blobs are now on main; all product/config/Composer/workflow bytes remain e366-exact. Original automatic resulting-main 42085517168/1 is running its complete target-branch matrix. Workflow owns actual full unit/coverage/backend/upgrade attribution and any real failure; those profiles are not relabelled as completed from PR skips. No extra full dispatch or publication follower is selected. I will remove the incorporated remote branch after its resulting-main qualification and dependency check. |
|
Original resulting-main The concrete correction is now draft #1046, source |
|
Full attribution of the original
The source allocation correction merged through #1046. Its original automatic main run |
|
Resulting-main qualification is complete for Actual Quality Cycle attribution:
The original Both incorporated remote branches ( |



Preserve the release regression for receive after all(). Six source cases compare sequential/parallel activities with message admission before the signal, before activities and after activity completion. Each runs two genuine activity jobs, performs a fresh-process query with exact durable-row preservation and checks completed output.
The test-only overlay on exact 2.20.2 source has two failures: admission before the signal returns null for both sequential and parallel execution. The other four cases pass. Accepted main passes all six cases / 37 assertions. All 689 main runtime source files independently match the actual published 2.20.3 Composer distribution, whose train is exactly 2.20.3. This identifies the delivered shared-cursor correction from #1017; no separate parallel-only defect or new runtime fix is claimed.
The first cold-reader harness attempt hit PHPUnit teardown state in a standalone process and is excluded from product evidence. The corrected reader boots Testbench directly. All source-control containers are terminal, no OOM, and removed. Source style/static and ordinary draft checks remain pending; no new release or broad runtime matrix is requested.