Keep your work within reach.

1. Save a private backup

Close other course tabs and copy any unsaved editor text first. This backup contains saved learning records only—not files on your computer, temporary browser reports, tutor conversations, passwords or account sessions. Notes and code can still contain private information; review sharing yourself.

Confirm the download saved before clearing browser storage. Keep your local project files separately. Empty, corrupt or older saved values remain raw in the backup; exporting does not repair them or certify their results.

2. Preview an import

Choose your own version-1 DVP Python backup, up to 8 MiB. This preview sends nothing to a server and runs no imported Python or HTML. Unknown keys, duplicate records and future formats are refused before learning records change.

I deliberately want to replace the listed conflicts.

Import preserves unrelated records and does not delete entries absent from the backup. Identical imports are idempotent. Imported results are untrusted learning history, not proof of independent work. A new write attempt replaces the previous recovery snapshot, even if that attempt fails. Keep a separate backup before every import. Close other course tabs before importing.

3. Recover the last write attempt

Before writing, import saves the affected original values on this device. If that recovery snapshot cannot be saved, learning records do not change. A failed write attempts recovery and reports if it is incomplete; browser storage is not an atomic transaction.

Undo refuses to overwrite affected records edited after import. Keep both your original backup and recovery download if repair is needed; do not blindly clear storage. Unrelated product/account data is never restored or removed.

4. Bring original Studio history with you

The original Studio is on a separate website. This page cannot read its browser storage or cloud notebook. Open original Studio in another tab and leave it available during the transition. No automatic sync or original-site change occurs.

1. Download the native backup above first. In the original Studio, review the course map and your completion ticks.
2. Expand a module below and select only the builds you remember marking complete there. The zero-based old key is shown beside its exact native destination. These are historical self-reports, not new passes.
3. For each notebook entry, use your own private text file as a backup. Copy the visible original lesson note, open its native Notes link below, then deliberately paste it after reviewing any existing text. This importer does not touch notes. Keep the original master notebook in your private file; there is no claimed cloud-note export.
4. Choose Preview historical record, inspect the mapped IDs in the import preview above, then Import or Cancel. Keep-current leaves an existing historical record unchanged; replacing it requires the same deliberate confirmation and recoverable before-image as a normal import.
5. Download another backup after importing, then reload this page to see saved history. Keep your original copies. A quiz, fresh coding task and defense still require their own evidence.

Loading the public 48-build source map. No learner data is requested.