fix(server): bound session listing and keep a full idle window after turns

[leoisadev1]

Problem

Session listing and idle reaping both scaled from the wrong clocks.

listSessions loaded every persisted thread binding, then looked each one up, so the call grew with conversation history instead of the live adapter session set. The session reaper treated binding lastSeenAt as the only idle timestamp. That stamp is updated when a turn is sent, so a long turn that later completed or aborted could be stopped as soon as it finished instead of getting a full inactivity window.

Changes

Look up bindings only for the unique thread ids of currently active adapter sessions. Historical bindings stay out of this path.

Idle time is max(binding.lastSeenAt, session.updatedAt) after the cheap lastSeenAt skip. Ingestion updates session.updatedAt when a turn settles, so ready, interrupted, and error sessions get the full window after that transition. Active turns and live backgroundLiveness still skip reaping. Akeru still uses AgentController rather than ProviderService for stop.

Upstream

Reviewed adaptations of pingdotgg/t3code:

• #8909 bound session lookups
• #10689 full post-completion idle window

Scope

This PR is session listing and idle timing only. Independent of #220 and #229.

Assigned checkpoint and attachment ports are in those PRs:

• checkpoint capture, nested git, numstat, git-init resume, capture-before-status-refresh (perf(server): avoid full patches for checkpoint summaries pingdotgg/t3code#9694, fix(server): detect nested Git workspaces for checkpoints pingdotgg/t3code#9842, fix(server): capture turn checkpoints after all edits finish pingdotgg/t3code#9841, fix(server): resume checkpointing after git init pingdotgg/t3code#10078, fix(server): capture checkpoints before refreshing PR status pingdotgg/t3code#10347) — #220
• attachment transaction cleanup and first-send retry (fix(server): keep attachments until the command commits pingdotgg/t3code#7941, fix(server): a draft can retry its first send after a failed bootstrap pingdotgg/t3code#8226) — #229

Restart continuation remains with the capabilities worker.

Verification

• vp test run of ProviderService and ProviderSessionReaper: 50 tests passed. New cases use Clock overrides and a deferred sweep, not sleeps.
• Targeted lint and format passed (0 errors). One pre-existing unused dispatch parameter warning in ProviderService.test.ts is unchanged.

No UI layout or client-visible chrome change. Proof is adapter-session listing and reaper sweep tests.

Limitations

backgroundLiveness skip is preserved. Capabilities-owned restart continuation is not in this PR.

Implemented and verified by Grok 4.6 High in Grok Build via Orca.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
akeru-bot-landing	Skipped		Sep 10, 2026 6:11pm UTC

[greptile-apps]

Greptile Summary

Summary

• Session binding lookups are limited to unique active adapter thread IDs rather than historical bindings.
• Idle-session reaping uses the newest persisted or projected activity timestamp, preserving the full inactivity window after terminal turns.
• Targeted coverage verifies bounded lookups, timestamp precedence, and idle-window boundaries.

Confidence Score: 5/5

Safe to merge; there are no outstanding blocking issues.

No new findings or outstanding previous findings.

_{Reviews (2): Last reviewed commit: "Merge branch 'main' into leoisadev1/t3-p..." | Re-trigger Greptile}