sl0p: tag fork builds as 0.45.0+sl0p1

`zellij --version` was identical to upstream, so there was no way to tell a
fork binary from a stock one.

Uses BUILD METADATA (+sl0p1) rather than a prerelease (-sl0p1): cargo ignores
build metadata when matching version requirements, so the intra-workspace
`zellij-utils = "0.45.0"` dependencies still resolve. The prerelease form was
tried first and fails to resolve - it would require updating every member
manifest to depend on the exact prerelease.

Checked against the places VERSION is actually consumed:
  - shared::version_number() yields 4500 for both 0.45.0 and 0.45.0+sl0p1, so
    terminal version reporting is byte-identical, and still orders below 0.46.0.
  - client/server compatibility keys off CLIENT_SERVER_CONTRACT_VERSION, not
    this, so existing sessions are unaffected.
  - ZELLIJ_PLUGIN_ARTIFACT_DIR is keyed by VERSION, so the bundled wasm plugins
    are recompiled once on first run after a bump. One-time, harmless.

Baselines held: zellij-server 1421/30, zellij-utils 435/5.

1 files changed, 16 insertions, 1 deletions

diff --git a/Cargo.toml b/Cargo.toml
index 42772834..7061bc61 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -70,7 +70,22 @@ members = [
 edition = "2021"
 license = "MIT"
 repository = "https://github.com/zellij-org/zellij"
-version = "0.45.0"
+# sl0p fork: the `-sl0pN` suffix marks a fork build so `zellij --version` is
+# distinguishable from upstream. Bump the suffix for each published fork build;
+# reset it to 1 when rebasing onto a new upstream version.
+#
+# Safe against the places VERSION is consumed:
+#   - it is BUILD METADATA ('+'), not a prerelease ('-'): cargo ignores build
+#     metadata when matching version requirements, so the intra-workspace
+#     `zellij-utils = "0.45.0"` deps still resolve. A `-sl0p1` prerelease does
+#     NOT resolve and would need every member manifest updated.
+#   - shared::version_number() still yields the same number as 0.45.0, so
+#     terminal version reporting is unaffected.
+#   - client/server compatibility keys off CLIENT_SERVER_CONTRACT_VERSION, not
+#     this, so sessions are unaffected.
+#   - ZELLIJ_PLUGIN_ARTIFACT_DIR is keyed by VERSION, so a bump means the wasm
+#     plugin cache is rebuilt once on first run.
+version = "0.45.0+sl0p1"
 # NOTE: When updating this, modify `channel` in `rust-toolchain.toml` accordingly
 rust-version = "1.95"