Firebase Hosting and Configuration

Use this when Firebase Hosting, Google Cloud permissions, Firebase project wiring, or related app/site/documentation configuration is failing or inconsistent.

Procedure

1. Pin down the affected surface: Flutter app, Firebase Hosting site, Google Cloud project/API, CI deployment, or user-facing copy. Start with the exact error or requested change.
2. Inspect the repository's Firebase configuration, relevant workflow, app configuration, and documentation together. Compare project IDs, hosting targets, enabled services, and deployment triggers; do not assume similarly named projects or environments are interchangeable.
3. For a permission error, identify the caller, API, and required permission from the error. Separate local credentials from CI identity and explain the minimum permission needed. Do not grant IAM roles, enable paid services, or change cloud resources without explicit authorization.
4. For text or configuration consistency, identify the source of truth and update only the requested surfaces. Preserve platform-specific guards and existing deployment behavior unless the request explicitly changes them.
5. Validate local JSON/YAML and run the narrowest available build or configuration check. Do not deploy merely to validate a change; first confirm the target project and get explicit deployment authorization.
6. Report which configuration was inspected, the evidence for the cause, and any manual Cloud Console or CI-secret steps that remain.

Safety

• Never expose Firebase tokens, service-account contents, signing material, or other secrets in output or committed files.
• Do not remove Firebase code or change hosting targets based only on branch names; inspect the active environment and preserve user edits.
• Treat successful local configuration validation separately from successful remote deployment.