@elyx-design/cli 0.0.1-preview.15667.gc9ae1908b → 0.0.1-preview.16156.g8557f06bc

package/README.md

@@ -32,20 +32,20 @@ Alpine and other musl-based distributions are not currently supported.
 `cli.ts` is the npm launcher. `src/` contains the native entry point, commands,
 and their tests and fixtures. `CMakeLists.txt` builds the native `elyx` executable
 using Mosaic's shared language and rendering code. `cmake/` contains embedded
-resource generators. `cpp-vendors.yml` declares CLI11, libgit2, and the demo
-project used by `--create`.
+resource generators. The root `cpp-vendors.yml` declares its dependencies,
+including CLI11, libgit2, and the demo project used by `--create`.
 
 Run from the repository root:
 
 ```sh
-mise run vendors:elyx
+mise run vendors:cpp
 mise run elyx:build
 mise run elyx:test:cpp
 mise run cli:build
 ```
 
-The native debug executable is written to `out/native/debug/elyx` within this
-directory. The npm launcher builds to `dist/cli.js`. The published npm package
+The native debug executable is written to `out/native/debug/elyx` at the
+repository root. The npm launcher builds to `dist/cli.js`. The published npm package
 includes only the launcher, README, and license; platform packages supply the
 native executable.
 
@@ -53,9 +53,8 @@ The daemon also compiles rendering, inspection, lint, and scene code from
 `src/`. Mosaic uses its native font-loading code.
 
 The Figma reader and its CLI adapter live in `src/fig/`. Its miniz
-and Zstandard dependencies are also listed in `cpp-vendors.yml` and are only
-configured by the native CLI build. The daemon also builds the reader and
-converter using its own pinned dependencies for sidebar `.fig` imports.
+and Zstandard dependencies are also listed in the root `cpp-vendors.yml`. The
+daemon links the same reader and converter for sidebar `.fig` imports.
 Both native targets use libcurl for Google Fonts downloads (on Linux, install
 `libcurl4-openssl-dev` to build; macOS provides libcurl in its SDK).
 Windows builds the vendored curl with Schannel. Linux AppImages bundle the
@@ -165,36 +164,48 @@ files.
 ## Layer targets
 
 `elyx render` follows the input file's `__file__ {draw-connections: .true}`
-setting when drawing connection arrows. When rendering a layer with `--symbol`,
+setting when drawing connection arrows. When rendering a layer with `--ref`,
 only connections contained within that layer appear. Pass `--no-connections`
 to omit arrows from the PNG without changing the file.
 
-Inspection returns a `target` on component nodes and bounds, hit, and rectangle
-results. It contains `filePath`, `sourceRef`, and `overridePath`; a null target
-means the runtime layer has no reusable source address. Other fields such as
-`symbol`, `ref`, and `path` describe the layer, rather than identifying an exact
-instance occurrence.
+`elyx find` locates layers by exact reference (`--ref`), the topmost layer at a
+board-space point (`--at X,Y`), or the layers within a rectangle
+(`--in X,Y,W,H`), and returns their geometry in a `results` array. `elyx tree`
+returns the resolved layer tree of one layer (`--ref`) or, without one, of the
+file's board. Both echo their inputs: `find` under `query`, and `tree` as `ref`
+and `depth` (`"shallow"`, `"full"`, or an instance budget).
 
-Component nodes also carry the layer's `doc` note and its `meta` map, or null
-when absent. `meta` values keep their Elyx kind (string, number, or boolean),
-and instances report the `meta` they inherit from their source.
+Each find result and tree node carries a `target` containing `filePath`,
+`sourceRef`, and `overridePath`; a null target means the runtime layer has no
+reusable source address. Other fields such as `symbol`, `ref`, and `path`
+describe the layer, rather than identifying an exact instance occurrence.
 
-Every inspect result names its `command` and echoes its inputs under `query`.
-For `component`, that is the `selector` and the requested `depth` (`"shallow"`,
-`"full"`, or an instance budget).
+Tree nodes also carry the layer's `doc` note and its `meta` map, or null when
+absent. `meta` values keep their Elyx kind (string, number, or boolean), and
+instances report the `meta` they inherit from their source.
 
-Use the target's file path as the CLI input, `sourceRef` as inspect's `--ref` or
-render's `--symbol`, and `overridePath` as `--override-path`. For example:
+A value bound to a design token is written as `{"value": …, "token":
+"<file>#<group>.<member>"}` instead of the plain value. The token names the
+context-free declaration, so it stays the same under every `--context`, while
+`value` is resolved under the selection the tree reports as `contexts`. Sizes
+and constraints are `"auto"` for hugging content, numbers for fixed values,
+`"N%"` for relative values, and null when unset.
+
+Use the target's file path as the CLI input, `sourceRef` as `--ref`, and
+`overridePath` as `--override-path`. For example:
 
 ```sh
-elyx inspect component screen.elyx --ref=musicPlayer.track.save
-elyx inspect bounds screen.elyx --ref=card --override-path="'ui.Body.Label"
-elyx render screen.elyx --symbol=card --override-path="'ui.Body.Label" -o label.png
+elyx tree screen.elyx --ref=musicPlayer.track.save
+elyx find screen.elyx --ref=card
+elyx render screen.elyx --ref=card -o card.png
 ```
 
-Copy override paths from inspection; their namespace qualifiers distinguish
-imported descendants. Ambiguous source references fail instead of choosing an
-instance. In MCP, pass the returned object as `query.target` to inspect
-bounds/component, `target` to render, or an entry in focus's `targets` array.
-Spatial inspect queries use `query.filePath`. To render a whole document, pass
-`target: {filePath: "screen.elyx"}`.
+For descendants, copy `sourceRef` and `overridePath` from a target returned by
+find or tree without interpreting them. Ambiguous source references fail instead
+of choosing an instance. In MCP, pass the returned object as `select.target` to `elyx_find`,
+`root.target` to `elyx_tree`, `target` to render, or an entry in focus's
+`targets` array. Point and rectangle finds and whole-file trees use `filePath`.
+To render a whole document, pass `target: {filePath: "screen.elyx"}`.
+
+`elyx inspect bounds|hit|rect|component` are deprecated aliases for
+`find` and `tree`. They print a notice on stderr and emit the new output.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elyx-design/cli",
-  "version": "0.0.1-preview.15667.gc9ae1908b",
+  "version": "0.0.1-preview.16156.g8557f06bc",
   "description": "Command-line tools for Elyx",
   "license": "SEE LICENSE IN LICENSE",
   "repository": {
@@ -22,7 +22,7 @@
     "dist"
   ],
   "optionalDependencies": {
-    "@elyx-design/cli-darwin-arm64": "0.0.1-preview.15667.gc9ae1908b",
-    "@elyx-design/cli-linux-x64": "0.0.1-preview.15667.gc9ae1908b"
+    "@elyx-design/cli-darwin-arm64": "0.0.1-preview.16156.g8557f06bc",
+    "@elyx-design/cli-linux-x64": "0.0.1-preview.16156.g8557f06bc"
   }
 }