3233 - Provenance — ContextQMD

Hatari TOS BIOS entries — Added 8 new optional BIOS entries for common .rom-suffixed TOS variants: tos100us.rom, tos102us.rom, tos104us.rom, tos104se.rom, tos106us.rom, tos205us.rom, tos206uk.rom, tos206us.rom. These are now importable via the BIOS import screen.

Hatari TOS .rom extension — TOS ROM files distributed with the .rom extension (e.g. tos102us.rom, tos206uk.rom) are now recognised by the BIOS importer and TOS search logic. Previously only .img files were accepted, silently blocking common ROM dump filenames.
Unknown BIOS MD5/size handling — BIOS entries with no known MD5 (empty string) or size (zero) no longer report false validation mismatches; a file that matches by filename is now accepted as valid when the expected MD5/size is unknown.
BIOS identity collision — PVBIOS now uses expectedFilename (the Realm primary key) as its Identifiable.id instead of expectedMD5, preventing non-unique IDs in SwiftUI ForEach when multiple BIOS entries have empty or identical MD5 values.
BIOSStatus size-check false positive — Size validation is now only skipped when a known MD5 matches, not when the expected MD5 is empty. Previously, an empty expectedMD5 would short-circuit size validation even when expectedSize was non-zero, allowing a wrong-size BIOS file to pass as valid.