# feat\(server\): evaluate automatic thread settlement in the v2 orchestrator · pingdotgg/t3code

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

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

Visibility: public

Requested revision: cfa62ce4a1d3a050bf7a0694f13bda01ed70f1cf

Requested commit: cfa62ce4a1d3a050bf7a0694f13bda01ed70f1cf

Commit: cfa62ce4a1d3a050bf7a0694f13bda01ed70f1cf

Tree: 7fecc5293fc56bab94b36864cf9a09f2cb0d7aec

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
feat(server): evaluate automatic thread settlement in the v2 orchestrator

Ports #8600's server-owned settlement to orchestration v2 instead of
keeping client-side evaluation. A ThreadSettlementService sweep runs at
startup, on auto-settle settings changes, and once per minute: it
evaluates inactivity and merged or closed pull requests over v2 thread
shells and dispatches the new guarded thread.auto-settle command, which
rejects threads that changed after the sweep's snapshot or carry any
explicit override, then reuses the orchestrator's settle lifecycle.
With the server deciding, the clients drop their effectiveSettled
evaluation and partition on the persisted settledOverride like main.

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

```

## Parents

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

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