@tuned-tensor/cli 0.27.0 → 0.28.0

package/dist/{prefetch-B6I7B4LR.js → prefetch-LBIOO7ZO.js}

@@ -6,7 +6,7 @@ import {
   safeName,
   verifyLocalBaseModel,
   verifyModelPrefetchCacheReport
-} from "./chunk-2AIP63QO.js";
+} from "./chunk-FSVTMX4L.js";
 export {
   buildModelPrefetchPayload,
   buildModelSourcePrefetchPayload,
@@ -15,4 +15,4 @@ export {
   verifyLocalBaseModel,
   verifyModelPrefetchCacheReport
 };
-//# sourceMappingURL=prefetch-B6I7B4LR.js.map
+//# sourceMappingURL=prefetch-LBIOO7ZO.js.map

package/docs/windows.md

@@ -0,0 +1,151 @@
+# Windows and PowerShell
+
+The CLI runs natively in Windows PowerShell 5.1 and PowerShell 7. Windows x64
+setup includes a private Node.js runtime, installs for the current user without
+administrator access, and adds `tt` to the user PATH. It does not change your
+PowerShell execution policy or your system Node.js installation.
+
+## Install
+
+Until the first Windows release and WinGet catalog submission are published,
+use the npm route below. Merging CLI changes alone does not publish a package.
+
+For a release with Windows assets, download and run
+`tuned-tensor-cli-<version>-windows-x64.exe` from the
+[GitHub releases](https://github.com/tunedtensor/tuned-tensor-cli/releases).
+Open a new terminal and run:
+
+```powershell
+tt --version
+tt
+```
+
+An inspectable PowerShell installer is available in
+[`scripts/install.ps1`](../scripts/install.ps1). Download it, inspect it, and
+execute it with a policy permitted by your organization. It downloads the
+release installer, checks its SHA-256 against the release checksum, and runs
+setup. `-Version 0.27.0` (example) or `$env:TT_VERSION` pins an exact release;
+the default is the latest stable release. It fails if that release has no
+Windows asset. The standalone installer currently supports x64 only.
+
+After `TunedTensor.CLI` is accepted into the public WinGet catalog:
+
+```powershell
+winget install --id TunedTensor.CLI --exact --source winget
+# Open a new PowerShell window after installation.
+tt --version
+winget upgrade --id TunedTensor.CLI --exact --source winget
+winget uninstall --id TunedTensor.CLI --exact
+```
+
+The first catalog submission requires a published stable installer; these
+commands are not available just because this repository contains manifests.
+Setup can also be updated by running a newer installer, and removed through
+Windows **Installed apps**. Close running TT sessions before updating.
+`tt upgrade` detects setup-managed installs and shows the appropriate instructions.
+Uninstall removes the application's PATH entry and managed files, preserving
+`~/.tuned-tensor` and project data.
+
+## npm installation, including Windows ARM64
+
+With Node.js 22.19.0 or newer already installed:
+
+```powershell
+npm.cmd install -g --ignore-scripts @tuned-tensor/cli
+tt.cmd --version
+tt.cmd
+tt.cmd upgrade
+```
+
+You can install Node.js through WinGet first:
+
+```powershell
+winget install --id OpenJS.NodeJS.LTS --exact --source winget
+# Open a new terminal so Node and npm are on PATH, then run the npm commands above.
+```
+
+Use `npm.cmd` and `tt.cmd` explicitly when PowerShell blocks npm's generated
+`.ps1` launchers. No execution-policy change is needed. The standalone setup
+ships only `tt.cmd`, so plain `tt` works there even with Restricted policy.
+`TT` also works because Windows command lookup is case-insensitive.
+
+For npm installs, uninstall with `npm.cmd uninstall -g @tuned-tensor/cli`.
+If you selected a custom npm `--prefix`, supply the same prefix on uninstall
+and add that directory itself (not a `bin` subdirectory) to your user PATH.
+Use an install prefix without `&`: npm's generated `tt.cmd` launcher can fail
+when that character appears in its directory, including in a Windows username.
+If affected, select an accessible prefix such as `C:\TunedTensor` and add it
+to your user PATH. Quoted paths containing spaces work.
+`tt upgrade` finds the prefix of the running installation automatically.
+Use `Get-Command tt -All` to find older installations if the wrong version runs.
+
+## Native CLI scope
+
+Account commands, the conversational interface, hardware discovery, spec
+inspection, data commands, and pipeline previews run from PowerShell. Environment
+variables use PowerShell syntax, for example `$env:TT_NO_UPDATE_CHECK = '1'`.
+Use Windows paths and quotes around paths containing spaces.
+Inside TT's conversational terminal, backslashes stay literal on Windows:
+`/cd "C:\work files"` and `spec view .\tunedtensor.json` work as expected.
+
+Agent-approved spec creation, editing and revision history also work on Windows.
+TT pins real workspace directories while applying the reviewed changes. These
+operations require the built-in Windows PowerShell host with .NET interop allowed;
+an organizational policy that blocks it causes TT to refuse the write. No global
+execution-policy change is made. `tt init`, your editor, `tt spec view` and
+`tt pipeline run --dry-run` remain available for manual workflows.
+
+Some runtime features have narrower platform requirements:
+
+- Native Windows x64 decision training is not yet end-to-end certified; Windows
+  ARM64 lacks compatible wheels in the current Python lockfiles. The packaged
+  LLM training/serving stack still requires a supported Linux/CUDA environment.
+- AWS GPU transport uses local rsync and POSIX path conventions. Run that
+  workflow, including background training and cancellation, inside WSL2/Linux.
+  A native Windows install does not provide those tools or certify that workflow.
+
+See the platform table in the [README](../README.md) and the
+[AWS guide](local-runtime/aws-gpu.md) for training prerequisites.
+
+## Release and WinGet maintenance
+
+`scripts/build-windows.ps1` builds the CLI, packs and installs the npm artifact
+with `--ignore-scripts`, includes the build's Node 22 x64 runtime and its license,
+and compiles an Inno Setup 7 installer. Run it on Windows with Node/npm and
+Inno Setup 7 installed (or supply `-CompilerPath`). Version 7 is required for
+[extended-length dependency paths](https://jrsoftware.org/files/is7-whatsnew.htm).
+CI downloads a pinned compiler and verifies its SHA-256. Outputs are under
+`windows-dist/`.
+
+The Windows CI job runs on PRs and gates npm releases. It tests the built
+installer in PowerShell 5.1 and 7: repeated install, private runtime without
+system Node on PATH, CLI inspection and dry-run, upgrade ownership, and uninstall
+with unrelated PATH entries and user data preserved. It also exercises npm
+global installation, including actual status, spec inspection, hardware discovery
+and pipeline previews in both shells. A native Windows ARM64 job checks the npm
+route, architecture rejection in the x64 downloader, and the same CLI regressions.
+The complete CLI suite runs on both Windows architectures, including the real
+agent loop with scripted provider responses, approved spec writes, resume,
+dataset splitting, CLI handoff and cancellation. POSIX rsync transport fixtures
+run in Linux/WSL; file-symlink fixtures require Developer Mode or the relevant
+Windows privilege. Directory junction refusal is tested without that privilege.
+This is CLI/distribution coverage, not a real model-training
+certification.
+
+The release workflow attaches the tested `.exe`, `.exe.sha256`, and, for stable
+versions, `winget-manifests.zip` to the same GitHub release after npm publication.
+The manifests contain the actual installer hash and versioned release URL.
+Prereleases never generate stable WinGet manifests.
+
+For each stable release:
+
+1. Download and extract `winget-manifests.zip` from the release.
+2. Run `winget validate --manifest .\manifests\t\TunedTensor\CLI\<version>`.
+3. Follow Microsoft's [sandbox test and submission procedure](https://learn.microsoft.com/en-us/windows/package-manager/package/repository)
+   to test the published installer and submit that directory to `microsoft/winget-pkgs`.
+4. Wait for the catalog PR to be accepted before announcing WinGet availability.
+
+No catalog PR is opened by the release workflow. Keep the installer AppId and
+manifest ProductCode stable so upgrades and uninstall identify the same app.
+Release assets must remain immutable; regenerate checksums/manifests after any
+signing step if signing is added to the release process.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tuned-tensor/cli",
-  "version": "0.27.0",
+  "version": "0.28.0",
   "description": "Local TT agent and CUDA fine-tuning CLI for Tuned Tensor workflows",
   "repository": {
     "type": "git",
@@ -16,6 +16,7 @@
     "typecheck": "tsc --noEmit && tsc --noEmit -p tsconfig.scripts.json",
     "test": "npm run test:cli && npm run test:local-runtime && npm run test:python",
     "test:cli": "vitest run",
+    "test:windows": "npm run test:cli && npm run test:local-runtime",
     "test:workflows": "vitest run src/__tests__/workflows",
     "eval:agent": "tsx scripts/eval-agent.ts",
     "test:local-runtime": "node --import tsx --test \"test/local-runtime/**/*.test.ts\"",
@@ -38,6 +39,7 @@
     "training/decision/src/*.py",
     "docs/local-runtime",
     "docs/spec-workflow.md",
+    "docs/windows.md",
     "docs/spec-architecture.html",
     "examples/local-runtime/*.json",
     "examples/local-runtime/*.jsonl",