Robin Braumann dcf535a1c6 feat(core): Handle a busy agent session on each surface (no-changelog) ... Each starter now reacts to a busy session in its own way: - An integration message gets a busy notice. The bridge deletes its stored attachments and does not run the message. - An integration button resume waits for the session for 5 seconds. Then it posts "This action has already been handled". A Preview resume waits the same time and then gets `turn_already_running`. - A workflow-tool resume tries again with a backoff from 1 s to 30 s. It stops when the run is no longer suspended. - A background wake skips without a failure count. The turn that holds the session requests a new wake when it settles. - A busy sub-agent resume is retryable, so the parent stays suspended. The session lease replaces the in-process HITL guard and the running check of the wake, so this removes both and `existsRunningByThread`. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>		2026-09-23 12:26:12 +02:00
..
repositories	feat(core): Handle a busy agent session on each surface (no-changelog)	2026-09-23 12:26:12 +02:00
services	feat(core): Add the credentialSave policy enforcement point (no-changelog) (#39099)	2026-09-21 19:44:58 +00:00