@remnic/cli 9.69.38 → 9.69.40
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 +5 -1
- package/dist/index.js +9284 -9079
- package/package.json +32 -32
package/README.md
CHANGED
|
@@ -91,7 +91,11 @@ 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
92
|
full runs need a real benchmark dataset. The CLI resolves
|
|
93
93
|
`~/.remnic/bench/datasets/<benchmark>` automatically in both repo checkouts and packaged installs; alternatively pass
|
|
94
|
-
`--dataset-dir <path>` explicitly.
|
|
94
|
+
`--dataset-dir <path>` explicitly. If a dataset is missing from the canonical
|
|
95
|
+
store but still present at the legacy `evals/datasets/<benchmark>` location,
|
|
96
|
+
the CLI uses it read-only and prints a once-per-process hint to re-download
|
|
97
|
+
with `remnic bench datasets download <benchmark>` — nothing is moved or
|
|
98
|
+
linked automatically.
|
|
95
99
|
|
|
96
100
|
Package-backed benchmark runs also write `MANIFEST.json` in the results
|
|
97
101
|
directory. The manifest records result artifact hashes, dataset file hashes,
|