Already fixed in v0.0.1.1 and gave you a shoutout in the patch notes for catching it! Thanks for taking the time to report it, genuinely helps a lot.
