v0.5.0

Changes in 0.5.0

Fixed

• After a Schedule I update Polyfill starts from the game's new files. It used to keep writing its copy of
  the old ones back over them, which broke mods that had been fine.
• Repairs keep working when the game reaches 0.5.0 or 1.0. Version numbers were compared in a way that read
  0.5.0 as older than 0.4.6f5, which would have switched the rename history off.
• A repair a person wrote by hand is used before one guessed from spelling. Two similar-looking names could
  stop the better answer from being used at all.

Added

• The report says what Polyfill DID, not only what it found. polyfillexport gains a REFUSED section for
  every repair it had a candidate for and did not trust.
• polyfillregen has MelonLoader build the game's generated files again, for when Polyfill reports that it
  has no untouched copy of one left.

Installing by hand: Polyfill.Boot.dll goes into Plugins/, Polyfill.dll into Mods/. The plugin
does the work and has to be a plugin - it runs before any mod is read - so a copy of it in Mods/ is
ignored by MelonLoader. The mod only adds the console commands and can be left out.

Polyfill patches the game, not your mods. Your own files are never changed, and polyfillrestore in
the console takes the patch back out on the next launch.

What's Changed

• fix(inject): stop writing the previous game version over the new one by @DooDesch in #15
• refactor(contract): one version arithmetic, one report format, and a suite to hold them by @DooDesch in #16
• feat(versiondb): read the game's history as steps, walked to the installed build by @DooDesch in #17

Full Changelog: v0.4.3...v0.5.0