Ok, I found this site while searching for the missing version .jar file, which didn't show up in a net query through DuckDuckGo. The thread on this site was closed after a comment from someone listed as a coder who stated that it was meant to work in this way, without a .jar file which is no longer necessary. From earlier posts it seems that this person believed the OP had issues due to use of non vanilla launcher, which to me means he thinks they use a client or something like this. The OP immediately said that they use vanilla, but doesn't seem like the coder believed them. They began asking for logs, OP did not provide them. No need to go further into details.
I just reinstalled Windows on an SSD and just installed Minecraft Java, Optifine, Shader, Forge. That is all that exists on my pc right now, and I had the same issue with 1.19.2 Forge versions not creating .jar file.
Now I admit that I am likely missing something here and there is a technicality that isn't being fulfilled, but I have to say that it is not due to using a modified launcher. All i have done is install optifine, put a shader into the shader folder, installed forge. No mods yet, nothing.
What is interesting, and is the only reason I felt the need to post here, is that when I went into minecraft library folder and copied forge-1.19.2-43.1.65-client.jar, (I renamed it without the -client,) the Forge version starts up just fine with no further issues.
From my point of view it seems that coders are dismissing some valid issues out of hand. I mean, there are lots of really stupid and lazy people using computers and playing games, but not all of them are really stupid and lazy. We all have bias, I know that I do as well, and I think it's helpful to be aware of our bias as far as we have the ability to be aware of it.
Again, it could be that my assumption that there is a problem with the installer not creating a version .jar file, but I couldn't get it to work, always failed with the same message and then put the .jar file in the version folder and worked without a hitch.
Oh, almost forgot, I also went into each installation and changed from 2 to 20GB RAM for the game. In the past I had issues crashing with many mods installed due to lower RAM allocations and I have 48GB, so felt that was safe enough either way. Maybe that caused the issue, for all I know.
Just saying, would have been nice if the coder had said go to (generic/vanilla path) and copy (version I used as example) forge-1.19.2-43.1.65-client, paste into forge version folder, rename to forge-1.19.2-43.1.65 and see if that does it.