fix: use synced openapi.json instead of downloading from production

The workflow was downloading openapi.json from production API, which caused it to skip publishing since the version was unchanged.

Now it uses the synced file from server repo first, only downloading from production as a fallback if the synced file is missing.

This fixes the chicken-and-egg problem where server changes weren't reflected in the SDK until they were deployed to production.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: esteininger

.github/workflows/sync-and-publish.yml

@@ -41,8 +41,16 @@ jobs:
           python -m pip install --upgrade pip
           pip install build twine setuptools wheel
       
-      - name: Download OpenAPI Spec
-        run: curl -s https://api.mixpeek.com/docs/openapi.json -o openapi.json
+      - name: Use synced OpenAPI Spec (or download as fallback)
+        run: |
+          if [ -f "openapi.json" ]; then
+            echo "✅ Using synced openapi.json from server repo"
+            echo "📄 File size: $(wc -c < openapi.json) bytes"
+          else
+            echo "⚠️  No synced openapi.json found, downloading from production..."
+            curl -s https://api.mixpeek.com/docs/openapi.json -o openapi.json
+            echo "📥 Downloaded from production API"
+          fi
       
       - name: Extract version from OpenAPI spec
         id: get-version