v0.31.2 what the reviews found and nobody had mended

A session forgot a message after 256 newer ones, and a message carries no clock, so one captured earlier
could be replayed into it as if its robot had said it again. A session now remembers 1,024 and then ends,
since a new hello has new nonces. A peer that kept a link talking kept the beacon id from changing, and could
follow the robot by it, so after an hour the robot now ends what holds the id and only then takes a new one.
quackd onboard preflight names a robot key or robot.env others can read.

The radio asks the board for its adapter each time it comes up, so one that appears later under another name
needs no restart, though no real adapter has run this. A robot a LAN address turns away tries its link, which
a robot that does not advertise could never reach otherwise. The advert's BUSY flag is set at a limit and
read. A robot grants only what its passport offers. A robot that answers under another beacon id no longer
logs a meeting. A robot told its session is gone ends its side, and a link that closes ends the sessions it
carried, so the two can meet again. quackd onboard sign says when the running service keeps the passport it
had. A service that stops answering and a third party's board or adapter no longer end a command in a
traceback.

What it leaves is in the note under Known limitations: a stranger claiming a beacon id, strangers holding
every link, a flood filling the table of robots heard, a local reconnect loop on the control socket, and a
controller's own duplicate filter.

Ten distributions, one version between them: quackd, quackd-microduck, quackd-lerobot, quackd-rosbridge,
quackd-open-duck, quackd-xlerobot, quackd-alohamini, quackd-toddlerbot, quackd-huebot and quackd-moss. The
full note is in CHANGELOG.md.