@norskvideo/ctl-dev-kit 0.1.88 → 0.1.90

package/conventions/smoke.yml

@@ -264,6 +264,9 @@ jobs:
           NORSK_CTL_BINARY: ${{ runner.temp }}/norsk-ctl
           NORSK_LICENSE_FILE: ${{ runner.temp }}/norsk-license.json
         run: |
+          # Outer pipefail so the step reports the journey's exit, not tee's --
+          # otherwise a failed smoke run over the `| tee` below scores green.
+          set -euo pipefail
           nix develop .#build --command bash -c '
             set -euo pipefail
             # A frozen install does not reliably relink a hoisted package whose
@@ -279,7 +282,22 @@ jobs:
             echo "smoke image: $IMAGE_TAG"
             bun run build:image
             SMOKE_IMAGE_TAG="$IMAGE_TAG" bun run test:smoke
-          '
+          ' 2>&1 | tee "$RUNNER_TEMP/smoke.log"
+
+      # We pretty much always want the Norsk logs from a smoke run: the journey
+      # runs the RELEASED media + studio images, and the harness dumps each
+      # launched instance's container logs (diagnose hook) into the run output
+      # at a failure -- but the containers are gone after teardown, so those
+      # internals only survive if the run log is persisted. Upload it so the
+      # engine's own log is downloadable, not buried in the step output.
+      # always() so a red run keeps its evidence.
+      - name: Upload smoke run log
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: smoke-log-attempt-${{ github.run_attempt }}
+          path: ${{ runner.temp }}/smoke.log
+          retention-days: 7
 
   # Report this pipeline's result to the aggregated product CI dashboard
   # (id3as/ci-workflows). !cancelled() so a real pass/fail reports, but a

package/package.json

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

package/testing/INVARIANTS.customer.template.md

@@ -25,13 +25,13 @@ way resolved defaults (segment durations, as-rendered resolutions, output count)
 are guarded too, not only literal fields. When a code comment carries one of
 these rules, cite the ID there too instead of restating the rule.
 
-| ID               | Invariant                                                                                                     | Guarded by                       |
-| ---------------- | ------------------------------------------------------------------------------------------------------------- | -------------------------------- |
-| INV-PLAYLIST-001 | This customer serves legacy playlists only — every composed CMAF playlist is non-low-latency, never LL-HLS    | `<slug>/<slug>-invariants.test.ts` |
-| INV-SEG-001      | CMAF segment duration is 4s on every rendition (a resolved default — only guardable via the composed graph)   | `<slug>/<slug>-invariants.test.ts` |
-| INV-OUT-001      | Exactly three delivery rungs in a single named CMAF group, one playlist per rung                              | `<slug>/<slug>-invariants.test.ts` |
-| INV-RES-001      | The delivery resolutions are exactly the ladder the customer signed off (e.g. 1280x720 / 640x360 / 320x180)   | `<slug>/<slug>-invariants.test.ts` |
-| INV-MOQ-001      | The low-latency return / monitor rides MoQ, never a WHIP/RTMP fallback                                        | `<slug>/<slug>-invariants.test.ts` |
+| ID               | Invariant                                                                                                   | Guarded by                         |
+| ---------------- | ----------------------------------------------------------------------------------------------------------- | ---------------------------------- |
+| INV-PLAYLIST-001 | This customer serves legacy playlists only — every composed CMAF playlist is non-low-latency, never LL-HLS  | `<slug>/<slug>-invariants.test.ts` |
+| INV-SEG-001      | CMAF segment duration is 4s on every rendition (a resolved default — only guardable via the composed graph) | `<slug>/<slug>-invariants.test.ts` |
+| INV-OUT-001      | Exactly three delivery rungs in a single named CMAF group, one playlist per rung                            | `<slug>/<slug>-invariants.test.ts` |
+| INV-RES-001      | The delivery resolutions are exactly the ladder the customer signed off (e.g. 1280x720 / 640x360 / 320x180) | `<slug>/<slug>-invariants.test.ts` |
+| INV-MOQ-001      | The low-latency return / monitor rides MoQ, never a WHIP/RTMP fallback                                      | `<slug>/<slug>-invariants.test.ts` |
 
 The rows above are worked examples (drawn from the datum commentary deployment);
 delete them when seeding a new customer.