erikgerrits

Cut a release of the `machine-learning` library — ship to npm and deploy the playground site, in the correct, safe order. Use this whenever the user wants to release, publish, "cut a version", "ship it", bump the version, tag a release, or "merge and publish" for this repo — even if they only say "publish" or "release the new chapter". Runs the full ordered flow (feature branch → commit → PR → CI → version bump → merge → tag → automated npm publish) and bakes in the ordering gotchas so a release can never half-ship.