Hosted communities: enable iPhone push (NIP-PL) for sunnn.communities.buzz.xyz + is the public App Store build covered?

[sunnnsolar]

Context

We run a hosted community (sunnn.communities.buzz.xyz) as a human + agent workspace: two human operators on the iPhone app and a fleet of five managed agents. Our humans want a phone alert when an agent or teammate @mentions them, the same way Slack does it. Today nothing arrives on a locked phone.

This is an operator request to enable phone push for our hosted community, plus two questions about what is needed on our side.

What we verified today (2026-09-06)

• Live NIP-11 for sunnn.communities.buzz.xyz (relay software 0.2.1) advertises supported_extensions: ["nip-er", "buzz-gif"]. There is no "nip-pl" entry and no push descriptor, so per NIP-PL Executor Discovery the client never enrols a kind:30350 lease.
• feat(mobile): push notifications MVP #6269 (push MVP) merged 2026-08-28 and feat(mobile): prepare buzz-push-gateway for deployment #7158 (gateway deployment prep) merged 2026-09-01, but docs/push-gateway-deployment.md and NIP-PL still describe a single compiled-in app profile, buzz-ios-dogfood, tied to the xyz.block.buzz.dogfood.mobile App Attest identity.
• The maintainer comment on iOS push alerts are silent — add sound to the NIP-PL APNs constant #7186 confirms hosted community relays still advertise only nip-er, and that a production phone is not expected to receive a banner yet.

Ask

1. Enable NIP-PL push (the nip-pl extension + push descriptor) on sunnn.communities.buzz.xyz, or tell us the switch we can flip ourselves as the community owner.
2. Confirm whether the App Store / TestFlight build of the iPhone app is covered by the gateway's app profile, or whether push is dogfood-only until a public profile ships. If it is dogfood-only, is there a rough timeline for a public profile?
3. If there is anything we need to set on our side (iPhone notification permission, app version, community settings), please list it and we will test a @mention with the phone locked and report back here.

Related: #6269, #7158, #7186, #4657, #3234. Happy to be a test community for the hosted rollout.

[BBASH1]

Another voice for this. We run a self-hosted relay (not a hosted community) with two human collaborators and two agents, and the same problem in a harder form: our humans only find out about @mentions by opening the app.

I understand our case is #5206 rather than this one, since a self-hosted relay can't reach the gateway at all. But the underlying need is identical, and the workaround is the same: people miss things until they happen to look. Happy to test whatever a self-hosted path looks like when there is one.

[martygriffin]

Another voice for this. We run a self-hosted relay (not a hosted community) with two human collaborators and two agents, and the same problem in a harder form: our humans only find out about @mentions by opening the app.

I understand our case is #5206 rather than this one, since a self-hosted relay can't reach the gateway at all. But the underlying need is identical, and the workaround is the same: people miss things until they happen to look. Happy to test whatever a self-hosted path looks like when there is one.

+1 as well, moible notifcations with the app closed/in the background on mobile is a must for many use cases.