Update the duplicate-metadata wording: the Android writer fix landed

The save path replaces previous metadata instead of accumulating it as of
phyphox-android f248871b (2026-08-24), so the fixture description and the
duplicate-metadata-last-wins rationale/state no longer claim the writer
can still produce duplicates - files in that shape remain in the wild,
which is what keeps the fixture and the tolerance relevant.

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

Author: Staacks

corpus/invalid/state-title-duplicate.phyphox

@@ -5,11 +5,12 @@
     <category>Saved states</category>
     <description>
         A saved state whose re-save appended a second state-title instead of
-        replacing the first, the shape old Android versions wrote (and the
-        current writer can still produce, see the live-NodeList removal skip
-        in PhyphoxExperiment.java). Parsers tolerate the duplicate and the
-        last occurrence wins (rule duplicate-metadata-last-wins); writing
-        one remains an error, which is what the validators flag here.
+        replacing the first, the shape old Android versions wrote (the
+        writer bug, a live-NodeList removal skip in PhyphoxExperiment.java,
+        was fixed on the development branch 2026-08-24; files in this shape
+        remain in the wild). Parsers tolerate the duplicate and the last
+        occurrence wins (rule duplicate-metadata-last-wins); writing one
+        remains an error, which is what the validators flag here.
     </description>
     <data-containers>
         <container size="0">t</container>

spec/rules.yml

@@ -320,9 +320,10 @@ rules:
       versions appended a fresh state-title on every re-save of a saved
       state without removing the previous one
       (corpus/valid/taipei101_down.phyphox was collected from a real 2018
-      recording in exactly that shape, fixed 2026-08-24), and the current
-      Android writer can still leave a stale element behind (live-NodeList
-      removal skip, PhyphoxExperiment.java). Rejecting duplicates would
+      recording in exactly that shape, fixed 2026-08-24), and until the
+      same day's writer fix the Android save path could still leave a
+      stale element behind (live-NodeList removal skip,
+      PhyphoxExperiment.java, fixed in f248871b). Rejecting duplicates would
       strand users' own recordings; last-wins matches what Android has
       always done, so existing files keep showing the title the user gave
       last.
@@ -335,8 +336,9 @@ rules:
         Conforms by long-standing behavior: phyphoxBlockParser assigns the
         read value unconditionally per tag (PhyphoxFile.java, e.g. case
         "state-title"), so the last occurrence wins. The writer-side bug
-        that produces the duplicates is a separate fix (handed off
-        2026-08-24).
+        that produced the duplicates is fixed on the development branch
+        (f248871b, 2026-08-24): the save path now replaces the previous
+        metadata instead of accumulating it.
       ios: >-
         Conforms as of the development branch (efff512c, 2026-08-24): the
         six root metadata handlers read lastResult() instead of