[orc] TASK-810: Fix inconsistent task lifecycle status across CLI and Home page#577
Open
randalmurphal wants to merge 1 commit into
Open
[orc] TASK-810: Fix inconsistent task lifecycle status across CLI and Home page#577randalmurphal wants to merge 1 commit into
randalmurphal 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
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.
Task: Fix inconsistent task lifecycle status across CLI and Home page
We observed real task-state inconsistencies while validating the new workflow. Examples: TASK-719, TASK-744, and TASK-745 show 'Status: closed' in 'orc show' even though they still have open phases, while the Home/My Work UI still surfaces old unfinished work as active backlog. The live UI also showed 'Running 1' while saying 'No threads yet', which makes execution state hard to understand. Fix the underlying lifecycle/status derivation or read path so task state, current phase, and execution activity are presented consistently across CLI and web surfaces. Focus on CLI/backend correctness first, then UI presentation where needed. Avoid papering over stale data if the root cause is status computation. Required verification: Go tests for status derivation/read paths, any affected web tests, and browser validation with Playwright against the live app so we can confirm the Home/My Work and task-detail surfaces reflect the same truth as the backend.
Created by orc workflow execution.