logEntryInternalFields_surviveAReopen

logEntryInternalFields_roundTripPerEntry on the far side of a restart — the boundary these three fields are actually lost at.

The two are not one property counted twice: they fail for different adapters. A storage whose schema has no column for is_no_op / config / dedup_key fails both. A storage that appends the LogEntry objects to a live list and serves entries() from it while persisting only three columns — the write-through cache, an entirely ordinary shape — passes the same-handle property and fails only here. And the restart is where the cost lands: the fields matter to a node that is rebuilding its state, not to one that never lost it.