vybekiit 0.7.32 → 0.7.33

package/dist/global-skills/firebase-crashlytics/references/android_setup.md

@@ -1,14 +1,14 @@
 # Firebase Crashlytics - Android Setup Guide (Kotlin)
 
-This guide describes the SDK setup and basic usage patterns for
-Firebase Crashlytics in an Android app using
-Kotlin DSL (`build.gradle.kts`) and Kotlin code.
+This guide describes the SDK setup and basic usage patterns for Firebase
+Crashlytics in an Android app using Kotlin DSL (`build.gradle.kts`) and Kotlin
+code.
 
 ## Prerequisites
 
-IMPORTANT: Before specifically working with Firebase Crashlytics, make sure
-to use the skill and reference `firebase_basics/references/android_setup` to
-ensure the following is done.
+IMPORTANT: Before specifically working with Firebase Crashlytics, make sure to
+use the skill and reference `firebase_basics/references/android_setup` to ensure
+the following is done.
 
 - The Firebase CLI is available and authenticated.
 - An Android project exists and is registered with a Firebase Project.
@@ -20,9 +20,9 @@ ______________________________________________________________________
 ## 1. Add dependencies to Gradle build files
 
 > [!IMPORTANT] **[AGENT] RESOLVING THE SDK & PLUGIN VERSIONS DETERMINISTICALLY**
