You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
P1 CMR-05: prove mixed create/update/delete target atomicity in one set #248
Parent acceptance: teaql/teaql-conformance#216. Existing target tests cover create separately from update/delete, so they do not directly prove all three operations in one atomic set. Add a runtime-owned regression with a final-create fault armed only after prior update/delete, verify rollback of rows/inbox/checkpoint, then retry and duplicate acknowledgement. Test-only formal P1 feature branch; no runtime API change, main merge or release. No runtime defect is claimed before execution.
The same numbered target audit also found no explicit Java unknown-entity rejection assertion (CMR-10), while the Rust counterpart already exercises it. Adding that negative assertion to the same test-only candidate before installed-package qualification; production code and APIs remain unchanged.
Activity
philipgreat commentedon Oct 21, 2026
The same numbered target audit also found no explicit Java unknown-entity rejection assertion (CMR-10), while the Rust counterpart already exercises it. Adding that negative assertion to the same test-only candidate before installed-package qualification; production code and APIs remain unchanged.