@descryy/viz 0.5.7 → 0.5.9

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.
Files changed (2) hide show
  1. package/README.md +3 -3
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -1,4 +1,4 @@
1
- # `@descry/viz`
1
+ # `@descryy/viz`
2
2
 
3
3
  A local, query-driven graph visualizer over an already-built graph. Search a
4
4
  symbol, see its bounded neighbourhood — never the whole graph at once.
@@ -7,7 +7,7 @@ symbol, see its bounded neighbourhood — never the whole graph at once.
7
7
  descry viz [--port <number>] [repository-path]
8
8
  ```
9
9
 
10
- Run `descry analyze` first — this reads an existing graph, it does not build one.
10
+ Build a graph first — this reads an existing graph, it does not build one. There is no `descry analyze` subcommand; build it from an MCP client with the `workspace` tool (`verb: "analyze"`).
11
11
 
12
12
  ## What it does
13
13
 
@@ -33,7 +33,7 @@ Run `descry analyze` first — this reads an existing graph, it does not build o
33
33
  - **No repository filter.** No per-node `repository` field exists in the graph schema today — a node's id hashes the repository but never hands it back. The filter is visibly present and disabled, with that reason stated, rather than omitted or faked.
34
34
  - **No force-directed layout, by choice.** Nodes lay out in deterministic depth-ordered columns from the search seed. "A legible path, not a cloud" was the actual design constraint; a physics simulation fights it at any real fan-out.
35
35
  - **No saved or bookmarked views** beyond the one-shot JSON export.
36
- - **Every edge renders dashed.** Resolution 4 (`observed`) is reserved for the runtime layer, which does not exist yet — nothing in a static-analysis graph can be `resolution === 4`, so the solid "observed" edge style is real but currently unreachable. It stays unreachable, honestly, until `descry-runtime` exists to produce it.
36
+ - **Only observed edges render solid.** Static edges (R0–R3) are dashed; resolution 4 (`observed`) edges are solid. A purely static graph has none — R4 edges appear only after the `observe` MCP tool (`verb: "runtime"`) has run the application and written what it witnessed.
37
37
 
38
38
  ## Reading the graph
39
39
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@descryy/viz",
3
- "version": "0.5.7",
3
+ "version": "0.5.9",
4
4
  "type": "module",
5
5
  "description": "A query-driven graph visualizer over the existing query layer: search a symbol, render its bounded neighbourhood, inspect the evidence behind a node or an edge. Never the whole graph at once.",
6
6
  "license": "MIT",
@@ -34,7 +34,7 @@
34
34
  "build": "tsc -b"
35
35
  },
36
36
  "dependencies": {
37
- "@descryy/core": "0.8.0",
37
+ "@descryy/core": "0.9.2",
38
38
  "@descryy/ir": "0.10.0"
39
39
  }
40
40
  }