@obita-ai/multica 0.11.14 → 0.11.16
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/README.md +37 -0
- package/build-metadata.json +3 -3
- package/package.json +7 -7
package/README.md
CHANGED
|
@@ -17,3 +17,40 @@ The CLI and daemon shipped in these packages query npm for updates. They do not
|
|
|
17
17
|
If installation succeeds but a platform package is absent, reinstall with `npm install -g @obita-ai/multica@latest --include=optional`. If an older `multica` appears first on PATH, inspect `command -v multica` (Unix) or `where.exe multica` (Windows) and adjust PATH to the desired npm prefix.
|
|
18
18
|
|
|
19
19
|
See LICENSE and NOTICE for licensing and attribution.
|
|
20
|
+
|
|
21
|
+
## Pause and maintain a daemon
|
|
22
|
+
|
|
23
|
+
These commands require a daemon and CLI that support maintenance protocol 1 (0.11.15 or newer). Select a named profile with `--profile NAME`; omit it for the default profile.
|
|
24
|
+
|
|
25
|
+
```sh
|
|
26
|
+
multica --profile NAME daemon pause --wait --timeout 30m
|
|
27
|
+
multica --profile NAME daemon status --output json
|
|
28
|
+
multica --profile NAME daemon upgrade --target-version 0.11.16 --timeout 45m
|
|
29
|
+
multica --profile NAME daemon resume
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
Pause stops new claims across all workspaces served by that profile. Owned runs, heartbeats and result reporting continue. Pause survives process restarts. `--wait` includes resource waiters, in-flight claims and terminal reports; failed reports require repair. A wait timeout leaves the daemon paused.
|
|
33
|
+
|
|
34
|
+
Upgrade is available for standalone global npm installations on macOS/Linux with a prefix owned exclusively by the current user. It pauses, drains, takes an installation lock, installs the exact version, checks the installed maintenance protocol and build metadata, restarts, and verifies the running version and commit. A daemon already paused before upgrade remains paused; a new manual pause during upgrade also wins. Otherwise successful verification restores admission. Automatic downgrade is rejected. Windows automatic maintenance is disabled pending ACL and native lifecycle validation; pause/resume remain available.
|
|
35
|
+
|
|
36
|
+
The command prints an operation ID. If the terminal disconnects, continue with:
|
|
37
|
+
|
|
38
|
+
```sh
|
|
39
|
+
multica --profile NAME daemon upgrade --operation-id OPERATION_ID
|
|
40
|
+
multica --profile NAME daemon upgrade --operation-id OPERATION_ID --cancel
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
Cancellation is accepted only before installation and preserves pause. Client `--timeout`, background `--drain-timeout` (30m default), and `--install-timeout` (10m default) are separate. Client timeout does not terminate an installer. Commands return JSON; failures include diagnostic status when the daemon is reachable.
|
|
44
|
+
|
|
45
|
+
Two profiles sharing one npm prefix cannot upgrade while either other daemon is alive, even if idle. Stop the other profile first, or use separate prefixes. A newly starting daemon waits behind an installer and checks the on-disk build before claiming. Legacy daemons do not participate in these locks: stop them before the initial manual upgrade. External `npm install` commands are not coordinated by daemon locks.
|
|
46
|
+
|
|
47
|
+
Any installer failure retains an installation journal and pause because npm may have partially replaced files. Stop the daemon, confirm the installer and all descendants have exited, repair/reinstall the intended package if necessary, then acknowledge the failure:
|
|
48
|
+
|
|
49
|
+
```sh
|
|
50
|
+
multica --profile NAME daemon maintenance-recover --operation-id OPERATION_ID --mark-failed
|
|
51
|
+
multica --profile NAME daemon start
|
|
52
|
+
multica --profile NAME daemon status --output json
|
|
53
|
+
multica --profile NAME daemon resume
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
Recovery requires both the profile and installation locks and keeps admission paused. Do not remove journals or restore an older binary to bypass uncertainty. If the installed CLI cannot run, use a known-good maintenance-capable executable for recovery after repairing the same global prefix. These commands operate locally and are rejected from task execution context.
|
package/build-metadata.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
|
-
"version": "0.11.
|
|
3
|
-
"revision": "
|
|
2
|
+
"version": "0.11.16",
|
|
3
|
+
"revision": "bcf3ca26d9b02aac172bda29fd429fb7be54ff4a",
|
|
4
4
|
"dirty": false,
|
|
5
|
-
"date": "2026-11-
|
|
5
|
+
"date": "2026-11-16T10:51:31Z",
|
|
6
6
|
"toolchain": "go version go1.26.11 darwin/arm64",
|
|
7
7
|
"distribution": "npm"
|
|
8
8
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@obita-ai/multica",
|
|
3
|
-
"version": "0.11.
|
|
3
|
+
"version": "0.11.16",
|
|
4
4
|
"description": "Obita Multica CLI and local agent runtime",
|
|
5
5
|
"engines": {
|
|
6
6
|
"node": ">=22"
|
|
@@ -26,11 +26,11 @@
|
|
|
26
26
|
"build-metadata.json"
|
|
27
27
|
],
|
|
28
28
|
"optionalDependencies": {
|
|
29
|
-
"@obita-ai/multica-darwin-x64": "0.11.
|
|
30
|
-
"@obita-ai/multica-darwin-arm64": "0.11.
|
|
31
|
-
"@obita-ai/multica-linux-x64": "0.11.
|
|
32
|
-
"@obita-ai/multica-linux-arm64": "0.11.
|
|
33
|
-
"@obita-ai/multica-win32-x64": "0.11.
|
|
34
|
-
"@obita-ai/multica-win32-arm64": "0.11.
|
|
29
|
+
"@obita-ai/multica-darwin-x64": "0.11.16",
|
|
30
|
+
"@obita-ai/multica-darwin-arm64": "0.11.16",
|
|
31
|
+
"@obita-ai/multica-linux-x64": "0.11.16",
|
|
32
|
+
"@obita-ai/multica-linux-arm64": "0.11.16",
|
|
33
|
+
"@obita-ai/multica-win32-x64": "0.11.16",
|
|
34
|
+
"@obita-ai/multica-win32-arm64": "0.11.16"
|
|
35
35
|
}
|
|
36
36
|
}
|