-> Never guess or hardcode a memorized out-of-date SDK or plugin version.
-> Before adding dependencies, you MUST query the latest available versions
-> directly from the Google Maven Repository:
+> Never guess or hardcode a memorized out-of-date SDK or plugin version. Before
+> adding dependencies, you MUST query the latest available versions directly
+> from the Google Maven Repository:
 >
 > ```bash
 > # Find the latest Firebase Android BoM version
@@ -62,30 +62,30 @@ plugins {
 
 ### Module (app-level) `build.gradle.kts` (`<project>/<app-module>/build.gradle.kts`)
 
-1.  Add the Crashlytics Gradle plugin to the `plugins` block:
+1. Add the Crashlytics Gradle plugin to the `plugins` block:
 
-    ```kotlin
-    plugins {
-        // ... other plugins
+   ```kotlin
+   plugins {
+       // ... other plugins
 
-        id("com.google.firebase.crashlytics")
-    }
-    ```
+       id("com.google.firebase.crashlytics")
+   }
+   ```
 
-2.  Add the Firebase Crashlytics dependency to the `dependencies` block:
+1. Add the Firebase Crashlytics dependency to the `dependencies` block:
 
-    ```kotlin
-    dependencies {
-        // ... other dependencies
+   ```kotlin
+   dependencies {
+       // ... other dependencies
 
-        // [AGENT] Fetch the latest resolved version using the Gradle command above
-        implementation(platform("com.google.firebase:firebase-bom:<latest_bom_version>"))
+       // [AGENT] Fetch the latest resolved version using the Gradle command above
+       implementation(platform("com.google.firebase:firebase-bom:<latest_bom_version>"))
 
-        // Add the dependency for the Firebase Crashlytics library
-        // When using the BoM, don't specify versions in Firebase library dependencies
-        implementation("com.google.firebase:firebase-crashlytics")
-    }
-    ```
+       // Add the dependency for the Firebase Crashlytics library
+       // When using the BoM, don't specify versions in Firebase library dependencies
+       implementation("com.google.firebase:firebase-crashlytics")
+   }
+   ```
 
 ______________________________________________________________________
 
@@ -96,38 +96,38 @@ native code, configure Crashlytics to report native crashes.
 
 App-level `build.gradle.kts` (`<project>/<app-module>/build.gradle.kts`)
 
-1.  Add the `firebase-crashlytics-ndk` dependency:
-
-    ```kotlin
-    dependencies {
-        // ... other dependencies
-
-        // [AGENT] Fetch the latest resolved version using the Gradle command above
-        implementation(platform("com.google.firebase:firebase-bom:<latest_bom_version>"))
-
-        // Add the dependency for the Firebase Crashlytics NDK library
-        // When using the BoM, don't specify versions in Firebase library dependencies
-        implementation("com.google.firebase:firebase-crashlytics-ndk")
-    }
-    ```
-
-2.  Enable the `nativeSymbolUpload` flag in the `buildTypes` configuration.
-    This will automatically upload symbol files for the native code, which are
-    required to symbolicate native crash reports.
-
-    ```kotlin
-    android {
-        // ... other config
-        buildTypes {
-            getByName("release") {
-                // ...
-                firebaseCrashlytics {
-                    nativeSymbolUploadEnabled = true
-                }
-            }
-        }
-    }
-    ```
+1. Add the `firebase-crashlytics-ndk` dependency:
+
+   ```kotlin
+   dependencies {
+       // ... other dependencies
+
+       // [AGENT] Fetch the latest resolved version using the Gradle command above
+       implementation(platform("com.google.firebase:firebase-bom:<latest_bom_version>"))
+
+       // Add the dependency for the Firebase Crashlytics NDK library
+       // When using the BoM, don't specify versions in Firebase library dependencies
+       implementation("com.google.firebase:firebase-crashlytics-ndk")
+   }
+   ```
+
+1. Enable the `nativeSymbolUpload` flag in the `buildTypes` configuration. This
+   will automatically upload symbol files for the native code, which are
+   required to symbolicate native crash reports.
+
+   ```kotlin
+   android {
+       // ... other config
+       buildTypes {
+           getByName("release") {
+               // ...
+               firebaseCrashlytics {
+                   nativeSymbolUploadEnabled = true
+               }
+           }
+       }
+   }
+   ```
 
 After these changes, Crashlytics will automatically report crashes in the app's
 native code.
@@ -139,38 +139,38 @@ ______________________________________________________________________
 To verify that Crashlytics is correctly set up in the Android project, force a
 test crash in the app.
 
-1.  Add code to the main activity (e.g., in `onCreate`) to trigger a crash a
-    few seconds after app startup:
+1. Add code to the main activity (e.g., in `onCreate`) to trigger a crash a few
+   seconds after app startup:
 
-    ```kotlin
-    import android.os.Handler
-    import android.os.Looper
+   ```kotlin
+   import android.os.Handler
+   import android.os.Looper
 
-    // ... in the Activity's onCreate method or similar startup logic
-    Handler(Looper.getMainLooper()).postDelayed({
-        throw RuntimeException("Test Crash") // Force a crash after 3 seconds
-    }, 3000)
-    ```
+   // ... in the Activity's onCreate method or similar startup logic
+   Handler(Looper.getMainLooper()).postDelayed({
+       throw RuntimeException("Test Crash") // Force a crash after 3 seconds
+   }, 3000)
+   ```
 
-2.  Run the app on a device or emulator. The app should crash after a short
-    delay.
+1. Run the app on a device or emulator. The app should crash after a short
+   delay.
 
-3.  Restart the app. The Crashlytics SDK will send the crash report to Firebase
-    on the next app launch.
+1. Restart the app. The Crashlytics SDK will send the crash report to Firebase
+   on the next app launch.
 
-4.  After a few minutes, the crash should be available in Firebase.
+1. After a few minutes, the crash should be available in Firebase.
 
-    - If the Firebase MCP server is installed, use the `get_report` tool to
-      verify that a crash was received.
-    - As a fallback, tell the human user to go to the Crashlytics dashboard in
-      the Firebase console to verify the new crash report. Provide the human
-      user with a constructed Firebase console URL using the Firebase PROJECT_ID
-      and the PACKAGE_NAME:
-      `https://console.firebase.google.com/u/0/project/PROJECT_ID/crashlytics/app/android:PACKAGE_NAME/issues`
+   - If the Firebase MCP server is installed, use the `get_report` tool to
+     verify that a crash was received.
+   - As a fallback, tell the human user to go to the Crashlytics dashboard in
+     the Firebase console to verify the new crash report. Provide the human user
+     with a constructed Firebase console URL using the Firebase PROJECT_ID and
+     the PACKAGE_NAME:
+     `https://console.firebase.google.com/u/0/project/PROJECT_ID/crashlytics/app/android:PACKAGE_NAME/issues`
 
