Symbols not loading from .bndb after upgrade/downgrade; possible plugin or version mismatch?

Reported via customer email.

Summary:
Customer recently updated to 3.6.4545-dev and attempted to open a .bndb file. Opening failed (possibly due to Homebrew upgrading Python). After downgrading to 3.5.4526 Personal (ec37d737) and fixing the Python environment, their m68k and neogeo plugins load fine—but opening the .bndb still results in zero loaded symbols.

Customer's expectation:
Symbols should load even if custom plugins are unavailable.

Logs after opening .bndb:

[BinaryView] Truncating segment @ 0x200000 with dataOffset @ 0x200000 and length 0x300000 to 0x100000 bytes.
[Analysis] Added M68000 entry point at 0xc00402 but that address has no backing data.
[Default] Binary Ninja has been updated since this database was saved, reanalysis may need to occur...
[Default]    Cache Build ID: 0xe7474acc (3.6.4528-dev Personal)   Core Build ID:0xec37d737 (3.5.4526 Personal)
[Default] is_valid: <FileMetadata: /Users/mblsha/src/mslug/memdump-3mb.bndb>
[Analysis] Auto-analysis skipping blacklisted function: M68000@0x28594
[Analysis] Auto-analysis skipping blacklisted function: M68000@0x28594
[Analysis] Analysis update took 0.125 seconds

Additional context:

• Binary uploaded: "lively garden dances cheerfully"

Start by reproducing the reported .bndb opening behavior across 3.6.4545-dev and 3.5.4526 Personal, with the m68k and neogeo plugins available and unavailable. Compare the logs and verify whether symbols load from the uploaded database; done means symbols load without the custom plugins or the compatibility limitation is clearly identified.