Merge branch 'v24docs'

Embed v2.3.0 in the release binary

Ready for a new release...

Gorelease tagged what was in github, rather than what was local...

Since I published v2.1.0 to github, I already need a dot release :-(

Fix possible crash related to coloring packets

The color array may not be adequately populated at the point I
dereference it. So check the length first. If the color isn't stored
yet, the next update will fix it.

Dot release - v2.0.3.

Now I understand how I should've versioned my go module.

https://stackoverflow.com/questions/53344471/taking-a-repository-to-v2
explains how to change the module path when upgrading the major version.

This is for homebrew...

I messed up and merged a v2.0.0 tag that was a day old from another
branch... This meant github's 2.0.0 source archive was out of date,
which Ross discovered when building from the updated homebrew
formula. So this is a 2.0.1 version, and I will tag it accordingly.

Move these out of the top-level, to avoid clutter.

Ready for pushing to github!