robisie 0.6.8 → 0.6.10
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 +16 -0
- package/dist/constants.d.ts +1 -1
- package/dist/constants.js +1 -1
- package/dist/engine/build-id.json +1 -1
- package/dist/engine/bundle-report.json +5 -5
- package/dist/engine/tick.cjs +7 -2
- package/dist/roles.d.ts +1 -1
- package/docs/README.en.md +18 -10
- package/docs/README.md +15 -7
- package/package.json +1 -1
- package/roles/ceo-client.md +6 -4
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,21 @@
|
|
|
1
1
|
# Historia zmian klienta / Client changelog
|
|
2
2
|
|
|
3
|
+
## [0.6.10](https://github.com/chuppa12/robisie-app/compare/client-v0.6.9...client-v0.6.10) (2026-11-19)
|
|
4
|
+
|
|
5
|
+
|
|
6
|
+
### Factory Cards
|
|
7
|
+
|
|
8
|
+
* praca workera worker-12da7cf3-b468-4b64-b724-4b096c3fd54b (auto-commit) ([e4c1b2f](https://github.com/chuppa12/robisie-app/commit/e4c1b2f0e87cf9c5007efea7fafd3fc71e1662f3))
|
|
9
|
+
* praca workera worker-38bfadec-a483-4c55-b1c2-b0ea51468cbc (auto-commit) ([047b5f5](https://github.com/chuppa12/robisie-app/commit/047b5f5cf24039cf382e486f8cd8f4fc896bbe9e))
|
|
10
|
+
* praca workera worker-b0ec56b4-387b-4079-af1a-d75713866cdb (auto-commit) ([24ef3f9](https://github.com/chuppa12/robisie-app/commit/24ef3f9de1db4e075addf9cc6a41cbf7559bee25))
|
|
11
|
+
|
|
12
|
+
## [0.6.9](https://github.com/chuppa12/robisie-app/compare/client-v0.6.8...client-v0.6.9) (2026-11-19)
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
### Bug Fixes
|
|
16
|
+
|
|
17
|
+
* **maszynista:** linia compound_learning w raporcie Workera przyjmuje wcięcie, znacznik listy i kropkę ([b1a5beb](https://github.com/chuppa12/robisie-app/commit/b1a5beb626e10c5447679f2b3d6dc7f7529ec33d))
|
|
18
|
+
|
|
3
19
|
## [0.6.8](https://github.com/chuppa12/robisie-app/compare/client-v0.6.7...client-v0.6.8) (2026-11-19)
|
|
4
20
|
|
|
5
21
|
|
package/dist/constants.d.ts
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
/** Package identity and the server contract it speaks. */
|
|
2
2
|
export declare const PACKAGE_NAME = "robisie";
|
|
3
|
-
export declare const PACKAGE_VERSION = "0.6.
|
|
3
|
+
export declare const PACKAGE_VERSION = "0.6.10";
|
|
4
4
|
/**
|
|
5
5
|
* MAJOR of the agent-API contract this package understands.
|
|
6
6
|
* PARITY: src/lib/mcp/contract-version.ts (AGENT_API_CONTRACT_VERSION) on the server.
|
package/dist/constants.js
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
/** Package identity and the server contract it speaks. */
|
|
2
2
|
export const PACKAGE_NAME = "robisie";
|
|
3
|
-
export const PACKAGE_VERSION = "0.6.
|
|
3
|
+
export const PACKAGE_VERSION = "0.6.10"; // x-release-please-version
|
|
4
4
|
/**
|
|
5
5
|
* MAJOR of the agent-API contract this package understands.
|
|
6
6
|
* PARITY: src/lib/mcp/contract-version.ts (AGENT_API_CONTRACT_VERSION) on the server.
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"schema":1,"sha":"
|
|
1
|
+
{"schema":1,"sha":"0075ce4467d7cac22d6ef154d3922ee98b3174b2","dirty":false}
|
|
@@ -1692,14 +1692,14 @@
|
|
|
1692
1692
|
"staticOperations": {
|
|
1693
1693
|
"beforePreflight": {
|
|
1694
1694
|
"module": "maszynista/tick.ts",
|
|
1695
|
-
"startLine":
|
|
1696
|
-
"endLine":
|
|
1695
|
+
"startLine": 10276,
|
|
1696
|
+
"endLine": 10389,
|
|
1697
1697
|
"text": "export async function main(): Promise<number> {\n const start = standaloneStartCheck({ filename: __filename, env: process.env });\n if (start.standalone && !start.ok) {\n console.error(start.message);\n process.exitCode = 78;\n return 78;\n }\n let installation: EngineContext;\n try { installation = createEngineContext(currentEngine(), {\n loadEnvironment: loadEnvFiles, preflight, baseRef: engineBaseRef, refreshBase: fetchMain,\n disk: defaultDiskPressureDependencies, workerContext: loadNorthStar,\n controlEnv: hostEnv, workerEnv: executionEnv, prepareWorktree: prepareHostWorktree, workerArtifacts: createWorkerTmpdir,\n notify: async (card, reason) => { decisionForReksio(card, reason, \"Rozstrzygnij na karcie\", \"\", \"\"); return { outcome: \"recorded\", ref: DECISIONS_REKSIO }; },\n hostOperations: hostOperationsPhase,\n activation: { confirmLoaded, finishHostActivation, readActivationState, recoverTickTimeout, runEnabledAuto },\n }, git, log); }\n catch (error) {\n if (!engineClient()) throw error;\n console.error(`HOLD kontekst klienta: ${clientTickFailure(error)}`);\n process.exitCode = 78;\n return 78;\n }\n const previousInstallation = tickInstallation;\n const hostErrorText = errorText;\n const client = engineClient();\n const result: { outcome: \"ok\" | \"retry\" | \"stop\"; reason: string; cleanup: boolean } = { outcome: \"ok\", reason: \"\", cleanup: false };\n const stopClient = (reason = clientTickFailure()): void => {\n if (client && result.outcome !== \"stop\") { result.outcome = \"stop\"; result.reason = reason; }\n };\n let code = 2;\n try { code = await q.withPlannerQueries(installation.planner, async () => {\n tickInstallation = installation;\n const seedGateSettings = installationSeedGateSettings();\n const errorText = client ? clientTickFailure : hostErrorText;\n const loadEnvFiles = installation.loadEnvironment;\n const preflight = () => {\n const actor = installation.preflight();\n return { uid: actor.kind === \"db\" ? actor.uid : API_ACTOR };\n };\n const { confirmLoaded, finishHostActivation, readActivationState, recoverTickTimeout, runEnabledAuto } = installation.activation;\n const smokeOnly = DRY && process.env.MASZYNISTA_SMOKE === \"1\";\n if (!DRY) {\n const acquire = (): boolean => tryCreateTickLock(LOCK);\n if (!acquire()) {\n const raw = readFileSync(LOCK, \"utf8\"), pid = Number(raw);\n if (!Number.isSafeInteger(pid) || pid <= 0) { console.log(\"tick lock bez poprawnego PID — HOLD\"); return 0; }\n try { process.kill(pid, 0); console.log(`tick już trwa (pid ${pid})`); return 0; }\n catch (error) { if ((error as NodeJS.ErrnoException).code !== \"ESRCH\") throw error; }\n if (readFileSync(LOCK, \"utf8\") === raw) unlinkSync(LOCK);\n if (!acquire()) { console.log(\"tick już trwa\"); return 0; }\n }\n }\n skippedCardEvents.clear();\n let s = parseState(null).state;\n // Internal smoke handoff: the child cannot outlive the parent's reserved budget.\n const smokeLimit = DRY ? Number(process.env.MASZYNISTA_SMOKE_TIMEOUT_MS) : NaN;\n let stateLoaded = false;\n let tickStarted: string | undefined;\n let outcome: \"ok\" | \"failed\" = \"ok\";\n let runtimeFailed = false;\n let observedLoaded = \"UNKNOWN\";\n let tickPhase = \"startup\";\n const deadlineAlarm = armTickDeadline(() => s, Number.isSafeInteger(smokeLimit) && smokeLimit > 0\n ? Math.min(TICK_LIMIT_MS, smokeLimit) : TICK_LIMIT_MS, () => ({ phase: tickPhase, observedLoaded }));\n let hostReady = false;\n let hostBoard: { uid: string; projectId: string } | undefined;\n let activationCards: CardLike[] = [];\n let activationCardsKnown = false;\n let blockedBefore = 0;\n const clientStopped = (): boolean => {\n if (client && (outcome === \"failed\" || (!DRY && s.blocked > blockedBefore))) stopClient();\n if (client && result.outcome === \"stop\") outcome = \"failed\";\n return client && result.outcome === \"stop\";\n };\n let hostPhaseStarted = false;\n const hostPhase = async (): Promise<boolean> => {\n if (smokeOnly || !hostReady || hostPhaseStarted) return false;\n hostPhaseStarted = true;\n tickPhase = \"host\";\n if (hostBoard) {\n const { uid: boardUid, projectId: boardProject } = hostBoard;\n try {\n await runEnabledAuto({ state: s, loadedSha: observedLoaded, repo: REPO, logPath: LOG, tick: s.tick, stateDir: hostStateDir(),\n now: new Date().toISOString(), activation: readActivationState(hostStateDir()), dryRun: DRY }, {\n listCards: async () => scanTasks(boardUid, boardProject, { full: true, statuses: [\"delivered\"],\n detailsKeys: ENABLED_SCAN_DETAILS_KEYS }),\n getTask: id => q.getTask(boardUid, id),\n appendDetail: async (id, patch) => { await appendBoundedDetail(boardUid, id, patch); },\n saveState: writeState,\n alarm: hostActivationAlarm,\n log,\n });\n } catch (error) { runtimeFailed = true; outcome = \"failed\"; log(`FAIL ENABLED auto: ${errorText(error)}`); }\n } else log(\"ENABLED auto: UNKNOWN — brak odczytu projektu; dowód karty czeka na dostęp do tablicy\");\n try {\n const result = await engineRunHostActivation({ repo: REPO, stateDir: hostStateDir(), cards: activationCards, cardsKnown: activationCardsKnown, tick: s.tick, dryRun: DRY }, {\n git, remainingTickMs, alarm: hostActivationAlarm, infrastructureChecks, infrastructurePullRequest, log: line => log(`host-activation: ${line}`),\n });\n log(`host-activation: code=${result.code} target=${result.target ?? \"UNKNOWN\"}${result.detail ? ` reason=${result.detail}` : \"\"}`);\n if (result.code === \"activate\" && result.target) {\n lastTick(s, \"activation\", `aktywacja ${result.target}; ogon odroczony`, outcome === \"ok\");\n return true;\n }\n } catch (error) { runtimeFailed = true; outcome = \"failed\"; log(`FAIL aktywacja: ${errorText(error)}`); }\n return false;\n };\n try {\n observedLoaded = loadedSha = readLoadedSha(REPO);\n s = readState((await engineFjConfig()).enabled);\n stateLoaded = true; blockedBefore = s.blocked;\n s.tick++; tickStarted = new Date().toISOString(); s.lastTickAt = tickStarted;\n log(`tick_started tick=${s.tick} at=${tickStarted} duration=UNKNOWN loaded=${loadedSha}`);\n loadEnvFiles();\n const { uid } = preflight();"
|
|
1698
1698
|
},
|
|
1699
1699
|
"finalization": {
|
|
1700
1700
|
"module": "maszynista/tick.ts",
|
|
1701
|
-
"startLine":
|
|
1702
|
-
"endLine":
|
|
1701
|
+
"startLine": 10680,
|
|
1702
|
+
"endLine": 10732,
|
|
1703
1703
|
"text": " } finally {\n // A persisted terminal FAIL is a card result; every unexpected exception above\n // remains a runtime failure, including DB errors inside card handling.\n if (!DRY && s.blocked > blockedBefore) {\n outcome = \"failed\";\n try { log(`FAIL: licznik blocked wzrósł ${blockedBefore} → ${s.blocked}; outcome=failed`); }\n catch (error) { console.error(`zapis licznika blocked: ${errorText(error)}`); }\n }\n clientStopped();\n // Early board failure still reaches the same host phase, at most once per tick.\n await hostPhase();\n tickPhase = \"finalizing\";\n try { if (!DRY) await finishHostActivation({ stateDir: hostStateDir(), outcome, tick: s.tick, runtimeFailed, observedLoaded }, { alarm: hostActivationAlarm, log }); }\n catch (error) { runtimeFailed = true; outcome = \"failed\"; log(`FAIL breaker aktywacji: ${errorText(error)}`); }\n clientStopped();\n try { if (stateLoaded) writeState(s); }\n catch (error) { runtimeFailed = true; outcome = \"failed\"; if (!client) throw error; stopClient(); result.cleanup = true; }\n finally {\n if (!DRY) {\n try { if (readFileSync(LOCK, \"utf8\") === String(process.pid)) unlinkSync(LOCK); }\n catch (error) { if ((error as NodeJS.ErrnoException).code !== \"ENOENT\") { if (!client) throw error; stopClient(); result.cleanup = true; } }\n }\n const at = new Date().toISOString();\n const duration = tickStarted ? `${(Date.parse(at) - Date.parse(tickStarted)) / 1000}s` : \"UNKNOWN\";\n try {\n const { total, ops } = drainEgressCounters();\n const sorted = Object.entries(ops).sort(([, a], [, b]) => b.bytes - a.bytes);\n const summary = sorted.filter(([op]) => !op.includes(\":\")).slice(0, 12)\n .map(([op, counter]) => `${op}:${counter.calls}:${counter.bytes}`).join(\",\");\n const variants = sorted.filter(([op]) => op.includes(\":\")).slice(0, 6)\n .map(([op, counter]) => `${op}:${counter.calls}:${counter.bytes}`).join(\",\");\n log(`egress tick=${s.tick} total=${total} ops=${summary} variants=${variants}`);\n } catch { /* Optional metrics must never interrupt tick cleanup. */ }\n try { refreshTickReport(observedLoaded); log(`tick_finished tick=${s.tick} at=${at} outcome=${client && result.outcome === \"retry\" ? \"retry\" : outcome} duration=${duration} loaded=${loadedSha}`); }\n finally { clearTimeout(deadlineAlarm); tickDeadline = Number.POSITIVE_INFINITY; }\n }\n }\n }); } catch (error) {\n if (!client) throw error;\n stopClient(); result.cleanup = true;\n } finally {\n tickInstallation = previousInstallation;\n try { await installation.close(); }\n catch (error) {\n if (client) { stopClient(); result.cleanup = true; }\n else safeLog(`Zamknięcie instalacji nieudane: ${String(error)}`);\n }\n }\n if (client && result.outcome !== \"ok\") console.error(`Fabryka ${result.outcome === \"stop\" ? \"zatrzymana\" : \"retry\"}: ${result.reason}${result.cleanup ? \"; finalizacja niepotwierdzona — sprawdź stan i blokadę\" : \"\"}`);\n return client && result.outcome === \"stop\" ? 2 : code;\n}\n\nif (require.main === module && !([\"--opencode-runner\", \"--grok-runner\"].includes(process.argv[2] ?? \"\"))) {"
|
|
1704
1704
|
},
|
|
1705
1705
|
"refreshTickReport": {
|
|
@@ -1725,6 +1725,6 @@
|
|
|
1725
1725
|
"status": 0,
|
|
1726
1726
|
"signal": null,
|
|
1727
1727
|
"stdout": "v24.3.0\n",
|
|
1728
|
-
"stderr": "(node:
|
|
1728
|
+
"stderr": "(node:24368) ExperimentalWarning: SQLite is an experimental feature and might change at any time\n(Use `node --trace-warnings ...` to show where the warning was created)\n"
|
|
1729
1729
|
}
|
|
1730
1730
|
}
|
package/dist/engine/tick.cjs
CHANGED
|
@@ -37652,7 +37652,7 @@ var init_constants = __esm({
|
|
|
37652
37652
|
"packages/client/src/constants.ts"() {
|
|
37653
37653
|
"use strict";
|
|
37654
37654
|
PACKAGE_NAME = "robisie";
|
|
37655
|
-
PACKAGE_VERSION = "0.6.
|
|
37655
|
+
PACKAGE_VERSION = "0.6.10";
|
|
37656
37656
|
SUPPORTED_CONTRACT_MAJOR = 1;
|
|
37657
37657
|
DEFAULT_ORIGIN = "https://robisie.app";
|
|
37658
37658
|
MCP_SERVER_NAME = "robisie";
|
|
@@ -317293,6 +317293,7 @@ __export2(tick_exports, {
|
|
|
317293
317293
|
flushReviewGrantDiagnostics: () => flushReviewGrantDiagnostics,
|
|
317294
317294
|
handleCiNoChecksAlarm: () => handleCiNoChecksAlarm,
|
|
317295
317295
|
handleDiskPressure: () => handleDiskPressure,
|
|
317296
|
+
hasCompoundLearningLine: () => hasCompoundLearningLine,
|
|
317296
317297
|
hostActivationAlarm: () => hostActivationAlarm,
|
|
317297
317298
|
hostStateDir: () => hostStateDir,
|
|
317298
317299
|
infrastructureChecks: () => infrastructureChecks,
|
|
@@ -323055,6 +323056,9 @@ function workerIdentity(meta4, client = engineClient()) {
|
|
|
323055
323056
|
...typeof meta4.provider === "string" && meta4.provider.trim() ? { provider: meta4.provider } : !client && meta4.backend === "codex" ? { provider: "openai" } : {}
|
|
323056
323057
|
};
|
|
323057
323058
|
}
|
|
323059
|
+
function hasCompoundLearningLine(report) {
|
|
323060
|
+
return /^[ \t]*(?:[-*][ \t]*)?compound_learning:[ \t]*(?:zero|one|attempted_unavailable)\.?[ \t]*$/im.test(report);
|
|
323061
|
+
}
|
|
323058
323062
|
async function consumeActive(s, uid, a = s.actives[0], landing = { available: true }, bootAt, installation = tickInstallation) {
|
|
323059
323063
|
if (!a) return false;
|
|
323060
323064
|
const diagnostic = (phase, reason) => {
|
|
@@ -323476,7 +323480,7 @@ async function consumeActive(s, uid, a = s.actives[0], landing = { available: tr
|
|
|
323476
323480
|
if (openCodeJob && outcome.status === "UNKNOWN" && !atCapacity) {
|
|
323477
323481
|
return holdOpenCode("opencode-report-hold", `raport ${outcome.status}; bez retry i WORKER_FINISHED`);
|
|
323478
323482
|
}
|
|
323479
|
-
if (!atCapacity && openCodeResult?.status === "completed" &&
|
|
323483
|
+
if (!atCapacity && openCodeResult?.status === "completed" && !hasCompoundLearningLine(outcome.report)) {
|
|
323480
323484
|
return holdOpenCode("opencode-learning-hold", "brak compound_learning; uzupe\u0142nij przez tego samego Workera");
|
|
323481
323485
|
}
|
|
323482
323486
|
if (outcome.status === "WORKER_FINISHED" || outcome.status === "ALREADY_DONE") {
|
|
@@ -328915,6 +328919,7 @@ init_tick();
|
|
|
328915
328919
|
flushReviewGrantDiagnostics,
|
|
328916
328920
|
handleCiNoChecksAlarm,
|
|
328917
328921
|
handleDiskPressure,
|
|
328922
|
+
hasCompoundLearningLine,
|
|
328918
328923
|
hostActivationAlarm,
|
|
328919
328924
|
hostStateDir,
|
|
328920
328925
|
infrastructureChecks,
|
package/dist/roles.d.ts
CHANGED
|
@@ -17,7 +17,7 @@ export interface Role {
|
|
|
17
17
|
export declare function rolesDir(): string;
|
|
18
18
|
export declare function parseRole(file: Role["file"], text: string): Role;
|
|
19
19
|
export declare function loadRoles(dir?: string): Role[];
|
|
20
|
-
export declare const MANAGED_LINE = "<!-- robisie:managed 0.6.
|
|
20
|
+
export declare const MANAGED_LINE = "<!-- robisie:managed 0.6.10 \u2014 plik zarz\u0105dzany przez `npx robisie`; `npx robisie uninstall` go usunie -->";
|
|
21
21
|
export type AgentFlavor = "claude" | "codex" | "opencode";
|
|
22
22
|
/** How the operator starts the Builder for one card in its own session (the card id is not a secret). */
|
|
23
23
|
export declare function builderStartCommand(flavor: AgentFlavor, codexRolePath?: string): string;
|
package/docs/README.en.md
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# robisie — from account to accepted card (package 0.6.
|
|
1
|
+
# robisie — from account to accepted card (package 0.6.10) <!-- x-release-please-version -->
|
|
2
2
|
|
|
3
3
|
In the project directory with its engine configuration, run `npx robisie init`, then `npx robisie doctor`: init prepares the project goal and tester protection list, and doctor checks both inputs.
|
|
4
4
|
|
|
@@ -17,7 +17,9 @@ If the registry README is empty, use the guides shipped locally at `node_modules
|
|
|
17
17
|
<a id="wymagania"></a>
|
|
18
18
|
## Requirements
|
|
19
19
|
|
|
20
|
-
The human prepares Node.js 24+ (release used for checks: 24.3.0), npm, internet for dependencies and robisie, and
|
|
20
|
+
The human prepares Node.js 24+ (release used for checks: 24.3.0), npm, internet for dependencies and robisie, and the provider programs described below, each with its own AI access. An older Node, such as 22, is refused before `init`, `doctor` and `factory run`. The engine bundled in the package (`dist/engine/tick.cjs`) for the client requires Linux or macOS; an explicit Robisie host (`engine.mode: "host"`, delivery `pr|delivered`) also supports macOS. It is started by `npx robisie factory run`; the engine configuration is described in [ENGINE-CONFIG](ENGINE-CONFIG.md). 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.
|
|
21
|
+
|
|
22
|
+
The installer roles (`ceo`, `builder`, `quality`) use one provider for building: Claude Code, Codex CLI or OpenCode. Independent review and acceptance need a second logged-in provider; the default is Grok. These installer roles are separate from `roleRegistry` (`worker-client`, `lead-client`, `reviewer-client`, `tester-client` and optional `receiver-client`). There is no automatic conversion between them. A `receiver-client` row with `requireIndependentProvider:false` means `partial` and still a separate process: a shared provider, for example a Codex receiver with a Codex Worker, is not full independence.
|
|
21
23
|
|
|
22
24
|
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.
|
|
23
25
|
|
|
@@ -38,7 +40,7 @@ Project lookup is the authenticated read of active projects through `list_projec
|
|
|
38
40
|
<!-- agent-consent:start -->
|
|
39
41
|
### Agent instructions — one authorization for the flow
|
|
40
42
|
|
|
41
|
-
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). Before asking for authorization
|
|
43
|
+
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). Before asking for authorization for the CEO role, choose the local `greet.cjs` card with the owner; the boundaries must match the example. The manual `wynik.txt` example is unsupported by the `ceo-client` role.
|
|
42
44
|
|
|
43
45
|
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.
|
|
44
46
|
<!-- agent-consent:end -->
|
|
@@ -246,6 +248,8 @@ Doctor checks the contract, project reads, configuration, roles, helper startup,
|
|
|
246
248
|
|
|
247
249
|
Doctor runs the helper file via node, the agent via npx. `ROBISIE_PROJECT_CONTEXT` selects context later and does not change cwd for package lookup. Start the agent in the installation directory and ask it to list available tools from BOTH servers: `client-launch-context` (`get_launch_context`, `get_project_context`, `run_project_check`, `prepare_review`, `create_review_receipt`, `verify_stored_review`) and `ceo-client-launcher` (`spawn_builder`, `verify_review_receipt`). Result: both servers available with all these tools in that session. Do not call spawn_builder just as a probe. If a helper is missing, return to the installation cwd, check the local version and configuration, run init/doctor, then start a fresh agent session. Doctor alone does not confirm provider tool availability.
|
|
248
250
|
|
|
251
|
+
Doctor does not attach the robisie board MCP to the old conversation. After doctor exits 0, open a new CEO session in the installation directory with the robisie board MCP and the existing helpers. The first read is `list_projects`. An old session without that MCP does not start the card.
|
|
252
|
+
|
|
249
253
|
<!-- sekcja: pierwsza-karta -->
|
|
250
254
|
## First card and Builder startup
|
|
251
255
|
|
|
@@ -284,6 +288,8 @@ git commit -m "Przygotuj lokalne powitanie"
|
|
|
284
288
|
|
|
285
289
|
Save the entire JSON below as `robisie.config.json` in the repo directory, without overwriting existing configuration. **Replace** fictitious `project` with the UUID from authenticated `list_projects`, and the `tracks` UUID and name with a real track from that project’s board. Replace `engine.repo` with the absolute current repo path and `stateDir` with a separate directory **outside the repo**. Complete all four `roleRegistry` entries. In the local flow, `worker-client` can select Codex or Grok, and `reviewer-client` can select Codex, Claude or Grok. The Grok reviewer requires `provider: grok`, `model: grok-cli`, `effort: none`. The reviewer supports optional boolean `requireIndependentProvider`: absent or `true` requires another provider; a reviewer sharing the Worker provider requires explicit `false`. Every reviewer `false`, including Claude or Grok, marks review and acceptance as `partial` with the note “częściowa: bez niezależnego sprawdzenia”. Review always runs in a separate process. An unsupported pair or a configuration change during the card causes `HOLD clientPair`. For Codex roles, choose a real model available on your account and supported effort; this example uses `gpt-6.1-sol` / `high`, not fixture models. Set the Codex or Claude reviewer model and effort in the registry; the installed Grok CLI selects its model (`grok-cli` / `none`). The local flow requires CLI availability and login only for the providers selected for the Worker, reviewer and receiver; an omitted receiver means Grok. `doctor --engine-config` with explicit `engine.mode:host` checks structure offline, without CLI checks. With `engine.mode:client` or a missing `engine.mode` field, after input validation and when the program is available, it checks login only for selected providers: `codex login status` for Codex and `grok models` for Grok (`grok models` requires a network; Grok confirms login only probably), plus `claude auth status` when `reviewer-client.provider: claude` or `receiver-client.provider: claude`. A missing program does not check login, and a missing CLI or unconfirmed login prevents readiness. Neither mode runs a real AI task. Parsing and this doctor do not prove model or provider availability. This execution registry is separate from the installer’s CEO/Builder/Quality Officer map.
|
|
286
290
|
|
|
291
|
+
The local review example assumes a working Grok CLI. If `grok --version` prints “no platform binary installed for darwin-arm64”, the command is on PATH but the macOS ARM64 binary is missing. Repair or install a working local version according to the provider's instructions, then check the version and login again. A trial on 18.11 then saw 1.0.89; that number is not a guarantee of the current release. Exit 0 from `grok models` does not prove login or a full review.
|
|
292
|
+
|
|
287
293
|
The Grok Worker runs only on Linux with working bubblewrap (`bwrap`). On macOS the client refuses before startup because child-process network blocking is unavailable; select Codex. Install Grok CLI and sign in with `grok login --device-auth`; preserve HOME and optional GROK_HOME (default `~/.grok`) without relocating login. Codex still needs Codex CLI and `codex login --device-auth`. `doctor --engine-config` checks bubblewrap availability, but does not prove kernel enforcement.
|
|
288
294
|
|
|
289
295
|
The Grok Worker requires Grok CLI 1.0.77 or newer. Below that, doctor and startup refuse: update Grok CLI with `grok update`.
|
|
@@ -377,7 +383,7 @@ npx robisie doctor
|
|
|
377
383
|
|
|
378
384
|
Start the CEO in this directory: `claude --agent ceo-client`, or `codex` with the robisie CEO role and the full file referenced by AGENTS.md, or `opencode` selecting `ceo-client`. Give it this request:
|
|
379
385
|
|
|
380
|
-
> CEO, create a local card to change greet.cjs using the goal and literal details object below. Use the real project from list_projects and its board track. Change only greet.cjs, without dependencies, accounts or publication. Use my existing authorization if it covers this goal, directory, scope and acceptance; otherwise ask before dependent work. Supply actual authoring providers and a future deadline
|
|
386
|
+
> CEO, create a local card to change greet.cjs using the goal and literal details object below. Use the real project from list_projects and its board track. Change only greet.cjs, without dependencies, accounts or publication. Use my existing authorization if it covers this goal, directory, scope and acceptance; otherwise ask before dependent work. Supply actual authoring providers and a future deadline. Prepare the card, promote it to ready and verify ready with a fresh read. Do not call spawn_builder. The human runs factory run and the engine takes the release. After execution I need an independent tester and ACK, three uses for Ala/Bartek/Celina, and separate final acceptance.
|
|
381
387
|
|
|
382
388
|
Choose a project with policy `enforced` and `engine.delivery: "local"` using the [engine configuration](ENGINE-CONFIG.md). The CEO creates a card through the board tools with the literal `details` object below; the dashboard cannot edit `details`. The only list of all promised criteria is `done_when`; Builder evidence goes to `verification` and `summary` without overwriting criteria. Goal: change the greeting in an existing tracked `greet.cjs`; without arguments print `Witaj z fabryki`, and with one argument Ala, Bartek or Celina create a new `greeting.txt` containing `Witaj z fabryki, <name>!` and a trailing newline. No dependencies, accounts or publication. The code write scope is only `greet.cjs`; `greeting.txt` is a usage artifact in a copy of the landed SHA in a run directory under `stateDir`.
|
|
383
389
|
|
|
@@ -402,7 +408,7 @@ Before promotion, replace the `<unikalny-identyfikator-karty>` segment with a un
|
|
|
402
408
|
|
|
403
409
|
Before creating the card, replace the example `deadline` with a future ISO 8601 timestamp including a timezone and enough time for execution, the tester and three uses. In `seed_provenance.authoring_providers`, record the actual providers of the seed author (`by`), proposal author (`proposal_by`) and package author (`packager_by`); copying example providers does not establish independence. The engine supplies transport, delivery and tester results; do not manufacture these records.
|
|
404
410
|
|
|
405
|
-
After authorization, the CEO prepares the content
|
|
411
|
+
After authorization, the CEO prepares the content, promotes this first card to `ready` and verifies `ready` with a fresh full read. Do not call `spawn_builder` for this card: the existing factory run takes the release. Run `npx robisie factory run --engine-config ./robisie.config.json --once` and observe the card until a real tester PASS on the landed SHA and settlement (ACK): no `.tester-job.lock`, `.tester-job.input.json` or `.tester-job.result.json` in `stateDir`. PASS without ACK is insufficient. A fresh `get_task({id, include:[], fullDetails:true})` (the created card’s id) must show `details.test.verdict=PASS` and `details.test.sha=details.landed.sha`; process transport alone is not tester PASS.
|
|
406
412
|
|
|
407
413
|
A full read is `get_task({id, include:[], fullDetails:true})`: it already includes `test`, `landed` and `local_receiver`, without adding them to `include`. A `list_tasks` list needs explicit `detailsKeys` for the required details and omits `done` by default; check the result and completion by the known ID, not by disappearance from the list. Review is asynchronous and takes minutes; “Recenzja … trwa” means progress. STOP is a nonzero tick exit code, not a count of repeated messages. One format repair within the same acceptance job is normal and does not consume another budget position: `response.repair` and `repair.error` are in the archive referenced by `local_receiver.ref`.
|
|
408
414
|
|
|
@@ -442,15 +448,17 @@ The bare message „Odmowa użycia: Niepoprawny kontrakt JSON” does not name t
|
|
|
442
448
|
|
|
443
449
|
Acceptance has three outcomes: PASS proceeds through independent acceptance recorded with key B to `done`; waiting keeps the card in “Awaiting acceptance” (“Do odbioru”); a blocking STOP moves it to “Blocked” (“Zablokowane”). Every job reaching the model consumes a budget position, including a job with a valid assessment. Without a valid assessment and with `n<3`, the card waits 30 minutes with `local_receiver.reason` containing the literal `zadanie n/3; najwcześniej <czas UTC>` (job n/3; not before <UTC time>); the tick has exit 0, and checking resumes on the first subsequent tick after that time. With `n>=3`, no valid assessment blocks the card. Returning does not reset the counter. `--once` needs another tick, including to settle the result; `factory run` without `--once` repeats ticks itself.
|
|
444
450
|
|
|
445
|
-
###
|
|
451
|
+
### CEO start and Builder startup
|
|
452
|
+
|
|
453
|
+
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 doctor, do this from this README in the npm installation, in a new session with the robisie board MCP, not in the conversation from before doctor.
|
|
446
454
|
|
|
447
|
-
The
|
|
455
|
+
The default first local card is `greet.cjs` and is the `ceo-client` path through the existing factory run. In the new session the CEO prepares the card, promotes it to `ready` and verifies `ready` with a fresh read. It does not call `spawn_builder` for that card. The human runs the existing `npx robisie factory run --engine-config ./robisie.config.json`; the engine takes the `ready` release and starts one Worker. Independent review and the tester, three uses, local acceptance and a fresh read of `done` follow.
|
|
448
456
|
|
|
449
|
-
|
|
457
|
+
The manual `wynik.txt` example (a file containing exactly “robisie działa” followed by a newline, that file only, without dependencies, accounts or publication) is unsupported by the `ceo-client` role. Do not assign it to the CEO as a complete acceptance flow.
|
|
450
458
|
|
|
451
|
-
After human approval, the CEO
|
|
459
|
+
After human approval, outside this local factory cycle and only when the factory is not already running that card, the CEO follows the `ceo-client` dispatch and calls `spawn_builder` with the ID of the card confirmed in `ready`. It selects the configured Builder provider (Claude, Codex or OpenCode) and does not run beside `factory run` for the same card. New work creates `draft`; continuation and restart require reading the existing card, without a duplicate or a second start of active work. Extension applies only to an agreed `draft` or `ready`; `blocked` keeps the described return of the same delivery. See [Review and explicit acceptance](#recenzja-i-odbior).
|
|
452
460
|
|
|
453
|
-
If `spawn_builder` fails, the CEO reports the error and resolves the cause before retrying; it does not automatically switch to manual startup.
|
|
461
|
+
If `spawn_builder` fails or times out, confirmation is missing but a process may already be running. The CEO reads a fresh index and all details, checks status and assignee, and observes the existing work when `in_progress` is assigned. It does not roll back to `ready`, does not start a second executor and does not retry blindly. The CEO reports the error and resolves the cause before retrying; it does not automatically switch to manual startup.
|
|
454
462
|
|
|
455
463
|
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.
|
|
456
464
|
|
package/docs/README.md
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# robisie — od konta do odebranej karty (paczka 0.6.
|
|
1
|
+
# robisie — od konta do odebranej karty (paczka 0.6.10) <!-- x-release-please-version -->
|
|
2
2
|
|
|
3
3
|
W katalogu projektu z konfiguracją silnika uruchom `npx robisie init`, potem `npx robisie doctor`: init przygotuje cel projektu i listę ochrony testera, a doctor sprawdzi oba wejścia.
|
|
4
4
|
|
|
@@ -19,7 +19,9 @@ Jeśli README w rejestrze jest puste, użyj lokalnych przewodników w `node_modu
|
|
|
19
19
|
<a id="wymagania"></a>
|
|
20
20
|
## Wymagania
|
|
21
21
|
|
|
22
|
-
Człowiek przygotowuje Node.js 24+ (wydanie użyte przy sprawdzeniach: 24.3.0), npm, internet do zależności i robisie oraz
|
|
22
|
+
Człowiek przygotowuje Node.js 24+ (wydanie użyte przy sprawdzeniach: 24.3.0), npm, internet do zależności i robisie oraz programy dostawców opisane poniżej, każdy z własnym dostępem do AI. Starszy Node, np. 22, otrzymuje odmowę przed `init`, `doctor` i `factory run`. Silnik w paczce (`dist/engine/tick.cjs`) dla klienta wymaga systemu Linux lub macOS; jawny host Robisie (`engine.mode: "host"`, dostawa `pr|delivered`) może działać także na macOS. Uruchamia go `npx robisie factory run`; konfigurację silnika opisuje [ENGINE-CONFIG](ENGINE-CONFIG.md). Sprawdź `node --version`, `npm --version` i wersję wybranego programu (`claude --version`, `codex --version` lub `opencode --version`). Jeśli programu nie ma w PATH, zainstaluj go według instrukcji dostawcy i sprawdź ponownie; sam katalog konfiguracji nie wystarcza. Windows/WSL są niezweryfikowane; poniższe przykłady używają ścieżek POSIX.
|
|
23
|
+
|
|
24
|
+
Role instalatora (`ceo`, `builder`, `quality`) używają jednego dostawcy do budowania: Claude Code, Codex CLI albo OpenCode. Niezależna recenzja i odbiór wymagają drugiego, zalogowanego dostawcy; domyślnie Grok. Te role instalatora są odrębne od `roleRegistry` (`worker-client`, `lead-client`, `reviewer-client`, `tester-client` i opcjonalny `receiver-client`). Nie ma automatycznej konwersji między nimi. Wpis `receiver-client` z `requireIndependentProvider:false` oznacza `partial` i nadal osobny proces: wspólny dostawca, na przykład receiver Codex przy Workerze Codex, nie daje pełnej niezależności.
|
|
23
25
|
|
|
24
26
|
Przygotuj pusty katalog na dysku. Nie potrzebujesz strony ani własnego pliku `package.json`; przed instalacją utworzy go poniższy krok Node.js. To katalog pracy agentów, niezależny od projektu w panelu.
|
|
25
27
|
|
|
@@ -209,7 +211,7 @@ npx robisie doctor
|
|
|
209
211
|
|
|
210
212
|
Łańcuch `&&` zatrzymuje wykonanie po błędzie. Przy odmowie napraw wskazaną przyczynę przed ponowieniem; nie zastępuj zwykłego doctor walidacją `--engine-config`, która nie sprawdza kluczy.
|
|
211
213
|
|
|
212
|
-
4. Dopiero po doctor z exit 0 przejdź do sekcji „Pierwsza karta i start Buildera”, zgodnie z uzgodnionym celem i zakresem zapisu.
|
|
214
|
+
4. Dopiero po doctor z exit 0 otwórz nową sesję CEO w katalogu instalacji z MCP robisie tablicy i przejdź do sekcji „Pierwsza karta i start Buildera”, zgodnie z uzgodnionym celem i zakresem zapisu.
|
|
213
215
|
|
|
214
216
|
<!-- agent-install:end -->
|
|
215
217
|
|
|
@@ -291,6 +293,8 @@ Gdy klucz A widzi dokładnie jeden projekt, doctor odczytuje jego `reviewPolicy`
|
|
|
291
293
|
|
|
292
294
|
Doctor uruchamia plik pomocnika przez node, agent przez npx. `ROBISIE_PROJECT_CONTEXT` wybiera kontekst później i nie zmienia cwd szukania paczki. Uruchom agenta w katalogu instalacji i poproś o wyświetlenie dostępnych narzędzi OBU serwerów: `client-launch-context` (`get_launch_context`, `get_project_context`, `run_project_check`, `prepare_review`, `create_review_receipt`, `verify_stored_review`) oraz `ceo-client-launcher` (`spawn_builder`, `spawn_quality`, `verify_review_receipt`). Wynik: oba serwery dostępne z kompletem tych narzędzi w sesji. Nie uruchamiaj spawn_builder tylko dla próby. Przy braku pomocnika wróć do cwd instalacji, sprawdź lokalną wersję i konfigurację, uruchom init/doctor, potem nową sesję agenta. Sam doctor nie potwierdza dostępności narzędzi u dostawcy.
|
|
293
295
|
|
|
296
|
+
Doctor nie dołącza MCP tablicy `robisie` do starej rozmowy. Po doctor z exit 0 otwórz nową sesję CEO w katalogu instalacji, z MCP robisie tablicy i istniejącymi pomocnikami. Pierwszy odczyt to `list_projects`. Stara sesja bez tego MCP nie zaczyna karty.
|
|
297
|
+
|
|
294
298
|
<!-- sekcja: pierwsza-karta -->
|
|
295
299
|
## Pierwsza karta i start Buildera
|
|
296
300
|
|
|
@@ -329,6 +333,8 @@ git commit -m "Przygotuj lokalne powitanie"
|
|
|
329
333
|
|
|
330
334
|
Zapisz cały poniższy JSON jako `robisie.config.json` w katalogu repo, bez nadpisywania istniejącej konfiguracji. **Podmień** fikcyjne `project` na UUID z uwierzytelnionego `list_projects`, a UUID i nazwę `tracks` na rzeczywisty tor z tablicy tego projektu. Podmień `engine.repo` na absolutną ścieżkę bieżącego repo, a `stateDir` na osobny katalog **poza repo**. Uzupełnij wszystkie cztery wpisy `roleRegistry`. W lokalnym przebiegu `worker-client` może wybrać Codex albo Grok, a `reviewer-client` może wybrać Codex, Claude albo Grok. Recenzent Grok wymaga `provider: grok`, `model: grok-cli`, `effort: none`. Recenzent ma opcjonalne boolean `requireIndependentProvider`: brak lub `true` wymaga innego dostawcy; recenzent współdzielący dostawcę z Workerem wymaga jawnego `false`. Każde `false` recenzenta, także przy Claude lub Groku, zapisuje review i acceptance jako `partial` z notą „częściowa: bez niezależnego sprawdzenia”. Recenzja zawsze działa w osobnym procesie. Niedozwolona para lub zmiana konfiguracji w trakcie karty daje `HOLD clientPair`. Dla ról Codex wybierz rzeczywisty model dostępny na swoim koncie i obsługiwany effort; przykład używa `gpt-6.1-sol` / `high`, nie modeli fixture. Dla Codex i Claude ustaw model oraz effort recenzenta w rejestrze; model Groka wybiera zainstalowany Grok CLI (`grok-cli` / `none`). Lokalny przebieg wymaga CLI i logowania dostawców wybranych dla Workera, recenzenta i odbiorcy; brak wpisu odbiorcy oznacza Groka. `doctor --engine-config` przy jawnym `engine.mode:host` sprawdza strukturę offline, bez kontroli CLI. Przy `engine.mode:client` albo braku pola `engine.mode` sprawdza logowanie tylko wybranych dostawców po walidacji wejść i przy dostępnym programie: `codex login status` dla Codexa i `grok models` dla Groka (`grok models` wymaga sieci; Grok potwierdza logowanie tylko prawdopodobnie), a `claude auth status` przy `reviewer-client.provider: claude` lub `receiver-client.provider: claude`. Brak programu nie pozwala sprawdzić logowania; brak CLI lub potwierdzenia logowania nie daje gotowości. Żaden tryb nie wykonuje prawdziwego zadania AI. Same parsowanie i ten doctor nie dowodzą dostępności modeli ani dostawców. Rejestr wykonania jest odrębny od mapy instalatora CEO/Builder/Quality Officer.
|
|
331
335
|
|
|
336
|
+
Lokalny przykład recenzji zakłada działające Grok CLI. Jeśli `grok --version` wypisze „no platform binary installed for darwin-arm64”, polecenie jest w PATH, ale brakuje binarki macOS ARM64. Napraw lub doinstaluj działającą lokalną wersję według instrukcji dostawcy, potem ponownie sprawdź wersję i logowanie. Próba z 18.11 zobaczyła wtedy 1.0.89; ta liczba nie jest gwarancją aktualnego wydania. Kod 0 z `grok models` nie dowodzi zalogowania ani pełnej recenzji.
|
|
337
|
+
|
|
332
338
|
Worker Codex na Linuksie może uruchamiać testy tworzące procesy, ale proxy deny-all blokuje dostęp do internetu: komenda próbująca ruchu sieciowego zostanie PRZERWANA (exit −1), zamiast zwrócić zwykły błąd. Zależności przygotuj poza Workerem. Runner dopisuje `127.0.0.1,localhost` osobno do `NO_PROXY` i `no_proxy`, zachowując istniejące listy użytkownika i dostęp HTTP do localhost. Pomiar dotyczy Codex 0.166.0 na Linux aarch64; nie potwierdza rzeczywistego użycia u Dota na Linux x64 po wydaniu.
|
|
333
339
|
|
|
334
340
|
Worker Grok działa wyłącznie na Linux z działającym bubblewrap (`bwrap`). Na macOS klient odmawia przed startem: brak blokady sieci potomnych; wybierz Codex. Zainstaluj Grok CLI i zaloguj `grok login --device-auth`; zachowaj HOME i opcjonalne GROK_HOME (domyślnie `~/.grok`), bez kopiowania logowania. Codex nadal wymaga Codex CLI i `codex login --device-auth`. `doctor --engine-config` sprawdza obecność bubblewrap, ale nie dowodzi ochrony jądra.
|
|
@@ -424,7 +430,7 @@ npx robisie doctor
|
|
|
424
430
|
|
|
425
431
|
Uruchom CEO w tym katalogu: `claude --agent ceo-client`, albo `codex` z rolą robisie CEO i pełnym odczytem pliku wskazanego w AGENTS.md, albo `opencode` z wyborem `ceo-client`. Przekaż mu gotową prośbę:
|
|
426
432
|
|
|
427
|
-
> CEO, utwórz lokalną kartę zmiany greet.cjs według celu i literalnego obiektu details poniżej. Użyj rzeczywistego projektu z list_projects i toru z tablicy. Zmień wyłącznie greet.cjs, bez zależności, kont i publikacji. Korzystaj z wcześniejszej zgody, jeśli obejmuje ten cel, katalog, zakres i odbiór; inaczej zapytaj przed zależnym krokiem. Wstaw prawdziwych dostawców autorstwa i przyszły deadline
|
|
433
|
+
> CEO, utwórz lokalną kartę zmiany greet.cjs według celu i literalnego obiektu details poniżej. Użyj rzeczywistego projektu z list_projects i toru z tablicy. Zmień wyłącznie greet.cjs, bez zależności, kont i publikacji. Korzystaj z wcześniejszej zgody, jeśli obejmuje ten cel, katalog, zakres i odbiór; inaczej zapytaj przed zależnym krokiem. Wstaw prawdziwych dostawców autorstwa i przyszły deadline. Przygotuj kartę, promuj ją do ready i zweryfikuj ready świeżym odczytem. Nie wołaj spawn_builder. Człowiek uruchamia factory run, a silnik przejmuje wydanie. Po pracy potrzebuję niezależnego testera i ACK, trzech użyć Ala/Bartek/Celina oraz osobnego końcowego odbioru.
|
|
428
434
|
|
|
429
435
|
Wybierz projekt z polityką `enforced` i konfiguracją `engine.delivery: "local"` według [konfiguracji silnika](ENGINE-CONFIG.md). CEO tworzy kartę przez narzędzia tablicy, z poniższym literalnym obiektem `details`. Panel nie edytuje `details`. Jedyną listą wszystkich obiecanych kryteriów jest `done_when`; dowody wykonania trafiają do `verification` i `summary`, bez nadpisywania kryteriów. Cel: zmień powitanie w istniejącym, śledzonym `greet.cjs`; bez argumentu wypisz `Witaj z fabryki`, a dla jednego argumentu Ala, Bartek lub Celina zapisz nowe `greeting.txt` z `Witaj z fabryki, <imię>!` i końcowym znakiem nowej linii. Bez zależności, kont i publikacji. Zakres zapisu kodu obejmuje tylko `greet.cjs`; `greeting.txt` jest artefaktem użycia w kopii landed SHA w katalogu przebiegu pod `stateDir`.
|
|
430
436
|
|
|
@@ -449,7 +455,7 @@ Zastąp segment `<unikalny-identyfikator-karty>` wartością unikalną dla karty
|
|
|
449
455
|
|
|
450
456
|
Przed utworzeniem karty zastąp przykładowy `deadline` przyszłym terminem ISO 8601 ze strefą czasową, obejmującym wykonanie, testera i trzy użycia. W `seed_provenance.authoring_providers` wpisz prawdziwych dostawców autorów: `by` autora zasiewu, `proposal_by` autora propozycji, `packager_by` autora pakietu; nie kopiuj przykładowych nazw dla pozorowania niezależności. Silnik dopisuje transport, dostawę i wynik testera — nie twórz tych dowodów ręcznie.
|
|
451
457
|
|
|
452
|
-
Po autoryzacji CEO przygotowuje
|
|
458
|
+
Po autoryzacji CEO przygotowuje treść, promuje tę pierwszą kartę do `ready` i weryfikuje `ready` świeżym pełnym odczytem. Nie wołaj `spawn_builder` dla tej karty: wydanie przejmuje istniejący factory run. Uruchamiaj `npx robisie factory run --engine-config ./robisie.config.json --once` i obserwuj kartę aż do rzeczywistego PASS testera na landed SHA oraz jego rozliczenia (ACK): brak `.tester-job.lock`, `.tester-job.input.json` i `.tester-job.result.json` w `stateDir`. Sam PASS bez ACK nie wystarcza. Świeży odczyt `get_task({id, include:[], fullDetails:true})` (id utworzonej karty) musi pokazać `details.test.verdict=PASS` oraz `details.test.sha=details.landed.sha`; sam transport procesu nie jest PASS testera.
|
|
453
459
|
|
|
454
460
|
Pełny odczyt to `get_task({id, include:[], fullDetails:true})`: zawiera już `test`, `landed` i `local_receiver`, bez dopisywania ich do `include`. Lista `list_tasks` wymaga jawnego `detailsKeys` dla potrzebnych szczegółów i domyślnie pomija `done`; wynik i zakończenie sprawdzaj po znanym ID, nie przez zniknięcie z listy. Recenzja jest asynchroniczna, trwa rzędu minut; „Recenzja … trwa” oznacza ruch. STOP rozpoznasz po niezerowym kodzie taktu, nie po liczbie powtórzeń komunikatu. Jedna naprawa formy w tym samym zadaniu odbioru jest normalna i nie jest kolejną pozycją budżetu: `response.repair` i `repair.error` znajdziesz w archiwum wskazanym przez `local_receiver.ref`.
|
|
455
461
|
|
|
@@ -491,11 +497,13 @@ Odbiór ma trzy wyniki: PASS prowadzi przez niezależny zapis odbioru kluczem B
|
|
|
491
497
|
|
|
492
498
|
### Start CEO i Buildera
|
|
493
499
|
|
|
494
|
-
Człowiek uruchamia CEO w katalogu instalacji: `claude --agent ceo-client`, albo `codex` i prosi o rolę robisie CEO (odczyt pełnego pliku wskazanego w AGENTS.md), albo `opencode` i wybiera `ceo-client`. Po instalacji npm i poprawnym odczycie projektów przekaż kompletną lokalną kartę `greet.cjs` z powyższego przykładu w tym README.
|
|
500
|
+
Człowiek uruchamia CEO w katalogu instalacji: `claude --agent ceo-client`, albo `codex` i prosi o rolę robisie CEO (odczyt pełnego pliku wskazanego w AGENTS.md), albo `opencode` i wybiera `ceo-client`. Po instalacji npm i poprawnym odczycie projektów przekaż kompletną lokalną kartę `greet.cjs` z powyższego przykładu w tym README. Po doctor zrób to w nowej sesji z MCP robisie tablicy, nie w rozmowie sprzed doctor.
|
|
501
|
+
|
|
502
|
+
Domyślna pierwsza lokalna karta `greet.cjs` jest drogą roli `ceo-client` przez istniejący factory run. CEO w nowej sesji przygotowuje kartę, promuje ją do `ready` i weryfikuje `ready` świeżym odczytem. Nie woła `spawn_builder` dla tej karty. Człowiek uruchamia istniejący `npx robisie factory run --engine-config ./robisie.config.json`; silnik przejmuje wydanie karty `ready` i uruchamia jednego Workera. Dalej są niezależna recenzja i tester, trzy użycia, odbiór lokalny i świeży odczyt `done`.
|
|
495
503
|
|
|
496
504
|
Ręczny przykład `wynik.txt` (plik z treścią „robisie działa” i końcowym znakiem nowej linii, tylko ten plik, bez zależności, kont i publikacji) jest niewspierany przez rolę `ceo-client`. Nie zlecaj go CEO jako kompletnego przebiegu do odbioru.
|
|
497
505
|
|
|
498
|
-
Po uzgodnieniu zakresu CEO wywołuje `spawn_builder` z ID karty potwierdzonej w `ready
|
|
506
|
+
Po uzgodnieniu zakresu, poza tym lokalnym cyklem factory run i tylko gdy dla tej karty nie działa fabryka, CEO wykonuje dyspozycję roli `ceo-client`: wywołuje `spawn_builder` z ID karty potwierdzonej w `ready` wyłącznie jako osobny start Buildera; adapter wybiera skonfigurowanego dostawcę Buildera (Claude, Codex albo OpenCode). Nie stawiaj tego wywołania obok `factory run` dla tej samej karty. Nowa praca tworzy `draft`; kontynuacja i restart wymagają odczytu istniejącej karty, bez tworzenia duplikatu lub ponownego startu aktywnej pracy. Rozszerzenie dotyczy tylko uzgodnionego `draft`/`ready`; `blocked` zachowuje opisany wyjątek powrotu tej samej dostawy. Automatyczny cykl lokalny i ręczny przykład rozróżnia sekcja [Recenzja i odbiór](#recenzja-i-odbior).
|
|
499
507
|
|
|
500
508
|
Przy błędzie lub timeout `spawn_builder` brakuje potwierdzenia, lecz proces może już działać. CEO odczytuje świeży indeks i wszystkie details, sprawdza status oraz assignee; przy przydzielonym `in_progress` obserwuje istniejącą pracę. Nie cofa do `ready`, nie uruchamia drugiego wykonawcy ani nie ponawia w ciemno. Nieczytelny stan eskaluje jako brak potwierdzenia. Ponowienie wymaga wyjaśnionej przyczyny oraz dowodu, że żaden wykonawca nie działa; ręczny start pozostaje jawnym wyborem operatora.
|
|
501
509
|
|
package/package.json
CHANGED
package/roles/ceo-client.md
CHANGED
|
@@ -146,7 +146,7 @@ Every `done_when` item must be a condition the builder or independent reviewer c
|
|
|
146
146
|
|
|
147
147
|
Canonical statuses are `draft`, `ready`, `in_progress`, `in_review`, `delivered`, `done`, and `blocked`.
|
|
148
148
|
|
|
149
|
-
- CEO owns: `draft → ready`. Promote only a complete, deduplicated card,
|
|
149
|
+
- CEO owns: `draft → ready`. Promote only a complete, deduplicated card and verify `ready`. For the first local card on factory run, the engine takes the release and you do not call `spawn_builder`. Outside that cycle, launch its builder.
|
|
150
150
|
- Builder owns: `ready → in_progress → in_review`. Observe these states; never perform these transitions for the builder.
|
|
151
151
|
- Automatic local acceptance owns: `in_review → delivered → done`, through the active installation's `localAcceptancePhase`, after independent receiver PASS, protected server acceptance and the required real-use evidence. Never use `update_task` to set `delivered` or `done`; the CEO has no server acceptance tool.
|
|
152
152
|
- A `blocked` card is not finished. Report the concrete obstacle and the next choice; do not disguise it as progress.
|
|
@@ -163,7 +163,9 @@ Before the tool call, require a Planer-issued card reference that is a canonical
|
|
|
163
163
|
|
|
164
164
|
The adapter passes the validated reference as J1's single positional argument. J1 maps it to `ROBISIE_CARD_REF`, carries `ROBISIE_KEY` through the environment, and supplies `ROBISIE_PROJECT_CONTEXT` as the builder's working directory. Never put a credential in tool input, command arguments, card content, logs, or transcripts. Never construct a launch request from a title or card details.
|
|
165
165
|
|
|
166
|
-
For
|
|
166
|
+
For the first local card on factory run, prepare the card and verify `ready`, then stop: (1) `update_task` to `ready`; (2) `get_task` via `readCompleteCard` and require exact status `ready` with unchanged complete details. Do not call `spawn_builder` for that card. The human runs the existing factory run and the engine takes the release and starts one Worker. obietnica kierownika klienta = karta, nie rozmowa.
|
|
167
|
+
|
|
168
|
+
For a new dispatch of an eligible `draft` or `ready` card outside that local factory cycle only, the strict dispatch sequence is: (1) `update_task` to `ready`; (2) `get_task` and verify the exact status and unchanged complete details; (3) `spawn_builder` once with that verified id; (4) `get_task` once via `readCompleteCard` for the handoff outcome. Never skip, reorder, or repeat these steps. Make exactly one launcher call for a dispatch. If a verification fails, stop before the next step and report only the customer-visible effect.
|
|
167
169
|
|
|
168
170
|
The adapter withholds a success acknowledgement until its own bounded authenticated read proves that the exact card is `in_progress` with a nonempty assignee. Treat `SPAWNED` and `ALREADY_RUNNING` as adapter confirmations only, and still perform exactly one independent post-tool `get_task` read. Tell the operator that work started only when that CEO-owned read returns the exact card in `in_progress` with a nonempty assignee. If the independent read cannot confirm that state, leave the card unchanged, flag the launcher-to-builder input contract for integration, and use the operator's current language for one concise semantic message saying that you cannot yet confirm the builder took the work and that the handoff integration needs repair. Never pair that message with “work started” or an equivalent stronger claim. A launcher error or timeout is missing confirmation, not proof that no process exists or that the card remains `ready`. Make a fresh `get_task` read via `readCompleteCard` to check status and assignee even after a tool error; if already assigned `in_progress`, observe that process. Never roll back to `ready`, start a second executor or retry blind. An unreadable state stays unconfirmed; escalate the named gap. A safe retry is considered only after its named cause is resolved and fresh state/process evidence establishes that no executor is running; never blindly.
|
|
169
171
|
|
|
@@ -186,7 +188,7 @@ For each review attempt on exactly one card, follow these steps in order without
|
|
|
186
188
|
## Delivery loop
|
|
187
189
|
|
|
188
190
|
1. Clarify the outcome, show the short plan and deduplicate. For new work only, use `create_task` to seed complete `draft` cards. For an existing `draft` or `ready` card, extend only the agreed scope after a complete read. For `in_progress`, `in_review`, or `delivered`, observe: no create and no spawn for the same work. For `blocked`, follow only the local receiver return exception when applicable; otherwise coordinate its obstacle without duplication.
|
|
189
|
-
2. For an eligible dispatch only, use `update_task` to flip the next eligible card to `ready`, confirm it with `get_task`, immediately invoke the builder command with that card's id, and perform the one post-launch card read required by the integration boundary.
|
|
191
|
+
2. For the first local card on factory run, flip that card to `ready`, confirm `ready` with `get_task`, and do not call `spawn_builder`; the engine takes the release. For an eligible dispatch outside that local factory cycle only, use `update_task` to flip the next eligible card to `ready`, confirm it with `get_task`, immediately invoke the builder command with that card's id, and perform the one post-launch card read required by the integration boundary.
|
|
190
192
|
3. After that read confirms an assigned `in_progress` card, tell the operator only that work has started and that you will return with a checked result. Otherwise report the unconfirmed handoff as described above; never convert launcher output into a stronger claim.
|
|
191
193
|
4. Refresh the board when the operator returns, asks for status, asks for the next action, or after an action you initiated. Do not poll in the background.
|
|
192
194
|
5. When a card enters `in_review`, run the Native quality review protocol exactly once for that review attempt. Do not inspect or grade the builder's evidence yourself.
|
|
@@ -223,5 +225,5 @@ Immediately before emitting text during a dispatch, apply this final protocol:
|
|
|
223
225
|
1. Give one product-only plan before the first tool. It describes only what will be made and delivered; it contains no workflow noun, UI state, or role name.
|
|
224
226
|
2. For any optional progress preamble, use one short semantic sentence in the operator's current language saying that the agreed plan is being carried out. Never combine the progress sentence with a technical explanation, heading, or stronger claim; when no such sentence is useful, emit no preamble.
|
|
225
227
|
3. After the final handoff read, when status and assignee do not confirm the start, use only the semantic unconfirmed-handoff message described by the integration boundary in the operator's current language. Do not add internal mechanics or a stronger claim.
|
|
226
|
-
4. Choose the Delivery loop path first: new work alone permits `create_task`; existing `draft` or `ready` may extend agreed scope before dispatch; `in_progress`, `in_review`, or `delivered` means observe, no create and no spawn; `blocked` permits only the bounded local receiver return. For an eligible dispatch, follow the strict dispatch sequence in the Integration boundary; each read is `readCompleteCard`, including after a launcher error.
|
|
228
|
+
4. Choose the Delivery loop path first: new work alone permits `create_task`; existing `draft` or `ready` may extend agreed scope before dispatch; `in_progress`, `in_review`, or `delivered` means observe, no create and no spawn; `blocked` permits only the bounded local receiver return. For the first local card on factory run, verify `ready` and do not call `spawn_builder`; the engine takes the release. For an eligible dispatch outside that cycle, follow the strict dispatch sequence in the Integration boundary; each read is `readCompleteCard`, including after a launcher error.
|
|
227
229
|
5. Follow this strict review sequence without batching or omission: fresh `get_task` confirming `in_review`; one runtime-specific independent review call (Claude: `Agent(quality-officer-client)`; Codex: `spawn_quality`; OpenCode: fail closed); exact receipt parse; fresh `get_task` confirming `in_review`; one `verify_review_receipt` call; one unchanged post-verification complete read; observe the automatic local acceptance cycle; confirm `done` by a complete read or escalate the concrete obstacle. Never relay `delivered`/`done` yourself.
|