robisie 0.1.0 → 0.1.2
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/CHANGELOG.md +79 -0
- package/README.md +109 -14
- package/dist/active-recovery.d.ts +58 -0
- package/dist/active-recovery.js +143 -0
- package/dist/agents.d.ts +34 -0
- package/dist/agents.js +77 -16
- package/dist/attempt-identity.d.ts +21 -0
- package/dist/attempt-identity.js +39 -0
- package/dist/ci-failure-result.d.ts +23 -0
- package/dist/ci-failure-result.js +90 -0
- package/dist/claude-headless.d.ts +7 -0
- package/dist/claude-headless.js +28 -0
- package/dist/cli.d.ts +17 -0
- package/dist/cli.js +54 -14
- package/dist/commands.d.ts +18 -0
- package/dist/commands.js +195 -88
- package/dist/constants.d.ts +32 -0
- package/dist/constants.js +3 -3
- package/dist/context.d.ts +24 -0
- package/dist/context.js +22 -6
- package/dist/dependency-readiness.d.ts +13 -0
- package/dist/dependency-readiness.js +80 -0
- package/dist/dispatch-scope.d.ts +18 -0
- package/dist/dispatch-scope.js +46 -0
- package/dist/done-evidence.d.ts +31 -0
- package/dist/done-evidence.js +216 -0
- package/dist/engine-config.d.ts +65 -0
- package/dist/engine-config.js +139 -0
- package/dist/fsops.d.ts +87 -0
- package/dist/fsops.js +117 -24
- package/dist/helpers.d.ts +15 -0
- package/dist/helpers.js +268 -45
- package/dist/intent-rules/admission.d.ts +10 -0
- package/dist/intent-rules/admission.js +35 -0
- package/dist/intent-rules/done-when-roles.d.ts +21 -0
- package/dist/intent-rules/done-when-roles.js +101 -0
- package/dist/intent-rules/hooks.d.ts +29 -0
- package/dist/intent-rules/hooks.js +23 -0
- package/dist/k3-codex-role.d.ts +20 -0
- package/dist/k3-codex-role.js +68 -0
- package/dist/manifest.d.ts +41 -0
- package/dist/manifest.js +59 -14
- package/dist/mcp.d.ts +18 -0
- package/dist/mcp.js +117 -40
- package/dist/opencode-result.d.ts +19 -0
- package/dist/opencode-result.js +136 -0
- package/dist/opencode-review-guard.d.ts +1 -0
- package/dist/opencode-review-guard.js +19 -0
- package/dist/opencode-session-export.d.ts +5 -0
- package/dist/opencode-session-export.js +28 -0
- package/dist/outcome-moves.d.ts +15 -0
- package/dist/outcome-moves.js +39 -0
- package/dist/planer-client.d.ts +214 -0
- package/dist/planer-client.js +351 -0
- package/dist/restart-recovery.d.ts +47 -0
- package/dist/restart-recovery.js +70 -0
- package/dist/review-source-packet.d.ts +17 -0
- package/dist/review-source-packet.js +44 -0
- package/dist/role-registry.d.ts +25 -0
- package/dist/role-registry.js +91 -0
- package/dist/role-results.d.ts +15 -0
- package/dist/role-results.js +42 -0
- package/dist/roles.d.ts +30 -0
- package/dist/roles.js +20 -16
- package/dist/seed-validation.d.ts +28 -0
- package/dist/seed-validation.js +294 -0
- package/dist/selection-result.d.ts +44 -0
- package/dist/selection-result.js +144 -0
- package/dist/sparse-policy.d.ts +8 -0
- package/dist/sparse-policy.js +49 -0
- package/dist/tester-identity.d.ts +11 -0
- package/dist/tester-identity.js +53 -0
- package/dist/worker-env.d.ts +5 -0
- package/dist/worker-env.js +34 -0
- package/docs/ENGINE-API.md +88 -0
- package/docs/ENGINE-CONFIG.md +113 -0
- package/docs/README.en.md +142 -20
- package/docs/README.md +144 -20
- package/docs/RELEASE-0.1.0.md +81 -8
- package/docs/RELEASE-0.1.1.md +110 -0
- package/helpers/ceo-client-launcher-mcp.mjs +36 -8
- package/helpers/client-spawn-session.sh +181 -0
- package/helpers/client-spawn.sh +825 -0
- package/package.json +9 -4
- package/roles/ceo-client.md +3 -2
- package/roles/manager-builder-client.md +18 -4
- package/roles/quality-officer-client.md +20 -6
|
@@ -0,0 +1,88 @@
|
|
|
1
|
+
# API silnika z paczki robisie
|
|
2
|
+
|
|
3
|
+
Po instalacji `npm i robisie` używaj publicznego importu `robisie/dist/planer-client.js` w module ESM. Nie potrzebujesz checkoutu aplikacji ani aliasów repozytorium. Poniższe bloki można zapisać jako osobne pliki `.mjs`; eksportują funkcje, a sam import nie wykonuje odczytów ani zapisów.
|
|
4
|
+
|
|
5
|
+
Caller przekazuje `config`: **dokładnie jedno z `origin` XOR `endpoint`**, np. `origin: 'https://robisie.app'` albo `endpoint: 'https://robisie.app/api/mcp'`, oraz własny `token`. Opcjonalne `fetch` pozwala wstrzyknąć transport (w teście wyłącznie fixture); bez niego SDK używa natywnego fetch. Opcjonalne `deadlineMs` ogranicza czas żądania. SDK nie pobiera tokena z pliku ani środowiska. Nie generuj, nie osadzaj i nie loguj tokena; przekaż go z bezpiecznego źródła callera poza rozmową i historią poleceń.
|
|
6
|
+
|
|
7
|
+
W obu przykładach wynik operacji i diagnostyka zamknięcia są oddzielne: błąd `close` nie zastępuje wyniku ani pierwotnego błędu operacji. Emituje tylko stałe ostrzeżenie, bez wyjątku, konfiguracji i patcha; awaria samej konsoli również nie zmienia wyniku. Błąd zamknięcia nie uzasadnia ponowienia append — zapis mógł już zostać wykonany.
|
|
8
|
+
|
|
9
|
+
## Odczyt i jednoznaczny wybór
|
|
10
|
+
|
|
11
|
+
Wywołaj `readCard(config, selection)`. `selection` może zawierać `projectId`, `trackId` i `id` rozpoznane przez callera. Brak identyfikatora pozwala kontynuować tylko wtedy, gdy discovery zwraca dokładnie jedną pozycję na danym poziomie. Przy pustej liście, braku wskazanego ID albo wielu kandydatach wynik `wybierz-jednoznacznie` wskazuje etap; caller ustala wybór przed kolejnym odczytem. Nie wybieraj przypadkowej pierwszej pozycji. Ten odczyt niczego nie zapisuje ani nie tworzy brakujących obiektów.
|
|
12
|
+
|
|
13
|
+
`detailsKeys` w `listTasks` oraz `include` w `getTask` są jawnymi listami kluczy, np. `detailsKeys: ['seed_brief']` i `include: ['seed_brief', 'scope']`. Puste `[]` oznacza brak `details` w wyniku. Wybrane `details` mogą być `null`; brak wybranego klucza nie oznacza błędu. SDK sam wysyła `full: true` w `list_tasks`. Przykład jawnie przekazuje wszystkie statusy, łącznie z `done`, które serwer domyślnie wyklucza z listy; dzięki temu można odczytać także zakończoną kartę po ID. `getTask` zwracające `null` oznacza brak karty. Wadliwa odpowiedź powoduje istniejący `PlanerClientError` SDK (np. `INVALID_RESPONSE`), bez normalizowania legacy ani dopisywania stanu HOLD. Funkcja przekazuje błąd callerowi i zamyka klienta w `finally`, także przy błędzie connect.
|
|
14
|
+
|
|
15
|
+
<!-- engine-api:read:start -->
|
|
16
|
+
```js
|
|
17
|
+
import { PlanerClient } from 'robisie/dist/planer-client.js';
|
|
18
|
+
|
|
19
|
+
export async function readCard(config, {
|
|
20
|
+
projectId, trackId, id, detailsKeys = [], include = [],
|
|
21
|
+
} = {}) {
|
|
22
|
+
const client = new PlanerClient(config);
|
|
23
|
+
try {
|
|
24
|
+
await client.connect();
|
|
25
|
+
const projects = (await client.listProjects())
|
|
26
|
+
.filter(project => projectId === undefined || project.id === projectId);
|
|
27
|
+
if (projects.length !== 1) return { outcome: 'wybierz-jednoznacznie', stage: 'list_projects' };
|
|
28
|
+
const project = projects[0];
|
|
29
|
+
const tracks = (await client.listTracks({ projectId: project.id }))
|
|
30
|
+
.filter(track => trackId === undefined || track.id === trackId);
|
|
31
|
+
if (tracks.length !== 1) return { outcome: 'wybierz-jednoznacznie', stage: 'list_tracks' };
|
|
32
|
+
const track = tracks[0];
|
|
33
|
+
const tasks = (await client.listTasks({
|
|
34
|
+
projectId: project.id, trackId: track.id, detailsKeys,
|
|
35
|
+
statuses: ['draft', 'ready', 'in_progress', 'in_review', 'blocked', 'delivered', 'done'],
|
|
36
|
+
}))
|
|
37
|
+
.filter(task => id === undefined || task.id === id);
|
|
38
|
+
if (tasks.length !== 1) return { outcome: 'wybierz-jednoznacznie', stage: 'list_tasks' };
|
|
39
|
+
const task = await client.getTask({ id: tasks[0].id, include });
|
|
40
|
+
return { outcome: task === null ? 'brak-karty' : 'odczytano', task };
|
|
41
|
+
} finally {
|
|
42
|
+
try { await client.close(); }
|
|
43
|
+
catch {
|
|
44
|
+
try { console.warn('Nie udało się zamknąć klienta.'); }
|
|
45
|
+
catch { /* awaria diagnostyki nie zmienia wyniku */ }
|
|
46
|
+
}
|
|
47
|
+
}
|
|
48
|
+
}
|
|
49
|
+
```
|
|
50
|
+
<!-- engine-api:read:end -->
|
|
51
|
+
|
|
52
|
+
## Jeden append, osobny wynik odczytu
|
|
53
|
+
|
|
54
|
+
Caller przekazuje rozpoznane `id` i `patch` do `appendCard(config, { id, patch })` dopiero po uzyskaniu zgody na ten zapis. `appendDetail` wykonuje jeden zapis i osobny readback tylko kluczy patcha. `write` jest potwierdzeniem zapisu, a `readback` wynikiem późniejszego odczytu. Gdy `readback.ok === false`, zachowaj `write`; nie powtarzaj append, aby naprawić odczyt. Caller może później wykonać wyłącznie dodatkowy `getTask({ id, include: Object.keys(patch) })`, przez połączonego klienta z `close` w `finally`.
|
|
55
|
+
|
|
56
|
+
`PlanerClientError.uncertain === true` oznacza, że zapis mógł dojść do serwera mimo utraty odpowiedzi lub błędu narzędzia. Wynik `wynik-niepewny` kończy automatyczne pisanie. Caller odczytuje stan i podejmuje decyzję; funkcja nie ponawia append ani żadnej innej mutacji. Pozostałe błędy są przekazywane callerowi. Nie loguj konfiguracji ani argumentów z tokenem.
|
|
57
|
+
|
|
58
|
+
<!-- engine-api:append:start -->
|
|
59
|
+
```js
|
|
60
|
+
import { PlanerClient, PlanerClientError } from 'robisie/dist/planer-client.js';
|
|
61
|
+
|
|
62
|
+
export async function appendCard(config, { id, patch }) {
|
|
63
|
+
const client = new PlanerClient(config);
|
|
64
|
+
try {
|
|
65
|
+
await client.connect();
|
|
66
|
+
const result = await client.appendDetail({ id, patch });
|
|
67
|
+
return { outcome: 'zapis-potwierdzony', ...result };
|
|
68
|
+
} catch (error) {
|
|
69
|
+
if (error instanceof PlanerClientError && error.uncertain) {
|
|
70
|
+
return { outcome: 'wynik-niepewny', error };
|
|
71
|
+
}
|
|
72
|
+
throw error;
|
|
73
|
+
} finally {
|
|
74
|
+
try { await client.close(); }
|
|
75
|
+
catch {
|
|
76
|
+
try { console.warn('Nie udało się zamknąć klienta.'); }
|
|
77
|
+
catch { /* awaria diagnostyki nie zmienia wyniku */ }
|
|
78
|
+
}
|
|
79
|
+
}
|
|
80
|
+
}
|
|
81
|
+
```
|
|
82
|
+
<!-- engine-api:append:end -->
|
|
83
|
+
|
|
84
|
+
Serwer stosuje **płytki merge**: patch zastępuje całą wartość pod wskazanym kluczem, bez deep merge. `null` jest wartością literalną, a brak klucza w patchu nie kasuje dotychczasowej wartości. Przykładowo patch `{ notes: { nowa: 2 }, literal: null }` zastąpi całe poprzednie `notes`, zapisze literalne `null` i pozostawi inne klucze.
|
|
85
|
+
|
|
86
|
+
Osobna operacja `updateTask({ id, status: 'ready', expected: { status: 'draft' } })` przekazuje warunek oczekiwanego statusu. Warunek, przejście statusu i uprawnienia rozstrzyga serwer; SDK nie implementuje własnego CAS. Powyższe przykłady nie wykonują update.
|
|
87
|
+
|
|
88
|
+
SDK nie tworzy projektu ani karty, nie nadaje uprawnień, nie dowodzi odbioru `done` i nie uruchamia silnika. Potwierdzenie append nie jest dowodem wykonania zadania ani niezależnej recenzji. Role, odbiór i uruchomienie pracy wymagają ich własnych kontraktów.
|
|
@@ -0,0 +1,113 @@
|
|
|
1
|
+
# Konfiguracja silnika z paczki
|
|
2
|
+
|
|
3
|
+
Ten przykład korzysta z modułu `robisie/dist/engine-config.js` z lokalnie
|
|
4
|
+
zainstalowanej paczki `robisie`. Wymaga Node.js 20 lub nowszego. Odczytuje
|
|
5
|
+
i waliduje plik; nie wykonuje komend z konfiguracji ani połączeń sieciowych.
|
|
6
|
+
Nie uruchamia silnika w tle i nie zapewnia samodzielnej realizacji zadań.
|
|
7
|
+
|
|
8
|
+
Opis operacji na tablicy znajdziesz w [API silnika](ENGINE-API.md),
|
|
9
|
+
a konfigurację agenta i instalatora w [przewodniku klienta](README.md).
|
|
10
|
+
|
|
11
|
+
## Zapisz konfigurację
|
|
12
|
+
|
|
13
|
+
Zapisz poniższy blok jako `robisie.config.json`, np. w `config/setup/`.
|
|
14
|
+
UUID projektu i toru są **fikcyjne** — nie wskazują rzeczywistych danych.
|
|
15
|
+
Przed użyciem własnej konfiguracji podmień:
|
|
16
|
+
|
|
17
|
+
- `project` na UUID swojego projektu; `tracks` na UUID i nazwy jego torów;
|
|
18
|
+
- `engine.repo` na ścieżkę swojego repozytorium i `engine.branch` na jego gałąź;
|
|
19
|
+
- `stateDir` na katalog stanu swojej instancji;
|
|
20
|
+
- `engine.commands.test`, `lint`, `build` na własne programy i argumenty;
|
|
21
|
+
- `engine.requiredChecks` na nazwy wymaganych kontroli CI;
|
|
22
|
+
- `roles` na własne nazwy i dokładne formy ról, `coordinator.id` na swój
|
|
23
|
+
identyfikator koordynatora, a `owner.genitive` na dopełniacz imienia właściciela.
|
|
24
|
+
|
|
25
|
+
`stateDir` i `engine.repo` są liczone względem **katalogu pliku konfiguracji**,
|
|
26
|
+
nie katalogu, z którego uruchamiasz Node. Dla `config/setup/robisie.config.json`
|
|
27
|
+
wartość `../repo with spaces` wskazuje `config/repo with spaces`.
|
|
28
|
+
|
|
29
|
+
Każda komenda to niepuste **argv**: program, następnie osobne argumenty.
|
|
30
|
+
Spacje w argumencie i metaznaki są danymi. Przykładowe `a b` i `$(never-run)`
|
|
31
|
+
mają pozostać dosłowne; nie sklejaj argv w polecenie powłoki. Poniższy odczyt
|
|
32
|
+
nie wykonuje nawet testu, lintowania ani budowania. Komendy są ilustracyjne
|
|
33
|
+
i wymagają podmiany przed wykorzystaniem konfiguracji do wykonywania pracy.
|
|
34
|
+
Nie wpisuj sekretów do argv — argumenty mogą trafić do listy procesów lub logów
|
|
35
|
+
narzędzi wykonujących komendy.
|
|
36
|
+
`delivery: "pr"` opisuje sposób dostarczenia; sam odczyt nie tworzy PR.
|
|
37
|
+
|
|
38
|
+
Role silnika to `coordinator`, `owner`, `planner`, `advisor`.
|
|
39
|
+
`forms` zawierają dosłowne formy z uwzględnieniem wielkości liter, a
|
|
40
|
+
`owner.genitive` służy m.in. do zapisu „Efekt dla Ali”. To osobne ustawienia
|
|
41
|
+
od `roleProviders` instalatora dla ról `ceo`, `builder`, `quality`.
|
|
42
|
+
|
|
43
|
+
<!-- engine-config:json:start -->
|
|
44
|
+
```json
|
|
45
|
+
{
|
|
46
|
+
"project": "11111111-1111-4111-8111-111111111111",
|
|
47
|
+
"tracks": [
|
|
48
|
+
{ "id": "22222222-2222-4222-8222-222222222222", "name": "Mój tor" }
|
|
49
|
+
],
|
|
50
|
+
"stateDir": "../state with spaces",
|
|
51
|
+
"roles": {
|
|
52
|
+
"coordinator": { "id": "przystan", "name": "Przystań", "forms": ["Przystań", "Przystani"] },
|
|
53
|
+
"owner": { "name": "Ala", "forms": ["Ala", "Ali"], "genitive": "Ali" },
|
|
54
|
+
"planner": { "name": "Mapa", "forms": ["Mapa", "Mapy"] },
|
|
55
|
+
"advisor": { "name": "Latarnia", "forms": ["Latarnia", "Latarni"] }
|
|
56
|
+
},
|
|
57
|
+
"engine": {
|
|
58
|
+
"repo": "../repo with spaces",
|
|
59
|
+
"branch": "main",
|
|
60
|
+
"commands": {
|
|
61
|
+
"test": ["node", "a b", "$(never-run)"],
|
|
62
|
+
"lint": ["npm", "run", "lint"],
|
|
63
|
+
"build": ["npm", "run", "build:check"]
|
|
64
|
+
},
|
|
65
|
+
"requiredChecks": ["Test", "Lint", "Build"],
|
|
66
|
+
"delivery": "pr"
|
|
67
|
+
}
|
|
68
|
+
}
|
|
69
|
+
```
|
|
70
|
+
<!-- engine-config:json:end -->
|
|
71
|
+
|
|
72
|
+
## Odczytaj plik
|
|
73
|
+
|
|
74
|
+
W katalogu, w którym dostępna jest paczka `robisie` w `node_modules`, zapisz
|
|
75
|
+
poniższy kod jako `read-engine-config.mjs`.
|
|
76
|
+
|
|
77
|
+
<!-- engine-config:esm:start -->
|
|
78
|
+
```js
|
|
79
|
+
import { loadEngineConfig } from 'robisie/dist/engine-config.js';
|
|
80
|
+
|
|
81
|
+
try {
|
|
82
|
+
const configPath = process.argv[2];
|
|
83
|
+
if (!configPath) throw new Error('Podaj ścieżkę do robisie.config.json');
|
|
84
|
+
const config = loadEngineConfig(configPath);
|
|
85
|
+
console.log(`Konfiguracja poprawna. Tory: ${config.tracks.length}; komendy: ${Object.keys(config.engine.commands).length}; kontrole: ${config.engine.requiredChecks.length}.`);
|
|
86
|
+
} catch (error) {
|
|
87
|
+
console.error(error instanceof Error ? error.message : String(error));
|
|
88
|
+
process.exitCode = 1;
|
|
89
|
+
}
|
|
90
|
+
```
|
|
91
|
+
<!-- engine-config:esm:end -->
|
|
92
|
+
|
|
93
|
+
Uruchom lokalnie, podając absolutną ścieżkę do zapisanego JSON:
|
|
94
|
+
|
|
95
|
+
```sh
|
|
96
|
+
node read-engine-config.mjs /absolutna/sciezka/robisie.config.json
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
Katalog skryptu może być inny niż katalog konfiguracji. Sukces oznacza exit 0,
|
|
100
|
+
pusty stderr i jedną linię na stdout: stałe etykiety oraz liczby torów, komend
|
|
101
|
+
i wymaganych kontroli. Wartości pól i nazwy kluczy konfiguracji nie są wypisywane.
|
|
102
|
+
Dla powyższego JSON wynik to:
|
|
103
|
+
|
|
104
|
+
```text
|
|
105
|
+
Konfiguracja poprawna. Tory: 1; komendy: 3; kontrole: 3.
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
Ścieżka pliku jest kanonizowana we wczytanym obiekcie `config`, więc przy
|
|
109
|
+
dowiązaniach wskazuje jego rzeczywistą lokalizację. Brak pliku, niepoprawny JSON lub błędne pola kończą
|
|
110
|
+
odczyt z niezerowym exit i komunikatem na stderr. Na przykład brak `test`
|
|
111
|
+
w `engine.commands` daje błąd zawierający `engine.commands.test`, a
|
|
112
|
+
`delivery: "invalid"` — `engine.delivery`. Odczyt nie dopisuje brakujących
|
|
113
|
+
komend ani nie zastępuje błędnego sposobu dostarczenia wartością domyślną.
|
package/docs/README.en.md
CHANGED
|
@@ -1,19 +1,21 @@
|
|
|
1
|
-
# robisie — from account to accepted card (package 0.1.
|
|
1
|
+
# robisie — from account to accepted card (package 0.1.2)
|
|
2
2
|
|
|
3
3
|
Polski: [README.md](README.md).
|
|
4
4
|
|
|
5
5
|
<!-- sekcja: dostepnosc -->
|
|
6
6
|
## Availability
|
|
7
7
|
|
|
8
|
-
|
|
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.
|
|
9
|
+
|
|
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).
|
|
9
11
|
|
|
10
12
|
<!-- sekcja: wymagania -->
|
|
11
13
|
<a id="wymagania"></a>
|
|
12
14
|
## Requirements
|
|
13
15
|
|
|
14
|
-
The human prepares Node.js 20+, npm, internet for dependencies and robisie, and one provider program: Claude Code, Codex CLI or OpenCode with their own AI access. Check `node --version`, `npm --version` and the chosen program's version (`claude --version`, `codex --version` or `opencode --version`). If absent from PATH, install it following its provider's instructions and check again; a configuration directory alone is insufficient.
|
|
16
|
+
The human prepares Node.js 20+, npm, internet for dependencies and robisie, and one provider program: Claude Code, Codex CLI or OpenCode with their own AI access. Check `node --version`, `npm --version` and the chosen program's version (`claude --version`, `codex --version` or `opencode --version`). If absent from PATH, install it following its provider's instructions and check again; a configuration directory alone is insufficient. Windows/WSL are unverified; examples below use POSIX paths.
|
|
15
17
|
|
|
16
|
-
Prepare an empty directory on disk
|
|
18
|
+
Prepare an empty directory on disk. You do not need a website or your own `package.json`; the Node.js step below creates it before installation. This is the agents' working directory, separate from the dashboard project.
|
|
17
19
|
|
|
18
20
|
<!-- sekcja: konto -->
|
|
19
21
|
<a id="konto"></a>
|
|
@@ -35,16 +37,34 @@ The package stores **one key for CEO, Builder and Quality Officer** as `ROBISIE_
|
|
|
35
37
|
|
|
36
38
|
<!-- sekcja: instalacja -->
|
|
37
39
|
<a id="instalacja"></a>
|
|
38
|
-
## Install
|
|
40
|
+
## Install from npm
|
|
39
41
|
|
|
40
|
-
|
|
42
|
+
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:
|
|
41
43
|
|
|
42
44
|
```sh
|
|
43
|
-
|
|
44
|
-
|
|
45
|
+
cd "/path/to/empty directory" &&
|
|
46
|
+
node -e 'try {
|
|
47
|
+
require("node:fs").writeFileSync("package.json", "{\"private\":true}\n", { flag: "wx" });
|
|
48
|
+
} catch (error) {
|
|
49
|
+
console.error(error.message);
|
|
50
|
+
process.exit(1);
|
|
51
|
+
}' &&
|
|
52
|
+
{
|
|
53
|
+
npm i robisie &&
|
|
54
|
+
unset ROBISIE_KEY &&
|
|
55
|
+
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 &&
|
|
59
|
+
npx robisie doctor
|
|
60
|
+
}
|
|
45
61
|
```
|
|
46
62
|
|
|
47
|
-
|
|
63
|
+
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
|
+
|
|
65
|
+
In an existing project, keep the manifest and follow the update instructions.
|
|
66
|
+
|
|
67
|
+
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.
|
|
48
68
|
|
|
49
69
|
<!-- sekcja: init -->
|
|
50
70
|
## Connect your agent
|
|
@@ -70,7 +90,9 @@ npx robisie init --agent opencode --role ceo=opencode --role builder=opencode --
|
|
|
70
90
|
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:
|
|
71
91
|
|
|
72
92
|
```sh
|
|
73
|
-
[ -r "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" ] &&
|
|
93
|
+
[ -r "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key" ] &&
|
|
94
|
+
ROBISIE_KEY="$(cat "${XDG_CONFIG_HOME:-$HOME/.config}/robisie/key")" &&
|
|
95
|
+
export ROBISIE_KEY
|
|
74
96
|
```
|
|
75
97
|
|
|
76
98
|
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.
|
|
@@ -108,11 +130,15 @@ Doctor runs the helper file via node, the agent via npx. `ROBISIE_PROJECT_CONTEX
|
|
|
108
130
|
<!-- sekcja: pierwsza-karta -->
|
|
109
131
|
## First card and Builder startup
|
|
110
132
|
|
|
111
|
-
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 with just README
|
|
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:
|
|
112
134
|
|
|
113
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.
|
|
114
136
|
|
|
115
|
-
|
|
137
|
+
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
|
+
|
|
139
|
+
If `spawn_builder` fails, the CEO reports the error and resolves the cause before retrying; it does not automatically switch to manual startup.
|
|
140
|
+
|
|
141
|
+
Manual startup is available only as the operator's explicit choice: the CEO then provides a command to run in a new terminal in the installation directory.
|
|
116
142
|
|
|
117
143
|
The ID comes from the created or freshly read card, not the project or session. Below is a fictitious lowercase canonical UUID; replace it with the exact card ID. The Codex example assumes XDG_CONFIG_HOME=/home/tester/Robisie config: replace the entire path with the actual installed path (default $HOME/.config/robisie/roles/codex/manager-builder-client.md). A tilde inside the quoted prompt will not expand. Choose one command:
|
|
118
144
|
|
|
@@ -128,16 +154,108 @@ Expected startup result: a fresh CEO read confirms the assigned card in_progress
|
|
|
128
154
|
<a id="recenzja-i-odbior"></a>
|
|
129
155
|
## Review and explicit acceptance
|
|
130
156
|
|
|
131
|
-
|
|
157
|
+
In Claude Code, the CEO starts an independent Quality Officer through `Agent(quality-officer-client)` after a fresh in_review read. The Quality Officer independently checks the result and records review and evidence on the card; the Builder does not review its own work. The CEO verifies the review confirmation (verified receipt) and performs the fresh card reads required by the protocol before moving to `delivered`; then explicit acceptance by the operator permits moving to `done`. Checking evidence and explicitly accepting the result is the operator's responsibility. After verified review and delivery, check the acceptance criteria; if evidence needed for your acceptance or your approval is missing, leave the card in `delivered`.
|
|
158
|
+
|
|
159
|
+
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.
|
|
132
160
|
|
|
133
|
-
|
|
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.
|
|
134
162
|
|
|
135
163
|
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.
|
|
136
164
|
|
|
137
165
|
<!-- sekcja: aktualizacja -->
|
|
138
|
-
## Update
|
|
166
|
+
## Update and private backup
|
|
167
|
+
|
|
168
|
+
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
|
+
|
|
170
|
+
```sh
|
|
171
|
+
set +x
|
|
172
|
+
umask 077 &&
|
|
173
|
+
config_home="${XDG_CONFIG_HOME:-$HOME/.config}" &&
|
|
174
|
+
codex_home="${CODEX_HOME:-$HOME/.codex}" &&
|
|
175
|
+
backup="$(mktemp -d "$HOME/robisie-backup.XXXXXX")" &&
|
|
176
|
+
mkdir -p "$backup/project" "$backup/robisie/backups" "$backup/robisie/roles/codex" \
|
|
177
|
+
"$backup/claude/agents" "$backup/codex" "$backup/opencode/agents" \
|
|
178
|
+
"$backup/opencode/plugins" "$backup/profile" "$backup/entries" &&
|
|
179
|
+
previous_version='0.1.1' &&
|
|
180
|
+
npm pack "robisie@$previous_version" --pack-destination "$backup"
|
|
181
|
+
```
|
|
182
|
+
|
|
183
|
+
Keep the installation's HOME, XDG_CONFIG_HOME and CODEX_HOME values (the commands use HOME defaults when ENV is absent). Keep them for restore too. Inspect the local `$config_home/robisie/manifest.json`: `manifest.entries` records actual `path` and prior `backup` paths. Do not paste configuration containing a key into chat. A readable legacy manifest without roleProviders still has useful entries; its age alone does not require a new installation. `roleProviders: null` means unassigned — follow doctor without guessing the map.
|
|
184
|
+
|
|
185
|
+
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
|
+
|
|
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"` |
|
|
213
|
+
|
|
214
|
+
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
|
+
|
|
216
|
+
<!-- update:start -->
|
|
217
|
+
```sh
|
|
218
|
+
set +x
|
|
219
|
+
XDG_CONFIG_HOME="$config_home" &&
|
|
220
|
+
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 &&
|
|
226
|
+
npm i robisie@latest &&
|
|
227
|
+
npx robisie init &&
|
|
228
|
+
npx robisie doctor
|
|
229
|
+
```
|
|
230
|
+
<!-- update:end -->
|
|
231
|
+
|
|
232
|
+
Doctor checks the contract MAJOR; exit 0 also requires its other checks. Choose a compatible release for a mismatch; reinstall damaged package files. Do not repeat the same incompatible installation.
|
|
233
|
+
|
|
234
|
+
### Return to the previous release
|
|
139
235
|
|
|
140
|
-
|
|
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.
|
|
237
|
+
|
|
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:
|
|
239
|
+
|
|
240
|
+
<!-- restore:start -->
|
|
241
|
+
```sh
|
|
242
|
+
set +x
|
|
243
|
+
npm i --no-save "$backup/robisie-$previous_version.tgz" &&
|
|
244
|
+
XDG_CONFIG_HOME="$config_home" &&
|
|
245
|
+
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 &&
|
|
251
|
+
npx robisie init &&
|
|
252
|
+
npx robisie doctor
|
|
253
|
+
```
|
|
254
|
+
<!-- restore:end -->
|
|
255
|
+
|
|
256
|
+
The `--no-save` option preserves the restored `package.json` and `package-lock.json` without recording a `file:` dependency on the private backup path.
|
|
257
|
+
|
|
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.
|
|
141
259
|
|
|
142
260
|
<!-- sekcja: odinstalowanie -->
|
|
143
261
|
## Uninstall
|
|
@@ -147,11 +265,13 @@ npx robisie uninstall
|
|
|
147
265
|
npm uninstall robisie
|
|
148
266
|
```
|
|
149
267
|
|
|
150
|
-
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.
|
|
268
|
+
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.
|
|
151
269
|
|
|
152
270
|
<!-- sekcja: diagnoza -->
|
|
153
271
|
## Diagnosis
|
|
154
272
|
|
|
273
|
+
Without an installation, begin with the account and Connect → init; repeating doctor does not create an account. With an existing installation, doctor reads the record and key first (ENV takes priority over the file), then checks the network. Resolve record/key-read problems first while preserving data; a network failure on an existing installation does not call for a new account. Check connectivity and server access.
|
|
274
|
+
|
|
155
275
|
CLI messages remain in Polish. Match the message, then follow the English explanation:
|
|
156
276
|
|
|
157
277
|
| ID | CLI message | Next step |
|
|
@@ -159,16 +279,18 @@ CLI messages remain in Polish. Match the message, then follow the English explan
|
|
|
159
279
|
| brak-klucza | `Brak klucza robisie.` | No key: generate one in Connect and supply it to init. |
|
|
160
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. |
|
|
161
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. |
|
|
162
|
-
| major | `Wersja kontraktu serwera (2.0.0) nie pasuje do paczki robisie 0.1.
|
|
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. |
|
|
163
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. |
|
|
164
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. |
|
|
165
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. |
|
|
166
286
|
| jsonc | `nie zmieniam automatycznie` | Preserve JSONC; prepare supported JSON or choose another provider for all roles. Remote MCP alone is insufficient. |
|
|
167
287
|
| niepelna-instalacja | `Claude Code: niepełna instalacja` | Example of missing configuration: repeat init for your agent. |
|
|
168
288
|
|
|
169
|
-
After repair,
|
|
289
|
+
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.
|
|
170
290
|
|
|
171
291
|
<!-- sekcja: ograniczenia -->
|
|
172
292
|
## Limitations
|
|
173
293
|
|
|
174
|
-
The
|
|
294
|
+
The installer does not start background services or the Builder on its own; after operator approval, the CEO can start the Builder through `spawn_builder`. Helpers run during agent sessions using the project directory (or `ROBISIE_PROJECT_CONTEXT`) as context. The installer contacts robisie to check the contract and key; the package file does not provide an account or AI provider access. One shared key identity does not provide three different permission levels. Acceptance requires independent review, evidence and the operator's approval.
|
|
295
|
+
|
|
296
|
+
Windows/WSL are unverified. Offline validation checks configuration structure, not project UUID, repo existence, model availability or provider execution.
|