Cached builds retain their compatibility evidence

Reloading an unchanged compiled module now preserves the input fingerprint recorded when it was built. The fingerprint is retained only when the assembly identity and its other dependency records still agree. This prevents a cache reload from discarding evidence used to check a module's compatibility.

Reconnecting…
The connection to the server was interrupted. Trying to restore it…
Trying again…
The connection could not be restored. Reloading the page…
The server was updated. Reloading the page to pick up the latest version.