@premsan/cli 0.0.0-stage → 0.1.0

package/package.json

@@ -1,6 +1,52 @@
 {
   "name": "@premsan/cli",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
+  "version": "0.1.0",
+  "description": "Every Premsan assistant in your terminal: your conversations in each product, answered where you work.",
+  "license": "MIT",
+  "type": "module",
+  "bin": {
+    "premsan": "./dist/premsan.mjs"
+  },
+  "files": [
+    "dist",
+    "skill",
+    "README.md"
+  ],
+  "engines": {
+    "node": ">=22"
+  },
+  "exports": {},
+  "devDependencies": {
+    "@earendil-works/pi-tui": "1.5.0",
+    "@xterm/headless": "6.0.0",
+    "@types/node": "^24.13.6",
+    "@types/react": "^19.3.0",
+    "esbuild": "^0.28.2",
+    "react": "^19.3.0",
+    "typescript": "^7.0.2",
+    "vitest": "^5.0.5",
+    "@agents/auth": "0.0.1",
+    "@agents/contract": "0.0.1",
+    "@agents/narrow": "0.0.1",
+    "@agents/client": "0.0.1",
+    "@agents/console": "0.0.1",
+    "@agents/loop": "0.0.1",
+    "@agents/i18n": "0.0.1",
+    "@agents/scripts": "0.0.0"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "keywords": [
+    "premsan",
+    "assistant",
+    "cli",
+    "tui"
+  ],
+  "scripts": {
+    "typecheck": "tsc --noEmit",
+    "test": "vitest run",
+    "build": "node scripts/bundle.ts && node ../../scripts/release-check.ts",
+    "local": "node scripts/bundle.ts local"
+  }
 }

package/skill/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: premsan
+description: Work with the assistants in Premsan's products (Paperingo, Resumical, PerSQL and the rest) through the premsan command - start and continue a conversation, answer the assistant's questions, apply its proposals. Use when the user asks for something done in one of those products.
+---
+
+# premsan
+
+`premsan` reaches the assistant in every Premsan product. Each assistant works on the user's own data in that product, so do only what the user asked.
+
+## Install
+
+- `npm install -g @premsan/cli` installs `premsan`, on Node 22 or later.
+- `npx -y @premsan/cli <command>` runs it once without installing.
+
+## Sign in
+
+- `premsan products` lists every product with its API host and the variable that holds its key.
+- A developer key signs in without a browser: the user makes one in the product's web app, under Settings, Account, Developer keys, and sets it as that variable (`PAPERINGO_KEY` for Paperingo).
+- In a sandbox, the product's API host must be allowed in the sandbox's network settings.
+- On the user's own machine, `premsan login <product>` signs in through the browser instead.
+
+## Find the tools
+
+- `premsan <product> tools --json` lists every tool the product offers, with its input schema.
+- Every tool is a command: `premsan <product> <tool> <required arguments, in order> [--name value]`.
+- `premsan <product> <tool> --help` shows its arguments. `--input '<json>'` passes them all at once, and `-` as a value reads it from standard input.
+- Results print as JSON.
+
+## Work with the assistant
+
+1. `premsan <product> list_conversations` lists the user's conversations. Where the product has its own assistant, its id is `conversation` and it comes first; new work starts there, or with the product's own tool, such as `premsan paperingo new_paper "<instruction>"`.
+2. `premsan <product> send_message <conversation> "<message>"` sends a message and waits for the reply for a while. When the result says `"running": true`, run `premsan <product> read_conversation <conversation> --wait` until it says `false`.
+3. When the last run has a `question`, ask the user, then answer each question by its id: `premsan <product> answer_question <conversation> '[{"id":"<id>","answers":["<an option, or the user's words>"]}]'`.
+4. A run's `proposals` change nothing until `premsan <product> decide_proposal <conversation> <proposal> true`, so ask the user first; `false` discards one.
+5. `premsan <product> stop_run <conversation>` stops a run; what it did stays.
+
+## Exit codes
+
+| Code | Meaning | What to do |
+| ---- | ------- | ---------- |
+| 0 | Done | Read the JSON |
+| 1 | Failed | Read the message |
+| 2 | The arguments do not fit the command | Run it with `--help` |
+| 3 | Not signed in | Set the key's variable, or run `premsan login <product>` |
+| 4 | The user has not allowed the assistant | The user allows it once in the product's web app, at the address in the message |
+| 5 | The plan does not cover this | The user subscribes in the product's Settings |
+| 6 | Too many turns this hour | Wait as long as the message says |
+| 7 | The API could not be reached | Allow the host the message names in the sandbox's network settings |
+
+With `--json`, a failure prints `{"error": {"message", "code", "url", "retryAfter"}}`.
+
+## MCP
+
+Each product also serves these tools over MCP at `https://<API host>/mcp`, with the key as `Authorization: Bearer <key>`, for clients that connect to MCP servers.