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

[View on GitCafe](https://git.cafe/flambo/t3code/commit/97773eef8d0245977dc4c636eb4335c304ae05d2)

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

Visibility: public

Requested revision: 97773eef8d0245977dc4c636eb4335c304ae05d2

Requested commit: 97773eef8d0245977dc4c636eb4335c304ae05d2

Commit: 97773eef8d0245977dc4c636eb4335c304ae05d2

Tree: 066dbdd0c8d8be46e282fa0bba27bdfbbde50c51

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

- [0a4a98a764616764464257060d211823e10d97d2](https://git.cafe/flambo/t3code/commit/0a4a98a764616764464257060d211823e10d97d2?format=markdown)

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