Firebase server keys

• nuclei-templates (projectdiscovery)

Neither Google's current documentation nor either of this suite's pinned scanners publishes a rule for this shape: TruffleHog's own proto/detector_type.proto reserves both Firebase = 33 and FirebaseCloudMessaging = 102, explicitly marked "Not yet implemented", and no gitleaks 8.30.1 rule names Firebase at all. The single corroboration source above (not one of this suite's pinned, version-tracked scanners) pins the exact two-segment width — AAAA + 7 bytes + ":" + 140 bytes, 152 bytes total, regex AAAA[A-Za-z0-9_-]{7}:[A-Za-z0-9_-]{140} — observed 2026-09-20 at the commit pinned in its URL. The AAAA prefix itself is additionally corroborated by two independent non-tool sources (a 2024 B4X developer-forum FCM-deprecation thread and an independent FCM-takeover security writeup, both observed 2026-09-20; recorded here as prose, not as further corroboration entries, since neither is a scanner). A shorter or longer segment, a missing or misplaced separator, or a wider embedded run is an intentional false negative rather than a fuzzy match. status-criteria.json requires a T1 providerSource for stable; this family cannot reach stable on this evidence and is expected to classify provisional.