Put validation values directly in comparison table

README.md

@@ -51,20 +51,14 @@ Bottom line:
 - The BF16 package reduces storage, not runtime memory.
 - This mixed q8/BF16 package reduces both storage and runtime memory. This is the package to use when generation memory footprint matters.
 
-| Layout | Disk | Runtime Memory | Improvement |
-| --- | ---: | --- | --- |
-| Original source snapshot | 118 GiB | Baseline | Baseline. |
-| BF16 package | 64 GiB | Same class as original | Storage only; output was byte-identical. |
-| This mixed q8/BF16 package | 40 GiB | Lower | Storage and memory; side-by-side quality validation passed. |
+| Layout | Disk | MLX Peak | Physical Peak | Time | Result |
+| --- | ---: | ---: | ---: | ---: | --- |
+| Original source snapshot | 118 GiB | 32.99 GiB | 48.90 GiB | 108.31 s | Baseline. |
+| BF16 package | 64 GiB | 32.98 GiB | 45.12 GiB | 114.39 s | Storage only; output was byte-identical. |
+| This mixed q8/BF16 package | 40 GiB | 20.84 GiB | 31.75 GiB | 110.34 s | Storage and memory; side-by-side quality validation passed. |
 
 Compared with the original source snapshot, this mixed q8/BF16 package cuts disk usage by about 66%, MLX peak memory by about 37%, and physical peak memory by about 35% in this validation run. It is not byte-identical to BF16, but the validation contact sheet stayed in the same visual family. The prepared q8/BF16 output was byte-identical to running `--quantize 8` from the upstream source snapshot.
 
-Raw measurements:
-
-- Original source snapshot: 32.99 GiB MLX peak, 48.90 GiB physical peak, 108.31 s.
-- BF16 package: 32.98 GiB MLX peak, 45.12 GiB physical peak, 114.39 s.
-- This mixed q8/BF16 package: 20.84 GiB MLX peak, 31.75 GiB physical peak, 110.34 s.
-
 ## Compatibility
 
 Requires `mlx-gen >= 0.18.8`.