Release v0.6.102

release: an open draft is a claim on a version number — read it

The version job picks the next patch above the newest tag, the newest npm
package and package.json. All three of those appear only when a run
publishes, about twenty-five minutes after it starts. A second run that
begins inside that window sees the old numbers and picks the same version,
cross-builds five targets, and dies on `npm publish`:

    npm error You cannot publish over the previously published versions: 0.6.101.

That is exactly what happened to v0.6.102. The draft release the first run
opened at second zero was already the reservation; nothing read it back.
Now it counts, so the window closes to the moment between reading and
opening a draft rather than the length of a whole build.

`concurrency: release` does not serialize these runs — two were in flight
at once, which is how the overlap arose in the first place.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>