Is there more reading material on the scope of the functionality that FedeProxy will provide? In earlier topics the discussion was focused on Federated Issue Management, whereas here the scope is broader. It looks good to me, though, how this is set up.
In other discussion I got the impression that FedeProxy instance A knowing that Forge A is e.g. Gitea and Forge B is e.g. Gitlab would tailor the AP message exchange according to a Gitea2Gitlab proxy mapping (i.e. AP messages from A to B become Gitlab-specific), rather than having a more universal FP wire format (Gitea2FP on Forge A and Gitlab2FP on Forge B). This in contrast to what ForgeFed does, where ForgeFed format dictates the message protocol.
(Just mentioning this again, in case I misunderstood)
With a universal FedeProxy protocol it would be more feasible to have other services to also hook in onto this configuration, e.g. a Trello board that updates itself with selected content from a forge.
Update: See Multi forge web service with unique features for more info on this idea.