Bytes-to-Pixels Ledger: which of a page's downloaded bytes actually painted anything

Counterfactual Browsing (two releases ago) subtracts one script from a saved page and shows you the pixels it caused. This generalizes the same move to DOWNLOADED RESOURCES: subtract an image, a stylesheet, a font or a tracking beacon from the sealed capsule, re-render deterministically, and diff - so you can see exactly which of a page's bytes turned into something you can see, and which cost download weight and painted nothing. The classic case it catches is the tracking pixel: a resource that downloaded real bytes and changed zero pixels is named as pure weight, offline, and the finding is sealed into the same re-derivable receipt as Counterfactual Browsing. It is proven end to end: a page loads a visible logo and an off-screen 1x1 beacon, both sealed into the capsule; the ledger attributes real pixels to the logo and exactly zero to the beacon even though the beacon cost bytes to fetch, bit-for-bit identically every run. This holds the score on purpose - it is a generalization of an existing capability rather than a new subsystem, so Security stays 44 and the overall stays 58 - but it is a real, useful tool that no other browser offers: an exact, offline, sealable answer to 'what did this resource actually do for me?'. It is available today under the hood, not yet as a one-tap panel in the app, and it shares the same honest limits as Counterfactual Browsing.