docs(runtime): separate pi dependency boundary

src/main/connector-definitions/apikey.ts

@@ -1,8 +1,8 @@
 /**
  * API-key pi-mono connectors.
  *
- * Each entry maps to a pi-ai `KnownProvider` (see
- * `pi-mono-reference/packages/ai/src/env-api-keys.ts`) — except for the two
+ * Each entry maps to a pi-ai `KnownProvider` from the pinned
+ * `@mariozechner/pi-ai` runtime, except for the two
  * Fireworks entries, which are resolved locally in `src/main/model-resolver.ts`.
  *
  * `envKey` is the standard environment variable pi-mono reads when no

src/main/connector-definitions/cloud.ts

@@ -4,7 +4,7 @@
  * Cloud providers have bespoke credential discovery — multi-variable AWS /
  * Azure setups, or gcloud Application Default Credentials for Vertex. The
  * `auth.type` marker tells the credential resolver which discovery path to
- * run (see `pi-mono-reference/packages/ai/src/env-api-keys.ts`).
+ * run in the pinned `@mariozechner/pi-ai` runtime.
  */
 
 import type { ConnectorDefinition } from "../connector-definitions";

src/main/connector-definitions/oauth.ts

@@ -1,8 +1,8 @@
 /**
  * OAuth-based pi-mono connectors.
  *
- * Each entry targets one of the five built-in pi-ai OAuth providers
- * (see `pi-mono-reference/packages/ai/src/utils/oauth/index.ts`). The
+ * Each entry targets one of the five built-in OAuth providers from the
+ * pinned `@mariozechner/pi-ai` runtime. The
  * runtime opens the provider's browser auth flow, stores the refreshed
  * token in the `credentials` table, and passes it as the API key when
  * invoking pi-ai.