Polish: the CJK rule slug owns #298; generator docstring tense

The differential rule now explains #298's B7 diffs, so its issue slug
says so -- compare.py output labels a B7 diff with the issue that
caused it. The sync test's substring selection (#271/#272) still
matches this one rule uniquely. And the corpus generator's docstring
spoke of #298 as future work it has since harvested.

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

Author: derek73

tools/differential/build_cjk_corpus.py

@@ -15,8 +15,9 @@
 Selection is by the shipped table (nameparser._policy._SCRIPT_RANGES,
 through the same _script_matcher the parser uses), so a script added
 to the table widens the harvest on the next regeneration, and a case
-row added for future CJK work (#298's 间隔号 forms, say) enters the
-corpus by being written down in the table everyone already reviews.
+row added for new CJK work enters the corpus by being written down in
+the table everyone already reviews (#298's 间隔号 forms arrived
+exactly this way).
 
 Regenerate after editing CJK case rows:
 

tools/differential/expected_changes.toml

@@ -7,7 +7,7 @@
 # ahead of `fields`-only ones before matching.
 
 [[change]]
-issue = "fix(#271/#272) native-script CJK: family-first order, hangul segmentation, the kana license and the nakaguro"
+issue = "fix(#271/#272/#298) native-script CJK: family-first order, hangul segmentation, the kana license and the dots"
 # '毛 泽东', '김민준': script_orders flips first/last for a name written
 # wholly in Han or Hangul, and the Korean surnames that now ship as
 # default vocabulary additionally split an unspaced hangul token into