#16295: fix: filter brew install options when brew is unavailable

## Summary - Filters out `brew`-based skill install options when `brew` is not available on the system - Prevents confusing "brew not installed" errors during onboarding in Docker containers and other environments without Homebrew - Skills with alternative install methods (npm, uv, go) automatically fall back to those options Closes #14593 ## Changes **`src/agents/skills-status.ts`** — Extended `normalizeInstallOptions()` to check `hasBinary("brew")` and filter out brew-kind install specs when brew is unavailable. Uses the existing `hasBinary` utility (already imported). **`src/agents/skills-status.filters-brew-when-unavailable.e2e.test.ts`** — New test file with 2 tests: 1. Brew-only skill gets empty install array when brew unavailable 2. Multi-install skill (brew + node) falls back to node when brew unavailable ## How it works Before: Skills with `kind: "brew"` install specs passed the OS filter (Linux includes Docker) and appeared selectable, then failed at install time with "brew not installed". After: Skills with `kind: "brew"` install specs are filtered out at selection time when brew is unavailable. This is environment-agnostic — works in Docker, bare-metal Linux without brew, WSL without brew, etc. ## Test plan - [x] New e2e tests pass (7/7 across related files) - [x] Lint: 0 warnings, 0 errors - [x] Existing skills-status tests unaffected - [ ] Manual: Run `openclaw onboard` in Docker container, verify brew skills not offered 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- greptile_comment --> <h3>Greptile Summary</h3> Filters out `brew`-based skill install options in `normalizeInstallOptions()` when Homebrew is not available on the system, preventing confusing "brew not installed" errors during onboarding in Docker containers and other environments without Homebrew. - Extended `normalizeInstallOptions()` in `skills-status.ts` to check `hasBinary("brew")` and exclude brew-kind install specs when brew is unavailable - Skills with alternative install methods (npm, uv, go) automatically fall back to those options - Added two well-structured e2e tests covering the brew-only and multi-install fallback scenarios - Clean, minimal change that integrates well with the existing OS-based filtering pattern <h3>Confidence Score: 5/5</h3> - This PR is safe to merge — it adds a straightforward availability check that prevents broken install options from being surfaced. - The change is minimal, well-scoped, and follows existing patterns in the codebase. It adds a `hasBinary("brew")` check (already used elsewhere in this file at line 93) to the filter pipeline, with no risk of regression. The brew availability result is correctly hoisted outside the filter callback for efficiency. Both new tests are properly structured and cover the key scenarios. No logical errors, security concerns, or edge cases found. - No files require special attention _{Last reviewed commit: 1636063} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->