fix(release): anchor next release after orphaned-tag recovery

Master's tag chain was broken (the original v0.5.10 tag pointed at an
orphaned commit after a prior history rewrite), which caused
semantic-release to fall back to walking the full commit history and
producing 'chore(release): 0.2.0' on every CI run without actually
publishing anything to npm. npm latest stayed pinned at 0.5.10 the
whole time; the noisy commits were misleading.

A fresh v0.5.11 tag has been pushed to current master, so semantic-
release can now find a reachable anchor via 'git describe --tags'.
This empty fix commit is the trigger that lets the next CI run prove
it works end-to-end: bump from v0.5.11 -> v0.5.12, publish to npm,
tag the GitHub release. Future commits then bump cleanly per the
configured rules (feat -> patch, fix -> patch, breaking -> minor).

Author: jddunn