Module history_mode 

Window-independent projection of a managed record’s historical states.

The controller reads a rolled-back clone of the live Automerge document. It therefore neither commits an app’s open transaction nor gives a historical renderer access to a live record, persistence, or dispatch.

Modules

capability

How a widget takes part in document History: the capabilities an app root or a document owner provides, and the walks the runner uses to reach them.

checked_files

Typed checked-file state. No Automerge identity or document fallback exists here.

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”.

pending_controls

Finite custody for live controls that were queued before History opened.

preview

Presentation-only inputs. No live widget, document loan or service enters a preview.

registration

Explicit ownership and presentation registration for managed roots.

restore

Checked content-only historical restoration. The caller owns authorization and commit.

Structs

FrozenPreviewAssets

Keys are immutable historical content hashes admitted by the source owner. Absence is an unavailable historical asset, never a request for current bytes.

FrozenRootPreview

A past version drawn by a read-only root of the app over its frozen document.

HistoricalAssetRequest

A source reads only this immutable selected version when resolving media.

HistoricalAssetResponse

A single request-bound completion capability, never a live document handle. The provider cannot relabel an old result with another request’s identity.

HistoryController

HistoryDefinition

HistoryOwner

Captured by the actual mounted owner; callers cannot manufacture custody.

HistoryRegistration

HistoryResource

Full authority namespace for one historical resource.

HistoryScopeDefinition

HistorySnapshot

Immutable Automerge bytes at one exact causal frontier.

MakeHistory

The History code, as a program that fetches it on first use hands it over (install_history_code).

ManagedRoot

PreviewAccessibility

Descriptions and closed page-navigation targets only; never arbitrary actions.

PreviewInput

PreviewView

RestoreReview

Opaque proof that a particular selected state was reviewed against a particular live frontier. Validation grants no authority and writes nothing; the host must separately recheck permissions before restoring.

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.

HistoryError

HistoryPresentation

HistoryRegistrationError

HistorySourceRegistration

Immutable identity supplied by the owning runner. This carries no document. Bound runners resolve their actual checkout instead of accepting a foreign identity.

PreviewNavigation

PreviewSide

Which exact frontier of a selected change or group is being previewed.

Constants

HISTORY_PAGE

How many of the newest changes a history view describes when it opens, and how many more each request for earlier ones adds. Describing a change costs a replay step, so a long history opens at its latest page instead of replaying everything.

Statics

HISTORY

History’s code: linked, or with lazy-history fetched the first time a window registers History. Until then a window keeps its registration and shows without History.

Traits

HistoricalAssetSource

Host-registered resolver. It may complete immediately or on a worker; the same captured response key is checked on the owner thread in both cases. The trusted domain resolver derives content-hash references from the supplied immutable snapshot, not a live record or current media path. The framework checks response custody and byte integrity; it cannot infer a domain’s media schema. A missing recorded hash must remain unavailable.

HistoryPreview

Functions

builtin_history

The History code this build links: what the module a program fetches on first use hands over.

outline_preview

A past version drawn as its document outline ([outline_root]): the preview of a document whose app draws no version of its own.

Type Aliases

PreviewFactory