Add post-4.0 chat product roadmap

Extend the chat ergonomics roadmap now that the core workspace and MCP path are in place for the narrowed chat-host persona.

Add the next planned phase around project-aware chat startup, host bootstrap and repair, reviewable agent output, opinionated use-case modes, and faster daily loops so the roadmap keeps pushing toward a repo-aware daily tool instead of a generic VM or SDK story.

Document the constraints explicitly: optimize the MCP/chat-host path first, keep disk tools secondary, and take advantage of the current no-users-yet window to make breaking product-shaping changes when needed.

docs/roadmap/llm-chat-ergonomics.md

@@ -8,10 +8,13 @@ interface.
 
 Current baseline is `4.0.0`:
 
-- the stable workspace contract exists across CLI, SDK, and MCP
-- one-shot `pyro run` still exists as the narrow entrypoint
+- `pyro mcp serve` is now the default product entrypoint
+- `workspace-core` is now the default MCP profile
+- one-shot `pyro run` still exists as the terminal companion path
 - workspaces already support seeding, sync push, exec, export, diff, snapshots,
   reset, services, PTY shells, secrets, network policy, and published ports
+- host-specific onramps exist for Claude Code, Codex, and OpenCode
+- the five documented use cases are now recipe-backed and smoke-tested
 - stopped-workspace disk tools now exist, but remain explicitly secondary
 
 ## What "Trivial In Chat" Means
@@ -33,9 +36,16 @@ More concretely, the model should not need to:
 - choose from an unnecessarily large tool surface when a smaller profile would
   work
 
-The remaining UX friction for a technically strong new user is now narrower:
+The next gaps for the narrowed persona are now product-shaping rather than raw
+capability gaps:
 
-- no major chat-host ergonomics gaps remain in the current roadmap
+- starting from the current repo still needs to feel native from the first chat
+- host setup and repair still lean on manual commands and config copying
+- reviewing what the agent actually did still requires digging through several
+  surfaces
+- the five use cases exist as docs and smokes, not yet as explicit product
+  modes
+- daily reset and retry loops can still feel heavier than they should
 
 ## Locked Decisions
 
@@ -43,9 +53,16 @@ The remaining UX friction for a technically strong new user is now narrower:
   or runner abstractions
 - keep disk tools secondary and do not make them the main chat-facing surface
 - prefer narrow tool profiles and structured outputs over more raw shell calls
-- capability milestones should update CLI, SDK, and MCP together
+- optimize the MCP/chat-host path first and keep the CLI companion path good
+  enough to validate and debug it
+- lower-level SDK and repo substrate work can continue, but they should not
+  drive milestone scope or naming
 - CLI-only ergonomics are allowed when the SDK and MCP surfaces already have the
   structured behavior natively
+- prioritize repo-aware startup, trust, and daily-loop speed before adding more
+  low-level workspace surface area
+- breaking changes are acceptable while there are still no users and the
+  chat-host product is still being shaped
 - every milestone below must also update docs, help text, runnable examples,
   and at least one real smoke scenario
 
@@ -62,6 +79,11 @@ The remaining UX friction for a technically strong new user is now narrower:
 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) - Done
 10. [`3.11.0` Host-Specific MCP Onramps](llm-chat-ergonomics/3.11.0-host-specific-mcp-onramps.md) - Done
 11. [`4.0.0` Workspace-Core Default Profile](llm-chat-ergonomics/4.0.0-workspace-core-default-profile.md) - Done
+12. [`4.1.0` Project-Aware Chat Startup](llm-chat-ergonomics/4.1.0-project-aware-chat-startup.md) - Planned
+13. [`4.2.0` Host Bootstrap And Repair](llm-chat-ergonomics/4.2.0-host-bootstrap-and-repair.md) - Planned
+14. [`4.3.0` Reviewable Agent Output](llm-chat-ergonomics/4.3.0-reviewable-agent-output.md) - Planned
+15. [`4.4.0` Opinionated Use-Case Modes](llm-chat-ergonomics/4.4.0-opinionated-use-case-modes.md) - Planned
+16. [`4.5.0` Faster Daily Loops](llm-chat-ergonomics/4.5.0-faster-daily-loops.md) - Planned
 
 Completed so far:
 
@@ -95,7 +117,11 @@ Completed so far:
 
 Planned next:
 
-- no further chat-ergonomics milestones are currently planned in this roadmap.
+- [`4.1.0` Project-Aware Chat Startup](llm-chat-ergonomics/4.1.0-project-aware-chat-startup.md)
+- [`4.2.0` Host Bootstrap And Repair](llm-chat-ergonomics/4.2.0-host-bootstrap-and-repair.md)
+- [`4.3.0` Reviewable Agent Output](llm-chat-ergonomics/4.3.0-reviewable-agent-output.md)
+- [`4.4.0` Opinionated Use-Case Modes](llm-chat-ergonomics/4.4.0-opinionated-use-case-modes.md)
+- [`4.5.0` Faster Daily Loops](llm-chat-ergonomics/4.5.0-faster-daily-loops.md)
 
 ## Expected Outcome
 
@@ -117,3 +143,8 @@ The intended model-facing shape is:
 - 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
+- starting from the current repo feels native from the first chat-host setup
+- supported hosts can be connected or repaired without manual config spelunking
+- users can review one concise summary of what the agent changed and ran
+- the main workflows feel like named modes instead of one giant reference
+- reset and retry loops are fast enough to encourage daily use