Repository navigation
Push notifications reached the API, so the tools can see and test them.
A live connection reaches a phone only while the app is on screen; the operating system closes it the moment the app goes to the background. What actually reaches someone whose app is closed is a push, and it now exists as a send_push automation action.
Added
push_status. Whether an app can notify phones, whose Firebase project it sends through, and how many devices have registered. When nothing is set up it says how to set it up — and says plainly that the service account is a private key which must not be pasted into a chat.send_test_push. One real notification to named app users, so the chain can be proven before an automation depends on it. The answer separates "delivered", "this user has no device yet" and "the service says this device is gone", because those are three different problems.
On the API
POST /apps/{slug}/api/devices registers a phone; POST /organizations/{org}/apps/{id}/push/credentials takes the customer's own Firebase service account, encrypted at rest; send_push is a new automation action that defaults to the row's owner.