fix(studio-server): history writes and claims follow Studio's write rule (#7988)

History undo, restore and Cmd+Z now leave alone every file that Studio's
file routes refuse to write. This covers tool-trusted, private, hidden and
node_modules paths, and scripts the project's package.json runs. Cmd+Z
passes over an edit that only changed such files. A claim no longer takes
such a file's pending change.

A claim's `overwrote` version now counts only when the server itself saw
that version at that path. A version stored for another file can no longer
become a file's earlier state.

The write rule also refuses more files that tools and agents load on
their own: opencode and crush settings, compose override files,
Dockerfile.* and Containerfile, every lefthook spelling, mise, nodemon,
devbox, wrangler, vercel and netlify settings, *.config.jsonc,
tsconfig.*.json, Taskfile.dist, simple-git-hooks, Ruby build files, and
.nix and .fish scripts.
This commit is contained in:
Michael Wang
2026-11-17 00:48:03 +00:00
committed by GitHub
parent 5979991d5f
commit 32fe10a8b3
7 changed files with 358 additions and 26 deletions
+5
View File
@@ -1874,6 +1874,11 @@ lists the newer entries. Run it again with `--just-this` to put back only that
entry's files over the newer edits, or `--back-to-before` to go back to before
it, undoing the newer entries too.
`undo` and `restore` put back only files that Studio itself may write. Package
and lock files, tool and agent configuration, scripts that `package.json` runs,
and hidden or private files keep their current content. Change those in your
editor.
## Render to a file
### `render`