From 49c3bcf0a583da107d77dc64008e86d72e43a6d9 Mon Sep 17 00:00:00 2001
From: frostebite <jas.f.ukcmti@gmail.com>
Date: Sat, 7 Mar 2026 02:35:16 +0000
Subject: [PATCH] fix(ci): restore missing k3d cluster step in
 orchestrator-integrity

A mangled comment merged the "Create k3d cluster" step header with
the previous yarn install step, causing a duplicate `run` key that
prevented the entire Integrity workflow from loading.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---
 .github/workflows/orchestrator-integrity.yml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/orchestrator-integrity.yml b/.github/workflows/orchestrator-integrity.yml
index 8a6a1a71..f64bb7c4 100644
--- a/.github/workflows/orchestrator-integrity.yml
+++ b/.github/workflows/orchestrator-integrity.yml
@@ -221,7 +221,9 @@ jobs:
           fi
 
       - run: yarn install --frozen-lockfile
-      # ===================================        timeout-minutes: 5
+
+      - name: Create k3d cluster
+        timeout-minutes: 5
         run: |
           LOCALSTACK_IP=$(docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' localstack-main 2>/dev/null || echo "")
           echo "LocalStack container IP: $LOCALSTACK_IP"