From fcb711b32089f15d04fcd6c69f03d0affc7fbca4 Mon Sep 17 00:00:00 2001
From: Yogthos <yogthos@gmail.com>
Date: Tue, 13 Oct 2026 15:32:24 -0400
Subject: [PATCH 1/2] Run CI on jolt's nightly build

The 0.8.2 pin missed jolt 0.8.21 moving the timer onto the monotonic clock,
which left every sleep and timeout armed for decades until v0.1.4. Tracking
nightly surfaces a breaking jolt change the day it lands. workflow_dispatch
can still pick a version for one run.
---
 .github/workflows/ci.yml | 23 +++++++++++------------
 1 file changed, 11 insertions(+), 12 deletions(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index ea1ccfc..a69eec8 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -5,16 +5,15 @@ name: CI
 # to build: a jolt project has no compile step, so the whole job is "install
 # jolt, run the tests".
 #
-# jolt is pinned for the same reason the rest of the jlt-commons fleet pins
-# it: a floating `latest` lets a release published overnight turn CI red on a
-# tree nobody touched. This workflow used to install with no version at all,
-# floating silently. `workflow_dispatch`'s `jolt-version` input overrides the
-# pin for a single run, which is what lets
-# https://github.com/jlt-commons/ci-builds fan this out across the org
-# against a candidate release (see that repo's README, "The pin convention").
-#
-# Moving JOLT_VERSION below is the cutover commit for a breaking jolt change.
-# Bump it and fix whatever it breaks in one reviewed commit.
+# jolt tracks the nightly build (release tag vnightly, the rolling build of
+# jolt's main), so a jolt change that breaks ebb shows up the day it lands.
+# The 0.8.2 pin this replaced missed jolt 0.8.21 moving the runtime's timer
+# onto the monotonic clock, which left every ebb sleep and timeout armed for
+# decades until v0.1.4 fixed it. The cost is that an overnight jolt commit
+# can turn CI red on a tree nobody touched; that red is the point.
+# `workflow_dispatch`'s `jolt-version` input still overrides it for a single
+# run, which is what lets https://github.com/jlt-commons/ci-builds fan this
+# out across the org against a candidate release.
 # ---------------------------------------------------------------------------
 
 on:
@@ -23,12 +22,12 @@ on:
   workflow_dispatch:
     inputs:
       jolt-version:
-        description: "jolt version to install (blank = the pinned JOLT_VERSION below)"
+        description: "jolt version to install (blank = nightly)"
         required: false
         default: ""
 
 env:
-  JOLT_VERSION: ${{ inputs.jolt-version || '0.8.2' }}
+  JOLT_VERSION: ${{ inputs.jolt-version || 'nightly' }}
 
 jobs:
   test:

From 26572fc7de0699cb900c3bd13a0383189944794a Mon Sep 17 00:00:00 2001
From: Yogthos <yogthos@gmail.com>
Date: Tue, 13 Oct 2026 16:38:17 -0400
Subject: [PATCH 2/2] Drop the CI note about the ebb-8nq.23 hang, which is
 closed

---
 .github/workflows/ci.yml | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index a69eec8..732176c 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -32,10 +32,9 @@ env:
 jobs:
   test:
     runs-on: ubuntu-latest
-    # A clean suite finishes in well under a minute. About one run in ten hangs
-    # instead, spinning every carrier (ebb-8nq.23), so expect intermittent red
-    # until that is closed. A low ceiling turns the hang into a fast failure
-    # rather than a job sitting on a runner until GitHub's 6-hour default.
+    # A clean suite finishes in well under a minute. A low ceiling turns a hang
+    # into a fast failure rather than a job sitting on a runner until GitHub's
+    # 6-hour default.
     timeout-minutes: 10
     steps:
       - uses: actions/checkout@v5