Module compare 

rk stage compare: what a landing from a stage would do, destination by destination, with the evidence that decides who owns each one.

The comparison reads the stage’s receipt, resolves its answers the way --stage does, and runs the production decision over the target as it stands, so the word a row carries is the word the landing prints. Each row states how the target’s bytes stand against the candidate, the destination’s kind, and, where the bytes differ, the provenance: the record half is whether the receipt vouches for the bytes on disk, and the history half is whether Git ever touched the path. A destination no receipt names also says whether its history shows an edit after the commit that brought it. The same verb is the proof after a landing: every rendered destination then reads equal.

SATISFIES staging:the-comparison-is-the-landing-decision

Structs

History

Whether the history half could be read.

Report

The machine form of rk stage compare.

Row

One destination, compared.

Constants

SCHEMA

The report’s shape version.

Functions

compare

Compare the stage at root with target.

rendered_equal

Whether every rendered destination of a report reads equal: the proof after a landing. A retired row is no candidate: the landing released it to the target, which owns its bytes from then on.