Release beta 1.0.0 baseline

docs/versioning.md

@@ -1,20 +1,24 @@
 # Versioning
 
-JWeBot uses an alpha version string:
+JWeBot uses a human-readable product version string:
 
 ```text
-alpha X.Y.Z.MMDD
+beta X.Y.Z.MMDD
 ```
 
 Rules:
 
-- `alpha` means the public API and deployment process may still change.
+- `beta` means the project has passed the local, staging, privacy, and
+  production-safety gates expected for wider testing, while still allowing
+  controlled breaking changes before a stable release.
 - `X.Y.Z` is the project version.
 - `MMDD` is the delivery date.
+- Python package versions use PEP 440 pre-release form. For beta builds,
+  `beta 1.0.0.1016` maps to `1.0.0b1+1016`.
 - Normal small updates increment only the patch version, for example
-  `alpha 0.0.1.1014` to `alpha 0.0.2.1014`.
-- Minor versions such as `0.1.x` require explicit user review and milestone
-  approval.
+  `beta 1.0.0.1016` to `beta 1.0.1.1016`.
+- Minor, major, or stable-release changes require explicit user review and
+  milestone approval.
 - Local repository migration does not imply a production deployment.
 - Production services must not be changed unless the operator explicitly asks
   for deployment or runtime verification.