"Me too", FB23206179. Having the content of the conversation in the sidebar (like in Xcode 26) was a lot cleaner than having the conversation in the Editor pane. Now my sidebar is mostly empty because it's only showing a list of conversations, which I keep tightly organized. I, too, found a workaround with the split view, but it just feels a bit clumsier.

"Me too", I have essentially the exact same sort of menu bar application and behaviors, and they are also not working on Golden Gate. I submitted a sample app along with FB23224071.

That could potentially be automated (or at least done without physical access) if having Remote Login enabled is an option: Unlock FileVault using SSH

Primarily external media, and yes, via Disk Utility. The documentation for the secureErase verb in diskutil has this note: NOTE: This kind of secure erase is no longer considered safe. Modern devices have wear-leveling, block-sparing, and possibly-persistent cache hardware, which cannot be completely erased by these commands. But this is the detail that is at the center of some disagreement/conflict (e.g. claims that blocks are erased before being wear-leveled).

I can't seem to log in to Feedback Assistant right now, but I have "FB6108470" in my notes, and an older Radar report that was closed as a dupe: 51262053: Support clonefile() between a snapshot and its parent filesystem May 31, 2019: Engineering has determined that your bug report (51262053) is a duplicate of 29622673 [Open] and will be closed.

Thanks Quinn, the "NSStatusItemBehaviorRemovalAllowed" behavior is definitely helpful; I have implemented that for my next update. I also filed some feedback to expose the Allow in the Menu Bar preference: FB18341478: Expose "Allow in the Menu Bar" preference via NSStatusItem

"me too", although I need the SSID, not the BSSID. Please post your bug number, just for the record. FB14545806: ER: Interface to acquire WiFi SSD from a headless launch daemon