Binary Ninja marks .efi file as modified with no user action

Version and Platform (required):

• Binary Ninja Version: 5.3 and 6.1.10594
• Edition: Ultimate
• OS: macOS, Windows 11
• OS Version: macOS Tahoe 26.5.2, Win11 10.0.26200 N/A Build 26200
• CPU Architecture: x64

Bug Description:
After opening a .efi file and performing no actions on it, Binary Ninja indicates that the analysis database has been modified (a dot appears next to the file name in the tab). Closing the file then prompts a save dialog, even though no changes were made by the user.

This has been observed across versions 5.3 and 6.1.10594, and reproduced on both macOS and Windows 11.

Steps To Reproduce:

1. Open a .efi file in Binary Ninja
2. Perform no actions on the file
3. Observe that the tab shows a dot next to the file name, indicating the analysis database has been modified
4. Close the file
5. Observe that a save prompt dialog appears

Binary:
efi_files.zip

No source file or test is named. First reproduce the issue with the attached efi_files.zip on the listed platforms and versions, then trace how opening and analyzing an EFI file marks the database dirty. Done means an untouched .efi file does not show as modified and closing it does not prompt to save.