@jefuriiij/synthra 0.9.0 → 0.11.0

package/CHANGELOG.md

@@ -7,6 +7,42 @@ For older versions, see [GitHub Releases](https://github.com/jefuriiij/synthra/r
 
 ---
 
+## [0.11.0] — 2026-06-24
+
+### Added
+
+- **`graph_read` now shows which tests cover a symbol.** A symbol read appends a
+  `Tests (file-level): …` line listing the test files linked to the symbol's file
+  (via the graph's `tests` edges) — so after an edit you run the *right* test
+  instead of guessing or running the whole suite. Ordinary source files with no
+  linked test get a one-line "none linked" nudge.
+- **`blast_radius` is now symbol-aware.** A `file::symbol` target returns the
+  exact caller **symbols** that transitively call it (`name → file:line`), plus a
+  line naming the test files that guard the impact — the precise view you want
+  before a rename. A bare file target keeps the existing file-level dependent
+  list. (The `graph_read` "Used by (N)" footer remains the cheap always-on
+  direct-caller summary; this is the complete, transitive, on-demand one.)
+
+---
+
+## [0.10.0] — 2026-06-20
+
+### Added
+
+- **Terminal-bypass visibility (observe-only).** The Moat blocks `Grep`/`Glob`,
+  but the agent can still explore the codebase through the shell — `rg foo src/`,
+  `cat src/x.ts`, `find …` — and every such call is a read the graph could have
+  served in ~50 tokens. Synthra now watches `Bash` too: it classifies these
+  exploration commands and records each one — with whether the graph could have
+  answered it — to `bash_log.jsonl`, surfaced on the dashboard's Moat card as
+  "N terminal hunts · M the graph could answer." It is **observe-only — it never
+  blocks a Bash command** — so you can measure the leak before deciding whether
+  to close it. Conservative by design (it ignores `npm`/`git`/builds, stdin
+  filters like `… | grep`, and any command with a redirect). Disable with
+  `SYN_NO_BASH_OBSERVE`.
+
+---
+
 ## [0.9.0] — 2026-06-20
 
 ### Added