Show adoption evidence beside team reports

[huangruiteng]

Problem and resulting behavior

The Goal conversation already opens accepted team artifacts, but its report reader hid requester adoption behind a generic “Acceptance and adoption” disclosure. An accepted source report looked the same whether nobody had adopted it, a downstream accepted result had used it, or that adoption evidence was unavailable.

The existing disclosure now states the observed adoption state above the readable report. A current adoption opens its versioned downstream report through the existing readback path. Missing adoption, unavailable adoption evidence, and a downstream report that references source versions retain distinct labels. This does not infer adoption from an accepted artifact or start a model while reading.

Visual and interaction evidence

• Before: the report started with “currently accepted”; the adoption state was hidden behind a generic disclosure below the report.
• After: one compact status line appears before the report. It opens the existing lineage details and downstream-result link, without adding another card or activity feed. The browser scenario captured both the source and downstream views at desktop width; keyboard focus and mobile overflow remain covered by the existing team-evidence scenario.
• A partial inventory still says that some work cannot be verified. The report and its adoption status come only from the accepted operation readback.

Validation

• npm run build passed on the final source and packaged chat assets.
• npm run smoke:personal-workspace-packaged passed all nine scenarios on the final rebased and packaged assets, including adoption state, downstream readback, unavailable evidence, and no model restart.
• Exact-scope change-quality receipt cqr_4135bffeb2617b54f604 is valid for seven changed files; no safe-fix pass or unresolved risk.
• loopx canary premerge --from-git-diff --goal-id loopx-meta passed: seven selected canaries and the public-boundary check, with no failures or manual holds.

The changed entry point is the Goal conversation in the packaged frontend. The Lark and CLI readback contracts are unchanged. This is one product slice: manager-originated requests still need their completed research result returned to the manager's original conversation, and real multi-agent launch/acceptance remains a separate open acceptance gap.

Future-facing review: the typed readback and existing disclosure already own this behavior; no related extraction or new state model improves this change.