With wrappers like these, It's hard to know which part is the actual action, so the transform defensively assumes that all functions present in the export might be. i don't think we can really improve this without unintentionally skipping transforming things that are supposed to be actions, and that'd be a pretty big issue, because we might leak server code to the client.

I'd recommend removing the top level directive and using an inline one instead:

export const $serverAction = actionClient
  .schema(
    z.object({
      things: z.enum(Object.entries(things).map(([kind]) => kind) as [string, ...string[]]),
    }),
  )
  .action(async () => {
    'use server'
  })

that way, the transform doesn't have to guess which functions need transforming.

While I do understand why this false positive is occurring and the difficulties of distinguishing function calls I don't like the suggestion at all since it goes against the common convention to use the directive at the top of the file and it stifles DX a bit.

In my particular use case I can easily move the Object.entries().map() expression into a separate file for the time being.

Thanks for following up though.