While a run is open, resumeSeq is that run's first event seq minus one, so a client can replay the process already produced.
After the run ends, resumeSeq equals lastSeq.
Test plan
TestConversationResumeSeq: hitl wait has resumeSeq = first-1 and less than lastSeq; after resolve the two cursors match
GOWORK=off go test ./...
owner merges
Refs: Dev fix/live-run-visibility
## Summary
- Conversation detail returns resumeSeq beside lastSeq.
- While a run is open, resumeSeq is that run's first event seq minus one, so a client can replay the process already produced.
- After the run ends, resumeSeq equals lastSeq.
## Test plan
- [x] TestConversationResumeSeq: hitl wait has resumeSeq = first-1 and less than lastSeq; after resolve the two cursors match
- [x] GOWORK=off go test ./...
- [ ] owner merges
Refs: Dev fix/live-run-visibility
Why: Refreshing or switching back only knew the latest event cursor, so process that had already happened was missing until the run finished.
Evidence: GOWORK=off go test -count=1 -run TestConversationResumeSeq ./internal/server passed. While a hitl run waits, resumeSeq is the run's first seq minus one and is less than lastSeq; after the run completes the two cursors match.
Impact: Conversation detail gains resumeSeq beside lastSeq. No core contract change. Clients that ignore the field keep the old cursor.
Refs: Dev fix/live-run-visibility
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: The pull request cannot merge while the head is behind main.
Evidence: origin/main is 5d59ee9, one commit ahead of this branch.
Impact: Keeps the resume cursor and the interrupted-run recovery together.
Refs: Backend #54
weichen
merged commit 28ccb741e4 into main2026-10-03 15:25:37 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Test plan
Refs: Dev fix/live-run-visibility