[2/3] Torch installation flow, package validation, and progress

.github/workflows/build.yml

@@ -259,6 +259,8 @@ jobs:
       - name: Build native RPC for Torch acceptance
         run: cargo build --locked --manifest-path rust/Cargo.toml -p pumas-rpc
       - name: Accept v2.14 CPU/Core via native RPC (${{ runner.os }})
+        env:
+          PUMAS_RELEASE_API_TOKEN: ${{ github.token }}
         run: python scripts/release/torch-managed-python-acceptance.py rust/target/debug --evidence-dir torch-native-evidence
       - name: Upload native Torch acceptance evidence
         if: always()

docs/plans/torch-cross-platform-runtime-management/reports/v2.14.0-linux-appimage-cu132-ui-acceptance/README.md

@@ -0,0 +1,56 @@
+# Torch 2.14.0 Linux AppImage UI progress acceptance
+
+**Status:** Pass for the local Linux x86_64 v0.7.0 AppImage install flow.
+This evidence covers the packaged Electron UI and its bundled backend. It does
+not qualify GPU execution, image generation, or packaged Windows/macOS use.
+
+The acceptance used the normal Torch release browser and review controls in the
+rebuilt AppImage, with an isolated Pumas library root and separate XDG profile.
+The window viewport was 800×1000. The previous v2.14.0 test runtime was removed
+through the UI before repeating the install. The reviewed preset was cu132,
+Python selected automatically, and Core runtime only; the preview reported 44
+exact official artifacts with hashes.
+
+| Claim | Result |
+| --- | --- |
+| Packaged artifact | Local `Pumas.Library-0.7.0.AppImage`; SHA-256 `a28f302822ce99a9d687797606574c93a5afb9c184f293526b16b972294a670b` |
+| Companion package | Local `pumas-library-electron_0.7.0_amd64.deb`; SHA-256 `d8effc33ba37466171c5fae0178e2555064850e40544c93249966fedbf4bce88` |
+| Target and runtime selection | Linux x86_64; Torch `v2.14.0`, cu132; Python selected automatically; 44 exact hashed artifacts resolved |
+| First sampled install state | At 9 seconds elapsed, header read `Installing Torch v2.14.0 · Installing resolved wheel artifacts`; dialog showed `Working…`, `Final Setup · In progress`, and `Cancel` |
+| Progress semantics | Overall and setup bars had no `aria-valuenow`; no 95% value was shown while setup progress was unmeasured |
+| Cancel affordance | Visible with accessible name `Cancel current installation`; cancellation was not triggered in this completion run |
+| Terminal state | `1 installed`; v2.14.0 row showed `Installed cu132 · python3.14 · none · unverified` and `Ready` |
+| Installed interpreter and CPU operation | Managed CPython `3.14.7`; Torch `2.14.0+cu132`; CPU tensor sum returned `5`; CUDA unavailable on this host |
+| Package smoke | Artifact naming/resource checks passed; both extracted package backends passed `/health` |
+| Isolation | Test used a workspace-owned launcher root; resolver scratch was removed; the pre-test host pip-cache snapshot was unchanged |
+
+The install used the isolated library's existing package cache. This run
+records activity feedback at the first sampled UI state (9 seconds elapsed),
+indeterminate setup presentation, and the terminal UI state without claiming a
+cold-cache download-speed sample. Focused source tests separately verify the
+pending-install state before the first progress poll. The full frontend test
+suite and typecheck passed for the reviewed progress behavior.
+
+The exact machine-readable result is [acceptance.json](acceptance.json). This is
+a local candidate only and was not uploaded to the toolbar-linked public
+release. The successful CPU tensor operation does not qualify CUDA device use,
+Tuldok image generation, or Windows/macOS packaged installation.
+
+## 2026-09-26 interaction and readability follow-up
+
+The rebuilt local v0.7.0 AppImage (`34a5ffc88f5f42aa03bd9ed72ead37e5ca385838037247b74186a67d9d128aaf`)
+was opened at the same 800×1000 viewport. Browser-level pointer input on the
+Torch v2.14.0 Install row showed the green hover state, darker pressed state,
+and scale response. The review heading and Install text rendered white; the
+Install action explained why it remains disabled until the artifact check
+finishes. Clicking Check showed an animated status immediately:
+“Checking official Torch artifacts… Package files may download to Pumas’
+private cache.” The footer changed to the checking explanation at the same
+time. Frontend tests also verify the header and dialog announce
+“Installing Torch v2.14.0 · Starting installation…” before the first backend
+progress response, with a visible Cancel action.
+
+This follow-up verifies interaction feedback and text contrast in the rebuilt
+package. It did not complete a new artifact preview or Torch installation; the
+successful runtime installation above remains tied to the AppImage hash in
+`acceptance.json`. See the exact [follow-up evidence](ui-interaction-follow-up.json).

docs/plans/torch-cross-platform-runtime-management/reports/v2.14.0-linux-appimage-cu132-ui-acceptance/acceptance.json

