mirror of
https://github.com/getpaseo/paseo.git
synced 2026-07-29 12:01:31 +00:00
86b291814b
What changed: - Updated packages/cli/tests/03-daemon.test.ts to match current daemon command semantics where reports local state and exits successfully when stopped. - Removed host-based failure assumptions from status/status --json checks and asserted deterministic output for an isolated PASEO_HOME. - Hardened restart coverage to use an isolated random port and explicit cleanup via . - Added best-effort forced cleanup in to avoid leaking a daemon process if assertions fail mid-test. Reasoning: - Recent CLI refactors switched from connection-failure behavior to local PID/config introspection, so the old test expectation () became incorrect and flaky. - The restart path can occasionally exceed graceful stop timeout immediately after spawn; forced cleanup makes the test reliable without changing product behavior. - This is a behavior-preserving test hardening refactor aligned with the refactor skill contract. Verification: - npx tsx packages/cli/tests/03-daemon.test.ts - npm run typecheck Accomplishments for next agent: - now validates current status semantics and no longer depends on transient host connectivity assumptions. - Restart coverage now cleans up deterministically, reducing local test pollution and follow-on failures. Challenges / notes for next agent: - Restart cleanup still depends on process management timing; this test now uses cleanup intentionally to keep CI/dev runs stable. - If you later tighten restart lifecycle behavior, consider adding a dedicated unit-level test around stop timeout + escalation in local daemon utilities.