-5.  After verifying that Firebase has received the crash report -- either using
-    the `get_report` tool or manually viewing it in the Firebase console --
-    remove the code that triggers the test crash.
+1. After verifying that Firebase has received the crash report -- either using
+   the `get_report` tool or manually viewing it in the Firebase console --
+   remove the code that triggers the test crash.
 
 ______________________________________________________________________
 

package/dist/global-skills/firebase-crashlytics/references/ios_setup.md

@@ -66,6 +66,7 @@ two options to be done manually.
 **For SwiftUI Apps (in `AppDelegate.swift`):**
 
 *File: `AppDelegate.swift`*
+
 ```swift
 import UIKit
 import FirebaseCore

package/dist/global-skills/firebase-data-connect/SKILL.md

@@ -2,6 +2,7 @@
 name: firebase-data-connect
 description: Builds and deploys Firebase SQL Connect (aka Firebase Data Connect) backends with PostgreSQL securely. Use when designing schemas with tables and relations, writing authorized queries and mutations, configuring real-time data updates, or generating type-safe SDKs. Use when you need a relational database with Firebase, or when the user mentions SQL Connect or Data Connect.
 metadata:
+  author: Google LLC
   category: Databases
 disable-model-invocation: true
 ---

package/dist/global-skills/firebase-data-connect/reference/config.md

@@ -47,15 +47,15 @@ schema:
 connectorDirs: ["./connector"]
 ```
 
-| Field               | Description                                                                              |
-| ------------------- | ---------------------------------------------------------------------------------------- |
-| `specVersion`       | Always `"v1"`                                                                            |
-| `serviceId`         | Unique identifier for the service                                                        |
-| `location`          | GCP region (us-central1, us-east4, europe-west1, etc.)                                   |
+| Field                                           | Description                                                                              |
+| ----------------------------------------------- | ---------------------------------------------------------------------------------------- |
+| `specVersion`                                   | Always `"v1"`                                                                            |
+| `serviceId`                                     | Unique identifier for the service                                                        |
+| `location`                                      | GCP region (us-central1, us-east4, europe-west1, etc.)                                   |
 | `schema.datasource.postgresql.schemaValidation` | Deployment mode: `"STRICT"` (must match exactly) or `"COMPATIBLE"` (backward compatible) |
-| `schema.source`     | Path to schema directory                                                                 |
-| `schema.datasource` | PostgreSQL connection config                                                             |
-| `connectorDirs`     | List of connector directories                                                            |
+| `schema.source`                                 | Path to schema directory                                                                 |
+| `schema.datasource`                             | PostgreSQL connection config                                                             |
+| `connectorDirs`                                 | List of connector directories                                                            |
 
 ### Cloud SQL Configuration
 

package/dist/global-skills/firebase-data-connect/reference/realtime.md

@@ -23,7 +23,10 @@ based on what you're querying:
 List queries require explicit `@refresh` to tell SQL Connect which mutations
 affect the result set.
 
-Clients consume all three using `subscribe()` instead of `execute()`. See [sdk_web.md](sdk_web.md), [sdk_android.md](sdk_android.md), [sdk_ios.md](sdk_ios.md), and [sdk_flutter.md](sdk_flutter.md) for per-platform subscribe patterns.
+Clients consume all three using `subscribe()` instead of `execute()`. See
+[sdk_web.md](sdk_web.md), [sdk_android.md](sdk_android.md),
+[sdk_ios.md](sdk_ios.md), and [sdk_flutter.md](sdk_flutter.md) for per-platform
+subscribe patterns.
 
 ______________________________________________________________________
 

package/dist/global-skills/firebase-data-connect/reference/sdk_android.md

@@ -1,14 +1,13 @@
 # Firebase SQL Connect - Android Setup Guide (Kotlin)
 
-This guide describes the SDK setup and basic usage patterns for
-Firebase SQL Connect in an Android app using
-Kotlin DSL (`build.gradle.kts`) and Kotlin code.
+This guide describes the SDK setup and basic usage patterns for Firebase SQL
+Connect in an Android app using Kotlin DSL (`build.gradle.kts`) and Kotlin code.
 
 ## Prerequisites
 
