Unclear What the gating condition controls, and when files_written/files_removed appear versus not, isn't stated.
What
- 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
pathPinsmap that persists across conversation restore. - Design-system save operations gained a matching
files_written(path + sha256) andfiles_removed(path) schema block in their response.
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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What the gating condition controls, and when files_written/files_removed appear versus not, isn't stated.