Module coverage 

What History can honestly do with a resource type: one classification the panel, the read door and the restore review all read, so “no past version here” is never confused with “this text does not read”, “written by a newer app” or “this type keeps no content history”.

The classification is derived from what the resource type itself declared, never guessed per app: the schema history restores content with, and whether the type has a read adapter. A version of a type that reads its record is answered by that adapter, exactly as the live record is; one with neither a restore schema nor a read adapter has nothing of its content to show.

Structs

TypeHistory

What the common historical surface of a resource type answers, whatever the app: the check run when a restore schema is registered, and the per-type classification the History panel and the read door read.

Enums

HistoricalGap

Why a version of a resource cannot be shown or restored, in the three ways they differ for a person: the type cannot at all, this record holds nothing to show, or the version was written by another schema.

HistoricalSupport

What History can do with one resource type.