Good sleuthing. The basic Name search was designed to include assumed, possible married surnames for women even though there might not be such a Primary or Alternate Name record for the person in the database NameTable. I think the pre-RM11 Advanced Search did, too (I may be wrong), but it suffered from being able to require that two or more criteria be met for the same record of any type. The RM11 Advanced Search does and would have undergone a major redesign. Perhaps the redesign overlooked the option to “include married names” or it added too much complexity because the assumed married name for the woman takes the surname from the Primary Name record of the husband spouse.
Basic Search shows in the surname field “Surname (or married name)”. The married name is based on the spouse they are linked to. It does not need to be an alternate name fact. It will search both primary and alternate names using basic search.
Advanced Search has deeper filter options. There are check boxes to “include married surname” and “only test primary names”.
I’m sort of repeating what Renee said, but you can always get the results for searching on a surname to match between Basic Search and Advanced Search. There is no bug. It’s just that basic search always searches for Birth or Married name and advanced search has no default. You have to select Birth name or you have to select Birth or Married name.
It’s always been this way, even as far back as RM1 and Family Origins. It used to be called Name Search and Search rather than Basic Search and Advanced Search, but it amounts to the same thing.