Update to Firebase

{
  "name": "firebase-app-hosting-basics",
  "description": "Deploys and manages full-stack web applications (Next.js, Angular) with Server-Side Rendering (SSR) using Firebase App Hosting. Use when deploying Next.js/Angular apps, configuring apphosting.yaml or firebase.json apphosting blocks, managing secrets, setting up GitHub CI/CD, or configuring Blaze billing requirements. Don't use for classic static web hosting, Auth, Firestore, Crashlytics, or Xcode.",
  "included_files": [
    {
      "relative_path": "references/cli_commands.md",
      "size_in_bytes": 3217
    },
    {
      "relative_path": "references/configuration.md",
      "size_in_bytes": 1742
    },
    {
      "relative_path": "references/emulation.md",
      "size_in_bytes": 1493
    }
  ],
  "skill_md_contents": "---\nname: firebase-app-hosting-basics\ndescription: >-\n  Deploys and manages full-stack web applications (Next.js, Angular) with Server-Side Rendering (SSR) using Firebase App Hosting. Use when deploying Next.js/Angular apps, configuring apphosting.yaml or firebase.json apphosting blocks, managing secrets, setting up GitHub CI/CD, or configuring Blaze billing requirements. Don't use for classic static web hosting, Auth, Firestore, Crashlytics, or Xcode.\nmetadata:\n  category: Serverless\n---\n\n# App Hosting Basics\n\n## Description\n\nThis skill enables the agent to deploy and manage modern, full-stack web\napplications (Next.js, Angular, etc.) using Firebase App Hosting.\n\n**Important**: In order to use App Hosting, your Firebase project must be on the\nBlaze pricing plan. Direct the user to\nhttps://console.firebase.google.com/project/_/overview?purchaseBillingPlan=metered\nto upgrade their plan.\n\n## Hosting vs App Hosting\n\n**Choose Firebase Hosting if:**\n\n- You are deploying a static site (HTML/CSS/JS).\n- You are deploying a simple SPA (React, Vue, etc. without SSR).\n- You want full control over the build and deploy process via CLI.\n\n**Choose Firebase App Hosting if:**\n\n- You are using a supported full-stack framework like Next.js or Angular.\n- You need Server-Side Rendering (SSR) or ISR.\n- You want an automated \"git push to deploy\" workflow with zero configuration.\n\n## Deploying to App Hosting\n\n### Deploy from Source\n\nThis is the recommended flow for most users.\n\n1. Configure `firebase.json` with an `apphosting` block.\n   \n   ```json\n   {\n     \"apphosting\": {\n       \"backendId\": \"my-app-id\",\n       \"rootDir\": \"/\",\n       \"ignore\": [\n         \"node_modules\",\n         \".git\",\n         \"firebase-debug.log\",\n         \"firebase-debug.*.log\",\n         \"functions\"\n       ]\n     }\n   }\n   ```\n1. Create or edit `apphosting.yaml`- see\n   [Configuration](references/configuration.md) for more information on how to\n   do so.\n1. If the app needs safe access to sensitive keys, use\n   `npx -y firebase-tools@latest apphosting:secrets` commands to set and grant\n   access to secrets.\n1. Run `npx -y firebase-tools@latest deploy` when you are ready to deploy.\n\n### Automated deployment via GitHub (CI/CD)\n\nAlternatively, set up a backend connected to a GitHub repository for automated\ndeployments \"git push\" deployments. This is only recommended for more advanced\nusers, and is not required to use App Hosting. See\n[CLI Commands](references/cli_commands.md) for more information on how to set\nthis up using CLI commands.\n\n## Emulation\n\nSee [Emulation](references/emulation.md) for more information on how to test\nyour app locally using the Firebase Local Emulator Suite.\n"
}