ci: install jolt via the install script; CLI is jolt, not joltc

.github/workflows/tests.yml

@@ -5,7 +5,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - name: Install joltc
+      - name: Install jolt
         run: |
           set -euo pipefail
           sudo apt-get update
@@ -16,11 +16,12 @@ jobs:
           # French month name.
           sudo locale-gen fr_FR.UTF-8
           sudo update-locale
-          url=$(curl -fsSL https://api.github.com/repos/jolt-lang/jolt/releases/latest \
-                | jq -r '.assets[] | select(.name | test("x86_64-linux\\.tar\\.gz$")) | .browser_download_url')
-          mkdir -p "$HOME/.jolt"
-          curl -fsSL "$url" | tar xz -C "$HOME/.jolt" --strip-components=1
-          chmod +x "$HOME/.jolt/joltc"
+          # Install through jolt's own install script rather than resolving the
+          # release asset here: it owns the archive and binary naming (which
+          # changed in v0.5.0, when the CLI was renamed from joltc to jolt) and
+          # verifies the checksum. Hardcoding either broke this workflow once.
+          curl -fsSL https://raw.githubusercontent.com/jolt-lang/jolt/main/install \
+            | bash -s -- --dir "$HOME/.jolt"
           echo "$HOME/.jolt" >> "$GITHUB_PATH"
       - name: Test
-        run: JOLT_PWD="$PWD" joltc -M:test
+        run: JOLT_PWD="$PWD" jolt -M:test

README.md

@@ -26,7 +26,7 @@ tick API.
 ## Test
 
 ```
-joltc -M:test
+jolt -M:test
 ```
 
 Runs tick's own suite plus the migrated jolt `java.time` cases. tick, spec.alpha,

deps.edn

@@ -17,4 +17,4 @@
   :stage {:extra-paths ["test"]
           :main-opts ["-m" "jolt.time.stage-test"]}}
 
- :tasks {test "joltc -M:test"}}
+ :tasks {test "jolt -M:test"}}