Durian-Pixel
If he had physical access to your laptop, it is way more likely that something was installed on your laptop when you weren't home! Are the USB ports set to need a supervisor password before anything can be run from them from the F12 menu (where you choose an external drive to boot from)? Do you have a superviso/boot password on it at all? How secure is your login password and is it needed when resuming from sleep/screen off? Ever put a password on your root user? (Many distributions don't have any password on su out of the box)
Before your login screen is it possible to get to an options menu and boot into a recovery terminal? This is where really nasty things can be installed, especially if root has no password... Ubuntu has this option, don't know about Fedora, but I'd hazard a guess they do, since it's the only way other than live CD to fix OS not booting correctly problems.
To wipe everything from your PC, (except BIOS/firmware bugs) just wipe your hard drive and reinstall, preferably with LUKS full dusk encryption. Ubuntu 23.10, and 24.04 if its out support TPM-backed FDE that has verified boot, a first in the desktop Linux world! Choosing this option also installs an all-snap base of software and system packages for enhanced security, and your system folders are not writeable. I would recommend that for reinstall.
Go ahead and flash your BIOS with a USB. Download the most recent from your laptop's drivers page and make a USB, they will walk you through how to do it safely! I do it whenever a new one comes out. You can also in Ubuntu run the firmware updater which will fetch the most recent firmware and update that safely!
After that put a good supervisor and boot password on your laptop, make them different and make the boot password needed on restart as well as on cold boot. Its what I do.
For your Pixel, once you unlock the bootloader as part of reinstalling GrapheneOS, all data is wiped. The reinstall even reinstalls your bootloader and radio firmware. Want to be extra sure? when done the install, get platform tools so you can run this command, then run the installer again to write over the other slot (probably not necessary, but if you want to):
fastboot --set-active=other
Will select the other boot slot, and the installer will overwrite it as well. I think that running it once the data gets copied over, but I'm not knowledgeable to say for sure. When I ran into problems with the command line based flash-all.sh script (which I think is what the web installer uses) and I saw it only writing one side, I just ran the command above and ran the script again. Got me away from my phone saying it was corrupted!