Jesse Vincent f076bd3431 Fix owner-PID false positive when owner runs as different user ...

ownerAlive() treated EPERM (permission denied) the same as ESRCH
(process not found), causing the server to self-terminate within 60s
whenever the owner process ran as a different user. This affected WSL
(owner is a Windows process), Tailscale SSH, and any cross-user
scenario.

The fix: `return e.code === 'EPERM'` — if we get permission denied,
the process is alive; we just can't signal it.

Tested on Linux via Tailscale SSH with a root-owned grandparent PID:
- Server survives past the 60s lifecycle check (EPERM = alive)
- Server still shuts down when owner genuinely dies (ESRCH = dead)

Fixes #879

2026-03-25 11:03:53 -07:00

..

scripts

Fix owner-PID false positive when owner runs as different user

2026-03-25 11:03:53 -07:00

SKILL.md

Reapply "Replace subagent review loops with lightweight inline self-review"

2026-03-25 11:03:53 -07:00

spec-document-reviewer-prompt.md

Tone down review loops: single-pass plan review, raise issue bar

2026-03-16 15:57:23 -07:00

visual-companion.md

Separate brainstorm server content and state into peer directories

2026-03-25 11:03:53 -07:00