chore(repo): other references to client libraries

Author: mandarini

.cursorrules

@@ -1,6 +1,6 @@
 # Cursor Rules for Supabase JS Libraries Monorepo
 
-You are working in a unified Nx monorepo that consolidates all Supabase JavaScript client libraries. This migration from 6 separate repositories addresses maintenance overhead, dependency duplication, and release coordination challenges.
+You are working in a unified Nx monorepo that consolidates all Supabase JavaScript SDKs. This migration from 6 separate repositories addresses maintenance overhead, dependency duplication, and release coordination challenges.
 
 ## Repository Context
 

CLAUDE.md

@@ -1,6 +1,6 @@
 # Claude AI Instructions for Supabase JS Libraries Monorepo
 
-You are assisting with development in a unified Nx monorepo that consolidates all Supabase JavaScript client libraries, built with Nx for optimal developer experience and maintainability. This strategic migration from 6 separate repositories addresses critical maintenance overhead, dependency duplication, and release coordination challenges while maintaining **zero breaking changes** for consumers.
+You are assisting with development in a unified Nx monorepo that consolidates all Supabase JavaScript SDKs, built with Nx for optimal developer experience and maintainability. This strategic migration from 6 separate repositories addresses critical maintenance overhead, dependency duplication, and release coordination challenges while maintaining **zero breaking changes** for consumers.
 
 > **📚 Essential Documentation**: Always refer to these guides for detailed information:
 >
@@ -777,4 +777,4 @@ _No user-facing changes in this release._
 - Unchanged packages show "No user-facing changes"
 - Single npm install updates entire SDK suite
 
-Remember: This monorepo optimizes for developer experience and maintenance efficiency while ensuring zero breaking changes for the millions of developers using Supabase client libraries.
+Remember: This monorepo optimizes for developer experience and maintenance efficiency while ensuring zero breaking changes for the millions of developers using Supabase SDKs.

docs/MIGRATION.md

@@ -325,7 +325,7 @@ Use these names with Nx commands:
 - `postgrest-js` - PostgREST library
 - `realtime-js` - Realtime library
 - `storage-js` - Storage library
-- `supabase-js` - Main client library
+- `supabase-js` - Main SDK
 
 ### Useful New Commands
 

packages/core/auth-js/src/lib/error-codes.ts

@@ -1,6 +1,6 @@
 /**
  * Known error codes. Note that the server may also return other error codes
- * not included in this list (if the client library is older than the version
+ * not included in this list (if the SDK is older than the version
  * on the server).
  */
 export type ErrorCode =

packages/core/postgrest-js/README.md

@@ -188,7 +188,7 @@ It performs these steps:
 - **Port 3000** - PostgREST server (API)
 - **Port 8080** - Database schema endpoint (for type generation)
 
-**Note:** Unlike a full Supabase instance, this uses a minimal PostgREST setup specifically for testing the client library.
+**Note:** Unlike a full Supabase instance, this uses a minimal PostgREST setup specifically for testing the SDK.
 
 ### Contributing
 

packages/core/supabase-js/src/lib/types.ts

@@ -97,9 +97,9 @@ export type SupabaseClientOptions<SchemaName> = {
   /**
    * Optional function for using a third-party authentication system with
    * Supabase. The function should return an access token or ID token (JWT) by
-   * obtaining it from the third-party auth client library. Note that this
+   * obtaining it from the third-party auth SDK. Note that this
    * function may be called concurrently and many times. Use memoization and
-   * locking techniques if this is not supported by the client libraries.
+   * locking techniques if this is not supported by the SDKs.
    *
    * When set, the `auth` namespace of the Supabase client cannot be used.
    * Create another client if you wish to use Supabase Auth and third-party