pi-outpost 0.17.1 → 0.19.0

package/README.md

@@ -7,7 +7,10 @@ npx pi-outpost init   # writes a starter pi-outpost.config.json here
 npx pi-outpost        # http://127.0.0.1:3141/
 ```
 
-Requires Node ≥ 22.19 and [pi](https://github.com/earendil-works/pi) configured (`~/.pi/agent/auth.json`, or a provider variable like `ANTHROPIC_API_KEY`).
+Requires Node ≥ 24 and a model credential (`~/.pi/agent/auth.json`, a provider variable
+like `ANTHROPIC_API_KEY`, or the setup screen). The default embedded runtime already carries
+the [pi coding agent](https://github.com/earendil-works/pi); a separate `pi` executable is
+needed only when `agentRuntime.mode` is `"rpc"`.
 
 ## It will not start without a configuration file
 
@@ -37,8 +40,12 @@ The **first** of these that exists is read, and only that one — configurations
 | `--cwd <dir>` | Directory the agent works in |
 | `--agent-dir <dir>` | pi config/session store (default `~/.pi/agent`) |
 | `--port <n>` / `--host <addr>` | Where to listen (default `127.0.0.1:3141`) |
+| `--offline` | Never fetch remote model catalogs |
+| `--open` / `--no-open` | Whether to open the interface once listening |
+| `--open-in window\|browser` | Open in a standalone window (default) or a browser tab |
 
-Environment: `PI_OUTPOST_PORT` (falls back to `PORT`), `PI_OUTPOST_HOST`, `PI_OUTPOST_CWD`, `PI_OUTPOST_AGENT_DIR`, `PI_OUTPOST_TOKEN`.
+Environment: `PI_OUTPOST_PORT` (falls back to `PORT`), `PI_OUTPOST_HOST`,
+`PI_OUTPOST_CWD`, `PI_OUTPOST_AGENT_DIR`, `PI_OUTPOST_TOKEN`, `PI_OFFLINE`.
 
 ## Security
 

package/dist/contract/README.md

@@ -118,6 +118,28 @@ Diagnostics name the rule and point at the value:
 
 Every broken rule is reported, not just the first.
 
+## Grouping graph and sequence elements
+
+Graphs and sequences may declare `data.containers`, then assign a node or participant with
+its `container` field:
+
+```json
+{
+  "schema": "urn:structured-exchange:1",
+  "kind": "graph",
+  "data": {
+    "containers": [{ "id": "backend", "label": "Backend", "kind": "service-group" }],
+    "nodes": [{ "id": "billing", "label": "Billing", "container": "backend" }],
+    "edges": []
+  }
+}
+```
+
+A container groups elements visually; it is not itself an element or relationship endpoint.
+Container identifiers must be unique, and every `container` reference must resolve to one
+declared in the same document. Moving an existing element between containers is a change, so
+put the new container id under `set.container` beside that element's `ref`.
+
 ## Getting a diagram into a document
 
 Use **download SVG**, then insert the file as a picture. Word does not accept an SVG
@@ -136,12 +158,14 @@ and an envelope declaring a table with a `target` or a `removal` is refused. It
 still report on a change it projects. Any row may declare what it plays:
 
 ```json
-"rows": [
-  { "role": "added",   "cells": ["REQ-5", "Log every actuation.", "draft"] },
-  { "role": "changed", "cells": ["REQ-2", "Signal a fault within 200 ms.", "in review"] },
-  { "role": "removed", "cells": ["REQ-3", "Read battery voltage at 10 Hz.", "withdrawn"] },
-  { "cells": ["REQ-1", "Stop within 40 m.", "approved"] }
-]
+{
+  "rows": [
+    { "role": "added",   "cells": ["REQ-5", "Log every actuation.", "draft"] },
+    { "role": "changed", "cells": ["REQ-2", "Signal a fault within 200 ms.", "in review"] },
+    { "role": "removed", "cells": ["REQ-3", "Read battery voltage at 10 Hz.", "withdrawn"] },
+    { "cells": ["REQ-1", "Stop within 40 m.", "approved"] }
+  ]
+}
 ```
 
 `role` is `added`, `changed`, `context` or `removed`, and it is rendered with the

package/dist/contract/conformance/README.md

@@ -23,11 +23,16 @@ JSON Schema decides shape. These are the relational rules that follow it, and th
 | Rule | What it refuses |
 |---|---|
 | `duplicate-identifier` | two elements sharing an envelope-scoped `id` |
+| `duplicate-container-identifier` | two containers sharing an `id` |
 | `unresolved-endpoint` | a relationship endpoint that no declared element carries |
+| `unresolved-container` | an element assigned to a container the document never declares |
 | `kind-data-mismatch` | a declared `kind` that disagrees with the data variant present |
 | `kind-not-proposable` | a `table` carrying a `target` or a `removal` |
 | `removal-without-target` | a removal in a document that targets nothing |
 | `duplicate-reference` | the same reference addressed twice — changed twice, or changed and removed |
+| `change-without-reference` | a `set` with no `ref` naming what should change |
+| `change-without-target` | a `set` in an envelope that names no target authority |
+| `too-many-kinds` | more distinct element or relationship kinds than the rendering can distinguish |
 | `row-column-mismatch` | a row whose length differs from the declared columns |
 
 Rules prefixed `schema/` come from the JSON Schema itself; the suffix is the keyword