refactor(canvas): drop comments from the Activity bell popover

Generated-By: PostHog Code
Task-Id: f89ba875-c0c8-4a08-b088-67b2a900e66d

Author: adboio

packages/ui/src/features/canvas/components/ChannelNav.test.tsx

@@ -108,14 +108,11 @@ describe("ChannelNav", () => {
     rerender(<ChannelNav />);
     await user.unhover(bell());
 
-    // Opening a notification from the Activity page navigates to its task: the
-    // card must not come along for the ride.
     mocks.view = { type: "task-detail" };
     rerender(<ChannelNav />);
     await new Promise((resolve) => setTimeout(resolve, 400));
     expect(screen.queryByText("Recent activity card")).not.toBeInTheDocument();
 
-    // ...and hover must still work there.
     await user.hover(bell());
     expect(
       await screen.findByText("Recent activity card", {}, { timeout: 1_000 }),

packages/ui/src/features/canvas/components/ChannelNav.tsx

@@ -138,12 +138,6 @@ function NavButton({
   );
 }
 
-// Only mounted off the Activity page, so the card's open state is born fresh on
-// every visit. That matters because refusing an open is not free: quill's
-// trigger applies it internally before we see it, so a `false` we hand back
-// leaves the trigger stuck in its pressed state with hover-open dead until it
-// remounts. Nothing here refuses one — the click prevents the trigger's own
-// open, and the Activity page renders the bell without a popover at all.
 function ActivityHoverPopover({ trigger }: { trigger: ReactElement }) {
   const [open, setOpen] = useState(false);