treewide: Document changes and release

I think it makes sense to track things a bit with releases as this makes it a bit simpler to reason about when something broke.

I've pushed an unsigned v0.0.0 tag to the last commit in 2023 (before the longer break) and this release contains the changes since then.

Would be nice to land !68 (merged) and maybe !65 (merged) in that release but not a requirement.