syntaqxThe runner guides cover g1t-runner 0.3.5's needs and the desktop app's Set up in full (#52). Self-hosted runners gets "What the sandbox needs": run `g1t-runner sandbox status` first, since it downloads nothing; a sample of what it prints; a row for each need it names (windows_update, virtualization, nested_virtualization, vm_platform, wsl, wsl_update, windows_edition, windows_sandbox, restart, kvm_module, kvm_group, qemu, macos_update, homebrew, vfkit) with its kind of job and the fix; that each is named only when the computer says it for certain, and Windows' facts are kept per boot; and that `sandbox up` stops before downloading the image when Linux jobs lack something, leaving out Windows jobs unless named with --only. Its JSON sample and field table gain `needs`, with the current cause and fix wording, and the troubleshooting rows and the desktop app section point at the new section.fcc5171History
- ..
- about.rs
- activity.rs
- addresses.rs
- alerts.rs
- archives.rs
- audit.rs
- billing.rs
- blobs.rs
- broker.rs
- caches.rs
- checks.rs
- commits.rs
- contents.rs
- coordination.rs
- deploy_keys.rs
- deployments.rs
- folios.rs
- follow.rs
- lib.rs
- limits.rs
- logs.rs
- mcp.rs
- notifications.rs
- oauth.rs
- oidc.rs
- onboarding.rs
- openapi.rs
- operations.rs
- packages.rs
- people.rs
- pins.rs
- projects.rs
- protection.rs
- reference.json
- renamed.rs
- responses.rs
- rest.rs
- rules.rs
- run_artifacts.rs
- runners.rs
- security.rs
- telemetry.rs
- token_policy.rs
- toolkit.rs
- tools.rs
- why.rs