@@ -62,4 +62,18 @@ jobs:
         run: uv sync --extra dev --extra ${{ matrix.extra }}
 
       - name: Live integration test
-        run: uv run pytest -q -m requires_integrations ${{ matrix.test }}
+        run: |
+          set +e
+          uv run pytest -q -m requires_integrations ${{ matrix.test }}
+          rc=$?
+          set -e
+          # Exit 5 = pytest collected nothing because the module self-skipped:
+          # the framework installed but is unimportable under our pinned deps
+          # (e.g. an upstream release incompatible with our Pydantic v2). That is
+          # an upstream conflict, not an Unplug regression — surface it loudly but
+          # don't block. Real test failures (exit 1) still fail the job.
+          if [ "$rc" -eq 5 ]; then
+            echo "::warning title=Live integration skipped::${{ matrix.extra }} installed but its live tests were skipped (framework unimportable under current deps). Tolerated; not blocking."
+            exit 0
+          fi
+          exit $rc
@@ -102,6 +102,13 @@ uv run pytest -q -m requires_integrations tests/optional/live/
 > Unplug guard's decision (block on injection / destructive tool, allow benign), so they stay
 > hermetic and need no API keys.
 
+**Tolerated skips.** Each leg installs its framework, so a test that runs and fails is a real
+regression. But some optional frameworks ship releases that are unimportable under our pinned
+core deps (e.g. a `semantic-kernel` build that imports `Url` from `pydantic.networks`, removed
+in Pydantic v2). When that happens the module `importorskip`s, pytest exits `5` ("no tests
+ran"), and the job emits a non-blocking `::warning::` rather than failing — that is an upstream
+conflict, not an Unplug bug. Genuine test failures (exit `1`) still fail the job.
+
 ## CI markers
 
 | Marker | When |