docs(maiden): point M2's accepted limits at the issues that track them

The two surviving join-swallows are recorded in M2 but named no issue,
unlike the fullwidth-colon limit beside them which points at #317. They
are #412 now. decisions.md's Open (M2) list also picks up #410 and
#411 -- the two empty-family paths a maiden name opens, both
pre-existing and both widened by the stop.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: derek73

docs/design/decisions.md

@@ -122,6 +122,10 @@ Open: [#380](https://github.com/derek73/python-nameparser/issues/380) covers "Be
 Open (M2):
 [#317](https://github.com/derek73/python-nameparser/issues/317)
 the fullwidth-colon marker (旧姓：佐藤 arrives as one word; the head-peel question).
+[#412](https://github.com/derek73/python-nameparser/issues/412)
+the two surviving join-swallows (P3's connective join and P5's bound-given join each absorb a marker before M2's bound can see it) — where the reorder set aside above would be re-weighed.
+[#410](https://github.com/derek73/python-nameparser/issues/410)
+a maiden name makes H1 decline, so a title-plus-surname name reports no family; [#411](https://github.com/derek73/python-nameparser/issues/411) the same empty family from P5's reserve counting words the maiden name takes away. Both pre-existing, both widened by the stop.
 
 ### N3 — the lone-word nickname rule
 

docs/design/rules.md

@@ -452,7 +452,7 @@ M2. Rationale: a maiden marker announces that what follows it is the
     text, not a marker; and the bound reaches only a marker standing
     as a word of its own, so the connective join (P3) and the
     bound-given join (P5) each still absorb a marker before the bound
-    can see it.
+    can see it; #412 tracks whether it should reach them.
       "Jane Smith, née Jones"          →  maiden=""
       "Jane van der Berg née y Jones"  →  maiden=""
       "van der Berg, abdul née Jones"  →  given="abdul née"