feat: add task supersede to rescue dependents of dead upstream tasks - #102
Open
zhangweijian97 wants to merge 1 commit into
Open
feat: add task supersede to rescue dependents of dead upstream tasks#102zhangweijian97 wants to merge 1 commit into
zhangweijian97 wants to merge 1 commit into
Conversation
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
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
task supersede OLD_ISSUE NEW_ISSUE: repoint every same-plan dependent of a dead task (rejected / failed_infra / retired) onto a live replacement task.task retire.Why
When a task ends in a terminal non-done phase, every task whose
spec.dependenciesreferences its id waits forever:dependencyBase()only releases a dependent on a verified merge. Today recovery means manually closing and republishing the entire dependent subtree, losing approvals and history. This keeps recovery an explicit operator action but makes it one command instead of a manual subtree republish — especially for agent operators that watch the board programmatically.How to Test
bun run typecheckandbun run lintpass.bun run test: 332 tests pass including new cases for the successful rewrite + re-approval, and the three refusals (cross-plan, terminal replacement, dependency cycle).