Migration acceptance

Compare candidate behavior.

These independent runs share a source commit, workload, adapter, upstream provenance and probe set. Their different SQL fixtures are the candidates being compared.

Breaking candidate

BLOCK

8/16 checks passed

Commit 2ec32c7eb316c4f1cedf6e92a27b3e240de55c60

Open full run

Expand candidate

GO_WITHIN_SCOPE

16/16 checks passed

Commit 2ec32c7eb316c4f1cedf6e92a27b3e240de55c60

Open full run

The same operations, two candidates

OperationBreakingExpand
Start independent old HTTP applicationv1PASSPASS
Read existing project itemv1PASSPASS
Create and read project itemv1PASSPASS
Apply candidate SQL-PASSPASS
Start independent new HTTP applicationv2PASSPASS
Read migrated project itemv2PASSPASS
Create and read project itemv2PASSPASS
Read migrated project itemv1FAIL / 42703PASS
Create and read project itemv1FAIL / 42703PASS
Old creates; new readsv1 → v2FAIL / 42703PASS
New creates; old readsv2 → v1FAIL / 42703PASS
New updates; old readsv2 → v1FAIL / 42703PASS
Old updates; new readsv1 → v2FAIL / 42703PASS
Stop both apps; restart v1; verify new process identityv1PASSPASS
Read latest acknowledged value after rolloutv1FAIL / 42703PASS
Read data committed by v2v1FAIL / 42703PASS

Run identities

Breaking: 764d92a0-8bda-487d-b198-aadae9eb899f
Expand: a4e4e550-089b-47dd-a32f-2cde77b4e02e