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 refuses the whole adoption listing every mismatch and every missing expected file in one run. On --apply the writer lands the configuration and then the receipt, last, inside .release-kit/ and nothing else. 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 target file is ever changed: not a byte, not a mode, not a sentinel.

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