Goal
Redesign the default session right panel into a lightweight work-progress panel. It should help users see what PawWork is doing and what this session has produced, without turning the panel into logs, diagnostics, source tracking, or a second conversation stream.
Visual baseline
Use this session workspace mockup as the first-phase visual baseline for the right panel. It also shows how the Summary panel fits with the #151 home and session UI language.
Relationship to #151
Part of the broader UI reshaping direction in #151. This issue owns the right-panel information architecture and first-phase Summary redesign. #151 owns the home starter, Skill entry model, and overall visual language.
Product language
Use 进展 / Summary for the default tab. This follows Feishu-style Chinese product language: 进展 describes where work has moved to, while 状态 is better reserved for system or flow states.
Use 产出 / Artifacts for generated or modified session files. Avoid 结果, which sounds too broad and can imply final answers instead of concrete files.
First-phase scope
Default visible tabs: show only 进展 / Summary, 文件 / Files, and the add-tab button. Other technical or review surfaces should not appear as default tabs in this first-phase design.
Show 进度 / Progress, synced directly with the model todo list. Do not add folding, summarization, auto grouping, or event-log logic in this phase.
Render 进度 as a compact checklist. Each row should be one lightweight line with a small status icon, task name, and optional subtle status text. Reduce row spacing so tasks feel connected and easy to scan. Do not use a vertical timeline rail or separate cards per task.
Show 产出 / Artifacts, limited to files explicitly generated or modified in the current session. Do not show historical files, inferred related files, or a full file browser.
Render 产出 as compact file rows, not large cards. Each row should use a small file-type icon, filename, and subtle status such as 已生成, 已更新, or 待生成. 产出 is an artifact summary. 文件 / Files remains the full file browsing surface.
Keep the existing right-panel tab shell and add-tab behavior. Keep 文件 / Files available for full file browsing.
Conversation relationship
The conversation-side SessionTodoDock should stay small, centered, and one-line. It gives lightweight live context near the composer. The detailed task list belongs in 进展 / Summary.
Skill state belongs in the conversation flow as a compact Skill start card. Do not duplicate it as a persistent composer chip or as a separate right-panel section.
Non-goals
Do not add 待确认; confirmations, questions, permissions, and user choices should stay in the conversation flow.
Do not add 来源 / Sources in this phase. Source data and raw context belong in advanced context surfaces.
Do not redesign Context / 上下文, Terminal / 终端, Review / 审查, or diagnostic surfaces in this issue.
Do not split technical diagnostics into a new 诊断 / Diagnostics tab in this phase. That can be a follow-up issue.
Do not include command counts, searched-file counts, read logs, or other execution traces in the default Summary panel.
Goal
Redesign the default session right panel into a lightweight work-progress panel. It should help users see what PawWork is doing and what this session has produced, without turning the panel into logs, diagnostics, source tracking, or a second conversation stream.
Visual baseline
Use this session workspace mockup as the first-phase visual baseline for the right panel. It also shows how the Summary panel fits with the #151 home and session UI language.
Relationship to #151
Part of the broader UI reshaping direction in #151. This issue owns the right-panel information architecture and first-phase Summary redesign. #151 owns the home starter, Skill entry model, and overall visual language.
Product language
Use
进展 / Summaryfor the default tab. This follows Feishu-style Chinese product language:进展describes where work has moved to, while状态is better reserved for system or flow states.Use
产出 / Artifactsfor generated or modified session files. Avoid结果, which sounds too broad and can imply final answers instead of concrete files.First-phase scope
Default visible tabs: show only
进展 / Summary,文件 / Files, and the add-tab button. Other technical or review surfaces should not appear as default tabs in this first-phase design.Show
进度 / Progress, synced directly with the model todo list. Do not add folding, summarization, auto grouping, or event-log logic in this phase.Render
进度as a compact checklist. Each row should be one lightweight line with a small status icon, task name, and optional subtle status text. Reduce row spacing so tasks feel connected and easy to scan. Do not use a vertical timeline rail or separate cards per task.Show
产出 / Artifacts, limited to files explicitly generated or modified in the current session. Do not show historical files, inferred related files, or a full file browser.Render
产出as compact file rows, not large cards. Each row should use a small file-type icon, filename, and subtle status such as已生成,已更新, or待生成.产出is an artifact summary.文件 / Filesremains the full file browsing surface.Keep the existing right-panel tab shell and add-tab behavior. Keep
文件 / Filesavailable for full file browsing.Conversation relationship
The conversation-side
SessionTodoDockshould stay small, centered, and one-line. It gives lightweight live context near the composer. The detailed task list belongs in进展 / Summary.Skill state belongs in the conversation flow as a compact Skill start card. Do not duplicate it as a persistent composer chip or as a separate right-panel section.
Non-goals
Do not add
待确认; confirmations, questions, permissions, and user choices should stay in the conversation flow.Do not add
来源 / Sourcesin this phase. Source data and raw context belong in advanced context surfaces.Do not redesign
Context / 上下文,Terminal / 终端,Review / 审查, or diagnostic surfaces in this issue.Do not split technical diagnostics into a new
诊断 / Diagnosticstab in this phase. That can be a follow-up issue.Do not include command counts, searched-file counts, read logs, or other execution traces in the default Summary panel.