scanruler-mcp 0.4.0 → 0.4.5

package/README.md

@@ -158,7 +158,10 @@ connects to that one, with the same token, and sends its calls through it.
 When the copy holding the port stops, another takes the port over, and the
 tab — which keeps trying — connects to it within ten seconds.
 `scanruler_status` says which this copy is (`server.role`: `holder`,
-`relay`, or `none` with `server.error` saying why). Copies with different
+`relay` — with the holding copy's version as `server.holder.version` —, or
+`none` with `server.error` saying why). The page judges the copy holding
+its connection: when that one is out of date, a relaying copy's status says
+so, and quitting the app that started it lets a current copy take over. Copies with different
 tokens cannot share a port: give them the same `SCANRULER_MCP_TOKEN`, or
 each its own `--port`. Changes from several agents run one after another in
 the tab, each one step of the same undo history.
@@ -221,8 +224,9 @@ that return a picture — `view_render`, `section_render`, `flat_render` and
   lets the model call a tool it was not given can call them directly too.
 - The tools that return a picture are listed so the model calls them
   directly and sees the picture. In a batch a picture is not shown: it is
-  written to a file, the call's `path` or a new file in the output folder
-  (`--out`), and the call's result names it. A tab that connects with
+  written to a file, the call's `path` or a new file in the open scan's
+  folder (the output folder, `--out`, while no scan or project was opened
+  from one), and the call's result names it. A tab that connects with
   another picture tool has the client list the tools again.
 
 **LM Studio**: add `--tools` and `compact` to the server's arguments as two
@@ -282,8 +286,9 @@ last tab that connected, which the server keeps in its config folder
 (`tools.json`), or, the first time, the app's own; a client that lists the
 tools once, when it starts, sees them all that way, and one that listens is
 told when the list changes. Six more are the server's: `scanruler_status`
-(is a tab connected, which version, how to pair one, and what the tab's
-session holds — its scan, project, unsaved changes and work counted — and,
+(is a tab connected, which version, how to pair one, what the tab's
+session holds — its scan, project, unsaved changes and work counted — the
+time on this computer with its offset from UTC (`server.now`), and,
 when the client's list is out of date, which tools were added, removed or
 changed since and which page it came from),
 `scanruler_open` (open ScanRuler in the default browser, paired, and wait
@@ -320,8 +325,34 @@ listed; the rest are read through a seventh of the server's own,
 - **Arguments from a file.** `{ "$file": path }` anywhere in a tool's
   arguments — an object of that one key — is replaced by the JSON the file
   holds: a long list of stations a script wrote need not pass through the
-  conversation. A relative path is taken from the folder the server was
-  started in.
+  conversation.
+- **Relative paths** — a batch's `file`, `$file`, a file to open, an
+  output's `path` — are taken from the open scan's folder, or from the folder
+  the server was started in while no scan is open; `scanruler_status` gives
+  both (`server.relativeTo`, `server.cwd`). A picture or file written into a
+  folder is numbered past one already there (`-2`, `-3`), never written over.
+- **Long answers.** An answer past what one carries (40 k characters; a
+  guide 90 k — several guides asked for together come while they fit about
+  80 k, the rest named in `next`) is written whole to a JSON file in the
+  open scan's folder, where an agent that may only read there can open it —
+  in the output folder (`--out`) while the scan open now was not opened from
+  a folder through this server. The answer says
+  `truncated: true`, the `file`, its short fields and the person's notes,
+  and its `note` says which folder it went to and how to ask for less — by
+  the command's own fields, as the command says it (a guide a section at a
+  time).
+- **Strings of JSON.** A client that sends a large nested value as a string
+  — a batch's `calls`, a call in it, or a call's `arguments` — has it read as
+  the JSON it holds; one that is not JSON is refused saying so, with nothing
+  run.
+- **A tab that reloaded.** A tab says who it is each time it loads. When a
+  tab that held work comes back as another — reloaded by the person, by the
+  dev server after an edit, or unloaded by the browser — the next answer
+  says so (`pageReloaded`), with the project file last opened or saved here,
+  which `scanruler_status` gives too (`lastProject`, kept in
+  `folders.json`). A tab older than the app it came from, which could not
+  load a part of it, answers `stale_page`, and the status says so from then
+  on (`page.stale`): save the project before the tab is reloaded.
 - **Pictures.** `view_render` comes back as an image the agent sees — the
   3D view as the tab shows it, after `view_set` has turned it if asked — and
   is written to a file only when the call gives `path`. `show` puts the
@@ -356,7 +387,9 @@ listed; the rest are read through a seventh of the server's own,
   `retried: "busy"`. `timings:
   true` gives each call its `ms`, the batch its `total_ms`, and a change's
   build the steps it played with their milliseconds (`result.steps.played`;
-  otherwise only how many it played and took up from a state held).
+  otherwise only how many it played and took up from a state held). The
+  notes left for the agent (`notes`), when a call answers with them, are
+  repeated at the batch's top as the last call gave them.
 - **Long changes.** Every tool that changes the session takes `wait`, and
   so does a read the tab marks long (a comparison over whole bodies, say);
   `wait: false` answers at once with `{ queued: true, job }` while the call

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "scanruler-mcp",
-  "version": "0.4.0",
+  "version": "0.4.5",
   "description": "Drive ScanRuler, the 3D-scan measuring tool, from an AI agent: a local MCP server that reaches the ScanRuler tab open in your browser.",
   "type": "module",
   "license": "AGPL-3.0-only",
@@ -11,11 +11,22 @@
     "url": "git+https://github.com/CNCKitchen/scanruler.git",
     "directory": "mcp"
   },
-  "keywords": ["mcp", "model-context-protocol", "3d-scan", "metrology", "scanruler"],
+  "keywords": [
+    "mcp",
+    "model-context-protocol",
+    "3d-scan",
+    "metrology",
+    "scanruler"
+  ],
   "bin": {
     "scanruler-mcp": "bin/scanruler-mcp.js"
   },
-  "files": ["bin", "src", "README.md", "LICENSE"],
+  "files": [
+    "bin",
+    "src",
+    "README.md",
+    "LICENSE"
+  ],
   "engines": {
     "node": ">=22"
   },