docs(fuzzing): sse_parser 45-min post-FWD-22 rerun clean

Exited 0 at 2765 s: 96k execs at ~33/s, coverage 1378 edges / 6655
features / 734 corpus, still growing at budget end, zero findings.
Wave 4 is fully done: five of five targets exited 0.

docs/plans/fuzzing.md

@@ -474,8 +474,9 @@ launched concurrently, five of five):
 - `sse_parser` — aborted at 1913 s on FWD-22 (above; the
   interior-CR round-trip loss, a harness fix); before the abort it
   had 57k execs at ~35/s (1269 edges / 5584 features / 509 corpus),
-  still growing. 45-min rerun of `sse_parser` post-fix in flight at
-  the time of writing.
+  still growing. 45-min rerun post-fix exited 0: 96k execs at ~33/s,
+  coverage still growing at budget end (1378 edges / 6655 features /
+  734 corpus) — zero findings.
 - A stale crash artifact from the wave-2 morning session (quoted-`""`
   YAML key, predating that fix) was still present in
   `fuzz/artifacts/spec_import/` at campaign start — not produced by
@@ -495,10 +496,11 @@ launched concurrently, five of five):
    with the OpenAPI-token set, fuzzing hubs in the three driven
    modules. Smoke campaign clean (see §5).
 3. ✅ **Done (2026-09-29, wave 4)** — long (45 min) release-budget
-   campaigns, all five targets (see §5; the one finding, FWD-22, was
-   a harness-assert fix). Corpus merges remain deliberately deferred
-   (grown corpora stay gitignored; nothing campaign-dropped has been
-   curated into seeds).
+   campaigns, all five targets, all exited 0 (see §5; the one
+   finding, FWD-22, was a harness-assert fix, fixed + re-run clean in
+   the same wave). Corpus merges remain deliberately deferred (grown
+   corpora stay gitignored; nothing campaign-dropped has been curated
+   into seeds).
 4. ✅ **Done (2026-09-29, wave 3)** — target 4 stateful
    (`ws_session_opseq` + `retry_throttle`): two harnesses + 16 seeds
    + the `byte_adapter::fuzzing` / `client::fuzzing` hubs + FWD-21