@tuned-tensor/cli 0.18.0 → 0.20.0

package/dist/local-runtime.js

@@ -88,7 +88,7 @@ import {
   withHuggingFaceCacheEnvironment,
   withOfflineHuggingFaceCacheEnvironment,
   writePrivateJsonAtomic
-} from "./chunk-U5HNS367.js";
+} from "./chunk-4Q54NHKR.js";
 
 // src/local-runtime/index.ts
 import { readFileSync as readFileSync3, realpathSync } from "fs";

package/docs/local-runtime/foundation-long-runs.md

@@ -4,8 +4,8 @@ The foundation engine can run recoverable, single-GPU pretraining from `.txt`
 files or JSONL shards whose rows contain a string `text` field. Keep training
 and validation data in different files or directories.
 
-The commands below also support an [AWS GPU](aws-gpu.md) configured in the
-adjacent `local-runner.json`. The CLI and tokenizer still run locally; the
+The commands below also support an [AWS GPU](aws-gpu.md) configured as
+`runtime.gpu` in `tunedtensor.json`. The CLI and tokenizer still run locally; the
 local machine must stay awake and connected throughout the pipeline.
 
 ## Spec

package/docs/local-runtime/serving.md

@@ -13,7 +13,7 @@ not mutate the training runtime.
   serving is not supported by this runtime; CLI/package commands still work
   there. Unsupported hardware or model/adapter combinations fail rather than
   silently falling back to the old server.
-- `gpu` in `local-runner.json` applies to training and evaluation. It does not
+- `runtime.gpu` in `tunedtensor.json` applies to training and evaluation. It does not
   move `tt serve` to AWS; returned artifacts still need a Linux/CUDA machine
   running the serving command.
 - Install `uv` and prefetch the certified model with `tt models prefetch`.

package/docs/spec-architecture.html

@@ -234,7 +234,7 @@
     "summary": "Validate the proposed document and bind it to the current file and workspace before approval.",
     "input": "Field changes + the hash returned by get_local_spec.",
     "output": "After /approve: atomic spec replacement and a before/after revision record.",
-    "boundary": "Stale edits fail. Arrays replace fields; foundation and hyperparameters merge by key. Secure edits currently require Linux.",
+    "boundary": "Stale edits fail. add_examples appends; other arrays replace fields; foundation and hyperparameters merge by key. Secure edits currently require Linux.",
     "flow": [
       "prepareSpecUpdate",
       "diff",

package/docs/spec-workflow.md

@@ -37,24 +37,29 @@ for an invalid spec.
 
 ```text
 › Keep my training settings, but require a single lowercase sentiment label.
-  [agent reads the spec and proposes a diff]
-› /spec diff
-› /approve
+  [agent reads the spec and shows the proposed diff]
+  ? Save this spec edit? y yes · n no · esc decide later
 › /spec
 › /spec history
 ```
 
 `get_local_spec` returns the document, validation diagnostics and content hash.
 `prepare_update_local_spec` requires that hash and a patch of supported fields.
-Arrays replace their whole field; `hyperparameters` and `foundation` merge by
+`add_examples` appends examples without resending existing ones; other arrays
+replace their whole field, and the diff lists only removed and added items.
+`hyperparameters` and `foundation` merge by
 key. `runtime` and `evaluation` merge recursively; null removes optional settings.
 `pipeline` replaces the entire recipe (null restores the derived default). Unmentioned fields remain unchanged. Identity and engine cannot change
-through this edit tool. The full resulting document must pass the runtime's
+through this edit tool. An adapter spec without an `id` gets one on its first
+edit, pinned to the ID its earlier runs used, so later edits keep the same run
+identity and evaluation split. Specs created by the agent start with an `id`. The full resulting document must pass the runtime's
 strict schema, readiness checks, nonblank content checks and distinct-example
 checks. Small example sets produce a warning; validation is not a claim of model
 quality or GPU readiness.
 
-Proposing an edit does not write anything. `/approve` revalidates the workspace,
+Proposing an edit does not write anything. tt asks for a decision right after the
+answer; pressing `Esc` leaves the edit pending, and `/spec diff` then shows it again
+until you run `/approve` or `/reject`. Approval revalidates the workspace,
 parent directory, current file bytes and proposed result, acquires the spec's
 writer lock and atomically replaces the file. `/reject` leaves it unchanged.
 If the file changes after review, prepare a fresh edit. A saved edit invalidates

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tuned-tensor/cli",
-  "version": "0.18.0",
+  "version": "0.20.0",
   "description": "Local TT agent and CUDA fine-tuning CLI for Tuned Tensor workflows",
   "repository": {
     "type": "git",