Issue with DSM movies parsing. Parser assumes run starts from savestate even though it doesn't

[McBobX-1]

So I just submitted my DS TAS to the site couple minutes ago, and the submission says that it starts from savestate, which is not. Input file also indicates that it doesn't (savestate 0).
Link to submission: https://tasvideos.org/9336S

[CasualPokePlayer]

The exact issue at least appears to be between 0.9.11 and 0.9.13 savestate anchored movies changed. The savestate key previously was meant for the actual savestate, embbed into the movie file (and so if the key is present, a savestate is present). With 0.9.13, the savestate is a separate file, and the savestate key is just for indicating if a savestate is present or not (so the key will be present regardless of whether a savestate is present or not). The site parser currently thus has the logic of assuming a savestate is present if the savestate header key is present.

[adelikat]

Wow! That's a terrible regression for the .dsm format, I'd recommend we not even accept savestate anchored movies after 9.11