[brow]

On Apple Watch, a Buzz notification showed the community name ("buzz") under the sender, taking a line of the small display without saying where the message came from. iPhone never showed it, because iOS draws the banner from the communication intent and drops content.subtitle. The Watch renders the plain fields.

The subtitle now carries the conversation name, the same one the intent uses for its group name:

• Team channels and forums: #channel
• Your own Solo chats: the bare name, no #
• DMs, and channels not yet in the presentation cache: no subtitle

The name logic moves into one helper so the subtitle and the iPhone group name can't drift apart. A channel that's known but isn't eligible for the communication style (for example, an unverified roster) now gets #channel as its plain-banner subtitle in place of the community name. Losing the community name means the Watch no longer tells communities apart. That seems like the right trade for most people, who are in one community.

Validation

• BuzzPushKit swift test: all 110 XCTest and 69 Swift Testing cases pass. Updated the resolver assertions: #General for a cached stream, both with and without communication styling, and no subtitle for DMs and uncached channels.
• Not yet exercised on a device or Watch.

🤖 Generated with Claude Code

[brow]

@codex review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-06T04:00:02.405894Z	f974806	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

Reviewed commit: f97480625b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[github-actions]

🔐 Codex Security Review

Note: This is an automated, security-focused review generated by Codex.
Use it as a supplement to human review; false positives are possible.

Scope

• Exact PR diff: 8cce12f591988f29cc2beab5ff0c89d51862f31b...229105cc40390fd58febbd8ae58586c0954f9e0d
• Model: gpt-6.1-sol

💡 Click "edited" above to see earlier reviews for this PR.

---

Review Summary

Overall Risk: NONE

No concrete security, correctness, or reliability issues found in the authorized PR range. Channel subtitles use verified, community-scoped metadata, and existing conversation membership checks remain intact.

Findings

No concrete security, correctness, or reliability findings were identified.

Notes

• Review used read-only source inspection. Builds and tests were not run, as instructed.

---

_{Generated by Codex Security Review |
Requested by: @brow |
Workflow run}

[tlongwell-block]

🤖 Meli, Tyler’s AI agent, posting on his explicit behalf.

Approved as directed by Tyler.

Native verification passed 111 XCTest and 70 Swift Testing tests; the full mobile suite also passed. The deliberate removal of community identity was raised for product review. A resolved notification before/after and Watch presentation remain unverified; this approval does not claim a visual pass.

Reviewed head: 229105cc40390fd58febbd8ae58586c0954f9e0d.