v1.44.0

Added

• A decision or an answer made in the console, the web chat or over a session API now continues a run asked in a chat, as the person who made it, and posts the answer in that chat. A key's decision is recorded and does not continue the run. (#2656)
• continues_in_chat on approvals, on a run's single read and on the result of a resume or an answer. It is true when the server continues the run in its chat. (#2656)
• A console Stop, an expiry and a decided run that nothing continued each tell the chat once, in one fixed message. (#2656)

Changed

• A session API client that decides a chat run no longer resumes it. Read continues_in_chat and skip POST /runs/{id}/resume when it is true; a late resume answers 400 with the run's status. (#2656)
• Chat runs whose approvals were all decided but never continued are now ended about an hour after the last decision. (#2656)
• On the first sweep after upgrading, such runs decided more than 7 days ago are ended without a chat message. (#2656)
• Schema: agent_runs gains a nullable chat_notice_sent_at, which records that a chat was told its run could not continue. No backfill. (#2656)

Fixed

• Chat buttons answered elsewhere no longer act on a stale question. (#2656)
• A Discord run parked before its server was removed from the bot's approved servers is no longer continued by a console decision; the server is read from Discord again and one that cannot be confirmed is refused. (#2656)
• A chat button pressed at the moment the request is decided elsewhere is now closed instead of staying open. (#2656)
• The question sweep no longer overwrites an answer pressed at the last moment. (#2656)
• The approvals queue, the dashboard widget, the CSV export, the approval email and the in-app approval notification name the chat account instead of the publisher for an unlinked asker, and filtering the queue by the publisher no longer lists those calls. Who receives the email is unchanged. (#2656)