# Pin the two liveness probes to identical behavior · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/28a69713edf29c821aa9a8cfc73f77b0c415d153)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 28a69713edf29c821aa9a8cfc73f77b0c415d153

Requested commit: 28a69713edf29c821aa9a8cfc73f77b0c415d153

Commit: 28a69713edf29c821aa9a8cfc73f77b0c415d153

Tree: 2a9b1cb8f08a16e7d43f5305f9c0b94aa444ea34

Author: Theo Browne

Committer: Theo Browne

## Message

```
Pin the two liveness probes to identical behavior

The sync probe added for the pre-commit re-check duplicates the Effect
one's rules by hand — positive pid, live process, unparseable means no.
Two implementations of one rule drift apart silently, and this branch has
already produced several bugs of exactly that shape.

Asserts every case against both probes rather than trusting them to
agree: live in either state dir, dead pid, pid 0 and -1, malformed JSON,
and JSON with no pid. Confirmed the parity test fails when the sync
probe's positive-pid guard is removed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

```

## Parents

- [bc12b990a43b000f22ff99e5e6a94a457a018c9f](https://git.cafe/pingdotgg/t3code/commit/bc12b990a43b000f22ff99e5e6a94a457a018c9f?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/28a69713edf29c821aa9a8cfc73f77b0c415d153?format=markdown)