TestEveryVersionedEntryPointMints counts RecordVersionInTx and
RecordVersionForCreateInTx as one seam. A create-shaped site that fell back
to the update-shaped entry therefore stayed green, though the fence then
reads the new row's NULL participation_generation as legacy and the record
is never versioned. The reverse case also stayed green: an update path that
reached the create-shaped entry would stamp an existing legacy row and
promote it, which R2.3 forbids.
Add the split to the structural guard. It is two small tests over the same
journalscan fixpoint and mintVersion edge discipline, with no AST changes:
- TestCreateShapedEntryPointsMintCreateShaped: the create-shaped mint sites
(finishCreateIssueInTx, CreateIssuesInTxWithContext,
PromoteFromEphemeralInTx, moveIssuePersistenceInTx, executeUpdate) must
each call RecordVersionForCreateInTx themselves. A delegate is not enough
here, because executeUpdate runs its move with mintVersion=false and a
batch switches finishCreateIssueInTx's mint off at run time. Every
create-shaped entry point, the delegates and #7205's
deferredCreates.flush included, must reach it.
- TestUpdateShapedEntryPointsNeverMintCreateShaped: every other
versionedEntryPoint must not reach RecordVersionForCreateInTx. The
exception is ApplyBatchInTx, which runs create and update items together
and is listed as mixed with a reason.
Mutation-checked, each probe reverted afterwards. executeUpdate's
EnteredIssuesPlane mint, PromoteFromEphemeralInTx's mint, or the batch's
deferred create-shaped mint switched to RecordVersionInTx: each fails the
create half. update.go's end-of-update mint switched to
RecordVersionForCreateInTx: fails the update half for UpdateIssueInTx and
every entry point that writes through it.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>