Also there's a small edge case I wanted to discuss:
Some of these special encounters are locked to certain forms of a pokemon (for example the male and female Jellicent encounters I added in this PR) but the way the current pokemon table is set up, alternative forms are pretty binary (we have a frillish and jellicent entry in their natdex position which default to being the male form, while the female form is in the 10000+ ID range, because it's an 'alternate form'), however the wild encounters with frillish and jellicent are gender neutral, the game rolls for gender while the encounter generates, this isn't compatible with the alternate form system since only the female form has an additional entry.
Should we add another entry for the specifically male counterpart, and leave the default entry as gender neutral? (I guess this would also apply to some other pokemon like Meowstic, Indeedee, Basculegion, and Oinkologne, don't know if you can think of another one this)
If you give me the green light I'll add them myself

Hmm, but I think that Jellicent in reality has two genders only, right? Male and female? There's no neutral I think.

So I think we encountered another limitation due to how the data is structured in our API.

It does but most encounters can result in either male or female, while some special encounters are forced into one or the other, the same can happen in other encounters (say unown)

This can be merged now

Thanks for the contribution!

I don't know if this issue still persists, but I merged anyways

A PokeAPI/api-data refresh has started. In ~45 minutes the staging branch of PokeAPI/api-data will be pushed with the new generated data.

The staging branch will be deployed in our staging environment and the entire API will be ready to review.

A Pull Request (master<-staging) will be also created at PokeAPI/api-data and assigned to the PokeAPI Core team to be reviewed. If approved and merged new data will soon be available worldwide at pokeapi.co.