[YTwsy]

Team Cross can now run its existing, complete WebGUI inside the local ChatGPT Work/Codex plugin and let users select published material versions or annotations directly from the composer. For example, searching “连接池 v1” returns “连接池调查 · v1”; selecting it attaches a reference to that exact published version. The local stdio MCP connects to the existing authenticated loopback Core, with no public inbound endpoint or cloud backend.

Changes

• Add local plugin export/install/status/upgrade/remove commands, embedded MCP Apps resources, global/conversation entrypoints, and the shared WebGUI with host API, sandbox storage and form adapters.
• Add explicit “Bring into this conversation” handoff for selected fixed references, with delivery receipts and no automatic replay after an uncertain result.
• Add app-only Composer mention search and scoped resource reads for material versions and annotations. Recheck access on reads, preserve paging, and exclude unpublished/private content from search.
• Accept the desktop host's actual {query,path:[]} compatibility payload as well as {query}. Reject nonempty or invalid paths. This fixes the empty picker results seen with a query-only validator.
• Integrate the latest Meta workbench from PR feat: add space workbench and optional coordinator conversations #46 (7ee5a0a) without replacing its business implementation. Retain both sets of documentation/translations, regenerate both embedded builds, and explicitly allow the workbench UI routes while keeping internal delivery and arbitrary RPC routes blocked.
• Run engineering CI on PRs targeting Meta, including plugin package race tests and both embedded asset checks. Preserve the original local probes and scoped acceptance records.

Validation

The integrated tree (a45fa81) passed locally:

• go test ./..., go vet ./..., and race tests for collab, mcp, sharing, nativecodex, nativeclaude, service, cliinstall and pluginpack.
• Web check (886 translations), 144 tests in 13 files, browser and plugin production builds, CLI build, and Homebrew release-rendering tests.
• Isolated plugin lifecycle checks and real stdio/native app-server discovery and reads. Standard and desktop search payloads match; fixed versions, annotation paging, reply deduplication, cross-Core rejection and withdrawal rejection pass.
• A real browser with the production HTML in an opaque iframe and connect-src 'none': workbench and receiver-list reads, one explicit brief save and revision-1 readback, 1440/1024/768 CSS-pixel screenshots, light/dark themes, and no horizontal overflow or business-tool errors.
• Markdown relative links and git diff --check.

The user also confirmed the actual desktop picker and sent both a material-v1 mention and an annotation mention after the search fix. This confirms picker selection/display; it does not claim that a model analyzed the content. Browser host message/context receipts are simulated. This integration run sent no model input, created no execution fork or native receiver, and makes no new cross-device LAN/Tailcat or cloud-host claim. Dedicated test processes were closed; the user's installed demo plugin/Core were left in place.

Evidence: integration record, desktop mention fix and user acceptance.