@jefuriiij/synthra 0.9.0 → 0.10.0
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 +18 -0
- package/dist/cli/index.js +247 -30
- package/dist/cli/index.js.map +1 -1
- package/dist/dashboard/index.js +31 -7
- package/dist/dashboard/index.js.map +1 -1
- package/dist/server/index.js +211 -20
- package/dist/server/index.js.map +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,24 @@ For older versions, see [GitHub Releases](https://github.com/jefuriiij/synthra/r
|
|
|
7
7
|
|
|
8
8
|
---
|
|
9
9
|
|
|
10
|
+
## [0.10.0] — 2026-06-20
|
|
11
|
+
|
|
12
|
+
### Added
|
|
13
|
+
|
|
14
|
+
- **Terminal-bypass visibility (observe-only).** The Moat blocks `Grep`/`Glob`,
|
|
15
|
+
but the agent can still explore the codebase through the shell — `rg foo src/`,
|
|
16
|
+
`cat src/x.ts`, `find …` — and every such call is a read the graph could have
|
|
17
|
+
served in ~50 tokens. Synthra now watches `Bash` too: it classifies these
|
|
18
|
+
exploration commands and records each one — with whether the graph could have
|
|
19
|
+
answered it — to `bash_log.jsonl`, surfaced on the dashboard's Moat card as
|
|
20
|
+
"N terminal hunts · M the graph could answer." It is **observe-only — it never
|
|
21
|
+
blocks a Bash command** — so you can measure the leak before deciding whether
|
|
22
|
+
to close it. Conservative by design (it ignores `npm`/`git`/builds, stdin
|
|
23
|
+
filters like `… | grep`, and any command with a redirect). Disable with
|
|
24
|
+
`SYN_NO_BASH_OBSERVE`.
|
|
25
|
+
|
|
26
|
+
---
|
|
27
|
+
|
|
10
28
|
## [0.9.0] — 2026-06-20
|
|
11
29
|
|
|
12
30
|
### Added
|