@mblua/agentscommander 0.30.5 → 0.32.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.
Files changed (3) hide show
  1. package/README.md +7 -8
  2. package/install.js +1 -1
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -35,20 +35,19 @@ 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. Do not probe the native binary for a self-reported version unless its exact tag proves support; `v0.30.3` and `main` at this documentation commit do not support such a flag.
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.30.3`
42
+ ### npm `0.32.0`
43
43
 
44
- The published `0.30.3` install script downloads the `v0.30.3` native release asset, and its launcher only spawns that binary from the package's `bin/` directory. It injects no configuration override. The native resolver:
44
+ `0.32.0` is the release described by this package. Its installer downloads the `v0.32.0` native release asset, verifies it against `SHASUMS256.txt`, and renames it to the unsuffixed executable in the package's `bin/` directory. The launcher spawns that binary and injects no configuration override.
45
45
 
46
- 1. immediately selects `<native-executable-folder>/.<native-executable-stem>` when the executable path has a parent and file stem; and
47
- 2. uses `$HOME/.agentscommander-new` only when that parent and stem cannot be derived.
46
+ The `v0.32.0` native resolver selects a non-blank `AGENTSCOMMANDER_CONFIG_DIR` value verbatim when present. Otherwise, the normal unsuffixed npm executable selects the user's home directory plus `.agentscommander`, independently of its install location and build profile. It does not inspect an adjacent `portable.txt` marker or probe an adjacent configuration directory on this route. Suffixed executables retain their separate instance-location rules.
48
47
 
49
- Release `v0.30.3` does not read `AGENTSCOMMANDER_CONFIG_DIR`, inspect `portable.txt`, probe candidate writability, or fall back to home because the adjacent path is read-only. For a normal npm `0.30.3` install, the selected directory is therefore `.agentscommander` beside the native executable under `@mblua/agentscommander/bin/`.
48
+ **This changes the default location from npm `0.31.0` and `0.30.5`.** Those versions normally selected `.agentscommander` beside the native executable under `@mblua/agentscommander/bin/` when that location was writable, with their documented home fallback and refusal rules. Version `0.32.0` does not discover, copy, move or migrate any old configuration automatically. Before updating, identify and back up the old version's active configuration. If you intend to keep using that directory, set `AGENTSCOMMANDER_CONFIG_DIR` to its verified path; otherwise arrange the intended configuration at the new home location separately.
50
49
 
51
- The public override, marker, write probes, and conclusively-unwritable home fallback documented for the newer resolver are present on `main` but unpublished in `0.30.3`. Apply them only to a development build from matching source, or to a later npm version after verifying that version's exact release tag and package launcher. 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 tag; do not extrapolate either `v0.30.3` or `main` and do not invent a cutoff version.
50
+ The older npm `0.30.3` resolver immediately selected an executable-adjacent directory when the parent and stem were available and did not support the configuration override or portable-marker/write-probe rules. npm never published `0.30.4`; that number exists only as a GitHub release. For other versions, inspect `src-tauri/src/config/mod.rs`, `src-tauri/src/config/profile.rs`, `npm/run.js`, and `npm/install.js` at the exact `v<version>` tag.
52
51
 
53
52
  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
53
 
@@ -69,7 +68,7 @@ npm list -g @mblua/agentscommander --depth=0
69
68
  agentscommander --help
70
69
  ```
71
70
 
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`.
71
+ 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
72
 
74
73
  ## Uninstall
75
74
 
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.30.5"; // Must match package.json
8
+ const VERSION = "0.32.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.30.5",
3
+ "version": "0.32.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": {