do it in optimizer ?
are there any more specific requirements if I want to do it ?

https://discord.com/channels/@me/1295311135586652191/1341655795703742495

wmertenssaid:
hmmm

it means having to read the q-manifest file at startup and finding symbols that look like this:

 "s_0EBpKMD7Km0": {
      "origin": "../../qwik-router/lib/index.qwik.mjs",
      "displayName": "index.qwik.mjs_serverQrl_rpc",
      "canonicalFilename": "index.qwik.mjs_serverQrl_rpc_0EBpKMD7Km0",
      "hash": "0EBpKMD7Km0",
      "ctxKind": "function",
      "ctxName": "$",
      "captures": true,
      "parent": null,
      "loc": [
        53568,
        56525
      ]
    },

So the displayName ending with serverQrl_rpc and ctxKind function. And then in the place where it executes qFunc, check the list
and then the same for actions

this is context

By looking at the symbol name you can see if it's a server qrl, so no optimizer changes needed.

However, it would be great if the optimizer could list out the function argument names and captured scope names. Then we can generate an API report that should be checked in, which helps show when the API changes.

@JerryWu1234 I'm not sure I understand the issue (can't access your link), but I think you can do a first PR without the change for the optimizer; and create a separate issue for the optimizer optimization.