What problem does it solve? Running a full macOS build of the tillandsias tray app manually is error-prone and leaves no shared record, so sibling Linux and Windows hosts cannot tell whether the macOS build is green or what regressed. ## Core Features & Use Cases - Full build cycle: Runs scripts/build-macos-tray.sh, verifies the binary embeds the current HEAD git SHA, and checks codesign and tarball artifacts. - Autonomous smoke testing: Launches the tray binary detached, validates --diagnose --json exit codes, and tests clean SIGTERM shutdown without user clicks, including a minimal-PATH LaunchServices simulation. - Structured findings log: Appends a greppable section per run to plan/issues/macos-build-findings-<DATE>.md with a fixed SECTION_KIND taxonomy, then commits and pushes per branch policy. - Use Case: A daily unattended loop invokes this skill on the osx-next host so the whole team sees whether the macOS tray build passed, failed, or regressed, with concrete next-step asks when it did not. ## Quick Start Run the build-macos-tray skill on the macOS Apple Silicon host to build the tray app, smoke-test it, install it locally, and record the findings.