Share reporter detail rendering

docs/roadmap/audit/catalog.md

@@ -1,6 +1,6 @@
 # Consolidated audit catalog
 
-Status: **19 distinct open findings: 19 P3**, consolidated from 30
+Status: **18 distinct open findings: 18 P3**, consolidated from 30
 numbered entries in seven audit documents. Reviewed audit state:
 `db732e3a1de55c844f77870e1c6db683c2685d5d`.
 
@@ -390,6 +390,10 @@ are selected.
 
 ## F20 — P3: Reporter message paths duplicate detail-rendering bookkeeping
 
+**Complete.** Both message paths share detail callback and error bookkeeping;
+focused reporter tests cover visibility, ordering, closed handles, and joined
+render/write evidence.
+
 Terminal and ordinary message paths repeat callback invocation, managed-writer
 setup, render-versus-write error classification, and first-error retention.
 Maintaining the same presentation policy in two branches increases the chance of
@@ -406,7 +410,7 @@ fix deferred-message loss or writer retention. After correctness repairs, favor
 F20, then F18 and F17, while keeping F19 modest. All four use private functions
 and existing types, with no intended public API or CLI behavior change. The
 [F17–F20 analysis](remediation-analysis.md#f17f20--proportionate-private-extractions)
-records the accepted scope; implementation remains pending.
+records the accepted scope.
 
 **Original:** [03-complexity M7](03-complexity.md#m7--p3-terminal-and-ordinary-messages-duplicate-detail-rendering-mechanics).