fix: preserve dev server background task classification - #50
Merged
Conversation
- Recover task identity from persisted lifecycle activities after restart - Prevent contradictory recovery events from promoting background tasks to agents
github-actions
Bot
added
vouch:trusted
Thread transfer impact
This comment will update automatically after the next completed run. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed
Preserve task identity and classification across sparse lifecycle events, server restarts, and recovery notifications. Background tasks such as dev servers now retain their background status instead of being promoted to the agent roster by contradictory or incomplete completion events.
Added focused server and client-runtime tests covering identity recovery and background-task exclusion.
Why
Provider recovery events may omit task metadata or contain stale classification fields after a restart. Previously, these events could cause background shell tasks to appear as interactive agents. Task classification is now anchored to the original
task.startedactivity, while missing identity fields are recovered from persisted task activities.Checklist