1dfa31ad04
The probe left studio_install_ok=absent undecided and judged those installs on whether the backend booted. preflight/managed.rs:445 tests studio_install_ok != Some(true), so an absent field is Stale exactly like a false one; a CLI too old to carry it is already rejected one check earlier on desktop_manageability_version. The gap mattered in both directions: a payload that stopped carrying the field reported HEALTHY on every booting leg and skipped the re-run assertion this workflow exists to make, and a torn venv with a working -h was failed as FALSE_READY even though the app would have offered repair. unsloth_cli/commands/studio.py is in this workflow's path filter precisely to catch that class of change, so it must not be the thing that silences it. The verdict also consulted cli_h_ok only in the repairable arm, so a CLI that cannot print help was called HEALTHY whenever the backend happened to boot. probe_managed_bin runs -h first and returns Stale cli_unusable before it ever reaches the capability probe (managed.rs:465-478), so that install goes to repair in the real app and the leg must assert it here. |
||
|---|---|---|
| .. | ||
| agent-guides-drive.sh | ||
| agent-guides-install.sh | ||
| assert-llama-loads.sh | ||
| assert-prompt-cache.sh | ||
| ci-connect-prompt.txt | ||
| ci-min-system-prompt.txt | ||
| hf-download-with-retry.sh | ||
| interrupt-install.ps1 | ||
| interrupt-install.sh | ||
| interrupted_install_probe.py | ||
| run-studio-permission-browser.sh | ||
| serve-unsloth-run.sh | ||