Module adopt 

rk adopt: a pre-record target becomes a recorded one.

A front over the direct writer: this binary’s projection is computed exactly as rk init would land it; every rendered destination must match it byte for byte, and one mismatch the operator did not name refuses the whole adoption, listing every mismatch and every missing expected file in one run. A mismatch or a missing file --replace names is a conflict the operator answered: on --apply its bytes are saved first, then the candidate is written. The writer then lands the configuration and the receipt, last. Blessing whatever is on disk would launder arbitrary drift into release-kit ownership, so nothing here ever takes the disk as the candidate, and no file outside .release-kit/ changes unless the operator named it.

SATISFIES landing:an-adoption-writes-the-record-and-nothing-else SATISFIES landing:a-missing-receipt-is-a-classification

Functions

run

Verify the target against the rendered candidate and, on --apply, write the config and receipt inside .release-kit/.