Antoine van der Lee d977023cb1 Add cached clean benchmark to capture COMPILATION_CACHING benefit ...

Standard clean builds show cache-population overhead without the
corresponding cache-hit benefit, making COMPILATION_CACHING appear
to regress performance. The new "cached clean" phase measures clean
builds with a warm compilation cache by deleting DerivedData (not
the system compilation cache) between runs. This captures the
realistic developer workflow: branch switching, pulling changes,
and Clean Build Folder.

Changes:
- benchmark_builds.py: auto-detect COMPILATION_CACHING and run
  cached clean builds using a controlled DerivedData path
- Schema bumped to 1.2.0 with optional cached_clean runs/summary
- Report generator shows Cached Clean column when data is present
- All skill docs and references updated to use the cached clean
  metric as the primary comparison for COMPILATION_CACHING impact

2026-03-23 13:59:32 +01:00

..

build-benchmark.schema.json

Add cached clean benchmark to capture COMPILATION_CACHING benefit

2026-03-23 13:59:32 +01:00