prepare for new release

Cargo.lock

@@ -1324,7 +1324,7 @@ dependencies = [
 
 [[package]]
 name = "jocalsend"
-version = "1.0.0"
+version = "1.6.1"
 dependencies = [
  "axum",
  "axum-server",

Cargo.toml

@@ -1,6 +1,8 @@
 [package]
 name = "jocalsend"
-version = "1.0.0"
+# 1.61803398874989484
+#----^
+version = "1.6.1"
 edition = "2024"
 authors = ["Joe Ardent <code@ardent.nebcorp.com>"]
 keywords = ["p2p", "localsend", "tui", "linux"]

VERSION

@@ -0,0 +1 @@
+1.61

VERSIONING.md

@@ -0,0 +1,31 @@
+# Golden Versioning
+
+This software is versioned under a scheme I call "goldver", as an homage to the
+vastly inferior [semver](https://semver.org).
+
+## What does "goldver" mean?
+
+When projects are versioned with goldver, the first version is "1". Note that it
+is not "1.0", or, "1.0-prealpha-release-preview", or anything nonsensical like
+that. As new versions are released, decimals from *phi*, the [Golden
+Ratio](https://en.wikipedia.org/wiki/Golden_ratio), are appended after an
+initial decimal point. So the second released version will be "1.6", the third
+would be "1.61", etc., and on until perfection is asymptotically approached as
+the number of released versions goes to infinity.
+
+## Wait, didn't Donald Knuth do this?
+
+No! He uses [pi for TeX and e for MetaFont](https://texfaq.org/FAQ-TeXfuture),
+obviously COMPLETELY different.
+
+## Ok.
+
+Cool.
+
+## What version is JocalSend now?
+
+Canonically, see the `VERSION` file. Heretically, once there have been
+at enough releases, the version string in the `Cargo.toml` file will
+always be of the form "1.6.x", where *x* is at least one digit long, starting
+with "1". Each subsequent release will append the next digit of *phi* to
+*x*.