# fix\(server\): keep threads armed to auto-resume out of inactivity auto-settle · pingdotgg/t3code

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

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

Visibility: public

Requested revision: 0a412bb9121e06df41e5797b666f235e7c876650

Requested commit: 0a412bb9121e06df41e5797b666f235e7c876650

Commit: 0a412bb9121e06df41e5797b666f235e7c876650

Tree: 29df4caa21b5fb0457074c3941132759d29248ec

Author: ScottN-PV

Committer: ScottN-PV

## Message

```
fix(server): keep threads armed to auto-resume out of inactivity auto-settle

A thread that hit a usage limit with auto-resume armed looked like any idle
thread to inactivity auto-settle, so a reset further away than the settle
window let the sweep settle it first, and settling drops the resume. An armed
resume for the latest run now parks the thread like a snooze until its reset,
and the reset restarts the inactivity window. Settlement candidates carry
limitRecovery so the sweep can see it.

Closes #18928

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

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

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