Exact-record canaries when a legacy tool lacks a tenant filter

A destructive workflow that lacks a tenant or entity filter can still be previewed safely only when its ordering and cursor semantics permit exact-record isolation: resolve the target record from authoritative relational ownership, find its immediate predecessor under the tool’s exact query predicate, run with that predecessor plus a one-record inspection cap, and verify the returned cursor/identity before considering any mutation. This method applies only when ordering is stable, the predicate is reproduced exactly, and state has not changed between predecessor lookup and execution; recompute immediately before every mutating invocation. It does not make a broad apply safe, and adding a first-class tenant/entity filter remains preferable.