docs(rfc): define truthful Goal workspace composition and return metrics

docs/architecture/rfcs/README.md

@@ -101,7 +101,7 @@ failure leaves the generated files untouched.
 - [LoopX Overall Roadmap v0](loopx-overall-roadmap-v0.md)
   ([中文版](loopx-overall-roadmap-v0.zh-CN.md))
   - **Delivery on `main`:** Planning and audit evidence, not runtime promotion.
-  - **Current boundary:** Maps all 30 pre-existing primary RFCs and important
+  - **Current boundary:** Maps every primary RFC and important
     non-RFC domains into 13 streams, G0–G5 product milestones and R1–R7 core
     execution cards. Covers product, multi-LoopX-Agent collaboration/handoff,
     kernel, hosts, memory, cost, security, operations, research, releases,
@@ -422,6 +422,15 @@ failure leaves the generated files untouched.
     Lark operation cards. Direct Goal workspace navigation and Overview compose
     bounded graph/acceptance readback, source navigation and snapshot export. General cross-channel disclosure,
     living documents and governed amendment/settlement review remain open.
+- [Goal Workspace Surface v0](goal-workspace-surface-v0.md)
+  ([中文版](goal-workspace-surface-v0.zh-CN.md))
+  - **Delivery on `main`:** Proposal only; Overview, Tasks, Chat, Files, the W1
+    map, usage, acceptance readback and lifecycle stop ship as separate regions.
+  - **Current boundary:** Owns one Goal page's composition and the display
+    semantics of its vitals: persistent masthead with scoped Stop, window- and
+    coverage-labeled figures, work grouped by owner, all-work rail, shared
+    selection and since-last-look delta. M1 requires first-screen preview
+    approval. No new authority, Todo field, lifetime usage or Lark parity.
 - [Live Team Workspace v0](live-team-workspace-v0.md)
   ([中文版](live-team-workspace-v0.zh-CN.md))
   - **Delivery on `main`:** Design proposal only; no live team-stream qualification.

docs/architecture/rfcs/STATUS.md

@@ -18,7 +18,7 @@ appendix may keep dated history, but no dated log heading may precede it.
 
 [中文版](STATUS.zh-CN.md) is the semantic mirror of this file.
 
-## Accepted (43)
+## Accepted (44)
 
 | RFC | Header status | Supersedes / closes | Ledger |
 | --- | --- | --- | --- |
@@ -42,6 +42,7 @@ appendix may keep dated history, but no dated log heading may precede it.
 | [Goal Instance Identity and Orphan Recovery (v0)](goal-instance-identity-and-orphan-recovery-v0.md) | Accepted | none | — |
 | [RFC: Goal-scoped Capability Portfolio and Connector Lifecycle (v0)](goal-scoped-capability-portfolio-v0.md) | Accepted | none | — |
 | [RFC: Per-Goal Usage, Token, and Cost Surfacing v0](goal-usage-token-cost-v0.md) | Accepted | none | — |
+| [RFC: Goal Workspace Surface v0](goal-workspace-surface-v0.md) | Accepted | none | — |
 | [DSH / Pi: L1 Observation and Managed Runtime Selection](harness-selection-dsh-pi-v0.md) | Accepted | none | — |
 | [RFC: Hierarchical Agent Stride Control v0](hierarchical-agent-stride-control-v0.md) | Accepted | none | — |
 | [RFC: Human Attention Wishlist v0](human-attention-wishlist-v0.md) | Accepted | none | — |

docs/architecture/rfcs/STATUS.zh-CN.md

@@ -15,7 +15,7 @@
 
 [English](STATUS.md) 与本文互为语义镜像。
 
-## 已接受 (43)
+## 已接受 (44)
 
 | RFC | 头部状态 | 替代 / 关闭 | Ledger |
 | --- | --- | --- | --- |
@@ -39,6 +39,7 @@
 | [Goal 实例身份与孤儿状态恢复（v0）](goal-instance-identity-and-orphan-recovery-v0.zh-CN.md) | 已接受 | 无 | — |
 | [RFC：Goal 级能力组合与 Connector 生命周期（v0）](goal-scoped-capability-portfolio-v0.zh-CN.md) | 已接受 | 无 | — |
 | [RFC: Per-Goal Usage, Token, and Cost Surfacing v0](goal-usage-token-cost-v0.md) | 已接受 | none | — |
+| [RFC：Goal 工作区页面 v0](goal-workspace-surface-v0.zh-CN.md) | 已接受 | 无 | — |
 | [DSH / Pi：L1 观察与 Managed Runtime 选型](harness-selection-dsh-pi-v0.zh-CN.md) | 已接受 | 无 | — |
 | [RFC：长程 Agent 分层步幅控制 v0](hierarchical-agent-stride-control-v0.zh-CN.md) | 已接受 | 无 | — |
 | [RFC：Human Attention Wishlist v0](human-attention-wishlist-v0.zh-CN.md) | 已接受 | 无 | — |

docs/architecture/rfcs/goal-usage-token-cost-v0.md

@@ -191,6 +191,11 @@ The slice must prove:
 4. Whether to add a dedicated `/usage.json` endpoint or continue surfacing
    through the existing status payload (this RFC assumes the latter).
 5. The duration capture anchor — which run boundary events delimit wall-time.
+6. Lifetime and coverage. The [Goal workspace](goal-workspace-surface-v0.md)
+   vitals show window-labeled cost and Agent time (its D2/D4). Should this owner
+   add an aggregate since Goal creation, with retention disclosure, and an
+   explicit field for measured versus observed runtimes? Until then consumers
+   must not sum windows into a lifetime figure or render absent cost as zero.
 
 ## Public References