# fix\(server\): release the tunnel when an explicit stop interrupts an update · screen/t3code-personal

[View on GitCafe](https://git.cafe/screen/t3code-personal/commit/f9e8236899f25653ce95d688fac798cd070afbc1)

Repository: [screen/t3code-personal](https://git.cafe/screen/t3code-personal)

Visibility: public

Requested revision: f9e8236899f25653ce95d688fac798cd070afbc1

Requested commit: f9e8236899f25653ce95d688fac798cd070afbc1

Commit: f9e8236899f25653ce95d688fac798cd070afbc1

Tree: b7a4ad34cb9ea4e8aaa8339a46097fd577e588a6

Author: Theo Browne

Committer: Theo Browne

## Message

```
fix(server): release the tunnel when an explicit stop interrupts an update

A pending update in the launcher state is not proof a replacement
server is coming: `t3 service uninstall` or `systemctl stop` during
the pending window also tears the server down, permanently. The
launcher now writes a stop marker before signalling its child on an
explicit stop and clears it on the next start; the shutdown tunnel
release keeps the tunnel only for pending updates without the marker.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

```

## Parents

- [8f341f20c91e708de1dab949dbd723e86f2ff328](https://git.cafe/screen/t3code-personal/commit/8f341f20c91e708de1dab949dbd723e86f2ff328?format=markdown)

[Source at this commit](https://git.cafe/screen/t3code-personal/tree/f9e8236899f25653ce95d688fac798cd070afbc1?format=markdown)