{"version":"2.1.246","anchor":"a-slow-artifact-publish-can-no-longer-leak-into-the-next-con","canonical_anchor":"a-slow-artifact-publish-can-no-longer-leak-into-the-next-con","heading":"A slow artifact publish can no longer leak into the next conversation","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/a-slow-artifact-publish-can-no-longer-leak-into-the-next-con","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### A slow artifact publish can no longer leak into the next conversation\n\nA slow artifact publish finishing after \/clear no longer writes into your new conversation.\n\n**What**\n\nPublishing an artifact now records the account and conversation it started in, and the session state written after the server responds is only kept if both still match. A publish that finishes after `\/clear` or an account switch no longer writes its slug, verification record or cached contract into the new session.\n\n**Details**\n\n- The state guarded this way includes the registry of slugs published by this session, the last-publish record used for verification, and the cached publish contract pin.\n- Resetting a conversation without continuing it bumps the conversation counter and clears the published-slug registry.\n- Unconditional; both counters start at 0.\n\n**Evidence**\n\n`ownPublishedSlugs`\n\n- Area: Artifacts\n- Names: `\/clear`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}