$unuseAll() / $unuse('policy') inside $transaction still apply PolicyPlugin #2906

Description and expected behavior

Inside an interactive transaction, a client derived with $unuseAll() or $unuse('policy') still enforces access policies. The same call outside a transaction bypasses them, as documented.

Expected: the derived client stays in the same transaction (as fixed in #2494) but runs without the removed plugins.

plugin policy {
  provider = '@zenstackhq/plugin-policy'
}

type AuthUser {
  id             String @id
  organizationId String
  @@auth
}

model Organization {
  id   String @id
  name String

  @@deny('all', auth() == null || auth().organizationId != id)
  @@allow('all', true)
}

const db = new ZenStackClient(schema, { dialect })
  .$use(new PolicyPlugin())
  .$setAuth({ id: 'u1', organizationId: 'o2' })

// table has one row: { id: 'o1', name: 'O1' }

const outside = await db.$unuseAll().organization.count()
const inside = await db.$transaction(tx => tx.$unuseAll().organization.count())
const unuse = await db.$transaction(tx => tx.$unuse('policy').organization.count())

console.log({ outside, inside, unuse })
// actual:   { outside: 1, inside: 0, unuse: 0 }
// expected: { outside: 1, inside: 1, unuse: 1 }

Environment:

• ZenStack version: 3.10.0 (the code below is unchanged on main)
• Database type: PostgreSQL 17
• Node.js version: 24.x
• Package manager: npm

Additional context

Looks like a side effect of #2497 (the fix for #2494). In the ClientImpl constructor:

if (baseClient?.isTransaction && !executor) {
    this.kysely = baseClient.$qb;
}

The derived client reuses the transaction's Kysely instance, whose executor is the ZenStackQueryExecutor created for the original client. That executor still runs the original plugin list, so $unuse* has no effect on queries run through the derived client. Keeping the transaction is right; the plugins should come from the derived client.

Impact: code that needs a policy-free client inside a transaction (e.g. an onEntityMutation hook with runAfterMutationWithinTransaction: true, or a procedure called within $transaction) silently gets filtered results instead of an error.