gcp-local-stacklisted

# Local development against Google Cloud **The question this answers:** can this product's tests run without touching a real GCP project? The answer decides vwf's `local_stack` harness capability, and it is per-service knowledge that no SDK reference states. The stakes are concrete. A service with a real emulator can be tested by anyone who clones the repo, offline, with no billing account and no shared-environment contention. A service without one forces a choice between a real project per developer, a fake you write and maintain, or tests that don't run. ## The emulator map **First-class emulators** — official, offline, and good enough that tests running against them are meaningful: | Service | Runs via | Fidelity caveat | | ----------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------- | | Firestore | Firebase Emulator Suite | security rules evaluated; **indexes are not** — a query that needs a composite index passes locally and fails in production | | Realtime Database | Firebase Emulator Suite | close to complete | | Firebase Auth | Firebase Emulator Suite | no real provider handshake — OAuth flows are stubbed, so