parse("Smith née Jones") reports no family name — a maiden clause empties a one-word name, where 1.4.0 kept it

[derek73]

A name of exactly one name word plus a maiden clause loses its family name:

parse("Smith née Jones")      # given='Smith'  family=''  maiden='Jones'
parse("Müller geb. Schmidt")  # given='Müller' family=''  maiden='Schmidt'
parse("Smith (née Jones)")    # given='Smith'  family=''  maiden='Jones'   (since #335)

1.4.0 kept the family. It had no maiden support, so Smith née Jones read first Smith, middle née, last Jones — the marker rode along as a middle name and Jones stayed the family. The emptying arrived with #274's marker consumption in 2.0, which makes this a v1-parity deviation rather than long-standing behavior.

This is the third instance of one shape

• Dr. Smith née Jones reports no family name — a maiden name suppresses the title-plus-one-word rule #410 fixed it for rules.md#H1: Dr. Smith née Jones reported no family because the rule counted the maiden name as a further name word. The fix removed the whole others term — a suffix, a nickname and a maiden name are annotations beside the name, not name words.
• Abd van der Berg née Jones reports no family name — the bound-given join counts words the maiden name takes away #411 fixed the same empty family arriving from P5's bound-given reserve.
• What remains is a name with no title and no bound given word, where rules.md#N3 — "a name that is only a nickname and one name word reads that word as the family name" — is the rule that would otherwise rescue it. A marker-led clause is not a nickname clause, so N3 does not reach it.

Why it surfaces now

#335 makes the bracketed spelling agree with the bare one, so Smith (née Jones) joins the shape instead of escaping it by being read as a nickname. That is correct and deliberate: it is recorded in rules.md#N3's Accepted block and pinned by a case row, with its own rule in all three differential ledgers (its diff moves four fields where the other marker-led names move two). The effect is that the shape is now reachable two ways rather than one.

Worth deciding

Whether #410's principle generalizes: a maiden name is announced beside the name and is not a further name word, so a lone name word standing before one is still the family — giving Smith née Jones → family Smith, maiden Jones, and matching what 1.4.0 reported. Or whether a one-word name genuinely names no family and the given-side reading is the right one, in which case the deviation from 1.4.0 should be classified and stated rather than left implicit.

decisions.md#H1 states the principle for titles and explicitly leaves the nickname-led case open: "N3 counts a suffix the other way, and which of the two readings is right for a nickname-led name is not decided here."

[derek73]

Normally if there is only one name, we assume it's a given name because we have to pick one. the current parse follows that rule (which may not have a rule recorded yet). Because maiden_markers mark previous surnames before marriage, it would not make sense to include one if there was no other surname for it to clarify. So given than, when there is a maiden marker that leaves only one name, we should switch that assumption to assume it's a family name.