-IMPORTANT: Before specifically working with Firebase SQL Connect, make sure
-to use the skill and reference `firebase_basics/references/android_setup` to
-ensure the following is done.
+IMPORTANT: Before specifically working with Firebase SQL Connect, make sure to
+use the skill and reference `firebase_basics/references/android_setup` to ensure
+the following is done.
 
 - The Firebase CLI is available and authenticated.
 - An Android project exists and is registered with a Firebase Project.
@@ -35,10 +34,10 @@ ______________________________________________________________________
 
 ## 1. Add dependencies to Gradle build files
 
-> [!IMPORTANT] **[AGENT] RESOLVING THE SDK VERSION DETERMINISTICALLY**
-> Never guess or hardcode a memorized out-of-date SDK or plugin version.
-> Before adding dependencies, you MUST query the latest available versions
-> directly from the Google Maven Repository:
+> [!IMPORTANT] **[AGENT] RESOLVING THE SDK VERSION DETERMINISTICALLY** Never
+> guess or hardcode a memorized out-of-date SDK or plugin version. Before adding
+> dependencies, you MUST query the latest available versions directly from the
+> Google Maven Repository:
 >
 > ```bash
 > # Find the latest Firebase Android BoM version
@@ -56,37 +55,37 @@ ______________________________________________________________________
 > ```
 
 In the **module (app-level)** `build.gradle.kts` (usually
-`<project>/<app-module>/build.gradle.kts`), add the
-Kotlin serialization plugin and the dependency for Firebase SQL Connect:
+`<project>/<app-module>/build.gradle.kts`), add the Kotlin serialization plugin
+and the dependency for Firebase SQL Connect:
 
-1.  Add the Kotlin serialization plugin to the `plugins` block:
+1. Add the Kotlin serialization plugin to the `plugins` block:
 
-    ```kotlin
-    plugins {
-        // ... other plugins
-        kotlin("plugin.serialization") version "1.8.22" // Must match Kotlin version
-    }
-    ```
+   ```kotlin
+   plugins {
+       // ... other plugins
+       kotlin("plugin.serialization") version "1.8.22" // Must match Kotlin version
+   }
+   ```
 
-2.  Add the required Firebase SQL Connect dependencies to the `dependencies`
-    block:
+1. Add the required Firebase SQL Connect dependencies to the `dependencies`
+   block:
 
-    ```kotlin
-    dependencies {
-        // ... other dependencies
+   ```kotlin
+   dependencies {
+       // ... other dependencies
 
-        // [AGENT] Fetch the latest resolved version using the Gradle command above
-        implementation(platform("com.google.firebase:firebase-bom:<latest_bom_version>"))
+       // [AGENT] Fetch the latest resolved version using the Gradle command above
+       implementation(platform("com.google.firebase:firebase-bom:<latest_bom_version>"))
 
-        // Add the dependency for the Firebase SQL Connect library
-        // When using the BoM, don't specify versions in Firebase library dependencies
-        implementation("com.google.firebase:firebase-dataconnect")
+       // Add the dependency for the Firebase SQL Connect library
+       // When using the BoM, don't specify versions in Firebase library dependencies
+       implementation("com.google.firebase:firebase-dataconnect")
 
-        // Add additional required dependencies
-        implementation("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.7.3")
-        implementation("org.jetbrains.kotlinx:kotlinx-serialization-core:1.5.1")
-    }
-    ```
+       // Add additional required dependencies
+       implementation("org.jetbrains.kotlinx:kotlinx-coroutines-core:1.7.3")
+       implementation("org.jetbrains.kotlinx:kotlinx-serialization-core:1.5.1")
+   }
+   ```
 
 ______________________________________________________________________
 

package/dist/global-skills/firebase-data-connect/reference/sdk_web.md

@@ -106,9 +106,14 @@ await executeQuery(queryRef, { fetchPolicy: QueryFetchPolicy.SERVER_ONLY });
 
 ### Subscriptions (Realtime)
 
