{"version":"2.1.234","anchor":"unsaved-artifact-edits-kept-across-a-reload-with-save-and-di","canonical_anchor":"unsaved-artifact-edits-kept-across-a-reload-with-save-and-di","heading":"Unsaved artifact edits kept across a reload, with Save and Discard buttons","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/unsaved-artifact-edits-kept-across-a-reload-with-save-and-di","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Unsaved artifact edits kept across a reload, with Save and Discard buttons\n\nUnsaved artifact edits could survive a reload with Save and Discard buttons, but the skill is off.\n\n**What**\n\nIn the artifact editing skill, edits you have not saved are stashed in the browser's session storage and offered back after a reload. The skill's registration check is false in this build, so nothing reaches it.\n\n**Details**\n\n- The copy is written on a 1 second throttle while the page is dirty and again on `pagehide`, under a key built from `'kit:unsaved:'` plus the page host, with a 24 hour expiry.\n- A page that loads with a stashed copy shows it in place of the served article, held read-only, with two new toolbar buttons: a second Save (`data-restore`) and a Discard (`data-discard`) that drops the copy and reloads the served version.\n- Cursor block index and scroll position ride a separate 2 minute stash keyed `'kit:restore:'` plus host, so a save-triggered reload lands where you were.\n- The status text distinguishes a copy taken over the same version from one taken over a newer one.\n\n**Evidence**\n\n`Showing recovered edits over a newer version. Saving replaces it.`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}