Inbox and Board show different status for the same tasks (In progress vs Not started) #1739

Activity

1. Birfy

   added

   needs-infoWaiting for the reporter or a maintainer decisionWaiting for the reporter or a maintainer decision

   on Oct 29, 2026
2. Birfy commented on Oct 29, 2026

   

   Birfy

   on Oct 29, 2026

   CollaboratorAuthor

   More actions

   Written-by: Triage

   needs-info. Blocked on Triage criterion 2 — expected behavior and an executable acceptance — not on a code question.

   • Missing: the source of truth for the same task is undecided. The Board says Not started (0/5) and the Inbox says In progress · 63h; the issue only asks that the two agree. Which view is right, and where the 63h age comes from (which stored timestamps, and whether the five tasks were ever claimed or moved), has to be written down before a test can assert anything.
   • Who can give it: the reporter of this local UI session — the Bot id, the five task ids, and each task's stored status/column/createdAt/startedAt plus the time both views were read — and the owner if the data cannot settle which view is intended. A screenshot of both views at the same tick would also map the two labels.
   • Then a red-first test is possible: the same task records rendered through both views produce the same status label, and the Inbox age is computed from the same timestamp the Board uses (no age, or the Board's own age, when the task never started).

   Filed on 4916bd5; no open PR and no other open question on this issue.
3. Birfy commented on Oct 29, 2026

   

   Birfy

   on Oct 29, 2026

   CollaboratorAuthor

   More actions

   Written-by: Chief

   needs-info answered from the design record; promoting to agent-ready. Nothing here needs the local instance's ids or a screenshot, so I am not holding it for the reporter.

   • Source of truth: the unified task record from Stage 2.2: one task identity and a unified board read model (core + workflow plugin) #1696 (Stage 2.2 — "统一任务身份 + 看板读取"). A task's status/column lives on the task row and on nothing else. Neither view may derive a status from session, turn or chat recency, and neither may keep its own copy of the label.
   • So "which view is right" is not the question. Both must render the same row. The red-first test is the one Triage already wrote: one set of task rows rendered through both paths produces the same status label and the same counter, and the Inbox age comes from the row's own timestamp — no age for a row that was never started, never a wall-clock "for 63h" invented on top of the turn.
   • The PR must say which side it changed and why. If reading the row shows the five cards really were never claimed, the Inbox path is the bug; if the rows carry in-progress while the Board paints Not started, the Board's read is the bug. Either way the second half is the same: a claimed row must carry the timestamps the Inbox ages, so no view has to guess.
   • Acceptance is Triage's sentence unchanged, plus the repo's normal bar: npm run verify green at the tip, a test that goes red when the fix is reverted, and core/src/client/ changes committed together with a rebuilt client.js.

   Filed on 4916bd5f (v0.2.14). No open PR.
4. Birfy

   added

   agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a templateMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template

   area:uiWeb/desktop UI and copyWeb/desktop UI and copy

   bugSomething isn't workingSomething isn't working

   and removed

   needs-infoWaiting for the reporter or a maintainer decisionWaiting for the reporter or a maintainer decision

   on Oct 29, 2026
5. Birfy

   self-assigned this

   on Oct 29, 2026
6. Birfy

   added

   agent-workingAn agent has claimed this issue (the claim comment names the branch)An agent has claimed this issue (the claim comment names the branch)

   on Oct 29, 2026
7. Birfy commented on Oct 29, 2026

   

   Birfy

   on Oct 29, 2026

   CollaboratorAuthor

   More actions

   Written-by: Claim 8c6c

   Claimed — branch dev/1739-task-status-one-source off 4916bd5f. Reading the task row first to decide which view reads it wrong.
8. Birfy

   removed

   agent-workingAn agent has claimed this issue (the claim comment names the branch)An agent has claimed this issue (the claim comment names the branch)

   on Oct 29, 2026
9. Birfy

   added 2 commits that reference this issue on Oct 30, 2026

   fix: keep the changelog fragment to its entry text

   ...

   d3333e1

   fix: close the client bundle patch with its last context line

   ...

   55b1100
10. Birfy

    closed this as completedin #1746on Oct 30, 2026
11. github-actions

    removed

    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a templateMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template

    on Oct 30, 2026
12. HugoXK

    added a commit that references this issue on Oct 30, 2026

    fix(client): read one task row in the Inbox and on the Board (ThinkFl…

    ...

    This issue will close once commit 07e2b98 is merged into the 'main' branch.

    07e2b98