-Use `subscribe()` to receive live updates. It accepts either an observer object (`SubscriptionOptions`) or positional callbacks:
-
-> **Note:** When passing an observer object literal, the error callback property is named **`onErr`** (`{ onNext, onErr, onComplete }`). Passing `onError` in an object literal fails TypeScript compilation (`TS2769`) and is ignored at runtime. The name `onError` is only used as the parameter name in the positional callback overload (`subscribe(ref, onNext, onError, onComplete)`).
+Use `subscribe()` to receive live updates. It accepts either an observer object
+(`SubscriptionOptions`) or positional callbacks:
+
+> **Note:** When passing an observer object literal, the error callback property
+> is named **`onErr`** (`{ onNext, onErr, onComplete }`). Passing `onError` in
+> an object literal fails TypeScript compilation (`TS2769`) and is ignored at
+> runtime. The name `onError` is only used as the parameter name in the
+> positional callback overload (`subscribe(ref, onNext, onError, onComplete)`).
 
 #### Web (Vanilla JS / TypeScript)
 

package/dist/global-skills/firebase-data-connect/reference/security.md

@@ -32,13 +32,13 @@ ______________________________________________________________________
 
 ## Access Levels
 
-| Level                 | Who Can Access                               | CEL Equivalent                                                           |
-| --------------------- | -------------------------------------------- | ------------------------------------------------------------------------ |
-| `PUBLIC`              | Anyone, authenticated or not                 | `true`                                                                   |
-| `USER_ANON`           | Any authenticated user (including anonymous) | `auth != null`                                                           |
-| `USER`                | Authenticated users (excludes anonymous)     | `auth != null && auth.token.firebase.sign_in_provider != 'anonymous'`    |
-| `USER_EMAIL_VERIFIED` | Users with verified email                    | `auth != null && auth.token.email_verified`                              |
-| `NO_ACCESS`           | Admin SDK only                               | `false`                                                                  |
+| Level                 | Who Can Access                               | CEL Equivalent                                                        |
+| --------------------- | -------------------------------------------- | --------------------------------------------------------------------- |
+| `PUBLIC`              | Anyone, authenticated or not                 | `true`                                                                |
+| `USER_ANON`           | Any authenticated user (including anonymous) | `auth != null`                                                        |
+| `USER`                | Authenticated users (excludes anonymous)     | `auth != null && auth.token.firebase.sign_in_provider != 'anonymous'` |
+| `USER_EMAIL_VERIFIED` | Users with verified email                    | `auth != null && auth.token.email_verified`                           |
+| `NO_ACCESS`           | Admin SDK only                               | `false`                                                               |
 
 > **Important:** Levels like `USER` are starting points. Always add filters or
 > expressions to verify the user can access specific data.
@@ -49,12 +49,12 @@ ______________________________________________________________________
 
 ### Available Bindings
 
-| Binding                 | Description                                |
-| ----------------------- | ------------------------------------------ |
-| `auth.uid`              | Current user's Firebase UID                |
-| `auth.token`            | Auth token claims (see below)              |
-| `vars`                  | Operation variables (e.g., `vars.movieId`) |
-| `request.time`          | Server timestamp                           |
+| Binding                 | Description                                                       |
+| ----------------------- | ----------------------------------------------------------------- |
+| `auth.uid`              | Current user's Firebase UID                                       |
+| `auth.token`            | Auth token claims (see below)                                     |
+| `vars`                  | Operation variables (e.g., `vars.movieId`)                        |
+| `request.time`          | Server timestamp                                                  |
 | `request.operationName` | Name of the GraphQL operation being executed (e.g., `"GetMovie"`) |
 
 ### auth.token Fields

package/dist/global-skills/firebase-firestore/SKILL.md

