Current update,2026-10-15: production SAVE issues two256-byte WRITE requests for every512-byte sector, advances the far pointer after each successful half, and advances the logical sector after the second half.720 sectors require1440 writes; reopen/content comparison still reads512-byte sectors. Failure-half0/1 is meaningful only for WRITE phase2/3. The actual paired hardware test proved512 corruption versus exact2x256; whole-disk physical verification remains pending. ROOT d883c678/88669999 passes428+298+73 fresh checks; standalone exporter4001 bytes/f4c7cadb, twelve other helpers unchanged. Historical validation below identifies the previous union; latest evidence is agentworking/evidence/split-save-current-root-20261015.json.

> Development note: see [current status](STATUS.md), [build instructions](BUILD.md) and [installation](INSTALL.md) for present qualification. Historical measurements below apply to their stated slice, not every current build.


# Paused native floppy SAVE on the current runtime

This implementation adds development command7 SAVE and command9 CANCEL to the real 6502 runtime. From coherent PAUSED5, SAVE accepts a fresh owned output path, writes all720 sectors from the mounted360KiB REU floppy using CREATE_NEW, CLOSE/reopens READ-only, requires successful FILE_INFO declaring exactly368640 bytes, compares every byte, probes EOF and requires known final CLOSE. Genuine DOS continues to own INT21h, FAT and application loading. The mailbox interface is a development control surface; an end-user save/discard UI and media-generation binding remain open.

Normal execution retains32 guest-cache frames. SAVE rejects pins and conflicting FILE/HD/overlay ownership, flushes dirty frames, then temporarily borrows frames24..31 as B000-BFFF. It invalidates only those map entries and the fetch hint, preserves write epochs/lower24 frames, and restores the replacement hand and32-frame limit. SAVER code occupies B010-B7FF; comparison staging is B800-B9FF. FILE stays independently replaceable at C900-CFFF; permanent HDBIOS continuations perform entry, completion and cache restoration. An online HD is explicitly rejected.

The seventh immutable2KiB asset is copied from startup B000-B7FF to REU343000-3437FF before bitmap/cache ownership. The PRG is45057 bytes, loading0801-B7FF; source identity includes the SAVER header, payload, zero tail and AE00-AFFF gap. Startup protects27 actual512-byte cache frames within a28-frame span. Physical REU addresses remain within the minimum4MiB budget.

Actual current link evidence: FILE1170/1792, PIT1764/1792, SAVER1543/2032, HDBIOS2810/3584 (774 free), DEVICE4082/4096 (14 free), MAIN1runtime/0unit free, DEVICESTATE1009, BSS206. ZP usage remains36runtime/48unit within the192-byte configured arena. Cold lifetimes use3067runtime/4042unit of4096 bytes. CGA, IEC registrations, UCF2 diagnostics, exact PIT fast conversion and bounded native REU observation remain composed.

The layout is funded by a native-only UCI initializer simplification. Initialization only writes RAM/immediates, so it preserves P/A/X and untouchedY without changing $00/$01 or performing unnecessary bank changes. It retains interrupt masking and carry-clear return. Its61 bytes replace the original88-byte initializer. Actual Peddle compares both linked implementations over6144 cases (all256 incomingP values, eight bank modes and three cold/readiness states), checking exact state, flags, registers, stack, guards, poisoned shadow avoidance and permitted writes. Generic standalone UCI remains unchanged.

FILE_INFO opcode07 requires the known current target handle, one response block, no MORE/overflow flags,13..75 metadata bytes, nonempty NUL-free filename, regular-file attributes and exact fresh00,OK status. The exporter checks all four LE32 size bytes before READ can overwrite the buffer. The preserved368641-byte/zero-EOF counterexample is rejected before content READ. Error and cancellation retain original REU authority and uncertain output diagnostics; unknown closure or infrastructure failure blocks RUN. Logical metadata/content/closure verification does not establish filesystem flush, power-loss durability or exclusion of concurrent external mutation.

Fresh current-target validation:428default Zig tests,4direct FILE_INFO tests,13existing FILE tests,12native SAVE tests/36scenarios,27UCF2 tests,6144 initializer comparisons,298tooling tests, and16+256+512 bounded REU observer controls. A genuine DOS workflow executes MD/CD/COPY/TYPE/REN/IF/DEL/RD through all11 commands. At COPY checkpoint, SAVE/reopen reproduces all368640 bytes, leaves the guest counter418049 unchanged, preserves all4MiB REU and restores32 cache frames. Independent FAT parsing preserves all38 original entries, metadata, chains and contents across every checkpoint; D64TEST/T.TXT equals the original50-byte CONFIG.SYS.

Runtime SHA256 `ab2d0d5f4fa3eb1590ad9f2496630d0ae21ba7dab04cfece3ed9245f90edf0e9`; unit `06a4eead2af9ccab30f4cacddfa8b9508a79435474897c0787178868e530e675`. Strict standalone exporter deliberately changes to3968 bytes, `96c3491b10b80d212b222d4910c57b40418f11db5c6cb3a6498b8ec9dc7cea6d`; the other12 standalone PRGs reproduce exactly, including40fe service and3880 recovery. The genuine proof's441 live inputs and441 immutable copies are unchanged after execution. The actual model executable was observed running and hashed after completion; its hash is not a launch attestation.

Physical installed-firmware SAVE/reopen, independent complete file retrieval, retained changed-media authority before outer restoration, native save/discard UI and generation binding, HD-mounted SAVE, and IEC SAVE remain open. No current-target physical persistence or speed claim is made. First harness failures and stale snapshot expectations are retained in the private candidate handoff; no parent source or active hardware session was changed.