@@ -0,0 +1,59 @@
+{
+  "success": true,
+  "evidence_kind": "user-workflow",
+  "environment": "representative-linux-x86_64",
+  "execution_mode": "manual-real-ui",
+  "application_version": "0.7.0",
+  "application_artifacts": {
+    "appimage": {
+      "name": "Pumas.Library-0.7.0.AppImage",
+      "sha256": "a28f302822ce99a9d687797606574c93a5afb9c184f293526b16b972294a670b"
+    },
+    "deb": {
+      "name": "pumas-library-electron_0.7.0_amd64.deb",
+      "sha256": "d8effc33ba37466171c5fae0178e2555064850e40544c93249966fedbf4bce88"
+    }
+  },
+  "viewport": {
+    "width": 800,
+    "height": 1000
+  },
+  "runtime": {
+    "release": "v2.14.0",
+    "build": "cu132",
+    "python_selection": "automatic",
+    "managed_cpython": "3.14.7",
+    "torch_version": "2.14.0+cu132",
+    "resolved_hashed_artifact_count": 44,
+    "terminal_state": "Ready",
+    "cpu_tensor_sum": 5,
+    "cuda_available": false
+  },
+  "progress_observation": {
+    "elapsed_seconds": 9,
+    "header": "Installing Torch v2.14.0 · Installing resolved wheel artifacts",
+    "phase": "Installing resolved wheel artifacts",
+    "setup_state": "indeterminate",
+    "cancel_visible": true,
+    "cancel_accessible_name": "Cancel current installation",
+    "cancel_triggered": false,
+    "aria_valuenow_present": false,
+    "false_95_percent_displayed": false
+  },
+  "isolation": {
+    "launcher_root": "task-owned isolated test root",
+    "host_pip_cache_unchanged": true,
+    "resolver_scratch_removed": true,
+    "package_cache_state": "warm"
+  },
+  "package_smoke": {
+    "artifact_names_and_resource_hashes": "passed",
+    "appimage_rpc_health": "passed",
+    "deb_rpc_health": "passed"
+  },
+  "limits": [
+    "This local AppImage result does not update the public toolbar-linked release.",
+    "CUDA/device execution, Windows/macOS packaged installation, and v2.14.0 Tuldok image generation were not tested.",
+    "The runtime cache was warm, so the report makes no cold-cache download-progress claim."
+  ]
+}

docs/plans/torch-cross-platform-runtime-management/reports/v2.14.0-linux-appimage-cu132-ui-acceptance/ui-interaction-follow-up.json

@@ -0,0 +1,73 @@
+{
+  "status": "passed_ui_feedback_only",
+  "date": "2026-09-26",
+  "environment": "Linux x86_64 local AppImage with an isolated Pumas library profile",
+  "execution_mode": "manual-packaged-ui",
+  "application_version": "0.7.0",
+  "application_artifacts": {
+    "appimage": {
+      "name": "Pumas.Library-0.7.0.AppImage",
+      "sha256": "34a5ffc88f5f42aa03bd9ed72ead37e5ca385838037247b74186a67d9d128aaf"
+    },
+    "deb": {
+      "name": "pumas-library-electron_0.7.0_amd64.deb",
+      "sha256": "fea54b4694d7ddb77a797327a9e15d0f0e66e0cf4f2d38fc9169feb4a4811386"
+    }
+  },
+  "viewport": {
+    "width": 800,
+    "height": 1000
+  },
+  "observations": {
+    "install_row": {
+      "label": "Install",
+      "hover": {
+        "foreground": "rgb(82, 255, 82)",
+        "background": "rgb(38, 38, 38)",
+        "border": "rgb(82, 255, 82)",
+        "transform": "scale(1.05)"
+      },
+      "pressed": {
+        "active": true,
+        "foreground": "rgb(82, 255, 82)",
+        "background": "rgb(29, 29, 29)"
+      }
+    },
+    "review": {
+      "heading_foreground": "rgb(255, 255, 255)",
+      "body_foreground": "rgb(255, 255, 255)",
+      "install_cta_foreground": "rgb(255, 255, 255)",
+      "install_cta_background": "rgba(82, 255, 82, 0.14)",
+      "install_cta_disabled_before_artifact_review": true,
+      "install_cta_explanation": "Check the selected combination to review its artifacts and enable installation."
+    },
+    "artifact_check": {
+      "hover_background": "rgba(82, 255, 82, 0.12)",
+      "pressed_background": "rgba(82, 255, 82, 0.157)",
+      "first_paint_status": "Checking official Torch artifacts… Package files may download to Pumas’ private cache.",
+      "button_label": "Checking…",
+      "install_cta_explanation": "Checking the selected combination before installation."
+    },
+    "install_status": {
+      "header_and_dialog_status": "Installing Torch v2.14.0 · Starting installation…",
+      "packaged_header_foreground": "rgb(255, 255, 255)",
+      "packaged_header_font_size": "12px",
+      "verified_by": [
+        "Header.test.tsx pending Torch status coverage",
+        "InstallDialogContent.test.tsx pre-progress status and Cancel coverage"
+      ]
+    }
+  },
+  "verification": {
+    "focused_frontend_tests": "60 passed",
+    "frontend_typecheck": "passed",
+    "scoped_eslint": "passed",
+    "linux_artifact_contract": "passed",
+    "appimage_and_deb_rpc_smoke": "passed"
+  },
+  "limits": [
+    "This follow-up confirms interaction feedback and text contrast; it did not complete a new artifact preview or Torch installation.",
+    "The prior successful Torch installation remains recorded separately in acceptance.json and applies to the AppImage SHA recorded there.",
+    "CUDA/device execution, Windows/macOS packaged installation, and Tuldok image generation were not tested."
+  ]
+}