@nervur-org/dock 0.3.1 → 0.4.1

package/{human/quo-human.md → quo-human.md}

@@ -131,7 +131,7 @@ running there, from her cells, and painted by the same painter.
   on every device and no class carries a layout. A kind an estate wants and
   the grammar lacks is asked for here, and never written around.
 - **The painter emits the kit and nothing else.** Every node paints as a
-  piece of `papers/quo-ui.md`'s catalogue, a `stack` as `.nv-stack`, a
+  piece of `papers/nervur-ui.md`'s catalogue, a `stack` as `.nv-stack`, a
   `list` as `.nv-list` of `.nv-item`, a `person` as `.nv-person` with an
   `.nv-avatar`, a title as `.nv-t-title`, a form as the kit's fieldset and
   fields and one `.nv-button`, an answer as `.nv-answer` with the word it
@@ -326,7 +326,7 @@ Read with the trunk's "Carrying" and "The look", which this applies.
 - **Worlds have addresses, and so do the beings one holds.** `web./<ward>`
   is that world's page, `web./` lists the worlds shown, and a hostname per
   world is one proxy line, the estate's choice. Shown is the ward's own
-  mark, `quo show` and `quo hide`, hidden at `init`: a hidden ward is not
+  mark, `nervur show` and `nervur hide`, hidden at `init`: a hidden ward is not
   listed and a stranger at its page meets the plain door, while a link
   still knocks with its invitation and the desk still answers a proof, so
   an estate shows its face and leaves every home hidden. `quo.` stays one per harbor,
@@ -339,24 +339,24 @@ Read with the trunk's "Carrying" and "The look", which this applies.
   device paints as nothing, since an address adds no right. Every section
   on the world's page says where its own page is.
 - **A link is the page with the invitation in the fragment**, under the one
-  reserved key `quo`, the invitation compact as `ward.heir.secret` or
-  `ward` alone: `web.acme.com/shop#quo=...`. The fragment never leaves the
+  reserved key `nervur`, the invitation compact as `ward.heir.secret` or
+  `ward` alone: `web.acme.com/shop#nervur=...`. The fragment never leaves the
   browser, where a query string would reach the server, its logs and every
   referer. The tab reads it, strips it from the address bar before anything
   else runs, and joins. A page's own routing keeps the query, the path and
-  the rest of the fragment; only `quo` is taken. `beings/link.ts`.
+  the rest of the fragment; only `nervur` is taken. `beings/link.ts`.
 - **An answer that is an invitation paints as the link it is.** The only
   thing to do with one is to open it, and a being does not know where her
   page lives while the side does: the side builds the link on the world's
   page address, which is why the grammar carries no URL and this is not a
   node. It is how devices beget devices on a page: a human asks her user
   being's `device` for the next one and gets back a link to send, the same
-  link `quo invite` prints on the box. A side with an `admit` shows a guest
+  link `nervur invite` prints on the box. A side with an `admit` shows a guest
   the door instead, and that is the door alone.
 - **An invitation is self-addressing.** It names its ward by pk, so the
   path of the page it was opened on is a hint for humans and nothing more:
   the tab joins in the local ward of the ward the invitation names, and
-  the address follows. `web./#quo=...` is a complete way in for anyone
+  the address follows. `web./#nervur=...` is a complete way in for anyone
   holding an invitation to any ward the harbor hosts, and every ward has a
   page, whether or not anyone is at its door, so that a link into one has
   somewhere to land; a ward with no public being says it admits by

package/{mcp/quo-mcp.md → quo-mcp.md}

@@ -70,7 +70,7 @@ the two words give it what it needs to decide.
 
 The client speaks OAuth and lands the human on the allow page of the web
 route, where nothing is typed but an invitation: the one the root minted
-for this client on the user being with `quo invite`, and the identity it
+for this client on the user being with `nervur invite`, and the identity it
 will be. The invitation names its ward, so the world the client is let
 into is the invitation's, and the grant remembers it: a bearer is an
 identity in a world and a session is that identity's there. A session
@@ -144,11 +144,11 @@ process runs as the human on the device, and the avatar lives in the laptop
 harbor. No droplet is needed for this. A dialer harbor is enough, because the
 model is on the same machine as the ward it talks to.
 
-One thing to know when a client launches `quo side` or `quo pilot`: the MCP
+One thing to know when a client launches `nervur side` or `nervur pilot`: the MCP
 SDK spawns the server with a stripped environment, without `TMPDIR`. A
 harbor folder whose path is long gets its sockets in the temp dir under a
 hashed name, and the child then computes a different temp dir and finds no
-daemon. The default `~/.quo` is short and unaffected; for a long folder,
+daemon. The default `~/.nervur` is short and unaffected; for a long folder,
 hand the client the full environment.
 
 ### Two ways a model is driven
