I mainly do the same, while for finished work I have a completely separate page in Figma that has all the final pages.

Oh I feel your pain on this one. I've actually had PM's dig through my files and send unfinished work straight to our developers because they didn't realize that it was discovery work.

I've found a couple little tricks useful for this. First, I use pages to separate rough work from anything ready to review. I use an "" to denote that a page contains unfinished work, so "Discovery" is a page that shouldn't be reviewed, where "Prototypes" are ready to review. I also include a cover page for prototypes and recently added a callout to it that indicates the status of the prototype so that even if you don't see the pages, you get an idea of where the work is at. Lately I've just been keeping rough work in my drafts and waiting until it feels pretty mature to move it into one of our team projects.

The majority of what I produce is the same, however for finished work, I have a separate page in Figma with all the final pages. x trench run

I have a final files with main flow, and I have a duplicate of that file by myself. when is time to get feedback I bring progress into the main file

I prefer people to jump in from time to time. Instead of stressing out that they are watching, I usually stop and slack them for input around a few points to engage in a conversation. Since the files are rough, All my (freelance)clients and my Day job PMs appreciate being able to take notes and check in on the status of things. They usually leave after or go inspect some of the other screens.

It also helps that I only share links to the Review pages. Normally they don't dig deeper.

I separate work by pages,

I'm more uncomfortable sharing a live link that they can now use to literally watch me design in real-time. I get stage freight lol

I literally name my files based on status, for example I have a file just for the devs called handover.