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

### 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.
- #6269 (push MVP) merged 2026-08-28 and #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 #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.

Start with docs/push-gateway-deployment.md and the NIP-PL documentation, then review the implementation and deployment changes from #6269 and #7158 alongside the hosted-relay status in #7186. Determine how hosted communities advertise push support and how the iPhone app profile is selected. Done means the required rollout and public-build coverage are documented or implemented, with the owner-side testing steps stated.

Written by the indexing model from the issue text.