If I make an optional web build, is it okay if I count it as a separate itch project, link to it from the original jam game, but have a warning on the link that mentions that it should only be played as a last resort and has some slightly broken audio (things don't play at the correct pitch sometimes due to changes of Clickteam Fusion 2.5's HTML5 exporter's audio behavior vs. the non-HTML5 exporter)?

...also, if I don't have time to fix the audio of such a web build now, but find I have time to fix it after the late submission period, would that be like... fair game, as part of the "small updates that don't change the game much" thing? Or not really?

I mean yeah but... why not just put it on the actual page?

Mostly so people have to read the disclaimer that it's not the ideal version and they should save it as a last resort

I'd say just put it at the top of the description.

...oh! Right. Another reason, forgot to mention this one earlier because I was still kind of waking up at the time: Web builds put themselves at the very top of itch pages. So like, it tends to be the first thing people look at on an itch page when one is there. Which I really don't want when the build in question is intended as a last resort fallback instead of the intended version of the game. I'd rather somebody try to download it, run it, and if they have issues, then use the web build.

...I suppose I could add a disclaimer into the web build itself...? I do have a few minutes right now... I'll see what I can do.

Ok, right. I think I have the web build working now: https://happy-frog-games.itch.io/yes-yes-skeletons-go-fight-the-m

The disclaimer not only warns you about the issues but requires you to do an intentionally-slightly-excessive sequence of key inputs to progress. It doesn't require any simultaneous key presses though. Should be fine? I think? Just going to post it here to make sure though all the same...