Advertise incremental_checkpoints capability in workhorse and frontend

Eduardo Bonetrequested to merge
feature/duo-workflow-checkpoint-blobs-capability into master

What does this MR do and why?

Wires the incremental_checkpoints capability through the workhorse session negotiation and the frontend client, completing the stack.

Changes

  • runner.go — adds incremental_checkpoints to both ClientCapabilities and ServerCapabilities so workhorse negotiates the feature with the Rails server on session start.
  • constants.js — adds incremental_checkpoints to DUO_AGENTIC_CHAT_CLIENT_CAPABILITIES so the web client sends the capability header.
  • Frontend spec expectations updated to include the new capability.

Stack

This MR is part of a stack — merge in order:

  1. DB layer: !239245 (merged)
  2. API + service: !239247 (merged)
  3. Cleanup worker: !239248 (closed)
  4. This MR — workhorse + frontend (targets MR 2)

The branch is stacked on top of MR 3's worker commit, so the diff against MR 2 includes the worker changes from MR 3. Once MR 3 merges into MR 1, those commits drop out of this MR's diff.

MR acceptance checklist

  • Tests added / updated (workhorse test, frontend spec)

Testing

See !239247 (merged)

References

!238814 (closed)

Edited by Eduardo Bonet

Merge request reports