AW6 — Stabilize release debug snapshots, diagnostics, and maintenance surfaces

[joris97jansen]

Description

Stabilize all release debug snapshots and diagnostics that are intended to be long-term maintenance surfaces.

Borrowser has many debug outputs: parser, CSS, layout, paint, accessibility, networking, compositor, compatibility, performance, and guardrails. AW should decide which are stable release surfaces and make them deterministic.

The goal is to make post-release debugging reliable.

Requirements

• Inventory all debug snapshot surfaces.

• Classify snapshots:

  • stable release surface;

  • internal unstable debug;

  • test-only fixture;

  • deprecated.

• Stabilize stable release surfaces:

  • HTML parser/debug snapshots;

  • CSS parse/cascade/computed snapshots;

  • layout snapshots;

  • paint snapshots;

  • accessibility snapshots;

  • networking/cache/cookie snapshots;

  • compatibility reports;

  • compositor/display-list/damage snapshots;

  • performance/guardrail reports.

• Ensure stable snapshots avoid nondeterministic ordering.

• Ensure stable snapshots avoid memory addresses.

• Ensure stable snapshots avoid host-specific values unless normalized.

• Add versioning for snapshot formats where useful.

• Add docs for interpreting snapshots.

• Add tests for snapshot determinism.

• Add policy for updating exact snapshots.

• Add diagnostic truncation/budget behavior.

• Ensure diagnostics remain useful when truncated.

Exit Criteria

• Stable release debug surfaces are identified.

• Stable snapshots are deterministic.

• Snapshot docs exist.

• Snapshot update policy exists.

• Diagnostic budgets are enforced.

• Tests cover representative snapshot stability.

• The issue is closeable without freezing every internal debug helper.