JD Davis 01161fe019 test(openclaw): match inherited PATH shell check (#2821) ... ## Description Fix the OpenClaw test failure on `main` by aligning its PATH-launcher expectation with the intentionally shipped `sh -c` behavior from #1459. The non-login shell preserves the PATH inherited from the OpenClaw process. Changing production code back to `sh -lc` would risk a login shell resetting that PATH and would undo the compatibility fix. This PR therefore corrects only the stale assertion; runtime behavior and defaults do not change. ## Type of Change - [x] Bug fix (non-breaking change that fixes an issue) - [ ] New feature (non-breaking change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Documentation update - [ ] Performance improvement - [ ] Code refactoring (no functional changes) ## Changes Made - Expect `sh -c` for the non-Windows lightweight `command -v headroom` check. - Preserve the existing Windows `where.exe` behavior and all launcher behavior. ## Testing - [x] Unit tests pass (`npm test`) - [x] Linting passes (`npm run typecheck`) - [x] Type checking passes (`npm run typecheck`) - [ ] New tests added for new functionality - [x] Manual testing performed ### Test Output ```text $ npm test Test Files 6 passed (6) Tests 75 passed (75) $ npm run typecheck > tsc --noEmit $ npm run build ESM Build success DTS Build success $ npm ci found 0 vulnerabilities ``` ## Real Behavior Proof - Environment: macOS, Node/npm, clean install from `origin/main` at `2954e37048`. - Exact command / steps: `cd plugins/openclaw && npm ci && npm test && npm run typecheck && npm run build`. - Observed result: all 75 OpenClaw tests pass, TypeScript typechecking succeeds, and both ESM and declaration builds succeed. - Not tested: Windows execution; its separate `where.exe` expectation and implementation are unchanged. ## Review Readiness - [x] I have performed a self-review - [x] This PR is ready for human review ## Checklist - [x] My code follows the project's style guidelines - [x] I have performed a self-review of my code - [x] I have commented my code, particularly in hard-to-understand areas - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [x] I did **not** edit `CHANGELOG.md` — it is generated by release-please from my Conventional Commit PR title (a CI guard enforces this) ## Screenshots (if applicable) N/A — test-only correction with no UI changes. ## Additional Notes History confirms #1459 deliberately changed `sh -lc` to `sh -c` while adding explicit uv-tool path detection. Reverting the implementation would change runtime discovery semantics; updating the stale test preserves the accepted behavior. Co-authored-by: JD Davis <jd@jds-macbook-air.tail2a279.ts.net>		2026-08-06 19:21:52 -07:00
..
headroom-agent-hooks	chore: release main (#2679)	2026-08-04 19:39:34 -07:00
headroom-oauth2	chore: remove committed node_modules + stray/internal markdown (repo hygiene) (#1528)	2026-06-27 23:32:54 -07:00
hermes	fix(ccr): make headroom_retrieve a hash-only full-content lookup (#1532)	2026-06-28 10:32:43 -07:00
openclaw	test(openclaw): match inherited PATH shell check (#2821)	2026-08-06 19:21:52 -07:00
opencode	fix(opencode): don't preload a missing transport shim into child processes (#2806)	2026-08-05 12:42:10 -07:00