Inline `"Use Server"` Function Fails When Returned From File-Level `"Use Server"` Function

Next.js's server action manifest collection for direct Client Component imports only registers top-level exported server actions from `"use server"` files. The SWC transform successfully generates hidden exports for nested inline actions, but the build plugin does not include these nested action IDs in the server reference manifest for that module, so the server cannot resolve the action ID sent by the client.

Create a file `app/imported/actions.ts` with `'use server'` at top, export `outer` returning an inner function marked with inline `'use server'`. Import `outer` directly in a Client Component. Call `outer('captured')` to obtain the inner reference, then call the retained function with `'client'`. Observe the server action not found error. Compare with passing `outer` from a Server Component as a prop, which succeeds.

This workaround changes the API contract: `outer` no longer returns a callable function, so any code that expects a function reference must be updated. If the original pattern is required, you must wait for an official Next.js patch or apply a framework-level fix. Rollback is straightforward by reverting to the original actions.ts and client component, but the bug will reappear. The workaround is safe for production as it uses only supported server action forms.