The family literal the library reports for a domain whose rules all
missed (the "empty fallback"). Verified against the current snapshot —
do not "fix" from memory:
- Library source: moon_ua_parser_lib/src/ua_parser/engine.mbt:33-65
(other_browser / other_os / other_device all emit
family: "Other" with every other field None).
- uap-core goldens: browser uap-core/tests/test_ua.yaml:1020-1024
(SomethingWeNeverKnewExisted -> family 'Other'); OS
uap-core/tests/test_os.yaml:710-715 (same UA -> family 'Other');
device uap-core/tests/test_device.yaml:398-401 (NCSA_Mosaic/2.0(Windows 3.1) -> family 'Other'; uap-core has no device catch-all
rule, see moon_ua_parser_lib/tests/semantics/semantics.mbt Test 12
comment).
- Runtime-verified for all three domains at once by the
SomethingWeNeverKnewExisted test in core_tests.mbt.
Note: a bot UA such as Googlebot reports device family "Spider"
because a real device rule produced it (rule 625,
uap-core/regexes.yaml:6217) — that is a match, NOT this fallback,
and must not trigger degradation by itself.