@zh-xx/antu 0.9.1 → 0.11.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@zh-xx/antu",
-  "version": "0.9.1",
-  "description": "Antu: legal diagrams (fact, procedure, relationship, justification) from JSON, as one offline HTML page. The command line and the MCP server.",
+  "version": "0.11.0",
+  "description": "Antu: legal diagrams (fact, procedure, relationship, justification) from JSON, as one offline HTML page. The command line, the MCP server, and the entries to embed a diagram in an application.",
   "license": "AGPL-3.0-or-later",
   "author": "Ji Cheng",
   "homepage": "https://github.com/zh-xx/Antu",
@@ -26,6 +26,21 @@
     "antu": "bin/antu.mjs",
     "antu-mcp": "bin/antu-mcp.mjs"
   },
+  "exports": {
+    "./embed": {
+      "types": "./embed/antu-embed.d.ts",
+      "default": "./embed/antu-embed.js"
+    },
+    "./validate": {
+      "types": "./lib/validate.d.ts",
+      "default": "./lib/validate.mjs"
+    },
+    "./html": {
+      "types": "./lib/html.d.ts",
+      "default": "./lib/html.mjs"
+    },
+    "./package.json": "./package.json"
+  },
   "engines": {
     "node": ">=18"
   },

package/server.json

@@ -6,12 +6,12 @@
     "url": "https://github.com/zh-xx/Antu",
     "source": "github"
   },
-  "version": "0.9.1",
+  "version": "0.11.0",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "@zh-xx/antu",
-      "version": "0.9.1",
+      "version": "0.11.0",
       "transport": {
         "type": "stdio"
       }

package/spec/agent/fact/guide.md

@@ -112,3 +112,15 @@ diagram looks good. Always run `preview` and look before delivering.
 - **Keep the summary short.** `summary` fits one line of the card (about 22 full-width
   characters); a longer one is **rejected**, not truncated, because it would overflow
   the card. Put the long text in `detail`.
+
+## The examples
+
+Each adds one idea (`<name>.zh-CN.json`, `<name>.en.json`):
+
+- `1-minimal`: two parties, no `groups` (every card on the axis)
+- `2-single-actor`: one party
+- `3-groups`: `groupId` picks the side
+- `4-views`: the same data, two views
+- `5-duration`: spans and approximate times
+- `6-sources`: facts traced to sources
+- `7-undated`: no `date`

package/spec/agent/justification/guide.md

@@ -75,8 +75,9 @@ it twice.
 ## Big diagrams
 
 A reader can fold each issue up to its conclusion (its box title is a button; the dock has "Fold issues"), so a
-diagram of several issues can be read at a glance. Nothing to write for it: it is not in the JSON. Still split a
-diagram that grows past about 60 nodes.
+diagram of several issues can be read at a glance. Nothing to write for it: it is not in the JSON. A diagram whose
+text would be under 9 px fitted to a screen **opens with its issues folded** (`layout` says "Opens with the issues
+folded"). Still split a diagram that grows past about 60 nodes.
 
 ## After writing
 
@@ -98,3 +99,14 @@ render      the self-contained HTML
 - **`holds` is not for facts and norms; `date` is only for facts** (`2032-04-14` or `2032-04-14T22:22`).
 - **At least one conclusion has no outgoing link**: the conclusion the whole reasoning leads to.
 - **Do not invent a date**: leave `date` out when the source does not give one.
+
+## The examples
+
+Each adds one idea (`<name>.zh-CN.json`, `<name>.en.json`):
+
+- `1-minimal`: conclusion, norm, element, two facts
+- `2-against-and-rejected`: the rejected side
+- `3-issues`: one box per issue
+- `4-shared-fact`: one fact, two issues
+- `5-sources`: time and sources
+- `6-all-or-any`: and / or

package/spec/agent/procedure/guide.md

@@ -107,3 +107,15 @@ delivering.
 The reader can switch to the **route map**: the main line as one line, with rework loops and early endings
 hanging below it. It needs a clear main line, so **mark `main` along the whole line from start to end**
 (or on none, and the engine infers it). `kind: "route"` on `layout`, `preview` and `render` shows it.
+
+## The examples
+
+Each adds one idea (`<name>.zh-CN.json`, `<name>.en.json`):
+
+- `1-minimal`: three steps in a line
+- `2-decision`: decision point, conditions, edge back
+- `3-branches`: several edges from one step
+- `4-stages`: stages, actors, outcomes
+- `5-inferred-spine`: engine infers the main line
+- `6-merged-edges`: several edges to one target
+- `7-rules`: what may happen at any time

package/spec/agent/relationship/guide.md

@@ -90,3 +90,13 @@ render      the self-contained HTML
 - **`share` is only for `equity`, `amount` only for `debt` and `contract`, `secures` only for `guarantee`.**
 - **An entity nothing relates to floats beside the diagram** (a hint): relate it or leave it out.
 - **`amount` is a string**, written the way it should be read, with the currency.
+
+## The examples
+
+Each adds one idea (`<name>.zh-CN.json`, `<name>.en.json`):
+
+- `1-minimal`: one loan
+- `2-equity`: who holds whom, how much
+- `3-guarantee`: names the claim it secures
+- `4-groups`: camps
+- `5-kinship`: undirected beside directed relations