@@ -4,16 +4,23 @@ description: >-
   Sets up, manages, queries, and configures Cloud Firestore databases (Standard/Enterprise edition), including data modeling, security rules, indexes, and SDK integrations (Web, Python, iOS, Android, Flutter). Use when creating/listing Firestore databases, defining data models/indexes, writing SDK queries, or integrating Firestore SDKs. For authoring or modifying Firestore Security Rules (firestore.rules), delegate to the firestore-rules-author subagent if subagent delegation is available, or use firestore-rules-creation otherwise. Don't use for Firebase Hosting, Data Connect, Auth, Storage/GCS, Crashlytics, Functions, or BigQuery.
 compatibility: This skill is best used with the Firebase CLI, but does not require it. Firebase CLI can be accessed through `npx -y firebase-tools@latest`.
 metadata:
+  author: Google LLC
   category: Databases
 disable-model-invocation: true
 ---
 
 # Cloud Firestore Database and Operations
 
-> [!IMPORTANT] **Security Rules Authoring (`firestore.rules`)**
-> Whenever your task requires creating, authoring, or modifying `firestore.rules`:
-> - **If subagent delegation AND the `firestore-rules-author` subagent are available**: delegate authoring `firestore.rules` to the `firestore-rules-author` subagent rather than writing `firestore.rules` directly in the main agent.
-> - **If subagent delegation is unavailable** (e.g., subagents not enabled in the IDE) **OR `firestore-rules-author` is not installed**: read and follow the `firestore-rules-creation` skill to write `firestore.rules` directly.
+> [!IMPORTANT] **Security Rules Authoring (`firestore.rules`)** Whenever your
+> task requires creating, authoring, or modifying `firestore.rules`:
+>
+> - **If subagent delegation AND the `firestore-rules-author` subagent are
+>   available**: delegate authoring `firestore.rules` to the
+>   `firestore-rules-author` subagent rather than writing `firestore.rules`
+>   directly in the main agent.
+> - **If subagent delegation is unavailable** (e.g., subagents not enabled in
+>   the IDE) **OR `firestore-rules-author` is not installed**: read and follow
+>   the `firestore-rules-creation` skill to write `firestore.rules` directly.
 
 Before setting up dependencies, writing data models, or configuring security
 rules, you MUST always identify the Firestore instance edition.
@@ -30,12 +37,15 @@ npx -y firebase-tools@latest firestore:databases:list
 
 1. For each database found, inspect its edition and details:
 
-    ```bash
-    npx -y firebase-tools@latest firestore:databases:get <database-id>
-    ```
+   ```bash
+   npx -y firebase-tools@latest firestore:databases:get <database-id>
+   ```
+
 1. Ask the user which database instance they wish to target or if they would
    prefer to create a new instance.
+
 1. Once the target instance is established:
+
    - If the **`edition`** is `STANDARD`, follow the guides under
      `references/standard/`.
    - If the **`edition`** is `ENTERPRISE` or native mode, follow the guides

package/dist/global-skills/firebase-firestore/references/enterprise/android_sdk_usage.md

@@ -1,14 +1,14 @@
 # Cloud Firestore (Enterprise edition) - Android Setup Guide (Kotlin)
 
-This guide describes the SDK setup and basic usage patterns for
-Cloud Firestore (Enterprise edition in Native mode) in an Android app using
-Kotlin DSL (`build.gradle.kts`) and Kotlin code.
+This guide describes the SDK setup and basic usage patterns for Cloud Firestore
+(Enterprise edition in Native mode) in an Android app using Kotlin DSL
+(`build.gradle.kts`) and Kotlin code.
 
 ## Prerequisites
 
-IMPORTANT: Before specifically working with Cloud Firestore, make sure
-to use the skill and reference `firebase_basics/references/android_setup` to
-ensure the following is done.
+IMPORTANT: Before specifically working with Cloud Firestore, make sure to use
+the skill and reference `firebase_basics/references/android_setup` to ensure the
+following is done.
 
 - The Firebase CLI is available and authenticated.
 - An Android project exists and is registered with a Firebase Project.
@@ -33,10 +33,10 @@ ______________________________________________________________________
 
 ## 2. Add dependencies to Gradle build files
 
