Add next chat UX roadmap milestones

Capture the next UX pass after the workspace-core readiness review so the roadmap reflects the remaining friction a new chat-host user still feels.

Add milestones for trustworthy use-case smoke coverage, host-specific Claude/Codex/OpenCode MCP onramps, and the planned 4.0 default flip to workspace-core so the bare server entrypoint finally matches the recommended path.

This is a docs-only roadmap update based on the live use-case review and integration validation, with the full advanced surface kept as an explicit opt-in rather than the default.

docs/roadmap/llm-chat-ergonomics.md

@@ -37,6 +37,12 @@ The remaining UX friction for a technically strong new user is now narrower:
 
 - the recommended chat-host onramp is now explicit, but human-mode file reads
   still need final transcript polish for copy-paste and chat logs
+- the five use-case smokes now exist, but the advertised smoke pack is only as
+  trustworthy as its weakest scenario and exact recipe fidelity
+- generic MCP guidance is strong, but Codex and OpenCode still ask the user to
+  translate the generic config into host-specific setup steps
+- `workspace-core` is clearly the recommended profile, but `pyro mcp serve` and
+  `create_server()` still default to `workspace-full` for `3.x` compatibility
 
 ## Locked Decisions
 
@@ -60,6 +66,9 @@ The remaining UX friction for a technically strong new user is now narrower:
 6. [`3.7.0` Handoff Shortcuts And File Input Sources](llm-chat-ergonomics/3.7.0-handoff-shortcuts-and-file-input-sources.md) - Done
 7. [`3.8.0` Chat-Host Onramp And Recommended Defaults](llm-chat-ergonomics/3.8.0-chat-host-onramp-and-recommended-defaults.md) - Done
 8. [`3.9.0` Content-Only Reads And Human Output Polish](llm-chat-ergonomics/3.9.0-content-only-reads-and-human-output-polish.md) - Done
+9. [`3.10.0` Use-Case Smoke Trust And Recipe Fidelity](llm-chat-ergonomics/3.10.0-use-case-smoke-trust-and-recipe-fidelity.md)
+10. [`3.11.0` Host-Specific MCP Onramps](llm-chat-ergonomics/3.11.0-host-specific-mcp-onramps.md)
+11. [`4.0.0` Workspace-Core Default Profile](llm-chat-ergonomics/4.0.0-workspace-core-default-profile.md)
 
 Completed so far:
 
@@ -84,6 +93,20 @@ Completed so far:
 - `3.9.0` added content-only workspace file and disk reads plus cleaner default human-mode
   transcript separation for files that do not end with a trailing newline.
 
+Planned next:
+
+- `3.10.0` makes the use-case recipe set fully trustworthy by requiring
+  `make smoke-use-cases` to pass cleanly, aligning recipe docs with what the
+  smoke harness actually proves, and removing brittle assertions against
+  human-mode output when structured results are already available.
+- `3.11.0` adds exact host-specific onramps for Claude, Codex, and OpenCode so
+  a new chat-host user can copy one known-good config or command instead of
+  translating the generic MCP example by hand.
+- `4.0.0` flips the default MCP profile from `workspace-full` to
+  `workspace-core` so the no-flag server entrypoint finally matches the
+  recommended docs path, while keeping explicit opt-in access to the full
+  advanced surface.
+
 ## Expected Outcome
 
 After this roadmap, the product should still look like an agent workspace, not
@@ -98,5 +121,9 @@ The intended model-facing shape is:
 - shells are readable in chat
 - CLI handoff paths do not depend on ad hoc shell parsing
 - the recommended chat-host profile is obvious from the first MCP example
+- the documented smoke pack is trustworthy enough to use as a release gate
+- major chat hosts have copy-pasteable MCP setup examples instead of only a
+  generic config template
 - human-mode content reads are copy-paste safe
+- the default bare MCP server entrypoint matches the recommended narrow profile
 - the five core use cases are documented and smoke-tested end to end