Release v0.5.5

[lchoquel]

Release v0.5.5

Bumps version from 0.5.4 to 0.5.5. Promotes dev → main.

Changelog

Fixed

• make serve where ps may not run: in a sandbox that refuses ps, as Codex's workspace-write sandbox does on macOS, the web app template's make serve now refuses with refused: no-ps before starting anything, where it used to start the server, stop it again and report failed: exited as if it had exited at once.
• make stop keeps the record of a server it cannot identify: while the recorded server's first process runs where ps may not, or its group runs where lsof sees none of its processes, make stop now refuses and keeps .serve/state.json, where it used to take the server for another process or for one that had ended, drop its record and report not-running while it still listened. The record of a server that has ended is still cleared.
• failed: still-running: a server that make serve or make stop meant to stop and could not, because the system refused the signal or it outlived SIGKILL, is now reported as failed: still-running with its record kept, where it used to be reported as stopped and its record dropped.
• make all where ps may not run: a project's tests now skip the cases that start a server where ps may not run, so its make all passes in such a sandbox instead of failing.

Closes L-260925-f7be21

🤖 Generated with Claude Code

---

Summary by cubic

Releases v0.5.5, which fixes make serve and make stop where ps cannot run, as in Codex's workspace-write sandbox on macOS. Bumps the version from 0.5.4 to 0.5.5 and promotes dev to main.

• make serve now refuses with refused: no-ps before starting anything when it cannot read a start time; it used to start the server, stop it again, and report it as exited.
• make stop keeps .serve/state.json and refuses while a recorded server still runs but cannot be identified, where it used to drop the record and report not-running; a running group lsof cannot see is refused as no-lsof the same way, and records for ended servers are still cleared.
• A server meant to be stopped that the system refuses to signal or that outlives SIGKILL is now reported failed: still-running with its record kept, instead of reported stopped.
• The lifecycle tests skip the cases that start a server where ps may not run, so the template's make all passes in such a sandbox.

Closes L-260925-f7be21

^{Written for commit adc953b. Summary will update on new commits.}