[Task][RFC]: Deliver the live team correction and adoption workspace #5210

Outcome / 目标

交付可理解的团队纠正、验收与采纳工作区。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree.

Canonical design: RFC. Roadmap: S3/S5/S7 · R2/R3, under #4574. Design acceptance is distinct from implementation, live qualification and promotion.

Current boundary

Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim.

#4828 shipped Goal Chat result/comparison and bounded team inspection. The RFC’s current L1 correction episode and L2 continuous-team qualification remain the acceptance targets; #4376 is an existing open workspace implementation.

Work remaining

• Complete one visible objection → revised artifact → independent acceptance → requester adoption episode using existing source/receipt identities.
• Include correction/stop feedback, evidence navigation, reconnect and original-coordinator continuation. Qualify two cycles before sustained-team claims; scale/semantic zoom follows that result.

Ownership and ongoing work

Reuse #4376, #4339 and #3786 plus the App conversation tracker. Current execution/return work is active. Do not create another orchestration store, demand a 3D rewrite or raise concurrency before the RFC’s L1/L2 exits.

Contribution route: implementation/integration overlaps active work. Start from the linked current owners/PRs and identify an unowned acceptance gap in a claim comment; do not begin a competing rewrite.

Acceptance

• A user can identify the claim that changed, why it changed and the accepted adopted revision in the packaged frontend and CLI.
• Quiet/failed/stale/disconnected states are truthful; scoped stop does not claim unowned work stopped.
• No synthetic activity is shown as live; repeated events, late results and reconnect do not duplicate progress or lose evidence.
• Reconcile the RFC's current delivery checkpoint and this issue with the integrated revision, commands, passed/failed/untested evidence and remaining gates. Close the accepted scope only; no claim that a merged PR alone completes the RFC.

Starting points and delivery boundary

• apps/presentation/dashboard/src/features/personal-workspace
• loopx/control_plane/collaboration
• docs/product/use-cases/steward/golden-queries.md

Base: latest main. Reuse the existing typed owner and provider boundaries. Include affected CLI/frontend/Lark companions; verify real entrypoints and backend where changed. Preserve existing first-screen review and maintainer merge gates. Public artifacts contain only synthetic/public-safe evidence, no private operational state. This task does not authorize provider promotion, benchmark launches, release/deployment or unrelated protected effects.