{"version":"2.1.275","anchor":"design-system-saves-now-report-which-files-were-written-vs","canonical_anchor":"design-system-saves-now-report-which-files-were-written-vs","heading":"File-tracking gains explicit written\/removed lists, including content-hash pins for artifacts","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/design-system-saves-now-report-which-files-were-written-vs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### File-tracking gains explicit written\/removed lists, including content-hash pins for artifacts\n\nArtifact and design-system save operations now report which files were written or removed, with artifacts also tracked by content hash\n\n**Unclear.** What the gating condition controls, and when files_written\/files_removed appear versus not, isn't stated.\n\n**What**\n\n- Artifact publish, read, and list results now feed a new tracking system that records each file's path, sha256 content hash, and version as a \"pin,\" tagged with where it came from (publish, list, or read). These pins are stored in a `pathPins` map that persists across conversation restore.\n\n- Design-system save operations gained a matching `files_written` (path + sha256) and `files_removed` (path) schema block in their response.\n\n**Why** This lets Claude Code know exactly which files a publish or save actually touched, including their content hashes, instead of only knowing that \"a save happened,\" making it possible to detect stale or unchanged files reliably.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}