Why: The same fast/slow work card appeared in the conversation and work pane, and a completed reply hid intermediate narration, thinking and full tool output.
Middle: chronological messages + one folded process record per run
Right: current work, decisions, results and files
- full work cards repeated in both panes
+ one detailed location with a conversation fallback
Impact: Pin the merged Backend, Frontend and UI revisions together; update DESIGN.md for one detail location and durable process review. No schema migration or model-call change.
Refs: task record, UI #55, Backend #199, Frontend #85.
Evidence
Before: repeated full card content; terminal assistant message replaced the live process with only partial tool records.
After: 272 Frontend unit tests, production build and 15 isolated Chromium scenarios pass, including refresh, child progress, card location and 320–1440px layouts. Backend full Go and UI tests/typecheck pass. On prior fixed combination c794587, isolated-localhost make test and make build pass (SELF source-out receipts). On 7d13f2f the native Backend suite, isolated-network governance suite and build pass separately (SELF); whole local make test inside outer Bubblewrap cannot nest Backend sandbox tests. Exact final head 8f5b64e has CI run 3200 in progress.
Sync and review
Manual delivery window: base bc76b68cd075379122430acb24fa080b0a38ff5e, head 8f5b64e50e3a78a93c2a41c0b80a8db718a0576e. Backend ead5ade contains both the reviewed history API (#199) and concurrent vendor-skills merge (#200); Frontend 710ef83 and UI 7c35a78 are their merged main commits. make task-sync changed=1 only to include the unrelated vendor task-card archive; candidate record links the source-out receipt. Independent code review found no Critical/Important issues before this sync; the sync-only diff is under final read-only review.
Merge Danger
Door: two-way
Blast Radius: conversation rendering and authenticated process-history reads
The 8788 instance runs an RDM composition. Its pin adoption and runtime cutover remain separate from this base merge.
## Summary
Why: The same fast/slow work card appeared in the conversation and work pane, and a completed reply hid intermediate narration, thinking and full tool output.
```diff
Middle: chronological messages + one folded process record per run
Right: current work, decisions, results and files
- full work cards repeated in both panes
+ one detailed location with a conversation fallback
```
Impact: Pin the merged Backend, Frontend and UI revisions together; update `DESIGN.md` for one detail location and durable process review. No schema migration or model-call change.
Refs: [task record](https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/src/branch/feature/work-companion-visibility/.task/feature-work-companion-visibility.md), [UI #55](https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-UI/pulls/55), [Backend #199](https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Backend/pulls/199), [Frontend #85](https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Frontend/pulls/85).
## Evidence
- Before: repeated full card content; terminal assistant message replaced the live process with only partial tool records.
- After: 272 Frontend unit tests, production build and 15 isolated Chromium scenarios pass, including refresh, child progress, card location and 320–1440px layouts. Backend full Go and UI tests/typecheck pass. On prior fixed combination `c794587`, isolated-localhost `make test` and `make build` pass (SELF source-out receipts). On `7d13f2f` the native Backend suite, isolated-network governance suite and build pass separately (SELF); whole local `make test` inside outer Bubblewrap cannot nest Backend sandbox tests. Exact final head `8f5b64e` has [CI run 3200](https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/actions/runs/3200) in progress.
## Sync and review
Manual [delivery window](https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/issues/518#issuecomment-6346): base `bc76b68cd075379122430acb24fa080b0a38ff5e`, head `8f5b64e50e3a78a93c2a41c0b80a8db718a0576e`. Backend `ead5ade` contains both the reviewed history API (#199) and concurrent vendor-skills merge (#200); Frontend `710ef83` and UI `7c35a78` are their merged main commits. `make task-sync` changed=1 only to include the unrelated vendor task-card archive; [candidate record](https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/issues/518#issuecomment-6351) links the source-out receipt. Independent code review found no Critical/Important issues before this sync; the sync-only diff is under final read-only review.
## Merge Danger
**Door:** two-way
**Blast Radius:** conversation rendering and authenticated process-history reads
The 8788 instance runs an RDM composition. Its pin adoption and runtime cutover remain separate from this base merge.
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-work-companion-visibility.md; R0=e1bc2602e18a89e4d75a4bf6cd80bc7f9b4d2164.
Impact: task metadata only; the feature workspace starts at e1bc2602e1.
Refs: .task/feature-work-companion-visibility.md
Why: The fast and slow channel UI duplicated work cards and hid intermediate output after the final reply.
Evidence: SELF isolated-network make test and make build; 15 browser scenarios; independent component review; component PRs #55, #199, #85.
Impact: Pin merged Backend, Frontend and UI revisions and update DESIGN.md for one detail location and durable folded history.
Refs: .task/feature-work-companion-visibility.md; Agent-System-UI #55; Agent-System-Backend #199; Agent-System-Frontend #85
Why: Dev main advanced with a vendor skills task while this UI combination was being verified.
Evidence: Backend main ead5ade contains both Backend #199 and #200; the component merge affects recipes, not run-history handlers.
Impact: Preserve the new main task card and pin the Backend merge containing both changes; combination checks follow on this head.
Refs: Agent-System-Dev #550; Agent-System-Backend #199 and #200
Why: Main advanced during UI delivery and task metadata must identify the new combined candidate.
Evidence: task-sync source-out receipt 6122ca6; Backend ead5ade includes both reviewed run history and concurrent vendor skills.
Impact: Fill the task PR link and mark the new Backend combination and final checks pending.
Refs: Agent-System-Dev #550; Agent-System-Backend #199 and #200
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=bc76b68cd075379122430acb24fa080b0a38ff5e.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Why: The same fast/slow work card appeared in the conversation and work pane, and a completed reply hid intermediate narration, thinking and full tool output.
Impact: Pin the merged Backend, Frontend and UI revisions together; update
DESIGN.mdfor one detail location and durable process review. No schema migration or model-call change.Refs: task record, UI #55, Backend #199, Frontend #85.
Evidence
c794587, isolated-localhostmake testandmake buildpass (SELF source-out receipts). On7d13f2fthe native Backend suite, isolated-network governance suite and build pass separately (SELF); whole localmake testinside outer Bubblewrap cannot nest Backend sandbox tests. Exact final head8f5b64ehas CI run 3200 in progress.Sync and review
Manual delivery window: base
bc76b68cd075379122430acb24fa080b0a38ff5e, head8f5b64e50e3a78a93c2a41c0b80a8db718a0576e. Backendead5adecontains both the reviewed history API (#199) and concurrent vendor-skills merge (#200); Frontend710ef83and UI7c35a78are their merged main commits.make task-syncchanged=1 only to include the unrelated vendor task-card archive; candidate record links the source-out receipt. Independent code review found no Critical/Important issues before this sync; the sync-only diff is under final read-only review.Merge Danger
Door: two-way
Blast Radius: conversation rendering and authenticated process-history reads
The 8788 instance runs an RDM composition. Its pin adoption and runtime cutover remain separate from this base merge.
Dev main 当前由 调度记录 #518按 manual 窗口协调。2026-10-14T15:13:20Z，闭卡 #551 在已登记的另一规则窗口内推进 main；该窗口已因候选失效释放，#518 正在对账写者覆盖。第二轮 r2 仍
pending-activation / waiting。请本 PR 的实际工作区 owner 在进行最终
task-sync、完整 PR CI 或合入前，于 #518 登记其原任务/阶段授权、当前 source HEAD、依赖/组件、活动写者和就绪时间，并由协调者确认目标窗口的领取与释放。若已有其他协调记录或在途合入请求，请在 #518 指向其具体对象以便对账。此评论仅协调共享 main；不接管 #550、不代签阶段评审或 Review，也不改变现有 CI/保护。