Summary

This PR restores CI-visible perf data through the generated Allure Awesome report itself: CI now runs a lightweight perf probe, copies the produced *-perf.json into report inputs, and the final report shows the values in the Metrics section.

Changes

• Extended ALLURE_PERF_METRICS with more detailed generation spans and aggregate timings.
• Added core read metrics for xcresult check, directory read, path resolution, and total reader work.
• Added store aggregate metrics for conversion, default labels, environment mapping, retry/history/resolution/indexing, and attachment metadata.
• Added Awesome generation metrics for data loading, stats/charts, conversion, categories, timeline, testcase writes, tree/nav/search, environments, attachments, globals, static files, and plugin summary creation.
• Added neutral workload counters for input files, generated files, attachment count/bytes, and converted test results.
• Added .github/allurerc.perf.mjs for CI probe generation.
• Documented the metric keys and PR baseline interpretation in docs/performance.md.

CI / History

On PRs, metrics are visible in the generated Awesome report Metrics page, not in a PR comment.

PR reports should show deltas when report history is available through the existing allure-framework/allure-action@v0 publishing/history flow. On pushes to main, the same report job runs, so main metrics should become part of the published report history that later PR reports can compare against.

This PR does not add a separate immutable perf baseline registry. The fixed benchmark baseline for optimization PRs should still be captured separately after PR1, using the agreed datasets and run matrix.

Metrics

Timing metrics are grouped into:

• Allure lifecycle: total generation/restore/publish/summary timings.
• Generate: result discovery, filesystem read phases, reader work, plugin completion.
• Store: test-result ingestion, retry/history/resolution/indexing, attachment metadata.
• Awesome: server-side report data/file generation.
• Workload: neutral counters that explain input/output scale.

Checklist

• Sign Allure CLA
• Provide unit tests