fix(workflow): stage timeline mixes Chinese event lines and tiny 「刚刚」 timestamps #1489

Activity

1. cursor

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

   fix(workflow): UI polish pass 4 - hide composer, fix locale, improve …

   ...

   cbb8a68

   docs: add changelog fragments for workflow UI polish fixes

   ...

   48c622d
2. Birfy

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

   fix(workflow,settings): UI polish passes 4-6 - composer, locale, head…

   ...

   cf72d48
3. Birfy commented on Oct 28, 2026

   

   Birfy

   on Oct 28, 2026

   CollaboratorAuthor

   More actions

   LIVE re-confirm (Asia/Shanghai 2026-10-28) — stronger symptom

   Owner asked bot-im to re-inspect two Workflows on prod tip ~55e1c27a (cookie proxy): 「FlyBot issue → 合入」 and 「PR → 合入」. Confirmed this issue’s 「刚刚」 timestamps, with a sharper correctness bug:

   Actual: Every timeline timestamp shows 「刚刚」, including old Done runs (e.g. #1445, #1499), not only in-flight events. Relative time never advances / never differentiates age.

   Expected: Relative (or absolute) times that age correctly for Done / historical events; “刚刚 / just now” only for truly recent lines.

   Still distinct from locale-only polish in the original body, but same root surface (timeline timestamp renderer). Please treat “stuck at 刚刚 for Done runs” as in-scope for this issue rather than filing a duplicate.

   Not filing separately (dedupe). Owner: 「这些问题也要提issue去改」 (t640u).
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

   on Oct 28, 2026
5. Birfy commented on Oct 28, 2026

   

   Birfy

   on Oct 28, 2026

   Last edited by Birfy

   CollaboratorAuthor

   More actions

   Triage: agent-ready

   Written-by: Triage (2026-10-28T04:29Z, base ThinkFlowLab/FlyBot @ main; read issue body, the 2026-10-28 LIVE re-confirm comment, labels [], assignees [], and merged PR #1494)

   Readiness against the three conditions. (1) No open design conflict: the timeline already stores at on every message (push() in plugins/workflow/src/service.js), and every other workflow string follows the shell locale through the plugin's tr() (the convention #1494 used for its sidebar/header copy), so "English here, Chinese in the zh shell" needs no owner decision. (2) Scope is clear and enumerable — the timeline producer, the one kind:'time' renderer, the .wf-ts rule, one test file. (3) Not hold, not a tracking/umbrella issue, not group work.

   Why it is still valid despite #1494 (merged 2026-10-27T17:01Z, body claimed Fixes #1489). #1494 only changed client-side copy (plugins/workflow/client.js strings + i18n entry + test). On main the defect is untouched:

   • plugins/workflow/src/service.js:522 pushes { kind: 'time', text: '刚刚' } as a literal once, at emit time; client.js:421 renders message.text verbatim (h('div',{className:'wf-ts'}, message.text)), so every timestamp is frozen at 「刚刚」 forever, including Done runs (fix(host): a Workflow run Bot keeps the team tools, whatever the node's tools list says #1445, fix(host): refuse the team tools to a deleted Bot's Sessions #1499) — the sharper symptom in the 2026-10-28 re-confirm.
   • Event lines are hard-coded Chinese regardless of shell locale: 任务已分配 · … (523), 排队 · … (568), Workflow「…」已创建 · … (743), ⏸ 已暂停 · … (849), ▶ 已继续 · … (865), ■ 已停止 · … (893), <node> 不能开始：缺少输入 … (341), <node> 没有接到这一步（…） (386), 进行中/… 收到。我继续处理「…」 (948).
   • .wf-ts is font-size:11px; color:var(--bt-ink-3,#9a9a9a) — the low-contrast small type from the original report.

   Reproduction (no prod needed). Build and run the workflow plugin, start one task, let the run reach done, reopen the room: the first kind:'time' line still reads 「刚刚」 next to an English issue title such as #1460 - …; the same line renders 「刚刚」 for a run finished days ago. In English shell the system lines are still Chinese.

   Executable acceptance.

   1. With the English shell (host Tasks ≠ 任务), a new run's timeline reads English: "Task assigned · …", "Queued · …", "⏸ Paused · …" / "▶ Resumed · …" / "■ Stopped · …", and the failure line in English; with the Chinese shell the same lines read Chinese. No line mixes an English title with a Chinese frame.
   2. A timestamp line ages: at = now renders "just now"; at = now − 2h renders "2h ago"; at = now − 3d renders "3d ago" (same ages in Chinese: 刚刚 / 2 小时前 / 3 天前). Done and historical runs no longer show 「刚刚」.
   3. .wf-ts is at least 12px on a readable ink token (--bt-ink-2 or better), still centered and muted, not competing with event lines.
   4. Legacy persisted messages that only carry a Chinese text still render (fallback to the stored text) — no blank timeline after upgrade.

   Files to change. plugins/workflow/src/service.js (push { kind:'system', key, params } or keep text plus a key; drop the literal 刚刚 from the kind:'time' line — at is already on every message), plugins/workflow/client.js (translate key/params in Bubble and in the kind:'time' branch, format relative time from message.at, add .wf-ts size/token), the plugin's ZH map in plugins/workflow/client.js (and core/src/client/i18n.js only if a shared key is reused), then regenerate the generated bundles (core/client.js, patches/ds-bot/) with node scripts/ds-bot-patches.mjs generate && check.

   Tests (red first). Add plugins/workflow/test/timeline-locale.test.js:

   • renders a timeline message {kind:'system', key:'Task assigned', params:{…}} in an English host and asserts the English frame → fails today (the view prints the Chinese literal);
   • renders {kind:'time', at: Date.now() - 2*3600e3} and asserts "2h ago"/"2 小时前" without a text → fails today (message.text is 刚刚);
   • asserts the same two lines with a zh host; and a legacy {kind:'system', text:'任务已分配 · …'} still renders its text.
     Extend plugins/workflow/test/client.test.js with one assertion that .wf-ts is not 11px/lowest-ink in the emitted style block. Reverting the source change must turn these red.

   Risk tier. T1 by judgment — one plugin's service + client copy/format and CSS, plus tests; no auth, secrets, queue/merge, release, or persisted-schema change (at already exists). The controller recomputes the tier at merge time; this line is advisory.

   Claimed scope for Dev: locale of the timeline lines and the aging timestamp and the .wf-ts readability, in one PR on #1489 (do not reopen #1494; one PR per issue).
6. Birfy

   self-assigned this

   on Oct 28, 2026
7. 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 28, 2026
8. Birfy commented on Oct 28, 2026

   

   Birfy

   on Oct 28, 2026

   CollaboratorAuthor

   More actions

   Claiming as Dev (implement). Branch: dev/1489-workflow-timeline-locale — will base on main 62023599, cover the English/Chinese event lines and the always-「刚刚」 time rows, and open a PR with Fixes #1489.
9. 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 28, 2026
10. Birfy

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

    fix(workflow): localize every stage-timeline frame (#1489)

    ...

    6ac1003

    fix(workflow): localize every stage-timeline frame (#1489)

    ...

    c59e715
11. Birfy

    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 28, 2026
12. Birfy commented on Oct 28, 2026

    

    Birfy

    on Oct 28, 2026

    CollaboratorAuthor

    More actions

    Written-by: Triage

    Reconcile at 2026-10-28T10:35:25Z: PR #1557 already exists for this issue (branch dev/1489-workflow-timeline-locale, head c59e715dd1a69e5e789a412e4e7c4dbf0e6a5ba7, repo branch), so agent-ready is removed and nothing new is implemented here.

    Two blockers sit on that pull request, not on this issue:

    • mergeable_state: dirty — it conflicts with main and needs a rebase or update-branch.
    • Its body carries no Fixes #1489 line anywhere (the checkpoint block has "issue": 1489, but enqueue-guard reads Fixes #<n>), so the queue would refuse it as it stands; check the Owner:/Reviewer: lines in the first 20 lines at the same time.

    One issue, one pull request: no second branch and no second pull request for #1489.
13. Birfy

    added

    agent-prPull request opened by an agentPull request opened by an agent

    on Oct 28, 2026
14. Birfy commented on Oct 28, 2026

    

    Birfy

    on Oct 28, 2026

    CollaboratorAuthor

    More actions

    Written-by: Triage

    Label repair at 2026-10-28T10:50:16Z: agent-pr added — this issue's open pull request is #1557 (this repository), head c59e715dd1a69e5e789a412e4e7c4dbf0e6a5ba7. Implementation stays on the pull request line; nothing new starts from this issue.
15. Birfy

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

    fix(workflow): localize the stage timeline and age its stamps (#1489)

    ...

    51f048f
16. Birfy

    closed this as completedin #1557on Oct 28, 2026
17. github-actions

    removed

    agent-prPull request opened by an agentPull request opened by an agent

    on Oct 28, 2026
18. HugoXK

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

    fix(workflow): localize the stage timeline and age its stamps (ThinkF…

    ...

    This issue will close once commit 22a1a38 is merged into the 'main' branch.

    22a1a38

    fix(core): route a card written through track_tasks to the board list…

    ...

    This issue will close once commit 034aba2 is merged into the 'main' branch.

    034aba2