fix: give the generator its own venv on PATH

It shells out to ruff for post-processing. Finding none, it warns and
exits 0, and the warning gate reports that as a spec it could not parse
-- a clean regeneration on a runner without a global ruff failed with a
message pointing at the wrong thing entirely.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014f9oEEYspPH4fmPULTnLkJ

Author: chandrasekharan-zipstack

tools/gen_sdk.sh

@@ -14,6 +14,10 @@ set -euo pipefail
 
 REPO="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
 VENV="$REPO/.gen-venv"
+# The generator shells out to ruff for its own post-processing. Without this it
+# finds whatever ruff the caller happens to have, or none, and reports the miss
+# as a warning -- which the gate below reads as an unparsable spec.
+export PATH="$VENV/bin:$PATH"
 OUT="src/unstract/api_deployments/sdk_docstudio"
 # Pinned: unpinned, a generator upgrade and a spec change produce the same diff,
 # and the drift gate can no longer tell them apart.