Merge branch 'inlined.crf-deploy' into inlined.run-functions-exp

Author: inlined

.github/ISSUE_TEMPLATE/mcp.md

@@ -23,4 +23,4 @@ template_path=.github/ISSUE_TEMPLATE/mcp.md
 
 ### Steps to Reproduce
 
-<!-- write a detailed description of how to reproduce>
+<!-- write a detailed description of how to reproduce -->

.gitignore

@@ -27,3 +27,4 @@ scripts/*.json
 lib/
 dev/
 clean/
+.gemini/

.prettierignore

@@ -6,6 +6,7 @@
 /scripts/webframeworks-deploy-tests/angular/**
 /scripts/webframeworks-deploy-tests/nextjs/**
 /src/frameworks/docs/**
+/prompts
 
 # Intentionally invalid YAML file:
 /src/test/fixtures/extension-yamls/invalid/extension.yaml

CHANGELOG.md

@@ -1,2 +1,2 @@
-- Updated the Data Connect emulator to use pglite 0.3.x and Postgres 17, which fixes some crashes related to wire protocol inconsistencies. (#8679, #8658)
-- Fixed an issue where the IAM enablement for GenKit monitoring would try to change an invalid service account. (#8756)
+- Fixed ext:export command so that it correctly returns system params in the .env file (#8881)
+- Fixed an issue where the MCP server could not successfully use Application Default Credentials. (#8896)

GEMINI.md

@@ -0,0 +1,54 @@
+# GEMINI.md
+
+This file provides guidance to Gemini CLI or other coding agents when working with code in this repository. It focuses on key conventions and best practices. For a comprehensive guide on the development setup and contribution process, see [`CONTRIBUTING.md`](CONTRIBUTING.md).
+
+## Essential Commands
+
+```bash
+# Build the project
+npm run build
+
+# Link the package - once this is run, you can manually test changes in your terminal
+npm link
+
+npm test                         # Full test suite with linting and compilation
+npm run mocha:fast               # Quick unit tests only
+npx mocha {testfile}             # Quick unit test for a specific file
+
+# Linting and formatting
+npm run lint                     # Check all code
+npm run lint:changed-files       # Lint changed files only (much faster)
+npm run format                   # Auto-fix formatting issues
+```
+
+## Best Practices
+
+### Code Quality & Utilities
+
+- **Look for existing utilities first:** Before writing common helper functions (e.g., for logging, file system operations, promises, string manipulation), check `src/utils.ts` to see if a suitable function already exists.
+- **Use the central `logger`** (`src/logger.ts`); never use `console.log()` for user-facing output.
+- **Throw `FirebaseError`** (`src/error.ts`) for expected, user-facing errors.
+- **API calls must use `apiv2.ts`** for authenticated requests.
+
+### TypeScript
+
+- **Never use `any` or `unknown` as an escape hatch.** Define proper interfaces/types or use type guards.
+- Use strict null checks and handle `undefined`/`null` explicitly.
+
+### Testing
+
+- **Avoid excessive mocking in unit tests.** If a test requires many mocks, it might be better as an integration test in `/scripts/[feature]-tests/`.
+- **Unit tests (`*.spec.ts`) should be co-located with their source files.**
+- Test error cases and edge conditions, not just the "happy path."
+
+## Git Workflow & Pull Requests
+
+1.  **Lint and Test Before Committing:** Run `npm run lint:changed-files` for a quick check, and run the full `npm test` before submitting your PR to catch any issues.
+2.  **Structure Commit Messages for Pull Requests:** To streamline PR creation, format your commit messages to serve as both the commit and the PR description:
+    - **Subject Line:** A concise, imperative summary (e.g., `feat: add frobnicator support`). This will become the PR title.
+    - **Body:** After a blank line, structure the commit body to match the PR template. This will pre-populate the PR description. Include:
+      - `### Description`
+      - `### Scenarios Tested`
+      - `### Sample Commands`
+      - Reference issues with "Fixes #123" in the description.
+3.  **Update Changelog:** For any user-facing change (new features, bug fixes, deprecations), add a corresponding entry to `CHANGELOG.md`.

firebase-vscode/CHANGELOG.md

@@ -1,6 +1,23 @@
 ## NEXT
 
+## 1.6.0
+
+- Update internal `firebase-tools` dependency to 14.11.1
+- [Changed] Now integrates with GCA in its agentic mode, powered by the Gemini CLI. This brings the Firebase MCP Server directly into the VS Code environment, enabling developers to use natural language to generate application schemas and queries without manually invoking explicit tools.
+
+## 1.5.1
+
+- Update internal `firebase-tools` dependency to 14.11.0
+- [Fixed] Language server now properly recognizes nested Dataconnect folders
+- [Fixed] Add Data and Read Data now properly support enum and list types
+
+## 1.5.0
+
+- Update internal `firebase-tools` dependency to 14.9.0
+- Update internal `graphql-language-server` dependency
+- Update internal `graphql-language-service-server` dependency
 - [Changed] Graphql Syntax Highlighter is now an extension dependency
+- [Fixed] Language server now recognizes fragments in other files
 
 ## 1.4.1
 

firebase-vscode/common/messaging/protocol.ts

@@ -123,6 +123,10 @@ export interface WebviewToExtensionParamsMap {
 
   // called from execution panel
   rerunExecution: void;
+
+  /** Docs clicked for analytics */
+  "docs.mcp.clicked": void;
+  "docs.tos.clicked": void;
 }
 
 export interface DataConnectResults {