synartesis 0.3.3 → 0.3.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +17 -0
- package/README.md +29 -4
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,23 @@
|
|
|
2
2
|
|
|
3
3
|
What changed, and why it mattered. Dates are release dates.
|
|
4
4
|
|
|
5
|
+
## 0.3.4 — 2026-09-03
|
|
6
|
+
|
|
7
|
+
### Changed
|
|
8
|
+
|
|
9
|
+
- **The README shows what the tool does.** It opened with a heading and five
|
|
10
|
+
badges, and nothing above the fold showed a single line of output — for a
|
|
11
|
+
tool whose whole argument is what its output looks like. It now carries a
|
|
12
|
+
header lockup and two terminal shots of real output from
|
|
13
|
+
`demo/filesystem-demo.sh`: a clean rollback, and an undo halting on drift
|
|
14
|
+
rather than overwriting a colleague's edit.
|
|
15
|
+
|
|
16
|
+
This is the only reason for the release. npm cannot refresh a package page
|
|
17
|
+
without a version, so 0.3.3 kept serving the old README while the repository
|
|
18
|
+
served the new one. **No code changed**: every file under `dist/` and
|
|
19
|
+
`manifests/` is byte-identical to 0.3.3, verified by unpacking the published
|
|
20
|
+
tarball and diffing it against this one.
|
|
21
|
+
|
|
5
22
|
## 0.3.3 — 2026-09-03
|
|
6
23
|
|
|
7
24
|
### Changed
|
package/README.md
CHANGED
|
@@ -1,9 +1,12 @@
|
|
|
1
|
-
|
|
2
|
-
|
|
3
|
-
|
|
1
|
+
<!-- Absolute URLs, not relative paths: this README is also the npm package
|
|
2
|
+
page, and npm does not resolve relative image paths against the repo. -->
|
|
3
|
+
[](https://synartesis.online)
|
|
4
4
|
|
|
5
5
|
[](https://github.com/ArhaanDev24/Synartesis/actions/workflows/check.yml)
|
|
6
|
-
[](https://www.npmjs.com/package/synartesis)
|
|
7
|
+
[](https://www.npmjs.com/package/synartesis)
|
|
8
|
+
[](https://nodejs.org)
|
|
9
|
+
[](LICENSE)
|
|
7
10
|
|
|
8
11
|
An agent with write access to a real system runs twenty steps, misreads step
|
|
9
12
|
seven, and applies the rest to the wrong records. Today your options are to
|
|
@@ -18,6 +21,28 @@ It is not a sandbox: the container your agent runs in is disposable, but the
|
|
|
18
21
|
CRM row it updated over the network is not. It is not a tracing tool: a trace
|
|
19
22
|
tells you `update_customer` ran forty times, not what the values were before.
|
|
20
23
|
|
|
24
|
+
## What it looks like
|
|
25
|
+
|
|
26
|
+
Two commands, both real. The output below was produced by
|
|
27
|
+
[`./demo/filesystem-demo.sh`](demo/filesystem-demo.sh) against the official
|
|
28
|
+
filesystem MCP server and pasted, not typeset.
|
|
29
|
+
|
|
30
|
+
An agent overwrote a file and tried to move another. One command puts the
|
|
31
|
+
first back and reports that the second never happened:
|
|
32
|
+
|
|
33
|
+
|
|
34
|
+
|
|
35
|
+
`skip` is the interesting row. `move_file` is irreversible on that server, so
|
|
36
|
+
it was never applied in the first place — there is nothing to undo.
|
|
37
|
+
|
|
38
|
+
Now the same damage, except a colleague edited the file before you got to the
|
|
39
|
+
undo. Writing the old contents back would destroy their work, so it does not:
|
|
40
|
+
|
|
41
|
+
|
|
42
|
+
|
|
43
|
+
It stops at the record that moved and exits non-zero. Anything it had already
|
|
44
|
+
put back stays put back; `synartesis show` tells you what is left.
|
|
45
|
+
|
|
21
46
|
## What it can and cannot do
|
|
22
47
|
|
|
23
48
|
Every tool gets one of four classifications, which you write down in a manifest:
|