build-windows-tray

Builds, installs, and verifies the Windows tray release binary with daily findings reports.

5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/8007342/tillandsias --skill build-windows-tray-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-windows-tray
Source: https://github.com/8007342/tillandsias/tree/main/skills/build-windows-tray
Command: npx skills add https://github.com/8007342/tillandsias --skill build-windows-tray-8007342

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running the daily build-and-install loop for the Tillandsias Windows tray binary requires many error-prone manual steps on the actual Windows host, including staging the embedded Linux guest binary, handling PowerShell quirks, and verifying the install with --diagnose. This Skill codifies the exact known-working workflow so it runs consistently on every daily iteration. ## Core Features & Use Cases - Deterministic build pipeline: Syncs the windows-next branch, stages the embedded Linux guest binary, and runs the release build via scripts/build-windows-tray.ps1 or direct cargo invocation. - Safe install and verification: Stops the running tray, installs to %LOCALAPPDATA%\Programs\Tillandsias, and runs the --diagnose --json post-install check with exit-code interpretation (0 healthy, 2 degraded, 1 failure). - Cross-host findings ledger: Appends structured per-run sections to plan/issues/windows-build-findings-YYYY-MM-DD.md so sibling hosts can grep SECTION_KIND to see whether the Windows build is green. - Use Case: A scheduled daily loop fires on the Windows host, fast-forwards the branch, rebuilds the tray with a freshly staged guest binary, installs it, verifies the 16-key diagnose schema, and commits a findings report flagging any regression. ## Quick Start Run the build-windows-tray workflow to sync the windows-next branch, build and install the tray binary, verify it with --diagnose, and record today's findings file.

Frequently Asked Questions about build-windows-tray

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build and install the Tillandsias Windows tray binary?▼

Run scripts/build-windows-tray.ps1 for the release build, then scripts/install-windows.ps1 to copy the binary to %LOCALAPPDATA%\Programs\Tillandsias, create shortcuts, and run post-install verification. Direct cargo build -p tillandsias-windows-tray --release also works for ad-hoc builds.

Why does the installed Windows tray fail to inject the Linux guest?▼

The tray embeds the guest binary via include_bytes! from crates/tillandsias-windows-tray/assets, and a fresh checkout contains a zero-byte placeholder. Stage a real musl build into that path and touch a .rs file before rebuilding, since cargo does not rebuild on asset-only changes.

What do the --diagnose exit codes mean for the Windows tray?▼

Exit code 0 means fully healthy with the distro registered and wire reachable, 2 means degraded such as an idled or unprovisioned VM, and 1 means a hard failure requiring escalation. Always capture output via cmd /c redirect because PowerShell drops large stdout writes from the GUI-subsystem binary.

Why does Copy-Item fail when installing over a running tray?▼

Windows can hold the .exe file handle briefly after the process exits, causing an IOException. Stop the tillandsias-tray process and wait about 2 seconds before copying the new binary with -Force.

Can this build workflow run on a non-Windows host or in the cloud?▼

No, the cargo build and install steps must run on the actual Windows host because they drive wsl.exe and write to %LOCALAPPDATA%. Cloud schedulers cannot perform these steps, which is why the skill targets a local daily loop.