Clarify workspace-core as the chat-host onramp
Make the recommended MCP profile visible from the first help and docs pass without changing 3.x behavior. Rework help, top-level docs, public-contract wording, and shipped MCP/OpenAI examples so is the recommended first profile while stays the compatibility default for full-surface hosts. Bump the package and catalog to 3.8.0, mark the roadmap milestone done, and add regression coverage for the new MCP help and docs alignment. Validation included uv lock, targeted profile/help tests, make check, make dist-check, and a real guest-backed server smoke.
This commit is contained in:
parent
7a0620fc0c
commit
407c805ce2
17 changed files with 150 additions and 50 deletions
|
|
@ -4,9 +4,10 @@ Requirements:
|
|||
- `pip install openai` or `uv add openai`
|
||||
- `OPENAI_API_KEY`
|
||||
|
||||
This example mirrors the `workspace-core` MCP profile by deriving tool schemas
|
||||
from `Pyro.create_server(profile="workspace-core")` and dispatching tool calls
|
||||
back through that same profiled server.
|
||||
This is the recommended persistent-chat example. It mirrors the
|
||||
`workspace-core` MCP profile by deriving tool schemas from
|
||||
`Pyro.create_server(profile="workspace-core")` and dispatching tool calls back
|
||||
through that same profiled server.
|
||||
"""
|
||||
|
||||
from __future__ import annotations
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue