Start with one documented promise and its owner. In this teaching record, cancellation after the first chunk must preserve the existing target. The requirement is a draft, with no real-project approval. Eligibility for the structural check does not make that promise approved for a real project. Three separate native snapshots each declare one cancellation cell. A missing witness file produces a warning and exit two. An existing weak witness and an existing strong witness both produce a structural pass and exit zero. These commands check the record and paths; they do not execute either witness. The separate behavior driver calls three renderer variants under two selected conditions, making six synchronous calls. Each begins with target bytes spelling KEEP and an unrelated file spelling OTHER. Independently authored expectations require unchanged files after cancellation, and target bytes A B after normal completion, with exact replies. The baseline returns cancelled with a published byte count of zero, yet the target contains A. Its normal case succeeds. The weak status check passes on that same cancellation observation. The stronger witness catches the changed target by comparing the complete reply and both selected files. The correction buffers in memory before an ordinary final write and matches both selected cases. A deliberately seeded always-cancel control preserves cancellation state but fails normal completion. Strong matches are one of two, two of two, and one of two. The successful wrapper records that expected contrast. Copy the free record and retain the exact source, commands, observations and limitations. For your project, assign the missing review or effect check and obtain the required approval. Asynchronous cancellation, failed writes, atomic publication, concurrency and general file-tree behavior were not tested. Those claims need their own evidence.