@norskvideo/ctl-dev-kit 0.2.82 → 0.2.84

package/conventions/build-docs.yml

@@ -37,7 +37,7 @@ permissions:
 
 concurrency:
   group: build-docs-${{ github.ref }}
-  cancel-in-progress: true
+  cancel-in-progress: false
 
 jobs:
   build:

package/conventions/build-image.yml

@@ -57,7 +57,7 @@ permissions:
 
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
+  cancel-in-progress: false
 
 env:
   # The Docker Hub repo this product publishes to (norskvideo org, e.g.
@@ -530,9 +530,9 @@ jobs:
     # !cancelled(): a red deterministic gate must not hide the engine tier's
     # result. The plan's output is set before any guide runs.
     if: ${{ !cancelled() && needs.gate-guides.outputs.engine == 'run' }}
-    runs-on: arm
+    runs-on: x64
     # One engine-tier run per repo at a time, nightly (publish-docs.yml) and
-    # this alike: both launch the same instance ids on the arm pool's shared
+    # this alike: both launch the same instance ids on the x64 pool's shared
     # docker daemon, and ctl names each compose project after its instance id.
     # Queue, never cancel.
     concurrency:

package/conventions/integration.yml

@@ -34,13 +34,10 @@
 #
 # Runner selection is a one-entry matrix carrying a JSON label array, because a
 # string like '[ARM64, nvidia]' in runs-on is ONE label, not two. Default
-# '["arm"]' — the 256-core docker-outside-of-docker pool, where launched
-# containers are host siblings and the harness reaches them by compose name on
-# norsk-net (the topology step below says so in NORSK_TEST_HOST/NORSK_TEST_NET);
-# the GPU box is '["ARM64","nvidia"]'. Not the x64 pool: its runners share a
-# docker daemon on a box too small for two engine-tier jobs, whose instances
-# run outside the runner's cpuset, and pinned to that cpuset they no longer
-# fit (commentary's audio-timing checks, 2026-10-15).
+# '["x64"]' — the docker-outside-of-docker pool, where launched containers are
+# host siblings and the harness reaches them by compose name on norsk-net (the
+# topology step below says so in NORSK_TEST_HOST/NORSK_TEST_NET); the GPU box
+# is '["ARM64","nvidia"]'.
 #
 # On a pull request the suite runs for a BOT branch only (bump/nightly, and the
 # retired bots' upgrade-latest/*, sync-dev-kit/* and chore/sync-ctl-packages,
@@ -83,7 +80,9 @@ permissions:
 # leaves those groups exactly as they were), and do not cancel a dispatch run.
 # A superseded PENDING run is dropped before it starts, fires no
 # report-candidate, and scores nothing — which is why queueing is safe here
-# where cancelling is not. Pushes still cancel pushes.
+# where cancelling is not. Nothing cancels a run in progress
+# (no-cancel-in-progress.test.ts): a burst of pushes queues and collapses to
+# the newest pending run.
 #
 # Trade-off, stated: two candidates' validations can now overlap in one repo,
 # and their tiers derive host ports from the same per-slug bands. The bands were
@@ -91,7 +90,7 @@ permissions:
 # ephemeral daemon port is the durable answer and is not wired yet.
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}-${{ github.event_name }}-${{ github.event.client_payload.version }}
-  cancel-in-progress: ${{ github.event_name != 'repository_dispatch' }}
+  cancel-in-progress: false
 
 jobs:
   integration:
@@ -99,7 +98,7 @@ jobs:
     strategy:
       matrix:
         include:
-          - runner: '["arm"]'
+          - runner: '["x64"]'
     runs-on: ${{ fromJSON(matrix.runner) }}
     steps:
       # Runs BEFORE checkout, and does two things: points the harness's temp base

package/conventions/publish-docs.yml

@@ -44,11 +44,11 @@ permissions:
 
 concurrency:
   group: publish-docs-${{ github.ref }}
-  cancel-in-progress: true
+  cancel-in-progress: false
 
 jobs:
   publish:
-    runs-on: arm
+    runs-on: x64
     outputs:
       engine: ${{ steps.engine.outcome }}
     # One guide run per repo at a time, nightly and publish gate alike: both

package/conventions/smoke.yml

@@ -37,12 +37,14 @@ on:
 permissions:
   contents: read
 
-# Key the group on event_name so a push never cancels an in-flight ctl-candidate
-# validation: pushes cancel pushes, candidate validations cancel only newer
-# candidates. A cancelled validation would score as a red at release-collect.
+# Key the group on event_name so a push never queues behind an in-flight
+# ctl-candidate validation. Nothing cancels a run in progress
+# (no-cancel-in-progress.test.ts): a run queues, and GitHub keeps only the
+# newest pending one. A cancelled validation would score as a red at
+# release-collect.
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}-${{ github.event_name }}
-  cancel-in-progress: true
+  cancel-in-progress: false
 
 jobs:
   smoke:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@norskvideo/ctl-dev-kit",
-  "version": "0.2.82",
+  "version": "0.2.84",
   "type": "module",
   "exports": {
     "./create-product": "./create-product/create-product.ts",