robisie 0.1.2 → 0.1.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/docs/README.en.md CHANGED
@@ -1,14 +1,16 @@
1
- # robisie — from account to accepted card (package 0.1.2)
1
+ # robisie — from account to accepted card (package 0.1.4)
2
2
 
3
3
  Polski: [README.md](README.md).
4
4
 
5
5
  <!-- sekcja: dostepnosc -->
6
6
  ## Availability
7
7
 
8
- An account and key are needed for init and the roles. Separately, `npx robisie doctor --engine-config ./robisie.config.json` checks only configuration structure offline: it does not confirm project UUID, repo, models or provider execution. The guides shipped in this package are local at `node_modules/robisie/docs/README.md` and `node_modules/robisie/docs/README.en.md`; no website fetch is needed.
8
+ An account and key are needed for init and the roles. Offline configuration validation is a separate entry point when the CLI is available: it does not check the installation, start providers or require a project UUID from you. Separately, `npx robisie doctor --engine-config ./robisie.config.json` checks only configuration structure offline: it does not confirm project UUID, repo, models or provider execution. The guides shipped in this package are local at `node_modules/robisie/docs/README.md` and `node_modules/robisie/docs/README.en.md`; no website fetch is needed.
9
9
 
10
10
  Install robisie from npm in the prepared directory; run subsequent commands and agent sessions there. [Preparation](#wymagania) → [account](#konto) → [key](#klucz) → [installation](#instalacja) → [acceptance](#recenzja-i-odbior).
11
11
 
12
+ If the registry README is empty, use the guides shipped locally at `node_modules/robisie/docs/`. Registry metadata and publication require separate release work.
13
+
12
14
  <!-- sekcja: wymagania -->
13
15
  <a id="wymagania"></a>
14
16
  ## Requirements
@@ -23,15 +25,23 @@ Prepare an empty directory on disk. You do not need a website or your own `packa
23
25
 
24
26
  The human signs in at https://robisie.app with Google or an email link. Wait for the first project's readiness screen. If readiness is missing, use the fallback link to https://robisie.app/dashboard/plugins/planer and prepare a project in the dashboard; the bounded readiness checks are not a provisioning time guarantee.
25
27
 
26
- The CEO requires authenticated discovery to return exactly one project. A dashboard project is not a directory on disk: confirm with the CEO that both concern the same goal before work. With zero projects, the human checks readiness and the dashboard fallback; with several, the human must organize/archive extras until discovery returns one. Clicking a project does not bind it for the CEO. Do not supply a project UUID in chat; the CEO takes its identifier only from discovery. Result: one recognized project before any agent write.
28
+ Project lookup is the authenticated read of active projects through `list_projects`; the key scopes what the agent sees. The CEO requires authenticated `list_projects` to return exactly one project. A dashboard project is not a directory on disk: confirm with the CEO that both concern the same goal before work. With zero projects, the human checks readiness and the dashboard fallback; with several, the human must organize/archive extras until `list_projects` returns one. Clicking a project does not bind it for the CEO. Do not supply a project UUID in chat; the CEO takes its identifier only from `list_projects`. Result: one recognized project before any agent write.
27
29
 
28
30
  <!-- sekcja: klucz -->
29
31
  <a id="klucz"></a>
30
32
  ## Key in Connect
31
33
 
34
+ <!-- agent-consent:start -->
35
+ ### Agent instructions — one authorization for the flow
36
+
37
+ At the start, ask once for authorization for a named flow and its boundaries: your own account, permission to generate a key, secure local storage of the key, init and the first agreed card (goal, directory, write scope and result criteria). The first-card example below covers only `wynik.txt`; agree on it with the owner before asking for authorization.
38
+
39
+ If the owner has already authorized this flow, do not ask again at those steps; continue within the agreed boundaries. A missing authorization, null, empty or unclear answer or scope change requires a question before the dependent step; continue independent authorized work. Respect a refusal: do not perform the refused steps. Authorization does not bypass protected human or provider confirmations; continue after confirmation. Keep the key out of chat, cards, arguments and command history; if secure storage or transfer is unavailable, the human uses init's hidden prompt. Someone else's open session gives no access to their account. Independent review and separate final acceptance of the result by the owner are still required.
40
+ <!-- agent-consent:end -->
41
+
32
42
  At https://robisie.app/dashboard/connect the human selects `worker` and a recognizable label, such as “tester laptop”, then generates the key. It is shown only once: store it like a password. The human supplies it outside chat to init's hidden prompt, never to chat, a card, a command argument or shell history.
33
43
 
34
- `worker` is the minimal path: read, create/update projects, tracks and cards, reserve work; no setting `done` through create/update. `observer` only reads. `full` adds deletion and closing decision matters; `owner_validator` has the same access level as full. `seeder` has narrow access to `get_task` and valid seeding through `append_detail`, without `list_projects`/board reads, so it cannot follow this guide.
44
+ `worker` is the minimal path: read, create/update projects, tracks and cards, reserve work; no setting `done` through create/update. `observer` only reads. Explicitly choose `worker` each time: later keys default to `observer` (the first-key screen may preselect worker); do not infer permissions from that default. `full` adds deletion and closing decision matters; `owner_validator` has the same access level as full. `seeder` has narrow access to `get_task` and valid seeding through `append_detail`, without `list_projects`/board reads, so it cannot follow this guide.
35
45
 
36
46
  The package stores **one key for CEO, Builder and Quality Officer** as `ROBISIE_KEY`. Role names do not change permissions. Do not use full to bypass acceptance of `done`: the owner accepts in the dashboard without broadening the agent's key.
37
47
 
@@ -39,6 +49,10 @@ The package stores **one key for CEO, Builder and Quality Officer** as `ROBISIE_
39
49
  <a id="instalacja"></a>
40
50
  ## Install from npm
41
51
 
52
+ All three installer roles use one provider: CEO (`ceo`), Builder (`builder`), Quality Officer (`quality`). Mixed assignments do not route execution across providers and doctor returns exit 1. For Claude, use the full assignment `npx robisie init --agent claude --role ceo=claude --role builder=claude --role quality=claude` in place of the init line below. For Codex/OpenCode, replace every `claude` with `codex`/`opencode`; `--agent` alone does not clear an earlier map.
53
+
54
+ The installer settings `ceo`/`builder`/`quality` (CEO/Builder/Quality Officer) are separate from the execution registry `roleRegistry`: `worker-client`, `lead-client`, `reviewer-client`, `tester-client`. Project names `coordinator`/`owner`/`planner`/`advisor` are another setting. There is no automatic conversion between these settings; the registry does not enable mixed installer-role execution.
55
+
42
56
  After preparing the account and key, the human opens a terminal and enters the chosen empty directory (replace the example path below). The Node.js step below creates a local `package.json` regardless of the directory name, including spaces and Polish characters. The manifest sets the installation directory even under an ancestor containing `node_modules`. If the `package.json` path already exists (including a symlink), the step refuses to write; it never overwrites it. Failure to enter the directory or create the manifest stops the rest of the block. Then: install, init with the hidden key prompt, doctor. In zsh/bash clear stale ENV before init and load the saved key before doctor — init cannot set its parent environment:
43
57
 
44
58
  ```sh
@@ -46,23 +60,67 @@ cd "/path/to/empty directory" &&
46
60
  node -e 'try {
47
61
  require("node:fs").writeFileSync("package.json", "{\"private\":true}\n", { flag: "wx" });
48
62
  } catch (error) {
49
- console.error(error.message);
63
+ console.error("Cannot create package.json; it may already exist or the path may be inaccessible. Next step: preserve the path and use the existing-project/reinstallation instructions below; resolve links/directories or access errors locally before retrying.");
50
64
  process.exit(1);
51
65
  }' &&
52
66
  {
67
+ set +x
53
68
  npm i robisie &&
54
69
  unset ROBISIE_KEY &&
55
70
  npx robisie init --agent claude &&
56
- [ -r "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" ] &&
57
- ROBISIE_KEY="$(cat "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key")" &&
58
- export ROBISIE_KEY &&
71
+ {
72
+ if [ ! -L "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" ] &&
73
+ [ -f "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" ] &&
74
+ [ -r "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" ] &&
75
+ ROBISIE_KEY="$(cat "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" 2>/dev/null)" &&
76
+ [ -n "$ROBISIE_KEY" ]; then
77
+ export ROBISIE_KEY
78
+ else
79
+ printf '%s\n' 'Cannot load a nonempty regular readable robisie key file.' 'Next step: check the key file and its permissions locally; resolve links/directories without overwriting data. If the key is missing or revoked, use Connect and init with the hidden prompt. Never paste the key into chat.' >&2
80
+ false
81
+ fi
82
+ } &&
59
83
  npx robisie doctor
60
84
  }
61
85
  ```
62
86
 
63
87
  The `&&` chain stops the block at the first error; assigning the key separately before `export` preserves the read status so doctor cannot mask it. After resolving the cause, retry the failed step and every subsequent step from the block in the same directory. If the manifest was already created, do not repeat its creation or delete it.
64
88
 
65
- In an existing project, keep the manifest and follow the update instructions.
89
+ For an existing project without `package.json`, run the fresh-install block above in that project directory: it creates only a private manifest and preserves other project files. If a regular manifest already exists, or you are reinstalling with a retained valid key, use the block below in the chosen project directory. It loads the saved key before npm/init/doctor, does not overwrite a regular manifest during preparation, and creates one with `wx` only if absent. npm itself may then add the robisie dependency and change the lockfile. It refuses a manifest link (including a dangling link) or directory with an explanation. After uninstall preserve the retained `package.json`. When no valid key remains, return to Connect and the hidden init prompt: for an existing regular manifest run the fresh-install block from `set +x` through doctor, without its `cd`/manifest creation step. Do not delete a manifest to repeat installation.
90
+
91
+ <!-- reinstall:start -->
92
+ ```sh
93
+ set +x
94
+ {
95
+ if [ ! -L "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" ] &&
96
+ [ -f "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" ] &&
97
+ [ -r "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" ] &&
98
+ ROBISIE_KEY="$(cat "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" 2>/dev/null)" &&
99
+ [ -n "$ROBISIE_KEY" ]; then
100
+ export ROBISIE_KEY
101
+ else
102
+ printf '%s\n' 'Cannot load a nonempty regular readable robisie key file.' 'Next step: check the key file and its permissions locally; resolve links/directories without overwriting data. If the key is missing or revoked, use Connect and init with the hidden prompt. Never paste the key into chat.' >&2
103
+ false
104
+ fi
105
+ } &&
106
+ node -e 'try {
107
+ const fs = require("node:fs");
108
+ let existing;
109
+ try { existing = fs.lstatSync("package.json"); }
110
+ catch (error) { if (error.code !== "ENOENT") throw error; }
111
+ if (existing) {
112
+ if (!existing.isFile()) throw new Error("package.json: expected a regular file; links and directories refused");
113
+ } else fs.writeFileSync("package.json", "{\"private\":true}\n", { flag: "wx" });
114
+ } catch (error) {
115
+ console.error(error.message);
116
+ console.error("Next step: check package.json locally; preserve the file and resolve its path before retrying.");
117
+ process.exit(1);
118
+ }' &&
119
+ npm i robisie &&
120
+ npx robisie init &&
121
+ npx robisie doctor
122
+ ```
123
+ <!-- reinstall:end -->
66
124
 
67
125
  For Codex or OpenCode replace `claude` with `codex` or `opencode`. With existing configuration, use the complete map in the next section; `--agent` alone does not clear it. Expected doctor result: exit 0. Prepare a compatible fallback tgz using Update below. Init configures `client-launch-context` and `ceo-client-launcher` for the package version; a local invocation is `npx robisie mcp <name>` from the installation cwd. Agent entries retain the transport generated by the package; this guide does not change it. npx may download the package when the required version is not available locally.
68
126
 
@@ -90,9 +148,19 @@ npx robisie init --agent opencode --role ceo=opencode --role builder=opencode --
90
148
  Profile support is limited to zsh/bash without `--no-shell`. With another shell or `--no-shell`, the human sets the agent session's environment securely. A POSIX shell can load the stored file without displaying its contents:
91
149
 
92
150
  ```sh
93
- [ -r "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" ] &&
94
- ROBISIE_KEY="$(cat "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key")" &&
95
- export ROBISIE_KEY
151
+ set +x
152
+ {
153
+ if [ ! -L "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" ] &&
154
+ [ -f "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" ] &&
155
+ [ -r "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" ] &&
156
+ ROBISIE_KEY="$(cat "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" 2>/dev/null)" &&
157
+ [ -n "$ROBISIE_KEY" ]; then
158
+ export ROBISIE_KEY
159
+ else
160
+ printf '%s\n' 'Cannot load a nonempty regular readable robisie key file.' 'Next step: check the key file and its permissions locally; resolve links/directories without overwriting data. If the key is missing or revoked, use Connect and init with the hidden prompt. Never paste the key into chat.' >&2
161
+ false
162
+ fi
163
+ }
96
164
  ```
97
165
 
98
166
  A new terminal alone does not guarantee the key: retain the installation's XDG_CONFIG_HOME and check doctor in the target session. With only `opencode.jsonc`, init refuses before writing. A remote MCP entry in jsonc does not install roles or helpers. Preserve the configuration; the human prepares a supported `opencode.json` without comments according to OpenCode settings, or selects another installed provider for all roles. The package does not convert JSONC.
@@ -130,9 +198,9 @@ Doctor runs the helper file via node, the agent via npx. `ROBISIE_PROJECT_CONTEX
130
198
  <!-- sekcja: pierwsza-karta -->
131
199
  ## First card and Builder startup
132
200
 
133
- The human starts the CEO in the installation directory: `claude --agent ceo-client`, or `codex` and requests the robisie CEO role (reading the full file referenced by AGENTS.md), or `opencode` and selects `ceo-client`. After successful discovery use this request, which works after npm installation with just README:
201
+ The human starts the CEO in the installation directory: `claude --agent ceo-client`, or `codex` and requests the robisie CEO role (reading the full file referenced by AGENTS.md), or `opencode` and selects `ceo-client`. After a successful project lookup use this request, which works after npm installation with just README:
134
202
 
135
- > Create wynik.txt in this directory with exactly “robisie działa” followed by a newline. Read it back and verify the exact contents. Boundaries: this file only, no dependencies, accounts or publication. Prepare the scope and wait for my approval; after the work I need independent review and my acceptance.
203
+ > Create wynik.txt in this directory with exactly “robisie działa” followed by a newline. Read it back and verify the exact contents. Boundaries: this file only, no dependencies, accounts or publication. Use my existing authorization if it covers this exact scope; otherwise ask before work. After the work I need independent review and separate final acceptance.
136
204
 
137
205
  After human approval, the CEO by default calls `spawn_builder` with the ID of the card confirmed in `ready`. The full flow in Claude Code is: `draft` → `ready` → `in_progress` → `in_review` → independent review and verified receipt → `delivered` → owner acceptance → `done`; see [Review and explicit acceptance](#recenzja-i-odbior) for acceptance limits in other sessions.
138
206
 
@@ -158,13 +226,25 @@ In Claude Code, the CEO starts an independent Quality Officer through `Agent(qua
158
226
 
159
227
  OpenCode: the card stays in `in_review` regardless of the availability of the Agent tool; there is no supported transition to `delivered`. Full acceptance requires the Claude Code route described above. A task/VERIFIED result, role label or receipt JSON alone does not open this transition; do not bypass a refusal with a manual status change or self-review.
160
228
 
161
- In other CEO sessions, including Codex, moving to delivered requires independent review and a verified receipt. If the CEO session lacks the Agent tool, the card stays in `in_review`: this is a product capability gap for CEO/CR to resolve. Do not substitute Builder self-review or a manual status change. Installing three roles does not provide that integration.
229
+ In other CEO sessions, including Codex, moving to delivered requires independent review and a verified receipt. If the CEO session lacks the Agent tool, the card stays in `in_review`: this is a product capability gap for the person responsible for the CEO integration to resolve. Do not substitute Builder self-review or a manual status change. Installing three roles does not provide that integration.
162
230
 
163
231
  The project owner can use Dashboard → Planer → card → Etap → “Zrobione” to move `delivered` to `done`, including when the agent uses a `worker` key. For the first card described here, the server does not enforce stored acceptance or evidence before a change to `done`: the dashboard lets the owner select “Zrobione” even without them. Do this only after checking and explicitly accepting the result. The dashboard cannot edit `details`; review and evidence are recorded through the supported board tool flow. This guide alone does not prove a customer has completed that flow.
164
232
 
165
233
  <!-- sekcja: aktualizacja -->
166
234
  ## Update and private backup
167
235
 
236
+ ### Update before the first init
237
+
238
+ In the prepared installation directory, before the first init, updating the npm package needs neither a key nor the installer's `manifest.json`. Preserve an existing project manifest; for an empty directory first create the local `package.json` using only the Node step above. Then run this one line; continue with the chosen init recipe when the account and key are ready.
239
+
240
+ <!-- before-init-update:start -->
241
+ ```sh
242
+ npm i robisie@latest
243
+ ```
244
+ <!-- before-init-update:end -->
245
+
246
+ ### Update after init
247
+
168
248
  Work in the installation directory. First prepare the backup below. Explicitly choose the previous release compatible with the server contract MAJOR; inspect the installed version with `node -p 'require("./node_modules/robisie/package.json").version'`. Replace the example `previous_version='0.1.1'` with that chosen version. `npm pack robisie@<wersja>` means pack the explicitly selected release, not an arbitrary tgz. Retain its filename and the backup directory. Disable xtrace; never print or paste secrets.
169
249
 
170
250
  ```sh
@@ -184,32 +264,66 @@ Keep the installation's HOME, XDG_CONFIG_HOME and CODEX_HOME values (the command
184
264
 
185
265
  Missing/null/empty/malformed project configuration or installation record cannot guarantee restore. Preserve available data, run local `npx robisie doctor` and follow its advice; new init cannot reconstruct a missing record. Resolve record or key-read errors before network errors. Never replace a damaged record with an empty one.
186
266
 
187
- The table contains separate commands for manual selection, not a block to run wholesale. Copy project and robisie files and only the providers used in the record, never all of `~/.claude/`, CODEX_HOME or the OpenCode directory. Before each command check the type and readability of source, destination and their ancestors. For `backups/` and `roles/codex/`, inspect every child as well. An unreadable file/entry or a symlink (including dangling links and linked ancestors) stops the recipe: preserve state and compare paths, never blindly cp through a link. A directory where a file is expected also needs investigation. If a file is absent, record its full path in `$backup/absent.txt`, e.g. `printf '%s\n' "$PWD/robisie.config.json" >> "$backup/absent.txt"`; skip cp in both directions. Do not delete files created later during restore.
188
-
189
- Set `profile` to the profile actually changed in manifest.entries: zsh `${ZDOTDIR:-$HOME}/.zshrc`; bash on macOS the first readable `$HOME/.bash_profile`, `$HOME/.bash_login`, `$HOME/.profile` (fallback `.bash_profile`); bash elsewhere `$HOME/.bashrc`. With `--no-shell`/another shell do not invent a profile; still preserve a prior profile entry if recorded. For each additional `path` and `backup` in entries, set `entry_path` to the exact absolute path, choose a unique numeric `entry_id`, and record that pair privately. Repeat the last row for every such file. Do not assume defaults cover prior installations or providers. Create only needed missing destination directories after the same path checks.
190
-
191
- | Source → private copy (before update) | Copy → restore destination (only after comparison) |
192
- |---|---|
193
- | `cp -p -- "$PWD/package.json" "$backup/project/package.json"` | `cp -p -- "$backup/project/package.json" "$PWD/package.json"` |
194
- | `cp -p -- "$PWD/package-lock.json" "$backup/project/package-lock.json"` | `cp -p -- "$backup/project/package-lock.json" "$PWD/package-lock.json"` |
195
- | `cp -p -- "$PWD/robisie.config.json" "$backup/project/robisie.config.json"` | `cp -p -- "$backup/project/robisie.config.json" "$PWD/robisie.config.json"` |
196
- | `cp -p -- "$config_home/robisie/key" "$backup/robisie/key"` | `cp -p -- "$backup/robisie/key" "$config_home/robisie/key"` |
197
- | `cp -p -- "$config_home/robisie/manifest.json" "$backup/robisie/manifest.json"` | `cp -p -- "$backup/robisie/manifest.json" "$config_home/robisie/manifest.json"` |
198
- | `cp -Rp -- "$config_home/robisie/backups/." "$backup/robisie/backups/"` | `cp -Rp -- "$backup/robisie/backups/." "$config_home/robisie/backups/"` |
199
- | `cp -Rp -- "$config_home/robisie/roles/codex/." "$backup/robisie/roles/codex/"` | `cp -Rp -- "$backup/robisie/roles/codex/." "$config_home/robisie/roles/codex/"` |
200
- | `cp -p -- "$HOME/.claude.json" "$backup/claude/claude.json"` | `cp -p -- "$backup/claude/claude.json" "$HOME/.claude.json"` |
201
- | `cp -p -- "$HOME/.claude/agents/ceo-client.md" "$backup/claude/agents/ceo-client.md"` | `cp -p -- "$backup/claude/agents/ceo-client.md" "$HOME/.claude/agents/ceo-client.md"` |
202
- | `cp -p -- "$HOME/.claude/agents/manager-builder-client.md" "$backup/claude/agents/manager-builder-client.md"` | `cp -p -- "$backup/claude/agents/manager-builder-client.md" "$HOME/.claude/agents/manager-builder-client.md"` |
203
- | `cp -p -- "$HOME/.claude/agents/quality-officer-client.md" "$backup/claude/agents/quality-officer-client.md"` | `cp -p -- "$backup/claude/agents/quality-officer-client.md" "$HOME/.claude/agents/quality-officer-client.md"` |
204
- | `cp -p -- "$codex_home/config.toml" "$backup/codex/config.toml"` | `cp -p -- "$backup/codex/config.toml" "$codex_home/config.toml"` |
205
- | `cp -p -- "$codex_home/AGENTS.md" "$backup/codex/AGENTS.md"` | `cp -p -- "$backup/codex/AGENTS.md" "$codex_home/AGENTS.md"` |
206
- | `cp -p -- "$config_home/opencode/opencode.json" "$backup/opencode/opencode.json"` | `cp -p -- "$backup/opencode/opencode.json" "$config_home/opencode/opencode.json"` |
207
- | `cp -p -- "$config_home/opencode/agents/ceo-client.md" "$backup/opencode/agents/ceo-client.md"` | `cp -p -- "$backup/opencode/agents/ceo-client.md" "$config_home/opencode/agents/ceo-client.md"` |
208
- | `cp -p -- "$config_home/opencode/agents/manager-builder-client.md" "$backup/opencode/agents/manager-builder-client.md"` | `cp -p -- "$backup/opencode/agents/manager-builder-client.md" "$config_home/opencode/agents/manager-builder-client.md"` |
209
- | `cp -p -- "$config_home/opencode/agents/quality-officer-client.md" "$backup/opencode/agents/quality-officer-client.md"` | `cp -p -- "$backup/opencode/agents/quality-officer-client.md" "$config_home/opencode/agents/quality-officer-client.md"` |
210
- | `cp -p -- "$config_home/opencode/plugins/robisie-review-guard.js" "$backup/opencode/plugins/robisie-review-guard.js"` | `cp -p -- "$backup/opencode/plugins/robisie-review-guard.js" "$config_home/opencode/plugins/robisie-review-guard.js"` |
211
- | `cp -p -- "$profile" "$backup/profile/selected"` | `cp -p -- "$backup/profile/selected" "$profile"` |
212
- | `cp -p -- "$entry_path" "$backup/entries/$entry_id"` | `cp -p -- "$backup/entries/$entry_id" "$entry_path"` |
267
+ Follow four steps; the command pairs below are a reference for selecting files, not twenty mandatory copies:
268
+
269
+ 1. Preserve project manifests (`package.json` and `package-lock.json`), project configuration and robisie’s installation record/key. Record absent files in `absent.txt`.
270
+ 2. From `manifest.entries`, select only installed providers, the recorded profile, roles and prior backups. Apply all path, type and readability checks below.
271
+ 3. Make and check only those copies; retain their paths and the selected release tgz privately.
272
+ 4. Update only after the copies are complete. To restore, compare later changes and restore BOTH project manifests before the tgz command, then load the key → install tgz → init → doctor.
273
+
274
+ The blocks below contain separate commands for manual selection, not a block to run wholesale. Copy project and robisie files and only the providers used in the record, never all of `~/.claude/`, CODEX_HOME or the OpenCode directory. Before each command check the type and readability of source, destination and their ancestors. For `backups/` and `roles/codex/`, inspect every child as well. An unreadable file/entry or a symlink (including dangling links and linked ancestors) stops the recipe: preserve state and compare paths, never blindly cp through a link. A directory where a file is expected also needs investigation. If a file is absent, record its full path in `$backup/absent.txt`, e.g. `printf '%s\n' "$PWD/robisie.config.json" >> "$backup/absent.txt"`; skip cp in both directions. Do not delete files created later during restore.
275
+
276
+ Set `profile` to the profile actually changed in manifest.entries: zsh `${ZDOTDIR:-$HOME}/.zshrc`; bash on macOS the first readable `$HOME/.bash_profile`, `$HOME/.bash_login`, `$HOME/.profile` (fallback `.bash_profile`); bash elsewhere `$HOME/.bashrc`. With `--no-shell`/another shell do not invent a profile; still preserve a prior profile entry if recorded. For each additional `path` and `backup` in entries, set `entry_path` to the exact absolute path, choose a unique numeric `entry_id`, and record that pair privately. Repeat the entry_path pair for every such file. Do not assume defaults cover prior installations or providers. Create only needed missing destination directories after the same path checks.
277
+
278
+ Copy: select only the required commands, checking each result.
279
+
280
+ ```sh
281
+ cp -p -- "$PWD/package.json" "$backup/project/package.json"
282
+ cp -p -- "$PWD/package-lock.json" "$backup/project/package-lock.json"
283
+ cp -p -- "$PWD/robisie.config.json" "$backup/project/robisie.config.json"
284
+ cp -p -- "$config_home/robisie/key" "$backup/robisie/key"
285
+ cp -p -- "$config_home/robisie/manifest.json" "$backup/robisie/manifest.json"
286
+ cp -Rp -- "$config_home/robisie/backups/." "$backup/robisie/backups/"
287
+ cp -Rp -- "$config_home/robisie/roles/codex/." "$backup/robisie/roles/codex/"
288
+ cp -p -- "$HOME/.claude.json" "$backup/claude/claude.json"
289
+ cp -p -- "$HOME/.claude/agents/ceo-client.md" "$backup/claude/agents/ceo-client.md"
290
+ cp -p -- "$HOME/.claude/agents/manager-builder-client.md" "$backup/claude/agents/manager-builder-client.md"
291
+ cp -p -- "$HOME/.claude/agents/quality-officer-client.md" "$backup/claude/agents/quality-officer-client.md"
292
+ cp -p -- "$codex_home/config.toml" "$backup/codex/config.toml"
293
+ cp -p -- "$codex_home/AGENTS.md" "$backup/codex/AGENTS.md"
294
+ cp -p -- "$config_home/opencode/opencode.json" "$backup/opencode/opencode.json"
295
+ cp -p -- "$config_home/opencode/agents/ceo-client.md" "$backup/opencode/agents/ceo-client.md"
296
+ cp -p -- "$config_home/opencode/agents/manager-builder-client.md" "$backup/opencode/agents/manager-builder-client.md"
297
+ cp -p -- "$config_home/opencode/agents/quality-officer-client.md" "$backup/opencode/agents/quality-officer-client.md"
298
+ cp -p -- "$config_home/opencode/plugins/robisie-review-guard.js" "$backup/opencode/plugins/robisie-review-guard.js"
299
+ cp -p -- "$profile" "$backup/profile/selected"
300
+ cp -p -- "$entry_path" "$backup/entries/$entry_id"
301
+ ```
302
+
303
+ Restore: the same source/copy pairs in the same order, only after comparison.
304
+
305
+ ```sh
306
+ cp -p -- "$backup/project/package.json" "$PWD/package.json"
307
+ cp -p -- "$backup/project/package-lock.json" "$PWD/package-lock.json"
308
+ cp -p -- "$backup/project/robisie.config.json" "$PWD/robisie.config.json"
309
+ cp -p -- "$backup/robisie/key" "$config_home/robisie/key"
310
+ cp -p -- "$backup/robisie/manifest.json" "$config_home/robisie/manifest.json"
311
+ cp -Rp -- "$backup/robisie/backups/." "$config_home/robisie/backups/"
312
+ cp -Rp -- "$backup/robisie/roles/codex/." "$config_home/robisie/roles/codex/"
313
+ cp -p -- "$backup/claude/claude.json" "$HOME/.claude.json"
314
+ cp -p -- "$backup/claude/agents/ceo-client.md" "$HOME/.claude/agents/ceo-client.md"
315
+ cp -p -- "$backup/claude/agents/manager-builder-client.md" "$HOME/.claude/agents/manager-builder-client.md"
316
+ cp -p -- "$backup/claude/agents/quality-officer-client.md" "$HOME/.claude/agents/quality-officer-client.md"
317
+ cp -p -- "$backup/codex/config.toml" "$codex_home/config.toml"
318
+ cp -p -- "$backup/codex/AGENTS.md" "$codex_home/AGENTS.md"
319
+ cp -p -- "$backup/opencode/opencode.json" "$config_home/opencode/opencode.json"
320
+ cp -p -- "$backup/opencode/agents/ceo-client.md" "$config_home/opencode/agents/ceo-client.md"
321
+ cp -p -- "$backup/opencode/agents/manager-builder-client.md" "$config_home/opencode/agents/manager-builder-client.md"
322
+ cp -p -- "$backup/opencode/agents/quality-officer-client.md" "$config_home/opencode/agents/quality-officer-client.md"
323
+ cp -p -- "$backup/opencode/plugins/robisie-review-guard.js" "$config_home/opencode/plugins/robisie-review-guard.js"
324
+ cp -p -- "$backup/profile/selected" "$profile"
325
+ cp -p -- "$backup/entries/$entry_id" "$entry_path"
326
+ ```
213
327
 
214
328
  Once the tgz and selected copies are ready, update. Init does not read the key file automatically: ROBISIE_KEY takes priority, then the hidden terminal prompt, then explicit `--key-stdin` (for example automation without a terminal). A key file alone is insufficient. Load the old key BEFORE init/doctor using the same XDG_CONFIG_HOME; separate assignment before export and `&&` retain read failures without printing the key:
215
329
 
@@ -218,11 +332,18 @@ Once the tgz and selected copies are ready, update. Init does not read the key f
218
332
  set +x
219
333
  XDG_CONFIG_HOME="$config_home" &&
220
334
  export XDG_CONFIG_HOME &&
221
- [ ! -L "$XDG_CONFIG_HOME/robisie/key" ] &&
222
- [ -f "$XDG_CONFIG_HOME/robisie/key" ] &&
223
- [ -r "$XDG_CONFIG_HOME/robisie/key" ] &&
224
- ROBISIE_KEY="$(cat "$XDG_CONFIG_HOME/robisie/key")" &&
225
- export ROBISIE_KEY &&
335
+ {
336
+ if [ ! -L "$XDG_CONFIG_HOME/robisie/key" ] &&
337
+ [ -f "$XDG_CONFIG_HOME/robisie/key" ] &&
338
+ [ -r "$XDG_CONFIG_HOME/robisie/key" ] &&
339
+ ROBISIE_KEY="$(cat "$XDG_CONFIG_HOME/robisie/key" 2>/dev/null)" &&
340
+ [ -n "$ROBISIE_KEY" ]; then
341
+ export ROBISIE_KEY
342
+ else
343
+ printf '%s\n' 'Cannot load a nonempty regular readable robisie key file.' 'Next step: check the key file and its permissions locally; resolve links/directories without overwriting data. If the key is missing or revoked, use Connect and init with the hidden prompt. Never paste the key into chat.' >&2
344
+ false
345
+ fi
346
+ } &&
226
347
  npm i robisie@latest &&
227
348
  npx robisie init &&
228
349
  npx robisie doctor
@@ -233,21 +354,28 @@ Doctor checks the contract MAJOR; exit 0 also requires its other checks. Choose
233
354
 
234
355
  ### Return to the previous release
235
356
 
236
- Before overwriting, preserve later user edits in a NEW private copy (`umask 077`, e.g. `later="$(mktemp -d "$HOME/robisie-later.XXXXXX")"`). Repeat directory preparation and the left column, substituting `$later` for `$backup`, without altering the original backup. Compare locally and merge user edits with the previous release's copy; configuration can contain a key, so do not publish the diff. Stop overwriting for unreadable configuration, links or an unresolved comparison. There is no promise of automatic rollback.
357
+ Before overwriting, preserve later user edits in a NEW private copy (`umask 077`, e.g. `later="$(mktemp -d "$HOME/robisie-later.XXXXXX")"`). Repeat directory preparation and the copy block, substituting `$later` for `$backup`, without altering the original backup. Compare locally and merge user edits with the previous release's copy; configuration can contain a key, so do not publish the diff. Stop overwriting for unreadable configuration, links or an unresolved comparison. There is no promise of automatic rollback.
237
358
 
238
- After comparison run the selected right-column commands to the same destinations, honoring absent.txt. Directory rows copy contents through `/.` without nesting another directory; before restore prepare checked destination directories if missing. When merging `backups/` and `roles/codex/`, do not delete additional later files. Then in the same cwd install the retained compatible tgz, load the restored old key into ENV, and only then run init and doctor:
359
+ After comparison run the selected restore-block commands to the same destinations, honoring absent.txt. Directory commands copy contents through `/.` without nesting another directory; before restore prepare checked destination directories if missing. When merging `backups/` and `roles/codex/`, do not delete additional later files. Restore `package.json` AND `package-lock.json` first. Then in the same cwd load the restored old key into ENV, install the retained compatible tgz, and only then run init and doctor:
239
360
 
240
361
  <!-- restore:start -->
241
362
  ```sh
242
363
  set +x
243
- npm i --no-save "$backup/robisie-$previous_version.tgz" &&
244
364
  XDG_CONFIG_HOME="$config_home" &&
245
365
  export XDG_CONFIG_HOME &&
246
- [ ! -L "$XDG_CONFIG_HOME/robisie/key" ] &&
247
- [ -f "$XDG_CONFIG_HOME/robisie/key" ] &&
248
- [ -r "$XDG_CONFIG_HOME/robisie/key" ] &&
249
- ROBISIE_KEY="$(cat "$XDG_CONFIG_HOME/robisie/key")" &&
250
- export ROBISIE_KEY &&
366
+ {
367
+ if [ ! -L "$XDG_CONFIG_HOME/robisie/key" ] &&
368
+ [ -f "$XDG_CONFIG_HOME/robisie/key" ] &&
369
+ [ -r "$XDG_CONFIG_HOME/robisie/key" ] &&
370
+ ROBISIE_KEY="$(cat "$XDG_CONFIG_HOME/robisie/key" 2>/dev/null)" &&
371
+ [ -n "$ROBISIE_KEY" ]; then
372
+ export ROBISIE_KEY
373
+ else
374
+ printf '%s\n' 'Cannot load a nonempty regular readable robisie key file.' 'Next step: check the key file and its permissions locally; resolve links/directories without overwriting data. If the key is missing or revoked, use Connect and init with the hidden prompt. Never paste the key into chat.' >&2
375
+ false
376
+ fi
377
+ } &&
378
+ npm i --no-save "$backup/robisie-$previous_version.tgz" &&
251
379
  npx robisie init &&
252
380
  npx robisie doctor
253
381
  ```
@@ -255,7 +383,7 @@ npx robisie doctor
255
383
 
256
384
  The `--no-save` option preserves the restored `package.json` and `package-lock.json` without recording a `file:` dependency on the private backup path.
257
385
 
258
- Check the status of every separate table command; any error stops the recipe. The chain stops automatically. Never mask reads or combine key assignment with export. On failure preserve both copies and follow doctor before further overwrites.
386
+ Check the status of every separately selected command; any error stops the recipe. The chain stops automatically. Never mask reads or combine key assignment with export. On failure preserve both copies and follow doctor before further overwrites.
259
387
 
260
388
  <!-- sekcja: odinstalowanie -->
261
389
  ## Uninstall
@@ -267,6 +395,8 @@ npm uninstall robisie
267
395
 
268
396
  The first command removes robisie entries and blocks from files recorded in the installation manifest and undoes role installation. It does not restore old robisie entries. User-edited roles remain with a warning; backups remain and may contain an old key. Without an installation record the command changes nothing and **does not delete the key file**. A refusal during the Codex configuration check occurs **before key deletion**; after that check the key file is removed even if a later undo fails. A nonzero exit requires preserving your edits and resolving the reported problem before retrying. Open a new terminal. Uninstall does not revoke the key on the server: revoke it separately in Connect. The second command removes the package from the project and may change `package.json`, `package-lock.json` and `node_modules`; the npm cache may remain. Do not mass-delete those files or the cache. A later npx call may download the package again.
269
397
 
398
+ Retained backups, including private update copies, may still contain the key after uninstall. Keep them private according to your retention needs; uninstall does not erase or revoke those copies. This guide does not delete them automatically.
399
+
270
400
  <!-- sekcja: diagnoza -->
271
401
  ## Diagnosis
272
402
 
@@ -274,17 +404,24 @@ Without an installation, begin with the account and Connect → init; repeating
274
404
 
275
405
  CLI messages remain in Polish. Match the message, then follow the English explanation:
276
406
 
277
- | ID | CLI message | Next step |
278
- |---|---|---|
279
- | brak-klucza | `Brak klucza robisie.` | No key: generate one in Connect and supply it to init. |
280
- | odrzucony-klucz | `Serwer robisie odrzucił klucz (nieważny albo unieważniony).` | Generate a new worker key; in zsh/bash run `unset ROBISIE_KEY`, then init with the hidden prompt. |
281
- | brak-odczytu | `Ten klucz nie ma uprawnień do odczytu tablicy (np. rola seeder).` | Select worker in Connect; `unset ROBISIE_KEY`, then init with the hidden prompt. |
282
- | major | `Wersja kontraktu serwera (2.0.0) nie pasuje do paczki robisie 0.1.2 (obsługuje 1.x).` | Example of a MAJOR mismatch: install a release compatible with the server contract. |
283
- | brak-env | `Zmienna ROBISIE_KEY nie jest ustawiona — role i agenci jej potrzebują.` | Check profile support; with --no-shell/another shell load the key file into the session environment as shown in init, then doctor. |
284
- | brak-programu | `katalog jest, programu nie ma w PATH` | Install the named provider program or add it to PATH; a configuration directory alone is insufficient. |
285
- | brak-programu-i-katalogu | `brak programu w PATH i katalogu dostawcy` | Install the selected program, repeat init with the complete shared map and doctor. |
286
- | jsonc | `nie zmieniam automatycznie` | Preserve JSONC; prepare supported JSON or choose another provider for all roles. Remote MCP alone is insufficient. |
287
- | niepelna-instalacja | `Claude Code: niepełna instalacja` | Example of missing configuration: repeat init for your agent. |
407
+ - **brak-klucza** — `Brak klucza robisie.`
408
+ No key: generate one in Connect and supply it to init.
409
+ - **odrzucony-klucz** — `Serwer robisie odrzucił klucz (nieważny albo unieważniony).`
410
+ Generate a new worker key; in zsh/bash run `unset ROBISIE_KEY`, then init with the hidden prompt.
411
+ - **brak-odczytu** — `Ten klucz nie ma uprawnień do odczytu tablicy (np. rola seeder).`
412
+ Select worker in Connect; `unset ROBISIE_KEY`, then init with the hidden prompt.
413
+ - **major** — `Wersja kontraktu serwera (2.0.0) nie pasuje do paczki robisie 0.1.4 (obsługuje 1.x).`
414
+ Example of a MAJOR mismatch: install a release compatible with the server contract.
415
+ - **brak-env** — `Zmienna ROBISIE_KEY nie jest ustawiona — role i agenci jej potrzebują.`
416
+ Check profile support; with --no-shell/another shell load the key file into the session environment as shown in init, then doctor.
417
+ - **brak-programu** — `katalog jest, programu nie ma w PATH`
418
+ Install the named provider program or add it to PATH; a configuration directory alone is insufficient.
419
+ - **brak-programu-i-katalogu** — `brak programu w PATH i katalogu dostawcy`
420
+ Install the selected program, repeat init with the complete shared map and doctor.
421
+ - **jsonc** — `nie zmieniam automatycznie`
422
+ Preserve JSONC; prepare supported JSON or choose another provider for all roles. Remote MCP alone is insufficient.
423
+ - **niepelna-instalacja** — `Claude Code: niepełna instalacja`
424
+ Example of missing configuration: repeat init for your agent.
288
425
 
289
426
  After repair with an existing record, load the saved key as shown in Update before local `npx robisie init` and `npx robisie doctor`; reinstall missing package files from npm, and obtain a compatible release for MAJOR. For a missing record preserve data and follow doctor instead of blindly running init. If the problem remains, send the team the message, version and cwd without the key. Uninstall success means removed entries and exit 0; exit 1 needs the indicated repair and does not mean complete removal.
290
427