Skip to content

P1 CMR-05: prove mixed create/update/delete target atomicity in one set #248

Open

Description

@philipgreat

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.

Activity

  1. philipgreat commented on Oct 21, 2026

    @philipgreat
    ContributorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions