@remnic/cli 9.69.33 → 9.69.35

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 CHANGED
@@ -89,8 +89,8 @@ remnic benchmark run --quick longmemeval
89
89
  `--quick` uses the lightweight benchmark path with a single-item limit so you can
90
90
  smoke-test the harness without running a full benchmark pass. When a benchmark
91
91
  ships a bundled smoke fixture, `--quick` uses that tracked fixture by default;
92
- full runs need a real benchmark dataset. In a repo checkout the CLI will use
93
- `evals/datasets/<benchmark>` automatically; in packaged installs pass
92
+ full runs need a real benchmark dataset. The CLI resolves
93
+ `~/.remnic/bench/datasets/<benchmark>` automatically in both repo checkouts and packaged installs; alternatively pass
94
94
  `--dataset-dir <path>` explicitly.
95
95
 
96
96
  Package-backed benchmark runs also write `MANIFEST.json` in the results
@@ -1,11 +1,10 @@
1
1
  #!/usr/bin/env bash
2
2
  set -euo pipefail
3
3
 
4
- SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
5
- # Honor an explicit DATASETS_DIR from the environment so packaged CLI
6
- # installs can route downloads to a user-writable location (e.g.
7
- # ~/.remnic/bench/datasets) instead of a sibling of the script dir.
8
- DATASETS_DIR="${DATASETS_DIR:-$(cd "$SCRIPT_DIR/.." && pwd)/datasets}"
4
+ # Canonical dataset store is ~/.remnic/bench/datasets for every install
5
+ # mode (repo checkout and packaged CLI alike issue #2798). An explicit
6
+ # DATASETS_DIR from the environment still wins.
7
+ DATASETS_DIR="${DATASETS_DIR:-$HOME/.remnic/bench/datasets}"
9
8
 
10
9
  usage() {
11
10
  echo "Usage: $0 [--benchmark <name>]"
@@ -1,11 +1,10 @@
1
1
  #!/usr/bin/env bash
2
2
  set -euo pipefail
3
3
 
4
- SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
5
- # Honor an explicit DATASETS_DIR from the environment so packaged CLI
6
- # installs can route downloads to a user-writable location (e.g.
7
- # ~/.remnic/bench/datasets) instead of a sibling of the script dir.
8
- DATASETS_DIR="${DATASETS_DIR:-$(cd "$SCRIPT_DIR/.." && pwd)/datasets}"
4
+ # Canonical dataset store is ~/.remnic/bench/datasets for every install
5
+ # mode (repo checkout and packaged CLI alike issue #2798). An explicit
6
+ # DATASETS_DIR from the environment still wins.
7
+ DATASETS_DIR="${DATASETS_DIR:-$HOME/.remnic/bench/datasets}"
9
8
 
10
9
  usage() {
11
10
  echo "Usage: $0 [--benchmark <name>]"