@@ -218,8 +218,8 @@ the dock ward's `agents` faculty, the way a schedule is placed on the
 clock, and it lives in her cells and in no file:
 
 ```bash
-quo ask --ward dock agents keep '{"id":"claude","ward":"main","command":"claude","args":["-p","--model","haiku"],"dir":"/home/quo/claude"}'
-quo ask --ward dock agents keep '{"id":"kimi","ward":"main","url":"https://openrouter.ai/api/v1","model":"moonshotai/kimi-k2","key":"..."}'
+nervur ask --ward dock agents keep '{"id":"claude","ward":"main","command":"claude","args":["-p","--model","haiku"],"dir":"/home/nervur/claude"}'
+nervur ask --ward dock agents keep '{"id":"kimi","ward":"main","url":"https://openrouter.ai/api/v1","model":"moonshotai/kimi-k2","key":"..."}'
 ```
 
 She runs at once and again at every boot; `drop` stops her and forgets the
@@ -271,16 +271,16 @@ runner pins, in `packages/dock/mcp/runner.ts`:
 Ten is a ceiling, not a permission: a turn that ends there has no final
 text, and the gate decided everything the model reached. The proof is
 `packages/dock/test/runner.test.ts` over a scripted endpoint on loopback, and the
-same suite runs one live turn when `QUO_MODEL_URL` names a real endpoint.
+same suite runs one live turn when `NERVUR_MODEL_URL` names a real endpoint.
 
-From a terminal the runner is `quo run --as NAME --url URL --model NAME`:
-the same pipe as `quo side`, with the model named in the hello line, so
+From a terminal the runner is `nervur run --as NAME --url URL --model NAME`:
+the same pipe as `nervur side`, with the model named in the hello line, so
 the daemon runs the runner beside the avatar it boots for the name. A line
 typed is a turn; the model's final text is a line back; a push from the
 user being starts a turn of its own and its text comes back the same way.
 A turn that ends at the ceiling, `--turns`, has no final text and comes
 back as an empty line; a model that fails comes back as one line holding
-an error object. The bearer, `QUO_MODEL_KEY`, is read by the command from
+an error object. The bearer, `NERVUR_MODEL_KEY`, is read by the command from
 the device and crosses only the local socket.
 
 ### A model as the owner
@@ -297,7 +297,7 @@ nothing and logs nothing: what a model did with it is in the host's own
 transcript, and an invitation it was handed is in no file of the dock's.
 The pilot is handed to one local agent by the device's own rules. A remote
 pilot is a standing at the ward, and still not a route: a model without a
-ward of its own cannot be an owner anywhere. `quo pilot --via S` is that
+ward of its own cannot be an owner anywhere. `nervur pilot --via S` is that
 pilot: S is a standing the user being here holds at the
 far ward, taken when the root here knocked for her with an invitation the
 far root minted on its ward's pk, and every tool call is a sealed ask

package/cli/estate/systems.quo.plist

@@ -1,44 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-  The daemon on a Mac, as the user, forever: a launchd agent. It holds the
-  harbor at ~/.quo and the socket to every quo. route ~/.quo/dial.json
-  names, so a Mac behind NAT is reached through the droplet it dialed. The
-  daemon runs the dock's emitted `dist/cli/quo.js` from where the estate
-  installed it, never the source. Install, with node on the path:
-
-    sed "s#HOME#$HOME#g; s#NODE#$(which node)#g" mac/systems.quo.plist > ~/Library/LaunchAgents/systems.quo.plist
-    launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/systems.quo.plist
-
-  Remove with `launchctl bootout gui/$(id -u)/systems.quo`; restart after a
-  wire change with `launchctl kickstart -k gui/$(id -u)/systems.quo`. The
-  log is ~/.quo/serve.log. No HTTP door: a Mac is a dialer, not a listener.
--->
-<plist version="1.0">
-<dict>
-  <key>Label</key>
-  <string>systems.quo</string>
-  <key>ProgramArguments</key>
-  <array>
-    <string>NODE</string>
-    <string>HOME/ESTATE/node_modules/@nervur-org/dock/dist/cli/quo.js</string>
-    <string>serve</string>
-  </array>
-  <key>EnvironmentVariables</key>
-  <dict>
-    <key>QUO_DIR</key>
-    <string>HOME/.quo</string>
-  </dict>
-  <key>WorkingDirectory</key>
-  <string>HOME/ESTATE</string>
-  <key>RunAtLoad</key>
-  <true/>
-  <key>KeepAlive</key>
-  <true/>
-  <key>ThrottleInterval</key>
-  <integer>2</integer>
-  <key>StandardOutPath</key>
-  <string>HOME/.quo/serve.log</string>
-  <key>StandardErrorPath</key>
-  <string>HOME/.quo/serve.log</string>
-</dict>
-</plist>