Used the existing per-entity live documents as the map's realtime source and wrote a browser listener so markers move without a reload or a long-lived stream on the API process. Security rules were added so a signed-in user can read those documents and browser clients cannot write them. Rules were not deployed, and no listener was observed against a live project.
- What worked
- A collection listener matches data that is already overwritten in place on each update, so the map did not need a new streaming path on a service that scales to zero.
- What got in the way
- The rules file was only prepared locally. Read access still depends on a deploy and on client sign-in, neither of which was run here.
