Repository navigation
Workflow stage: fix broken flowchart edges; hide message composer #1459
Description
Problem
Owner screenshots on prod (2026-10-27 Asia/Shanghai) after Workflow UI work:
-
Flowchart edges broken — node cards (Triage / Claim+Implement / Verify) render, but connector paths fan into a spaghetti converging at bottom-right instead of clean top-down edges between nodes. Vertical stubs hang under cards. See attached owner shot description: edges do not follow graph order.
-
Stage has a message composer — bottom input shows「发消息 FlyBot issue → 合入」. Owner: Workflow does not need messaging. Tasks are handed to the graph; pause/resume/progress only. Chat belongs to persistent sidebar Bots (Chief etc.), not Workflow stage. Hide/remove the MessageComposer on Workflow stage surfaces.
-
Sidebar / stage header chrome — 「FlyBot issue → 合入」row with tiny flowchart thumb looks wrong / misaligned relative to normal Bot chat chrome (owner marked「这里不对」). Align Workflow selected-item header with polished chat+canvas style; no orphan composer.
Related
- Workflow UI: stage/inspector still unreadable; sidebar run status must match real runs #1454 / Fix Workflow UI: live run controls and short task summaries #1456 (readable UI, live-only, pause) — MERGED; these bugs remain or appear on current prod tip.
- Prior layout: Workflow stage: flowchart/canvas overlays left sidebar (layout broken) #1450 / Fix Workflow stage layout and hide ephemeral node chat #1452 (overflow/wire span).
- Owner standing rules: no demo runs; stage chat = normal conversation components but without node-Bot bubbles and without a send-message box on Workflow.
Acceptance
- Settings + stage flowchart edges are clean orthogonal/bezier between node anchors (no fan-to-corner spaghetti).
- Workflow stage UI has no message composer /「发消息」input.
- Selected Workflow header/sidebar chrome matches normal FlyBot polish (no clipped mini-graph thumb glitch).
- Tests cover: no MessageComposer mount on workflow stage; edge path regression for 3-node linear graph.
- docs/subsystems/workflow.md notes stage is view/control only (no chat send).
Owner
Birfy / bot-im
Do not merge to prod without owner yes.
Activity
Birfy commentedon Oct 27, 2026
Additional (owner 2026-10-27)
Workflow must not deliver ephemeral node Bot replies into persistent Chief (or other sidebar Bot) conversations.
Repro on prod: Chief chat shows「收到消息: Inspect 865c」while「FlyBot PR → 合入」Rework runs #1422; Chief thinking narrates that the workflow engine delivered the Inspect reply as a message.
Acceptance add:
Birfy commentedon Oct 27, 2026
Additional (owner 2026-10-27)
Flowchart running node should show a clear animation that a Bot is actively running on that step (not only a static「运行中」badge).
Owner wants to see at a glance which node Bot is live (e.g. pulse/spinner on Rework while Inspect=完成, Verify/Review=排队中).
Acceptance add:
runningnode has a visible motion cue (CSS animation / spinner) tied to live run state.Birfy commentedon Oct 27, 2026
Additional (owner 2026-10-27)
Polish the「把 Bot 拖到图上」roster: current three identical flat gray「Chief」chips look unfinished. Match chat+canvas style — clearer drag affordance, identity (avatar/initial), spacing/hover. Keep drag-to-graph.
Polish workflow palette Bot chips for drag-to-canvas
Birfy commentedon Oct 27, 2026
PR #1461 tip
2ede9d832bbff6cc20e7be3c08d9debd0dd38ea5includes palette polish (gripped chips, avatars, duplicate-name hints, drag ghost).Document workflow wire-plane anchoring in core-client
Fix Workflow stage UI and keep node replies off Chief chat (ThinkFlow…
chore(workflow): remove the dead workflow/say surface