{"version":"2.1.260","anchor":"publish-tool-now-tracks-approved-asset-copy-sources-across-a","canonical_anchor":"publish-tool-now-tracks-approved-asset-copy-sources-across-a","heading":"Publish tool now tracks approved asset-copy sources across a session","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/publish-tool-now-tracks-approved-asset-copy-sources-across-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Publish tool now tracks approved asset-copy sources across a session\n\nPublish now tracks approved asset-copy sources per session so consent persists.\n\nThe artifact publish permission-check path now threads an `approvedCopySources` set, keyed by `toolUseId`, through the publish flow, minted into the tool-call metadata (`copies`) alongside existing path\/redirect\/sha256 pin data. This is the plumbing that lets `copy_from`'s per-session consent persist without re-prompting.\n\n- Area: Artifacts\n- Names: `copy_from`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}