@descryy/viz 0.5.8 → 0.5.10

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Descry
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,4 +1,4 @@
-# `@descry/viz`
+# `@descryy/viz`
 
 A local, query-driven graph visualizer over an already-built graph. Search a
 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.
 descry viz [--port <number>] [repository-path]
 ```
 
-Run `descry analyze` first — this reads an existing graph, it does not build one.
+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"`).
 
 ## What it does
 
@@ -33,7 +33,7 @@ Run `descry analyze` first — this reads an existing graph, it does not build o
 - **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.
 - **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.
 - **No saved or bookmarked views** beyond the one-shot JSON export.
-- **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.
+- **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.
 
 ## Reading the graph
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@descryy/viz",
-  "version": "0.5.8",
+  "version": "0.5.10",
   "type": "module",
   "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.",
   "license": "MIT",
@@ -30,11 +30,11 @@
     "registry": "https://registry.npmjs.org",
     "access": "public"
   },
+  "dependencies": {
+    "@descryy/core": "0.10.0",
+    "@descryy/ir": "0.11.0"
+  },
   "scripts": {
     "build": "tsc -b"
-  },
-  "dependencies": {
-    "@descryy/core": "0.9.1",
-    "@descryy/ir": "0.10.0"
   }
-}
+}