AW7 — Finalize release performance, memory, resource budgets, and retained-reuse targets

[joris97jansen]

Description

Finalize release performance, memory, resource guardrails, and retained rendering reuse targets.

This issue should gather benchmark data from AU and AV, set release thresholds, and decide which regressions block release.

The goal is to make the static engine release measurable, not just functionally correct.

Requirements

• Finalize benchmark corpus.

• Finalize CI-safe benchmark subset.

• Finalize extended local benchmark subset.

• Track phase timings:

  • document load;

  • HTML parse;

  • CSS parse;

  • cascade/computed style;

  • layout;

  • paint;

  • accessibility tree;

  • compositor/display-list/damage;

  • total page assembly.

• Track memory/allocation metrics where feasible.

• Track retained reuse rates:

  • style;

  • layout;

  • paint;

  • display list;

  • raster artifacts.

• Track resource budgets:

  • DOM nodes;

  • CSS rules;

  • selectors;

  • layout boxes;

  • paint/display items;

  • accessibility nodes;

  • images;

  • cache/cookie state.

• Define release thresholds or review thresholds.

• Define release-blocking performance regressions.

• Add benchmark summary report.

• Add budget summary report.

• Add docs for interpreting benchmark changes.

• Ensure guardrails fail gracefully with typed errors.

• Add tests for budget report determinism.

Exit Criteria

• Release benchmark suite is finalized.

• Performance/memory/resource budget reports exist.

• Release thresholds or review rules are documented.

• Retained reuse metrics are reported.

• Guardrail behavior is release-audited.

• Performance regressions can be classified as blockers or accepted.

• The issue is closeable without claiming performance parity with existing browsers.