@mblua/agentscommander 0.30.5 → 0.31.0
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 +11 -8
- package/install.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -35,20 +35,23 @@ npm root -g
|
|
|
35
35
|
npm view @mblua/agentscommander@latest version
|
|
36
36
|
```
|
|
37
37
|
|
|
38
|
-
`npm list` reports the installed package version and can exit nonzero when the package is absent. `npm root -g` exits 0 and prints the global `node_modules` directory. Use that root to inspect the installed `@mblua/agentscommander/package.json`, `install.js`, `run.js`, and native file under `bin/`. Correlate the package-manager record and `package.json` version with the install script's version and release URL, the launcher's exact native path, and the corresponding GitHub tag, asset, and checksum. `npm view` reports the selected registry version without installing it. If the local records, independent release evidence, native file, or selected version disagree or cannot be identified exactly, stop before mutation.
|
|
38
|
+
`npm list` reports the installed package version and can exit nonzero when the package is absent. `npm root -g` exits 0 and prints the global `node_modules` directory. Use that root to inspect the installed `@mblua/agentscommander/package.json`, `install.js`, `run.js`, and native file under `bin/`. Correlate the package-manager record and `package.json` version with the install script's version and release URL, the launcher's exact native path, and the corresponding GitHub tag, asset, and checksum. `npm view` reports the selected registry version without installing it. If the local records, independent release evidence, native file, or selected version disagree or cannot be identified exactly, stop before mutation. `agentscommander --version` prints the native CLI version from `v0.31.0` onward; `v0.30.5` and older builds reject that flag, so probe a binary for a self-reported version only after its exact tag proves support.
|
|
39
39
|
|
|
40
40
|
The existing binary's exact resolver determines what must be preserved. The selected package's exact release tag determines post-install behavior. Verify both against the corresponding `v<version>` source tag; do not use `main` as evidence for a published npm package.
|
|
41
41
|
|
|
42
|
-
### npm `0.
|
|
42
|
+
### npm `0.31.0`
|
|
43
43
|
|
|
44
|
-
|
|
44
|
+
`0.31.0` is the npm `latest` at this documentation commit. Its published install script downloads the `v0.31.0` native release asset, verifies it against `SHASUMS256.txt`, and renames it to the executable in the package's `bin/` directory; the launcher only spawns that binary and injects no configuration override. The `v0.31.0` native resolver, unchanged from `v0.30.5`:
|
|
45
45
|
|
|
46
|
-
1.
|
|
47
|
-
2.
|
|
46
|
+
1. selects the `AGENTSCOMMANDER_CONFIG_DIR` value verbatim when that variable is set and non-blank, running no probes;
|
|
47
|
+
2. otherwise derives the candidate `<native-executable-folder>/.<native-executable-stem>`, checks for a `portable.txt` marker beside the executable, and write-probes the candidate;
|
|
48
|
+
3. selects that candidate when the write probe succeeds, with or without the marker;
|
|
49
|
+
4. falls back to `$HOME/.agentscommander-new` only when the executable's parent and stem cannot be derived, or when the marker is absent and the candidate is conclusively unwritable; and
|
|
50
|
+
5. refuses to start on every other probe outcome (marker present but candidate unwritable, or an indeterminate probe), reporting an error that says to set `AGENTSCOMMANDER_CONFIG_DIR`.
|
|
48
51
|
|
|
49
|
-
|
|
52
|
+
The npm installer writes no `portable.txt`. For a normal npm `0.31.0` install with a writable global `node_modules`, the write probe succeeds and the selected directory is therefore `.agentscommander` beside the native executable under `@mblua/agentscommander/bin/`, the same location `0.30.3` selected, now confirmed by a probe instead of assumed.
|
|
50
53
|
|
|
51
|
-
The
|
|
54
|
+
The previous npm version, `0.30.5`, shares this resolver exactly. The older npm version `0.30.3` ships none of this: its resolver immediately selects `<native-executable-folder>/.<native-executable-stem>` whenever that parent and stem can be derived, uses `$HOME/.agentscommander-new` only when they cannot, and never reads `AGENTSCOMMANDER_CONFIG_DIR`, inspects `portable.txt`, probes writability, or falls back to home because the adjacent path is read-only. npm never published a `0.30.4` package; that number exists only as a GitHub release. For any other published version, inspect `src-tauri/src/config/mod.rs`, `src-tauri/src/config/profile.rs`, `npm/run.js`, and `npm/install.js` at its exact `v<version>` tag; do not extrapolate from `0.31.0`, `0.30.5`, `0.30.3`, or `main`.
|
|
52
55
|
|
|
53
56
|
Before an npm update or uninstall, identify the active directory with the existing binary's verified rule and exact path. The presence of a directory alone is not proof of selection.
|
|
54
57
|
|
|
@@ -69,7 +72,7 @@ npm list -g @mblua/agentscommander --depth=0
|
|
|
69
72
|
agentscommander --help
|
|
70
73
|
```
|
|
71
74
|
|
|
72
|
-
Both commands must exit 0. Confirm that `npm list` and the installed `package.json` report the approved package version; re-check the installed scripts, native path, and checksum correlation described above. `--help` must print the AgentsCommander command help. The npm package is `@mblua/agentscommander`; the installed command is `agentscommander`.
|
|
75
|
+
Both commands must exit 0. Confirm that `npm list` and the installed `package.json` report the approved package version; re-check the installed scripts, native path, and checksum correlation described above. `--help` must print the AgentsCommander command help, and on `0.31.0` or newer `agentscommander --version` must print the same version `npm list` reports. The npm package is `@mblua/agentscommander`; the installed command is `agentscommander`.
|
|
73
76
|
|
|
74
77
|
## Uninstall
|
|
75
78
|
|
package/install.js
CHANGED
|
@@ -5,7 +5,7 @@ const crypto = require('crypto');
|
|
|
5
5
|
const os = require('os');
|
|
6
6
|
const { execSync } = require('child_process');
|
|
7
7
|
|
|
8
|
-
const VERSION = "0.
|
|
8
|
+
const VERSION = "0.31.0"; // Must match package.json
|
|
9
9
|
const OWNER = 'mblua';
|
|
10
10
|
const REPO = 'AgentsCommander';
|
|
11
11
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@mblua/agentscommander",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.31.0",
|
|
4
4
|
"description": "Install and run AgentsCommander, the local terminal session manager for AI coding agent teams with Claude Code, Codex, Hermes, Cursor CLI, OpenCode, and more to come.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"bin": {
|