Allure 3 report size inflates significantly compared to input files

The generated Allure 3 report size is disproportionately large compared to the source files.

### Details

* Total size of input files (with traces): **374 MB**
* Generated Allure report size: **2.9 GB**

This represents a substantial increase in disk usage during report generation.

The same source files were used across multiple plugins, but not to the extent of an 8× increase. At most, the files appear to be reused approximately 2× on average.

### Expected Behavior

The generated report size should be reasonably proportional to the size of the input files and should not increase by an order of magnitude without clear justification.

### Actual Behavior

Allure 3 generates a report that is nearly **8× larger** than the original data set.

### Screenshot

The issue names no files, tests, or entry points. Start by reproducing report generation with the reported 374 MB input set and measure which generated artifacts account for the size increase. Done means the report size is reasonably proportional to its inputs and the remaining reuse is understood.

Written by the indexing model from the issue text.