Looked deeper into the hooks and found that usePress stops propagation by default. Was able to workaround my issue by implementing onPressStart={(event) => { event.continuePropagation(); } on the Button within a Tab:
https://codesandbox.io/p/sandbox/elegant-shamir-xc2yl8

But it doesn't feel like it should be this hard and it feels pretty weird to have to implement a Button inside of a Tab to get this to work. It feels like the Tab should support the functionality directly

Of note, a Button inside a Tab is actually not valid ARIA.

I haven't had the time to check, but were you able to determine why the TooltipTrigger on a Tab doesn't work? is it because we haven't exposed the hover props yet? #6742 or is it something else?

I haven't had a chance to track down what the issue is. It's possible the above hover fix would help, but it doesn't appear to be released, so I can't test against it

I was able to verify in your Storybook that the addition of the hover events did not fix wrapping a Tab with a TooltipTrigger

So, I think this stems from the Tab never consuming the FocusableContext

None of the hooks call useFocusableContext or useFocusable, only ever useFocusRing

It appears that simply implementing useFocusable in Tab is not sufficient. I believe that due to complications introduced by the Collection pattern (implemented by Tabs), the trigger ref is never being set correctly onto the Tab, and the FocusableContext doesn't successfully penetrate into the Tab rendering scope.