[Feat] Add paired partnership guidance for MCP clients

[roomote-roomote]

​Opened on behalf of @daniel-lxs. View the task or mention @roomote-roomote for follow-up asks.

What changed

• Add the Fast-only packaged roomote-partnership skill with paired Roomote and client guidance for joint investigations, design or prompt reviews, and sustained discussions.
• Keep startup quiet and client-initiated: one bundled evidence-bearing request asks for an exact-name load only when needed, and Roomote reports load state in one line inside its substantive reply.
• Keep coordination evidence internal by default. Client and Roomote guidance foreground customer-relevant findings, decisions and tradeoffs, progress, limitations, blockers, and needed input; labeled relays are shown only when the user asks.
• Qualify the generic manage_tasks description with the same customer-facing output rule without changing its API shape, response types, or skill catalog.
• Update the Worker MCP tool-description test to match the generic on-request relay wording, merge the latest develop changes while preserving both type exports, and refresh the docs, tests, and existing changeset.

Why this change was made

The Roomote review check correctly found a stale Worker assertion after the shared management description stopped requiring default Client relay labels. The merge resolution also needed to preserve the partnership export alongside develop's new artifact export. No runtime MCP schema or parser behavior changed for this review fix.

Impact

The Worker MCP descriptor test now validates customer-facing synthesis and Agent → Roomote / Roomote → Agent labels only when the user asks to see the exchange. The PR's Roomote code review check now passes at 661e94e; the review summary reports no code issues and the finding is resolved. Worker tool-description tests pass 50/50; types and Worker typechecks pass. The clean origin/develop checkout passes @roomote/web check-types:fast, and the final normal pre-push checks pass 27/27 fast typechecks, residual lint, and knip after a fresh dependency install. The earlier local hook failure was stale dependency state, not a develop or source failure. No merge, approval, deploy, or issue action was performed.

[roomote-community]

No code issues found. See task

• Worker MCP tool-description test now expects the Agent → Roomote / Roomote → Agent labels.

_{Reviewed 661e94e}

[roomote-roomote]

Resolved on the existing PR branch at commit 661e94e:

• Updated the Worker MCP tool-description test to assert the generic customer-facing synthesis wording and on-request Agent → Roomote / Roomote → Agent relays without changing the schema.
• Merged the latest develop into the PR branch and preserved both the partnership and artifact type exports.
• The Roomote code review check now passes and reports no code issues. Worker tool-description tests pass 50/50; the resolved review thread and checklist are current.