Linux standalone runtime / before / fresh isolated T3 home
Local version labels: 0.1.9 -> 0.1.10 (same source except package version)
$ t3 __service-launcher  [background]
GET /.well-known/t3/environment: version 0.1.9
$ t3 --version
t3 v0.1.9
$ readlink ~/.local/bin/t3
~/.t3/runtime/versions/0.1.9/t3
$ RPC server.updateServer {targetVersion: "0.1.10"}
Update RPC response: {"_tag":"Success","value":{"targetVersion":"0.1.10","method":"boot-service","updateId":"a3e4377c-a315-4f27-bb2e-91983891991e"}}
Durable service state: {"protocol":4,"activeVersion":"0.1.10","update":{"id":"a3e4377c-a315-4f27-bb2e-91983891991e","fromVersion":"0.1.9","targetVersion":"0.1.10","status":"committed"}}
GET /.well-known/t3/environment: version 0.1.10
$ t3 --version
t3 v0.1.9
$ readlink ~/.local/bin/t3
~/.t3/runtime/versions/0.1.9/t3
$ ln -sfn ~/.t3/runtime/versions/0.1.9/t3 ~/.local/bin/t3
$ restart background launcher (no update request)
GET /.well-known/t3/environment: version 0.1.10
$ t3 --version
t3 v0.1.9
$ readlink ~/.local/bin/t3
~/.t3/runtime/versions/0.1.9/t3
Ordinary restart preserves intentional CLI pin: true