-> [!IMPORTANT] **[AGENT] RESOLVING THE SDK VERSION DETERMINISTICALLY**
-> Never guess or hardcode a memorized out-of-date SDK or plugin version.
-> Before adding dependencies, you MUST query the latest available versions
-> directly from the Google Maven Repository:
+> [!IMPORTANT] **[AGENT] RESOLVING THE SDK VERSION DETERMINISTICALLY** Never
+> guess or hardcode a memorized out-of-date SDK or plugin version. Before adding
+> dependencies, you MUST query the latest available versions directly from the
+> Google Maven Repository:
 >
 > ```bash
 > # Find the latest Firebase Android BoM version
@@ -54,8 +54,8 @@ ______________________________________________________________________
 > ```
 
 In the **module (app-level)** `build.gradle.kts` (usually
-`<project>/<app-module>/build.gradle.kts`), add the dependency for
-Cloud Firestore:
+`<project>/<app-module>/build.gradle.kts`), add the dependency for Cloud
+Firestore:
 
 ```kotlin
 dependencies {
@@ -113,26 +113,26 @@ ______________________________________________________________________
 
 ### Strict rules & accountability
 
-1.  **Mandatory Execution Engine**: Every repository lookup requiring related
-    data mapping, textual relevance scoring, or multi-document counting MUST be
-    authored natively using the server-side `db.pipeline()` API.
-1.  **Required Proof of Use**: In your task execution summaries, you MUST
-    explicitly highlight the exact pipeline stages (`.define()`, `.addFields()`,
-    `.search()`, `.aggregate()`) integrated into your primary data layer return
-    paths. Failure to implement pipelines natively constitutes an immediate
-    violation of instructions.
-1.  **Check API References**:
-    - **Locate**: Locate the standard Maven sources JAR (`-sources.jar`)
-      corresponding to the resolved `firebase-firestore` dependency version
-      inside your local Gradle or Maven dependency cache.
-    - **Extract Once**: Extract the documentation files `pipeline.docs.txt` and
-      `expressions.docs.txt` from the root directory of that `-sources.jar`
-      archive into a temporary workspace scratch directory of your choice.
-    - **Read & Reference**:
-      - **Read** the extracted `pipeline.docs.txt` once fully to understand core
-        pipeline structure and stage capabilities.
-      - **Reference** the extracted `expressions.docs.txt` on-demand for
-        specific function overloads and parameters.
+1. **Mandatory Execution Engine**: Every repository lookup requiring related
+   data mapping, textual relevance scoring, or multi-document counting MUST be
+   authored natively using the server-side `db.pipeline()` API.
+1. **Required Proof of Use**: In your task execution summaries, you MUST
+   explicitly highlight the exact pipeline stages (`.define()`, `.addFields()`,
+   `.search()`, `.aggregate()`) integrated into your primary data layer return
+   paths. Failure to implement pipelines natively constitutes an immediate
+   violation of instructions.
+1. **Check API References**:
+   - **Locate**: Locate the standard Maven sources JAR (`-sources.jar`)
+     corresponding to the resolved `firebase-firestore` dependency version
+     inside your local Gradle or Maven dependency cache.
+   - **Extract Once**: Extract the documentation files `pipeline.docs.txt` and
+     `expressions.docs.txt` from the root directory of that `-sources.jar`
+     archive into a temporary workspace scratch directory of your choice.
+   - **Read & Reference**:
+     - **Read** the extracted `pipeline.docs.txt` once fully to understand core
+       pipeline structure and stage capabilities.
+     - **Reference** the extracted `expressions.docs.txt` on-demand for specific
+       function overloads and parameters.
 
 ______________________________________________________________________
 

package/dist/global-skills/firebase-firestore/references/enterprise/indexes.md

@@ -53,7 +53,8 @@ create index entries with duplicate values.
   - Index Required: **Composite Index** on field `a` and `b`
 - **Multiple Ranges**: `where("a", ">", 1).where("b", ">", 2)`
   - Index Required: **Composite Index** on field `a` and `b`
-- **Array Contains + Equality**: `where("tags", "array-contains", "news").where("active", "==", true)`
+- **Array Contains + Equality**:
+  `where("tags", "array-contains", "news").where("active", "==", true)`
   - Index Required: **Composite Index** on field `tags` and `active`
 
 If no indexes is present, Firestore Enterprise will perform a full collection