Minted MJ: API Keys rows.
MJ: API Key Scopes rows granting the minted keys full_access.
Clone logs the bundle's Executes returned (successes and refusals); teardown deletes exactly these.
Every row created by the bundle or by a clone it executed, in creation order.
OptionalDeniedSecondary GraphQL provider authenticated as the subject through a user API key: the identity without clone authorizations.
Unique per-run prefix stamped on every row the bundle creates.
OptionalProvisionWhy provisioning the subject or its key failed, when it did.
When the bundle started.
OptionalSubjectThe subject's MJ: Query Categories row, the child RC5 forces to collide.
OptionalSubjectThe throwaway source user (UI role only, one app, three settings, one query category), once provisioned.
Throwaway users; their roles, applications, settings, audit logs and keys are swept before them.
Accumulator fixture for the
record-cloningbundle (client transport; IT96).Setup creates NO rows, so a deterministic-only run writes nothing: it only stamps the per-run prefix and start time. The mutating checks provision the throwaway subject user (and its API-key connection, the denied identity) on first use and append every row they, or a clone they ran, created. Teardown sweeps FK-safe: clone log items, clone logs and
ClonedFromlinks first, thenCreatedRowsin reverse creation order (retried so a parent that still has a child is picked up on a later pass), then everything hanging off the throwaway users, then the users themselves.