You are using 8.7GB of Swap which is getting to be a lot and indicates your workloads may be too much for the 8GB of memory in your Mac. It is a shame Apple keeps selling under spec'd systems like this since 8GB should not even be an option these days.....16GB of memory should be the bare minimum no matter how a computer is to be used.
Is your Logitech software completely up to date? And is it compatible with macOS 26.2? I have been seeing a lot of users reporting issues with the Logitech software causing problems as Logitech is a bit behind on compatibility with recent macOS update patches. Even if you have the mouse disconnected, this software could still be misbehaving if it is not fully compatible with the current patch level of macOS.
IvKate wrote:
• if the lid is closed, the screens stay off, but the mac periodically plays a system sound similar to power being connected or disconnected
• if the mac is fully shut down, it can turn itself on after 15–30 minutes and play the normal startup sound
no keyboard, mouse, trackpad or other input devices are being used at the moment of wake.
Re-reading your original post, this stood out to me today. If the sound is actually due to the power adapter connection sound, then it would indicate a hardware issue of some sort. Is the power adapter connected directly to this laptop? If not, then that could be a problem. Also, try connecting the power adapter to the other USB-C port to see if that makes any difference. It could also be a bad Logic Board, or possibly a battery. I have seen one of the MBPros have power & charging issues, but don't recall the exact model at this time (it was one with MagSafe3 though).
Did you run the Apple Diagnostics with the Power Adapter connected? What was the result?
Also, did you try using the "pmset" command(s) I gave you previously to see why the laptop is powering on by itself (or Waking up)? You can modify the filter to only use the "Start " item to show you the time & reasons for the system powering on which can reduce the amount of information displayed like this (I removed two of the filters so only power on (aka "Start ") events if you want to focus on cold power on events or reboots:
pmset -g log | grep -iE 'Start ' | grep -E "^$(date "+%F")|^$(date -v -1d "+%F")"
You can also save the output to a text file so you can use any text editor to search for "Start " within the full report of the Sleep, Wake, and Start events. Notice the " | tee -a ~/Desktop/pmset-SleepWakeStart-log__2025-12-19.txt" at the end of the line which will save a log of the output while also displaying it on the screen. This will create the file on the Desktop, or if the file already exists it will append the data to the existing file (don't use any spaces in the file name or path...use a dash or underscore instead like I have done here).
pmset -g log | grep -iE 'Sleep |Wake |Start ' | grep -E "^$(date "+%F")|^$(date -v -1d "+%F")" | tee -a ~/Desktop/pmset-SleepWakeStart-log__2025-12-19.txt
Some of the reasons shown for the Sleep, Wake, and Start/power on events may sometimes appear cryptic, but it may be possible to figure out the meaning using a system log....it can be tricky & time consuming. I find these commands are the easiest method to figure out what is occurring with macOS. Even @leroydouglas offered a similar suggestion, but mine reduces the clutter by restricting the events to the current day and/or the previous day depending on the command you choose to use.
Hopefully the events shown by these commands will be sufficient for identifying the source of the Wake & power on (aka Start) events. If not, then you will need to resort to the "log" command to look for what the system is doing at the time, but I hope you don't need to because that system log will have thousands of entries.....easily with hundreds of entries every second (perhaps even thousands). This is the only way I have found to figure out Sleep/Wake/PowerOn issues with macOS