@jefuriiij/synthra 0.1.23 → 0.1.24

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 CHANGED
@@ -7,6 +7,36 @@ For older versions, see [GitHub Releases](https://github.com/jefuriiij/synthra/r
7
7
 
8
8
  ---
9
9
 
10
+ ## [0.1.24] — 2026-06-06
11
+
12
+ ### Added
13
+
14
+ - **`syn doctor [path]` — setup and environment health check (issue #9).** New
15
+ read-only CLI subcommand that runs a one-shot checklist and exits. Checks: Node
16
+ version, `jq` availability (bash Stop/Prime hooks silently no-op without it),
17
+ `claude` CLI on PATH, graph freshness (symbol count, schema version, scan age),
18
+ `.mcp.json` project-scope registration (required for Synthra tools to appear in
19
+ the Claude Code IDE), CLAUDE.md policy-block version, and hook installation
20
+ status. Warnings surface with the exact `syn .` command needed to resolve them.
21
+ The command mutates nothing — safe to run at any time.
22
+
23
+ - **Graph-tool usage metric on the dashboard (issue #2).** The MCP server now
24
+ appends a record to `.synthra-graph/tool_log.jsonl` on every Synthra tool call
25
+ (`graph_continue`, `graph_read`, `graph_register_edit`, etc.). `delta.ts`
26
+ aggregates per-tool call counts into `ProjectStats.tool_calls` (per-project) and
27
+ `global.tool_calls` (cross-project totals). The dashboard shows a new "Graph
28
+ tools used" card in the right column with per-tool counts. This is a positive
29
+ signal complementing the Moat's blocked-Grep count: it captures Synthra pivots
30
+ that happen before a Grep fires, which the block counter misses entirely.
31
+
32
+ - **Session-aware routing — `graph_continue` seeds retrieval with the session's
33
+ touched files (issue #14).** Files the human recently saved (last 15 min) and
34
+ files the AI registered via `graph_register_edit` now get a ranking boost in
35
+ `graph_continue` results, so the returned context tracks what you're actually
36
+ working on. Mirrors the `/pack` route, which already seeded retrieval this way.
37
+
38
+ ---
39
+
10
40
  ## [0.1.23] — 2026-06-06
11
41
 
12
42
  ### Added