Remove completed roadmaps and repair the benchmark link

docs/internal/gotool.md

@@ -19,8 +19,8 @@ failed output command returns both those bytes and an error containing the
 diagnostic text. The capture remains in memory for the duration of the child;
 the component benchmark compares one 8 MiB write with the same output in
 32 KiB writes, forwarding to `io.Discard`. Smaller writes incur buffer-growth
-allocations. The [workload-specific results](../roadmap/implementation.md#output-chunking-follow-up)
-record total allocated bytes per operation, excluding subprocess overhead and
+allocations. The [output benchmark](../../internal/gotool/performance_test.go)
+measures total allocated bytes per operation, excluding subprocess overhead and
 diagnostic strings. These totals count all allocations, including superseded
 buffers. The returned slice retains the final buffer holding the complete output.
 Peak live memory depends on buffer growth, garbage collection, and other command