docs(readme): restore visible illustrations and fold supporting detail

README.md

@@ -64,9 +64,6 @@ engineering, research and operations. Human authorization still governs protecte
 | Manage personal projects, schedules and decisions in one place | [Personal Agent Workspace](#meet-the-personal-agent-workspace) |
 | Let agents collaborate and deliver verifiable results | [Agent collaboration guide](docs/product/use-cases/cross-runtime/README.md) |
 
-<details>
-<summary>How the control plane works and where it fits</summary>
-
 LoopX keeps the durable control state in one compact layer:
 
 <picture>
@@ -83,6 +80,9 @@ another agent framework or a provider-specific orchestration runtime.
   <img src="docs/assets/control-plane-board.en.svg" alt="One turn is a governed state transition—not just a timer." width="1200">
 </picture>
 
+<details>
+<summary>How the control plane works and where it fits</summary>
+
 A useful mental model is an
 **[agent-native Kanban for long-running work](docs/development/control-plane-course/00-concept-primer.md)**.
 Cards carry identity, authority, evidence, and continuation. Moves are validated
@@ -166,11 +166,11 @@ manual, App rollback and repair are unavailable, and the installer carries no
 Authenticode certificate (Windows may show a SmartScreen prompt).
 [Desktop installation, updates, and source development](apps/desktop/loopx-control-plane/README.md).
 
+<img src="docs/assets/personal-workspace/capability-1.0.webp" alt="Real Workspace recording: configure child-task capacity and allowed responsibility domains" width="960">
+
 <details>
 <summary>Capability settings and reproducible workspace scenarios</summary>
 
-<img src="docs/assets/personal-workspace/capability-1.0.webp" alt="Real Workspace recording: configure child-task capacity and allowed responsibility domains" width="960">
-
 From a source checkout, run `python -m demo.workspace serve` to explore a community
 event, a home-energy comparison, and a neighborhood website release. Each has four
 work roles, 18 tasks, two decisions, and two watches. The screenshot above comes
@@ -338,9 +338,6 @@ time, not continuous model execution or unattended production autonomy. Open
 each visual to inspect the public-safe task graph, evidence branches, and
 cross-turn decisions; each case states its source and reproducibility boundary.
 
-<details>
-<summary>Earlier 200+ hour project trajectories: OpenViking and ML experiments</summary>
-
 ### Open-Source Issue Fix
 
 **200+ hour public contribution arc: PR delivery and reusable fix knowledge
@@ -350,6 +347,9 @@ evolve together.**
   <img src="docs/assets/long-running-loop-openviking-trajectory.png" alt="Open-source issue-fix trajectory linking focused PR delivery with reusable LoopX capabilities" width="760">
 </a>
 
+<details>
+<summary>Contribution sources and evidence boundary</summary>
+
 LoopX's creator uses this path as an
 [OpenViking contributor](https://github.com/volcengine/OpenViking/pulls?q=is%3Apr+author%3Ahuangruiteng).
 The represented public contribution sequence spans more than 200 elapsed hours
@@ -359,6 +359,8 @@ repository context, revision-stamped fix knowledge, and reviewer-facing
 preferences separate; linked PRs plus current checkout source and tests remain
 authoritative.
 
+</details>
+
 ### Auto ML Experiment
 
 **Redacted owner-run showcase: a 200+ hour experiment arc keeps hypotheses,
@@ -373,8 +375,6 @@ The redacted public-safe graph preserves decision lineage across that 200+ hour
 elapsed window. It is an owner-run showcase, not a claim of continuous compute,
 independent reproduction, or a production result.
 
-</details>
-
 ### Used In Real Projects
 
 - **Independent user · `>13h` C++ accuracy run.** The user reported that a

README.zh-CN.md

@@ -57,9 +57,6 @@ Claude Code 使用 `/loopx <复杂任务>`。[其他宿主、安装方式与升
 | 在一个入口管理个人项目、定时任务与待决事项 | [个人 Agent 工作区](#认识个人-agent-工作区) |
 | 让多个 Agent 分工协作，交付可验收的结果 | [Agent 协作指南](docs/product/use-cases/cross-runtime/README.md#中文指南) |
 
-<details>
-<summary>控制面如何工作，适合哪些场景</summary>
-
 LoopX 把长期控制状态留在同一层紧凑状态里：
 
 <picture>
@@ -76,6 +73,9 @@ Agent runtime 负责执行，LoopX 负责治理跨运行延续的控制状态，
   <img src="docs/assets/control-plane-board.zh.svg" alt="一轮工作是受约束的状态迁移，不是定时器。" width="1200">
 </picture>
 
+<details>
+<summary>控制面如何工作，适合哪些场景</summary>
+
 一个形象化理解是：LoopX 是
 **[面向长程 Agent 的可执行看板](docs/development/control-plane-course/00-concept-primer.md)**。
 卡片带有稳定身份、权限、证据和 continuation；移动卡片要经过 claim、gate、
@@ -142,11 +142,11 @@ loopx dashboard
 App 为 ad-hoc 签名，尚未 notarize。Windows 预览版目前手动更新，需单独安装 CLI。
 [桌面安装、更新与源码开发指南](apps/desktop/loopx-control-plane/README.md)。
 
+<img src="docs/assets/personal-workspace/capability-1.0.webp" alt="工作区实录：配置子任务数量上限与允许的职责范围" width="960">
+
 <details>
 <summary>能力设置与可复现工作区场景</summary>
 
-<img src="docs/assets/personal-workspace/capability-1.0.webp" alt="工作区实录：配置子任务数量上限与允许的职责范围" width="960">
-
 在源码 checkout 中运行 `python -m demo.workspace serve`，可探索社区活动、家庭能源比较
 和社区网站发布三个复杂项目；每个项目有四个工作角色、18 项任务、两项决策与两项观察。
 上图来自这份可复现工作区。[场景与回放说明](demo/workspace/README.md)。
@@ -301,9 +301,6 @@ OpenViking 的公开贡献序列与脱敏的 owner-run Auto ML showcase 各自
 wall-clock 时间，不是连续模型执行时长或无人值守的生产自治。点击原图查看
 公开安全的任务图、证据分支和跨轮决策；各案例分别说明来源与可复现边界。
 
-<details>
-<summary>早期 200+ 小时项目轨迹：OpenViking 与 ML 实验</summary>
-
 ### 开源 Issue Fix
 
 **超过 200 小时的公开贡献轨迹：Focused PR 交付与可复用修复知识互相反哺。**
@@ -312,6 +309,9 @@ wall-clock 时间，不是连续模型执行时长或无人值守的生产自治
   <img src="docs/assets/long-running-loop-openviking-trajectory.png" alt="开源 Issue Fix 轨迹：连接 Focused PR 交付与 LoopX 通用能力沉淀" width="760">
 </a>
 
+<details>
+<summary>贡献来源与证据边界</summary>
+
 LoopX 的创建者以
 [OpenViking contributor](https://github.com/volcengine/OpenViking/pulls?q=is%3Apr+author%3Ahuangruiteng)
 身份把这条路径用于持续的 issue-to-PR 修复。图中公开贡献序列从首个 PR 创建到
@@ -320,6 +320,8 @@ LoopX 的创建者以
 repository context、带 revision 的修复知识和 reviewer-facing preference
 分开管理；所链接 PR 与当前 checkout 的源码、测试始终具有最高权威。
 
+</details>
+
 ### Auto ML Experiment
 
 **经过脱敏的 owner-run showcase：超过 200 小时的实验轨迹把假设、matched
@@ -332,8 +334,6 @@ evidence、无效谱系、运行中复现和 promote / stop gate 留在同一张
 这张 public-safe graph 保留了该 200+ 小时自然时间窗口中的决策谱系。它是
 owner-run showcase，不代表连续算力执行、独立复现或生产结果。
 
-</details>
-
 ### 真实项目中的使用
 
 - **外部独立用户 · `>13h` C++ 精度修复。** 用户报告多阶段任务持续对齐目标，

docs/development/design.md

@@ -223,6 +223,13 @@ Choose a default treatment by the user's task, before choosing components:
 | Definitions, methodology and routine provenance | One named contextual entry for the related region | Shared help or existing details, without repeating it inside every row |
 | Failure, stale evidence, unknown result, missing permission or consequential cost | A concise marker at the affected item/action, including disagreement that changes trust | Cause, recovery instructions and full evidence |
 
+README product illustrations and evidence diagrams belong in the default reading
+flow, with concise captions and material evidence limits. Fold supporting
+explanations, setup instructions and source detail after the visual; do not hide
+the illustration inside those disclosures when simplifying the page.
+README 的产品配图与证据图应默认展示，并保留简短图注和必要的证据边界；详细解释、
+配置步骤与来源说明可在图后折叠，精简页面时不要把图一起隐藏。
+
 Repeated items must not default to a stack of full documents. For example, a
 supporting-outcome list must not render every requirement, Agent review and
 independent-check explanation before the reader reaches the next main region.