[brow]

On iOS, opening a sheet over Home (for example a channel's long-press actions) left a hard horizontal edge and a light glow band under the filter chips. Home's header keeps a native UIKit soft-edge view behind its Flutter controls, and the sheet's dim barrier doesn't composite cleanly over it.

While another route covers Home, the header now switches to its Flutter backdrop through the existing FrostedAppBar.nativeViewSuppressed hook, the same mechanism other headers use while a backdrop covers them. Home already hides its native bottom controls under the same condition.

Before	After

Validation

• iPhone 17 Pro simulator (iOS 27), Builderlab test community: reproduced the artifact on main with Home scrolled and the channel actions sheet open, then confirmed it is gone with this change. Also opened and dismissed the sheet repeatedly and checked the header before, during and after.

• Transition timing, frame-stepped from simulator recordings of main (top row of each strip) and this PR (bottom row) on the same Home state:

  • The header and the bottom navigation controls switch on the same frame. A modal sheet doesn't drive Home's secondary animation (MaterialPageRoute.canTransitionTo is false for a sheet route), so the bottom controls' secondaryAnimation == 0 check reduces to the same isCurrent gate the header uses.
  • Known limitation: while the native header view is swapped out, the header blanks for about 2 display frames as the sheet opens and about 3 as it closes (about 30 to 50 ms, seen as the missing chips below). main has no blank frames but shows the hard edge.

  Opening:

  

  Closing:

  

• Extended the iOS Home widget journey: the native header view is removed while the channel actions sheet is open and restored after it is dismissed. Without the fix, the journey fails.

• Full mobile Flutter suite passes.

buzz-review-completed

🤖 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-05T23:21:52.873362Z	bd5dee1	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. Breezy!

Reviewed commit: bd5dee1064

ℹ️ 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...6f3e9fa9be727df426d4c5aae5973abca3ec68d3
• 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 findings were identified in the authorized PR range.

Findings

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

Notes

• Review used read-only source inspection. Tests and native iOS rendering were not executed.

---

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

[tlongwell-block]

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

The remaining concern is transition timing: the header uses route-current state while the bottom controls use the secondary animation reaching zero. Those gates can change at different points while a sheet opens or closes. Please validate both transitions with frame-stepped main/PR captures to rule out a visible mismatch. This is an unverified visual concern, not a reproduced defect. The full mobile suite passed.

Reviewed head: 6f3e9fa9be727df426d4c5aae5973abca3ec68d3.

[brow]

🤖 Checked with frame-stepped simulator recordings of main and this head (6f3e9fa), sheet open and close on the same Home state. The strips are now in the PR description under Validation.

No gate mismatch: the header and the bottom navigation controls switch on the same frame. A modal bottom sheet doesn't drive Home's secondary animation (MaterialPageRoute.canTransitionTo returns false for a sheet route, so secondaryAnimation stays at 0), and the bottom controls' check reduces to the same isCurrent gate the header uses. I left the gates as they are.

The recordings did show a separate cost. While the native header view is swapped out, the header blanks for about 2 display frames as the sheet opens and about 3 as it closes (about 30 to 50 ms). main has no blank frames. The description now records this as a known limitation in place of the earlier one-frame estimate.

[kazemek21]

Kyle reviewed this PR and the Nexus review-tracker notes and approved with no comments.

Posted by Codex (gpt-6.1-sol) on behalf of kylez