add milestones

docs/roadmap/llm-chat-ergonomics.md

@@ -36,16 +36,16 @@ More concretely, the model should not need to:
 - choose from an unnecessarily large tool surface when a smaller profile would
   work
 
-The next gaps for the narrowed persona are now product-shaping rather than raw
-capability gaps:
+The next gaps for the narrowed persona are now about real-project credibility:
 
-- 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
+- current-checkout startup is still brittle for messy local repos with unreadable,
+  generated, or permission-sensitive files
+- the guest-backed smoke pack is strong, but it still proves shaped scenarios
+  better than arbitrary local-repo readiness
+- the chat-host path still does not let users choose the sandbox environment as
+  a first-class part of host connection and server startup
+- the product should not claim full whole-project development readiness until it
+  qualifies a real-project loop beyond fixture-shaped use cases
 
 ## Locked Decisions
 
@@ -61,6 +61,14 @@ capability gaps:
   structured behavior natively
 - prioritize repo-aware startup, trust, and daily-loop speed before adding more
   low-level workspace surface area
+- for repo-root auto-detection and `--project-path` inside a Git checkout, the
+  default project source should become Git-tracked files only
+- `--repo-url` remains the clean-clone path when users do not want to trust the
+  local checkout as the startup source
+- environment selection must become first-class in the chat-host path before the
+  product claims whole-project development readiness
+- real-project readiness must be proven with guest-backed qualification smokes
+  that cover ignored, generated, and unreadable-file cases
 - 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,
@@ -84,6 +92,11 @@ capability gaps:
 14. [`4.3.0` Reviewable Agent Output](llm-chat-ergonomics/4.3.0-reviewable-agent-output.md) - Done
 15. [`4.4.0` Opinionated Use-Case Modes](llm-chat-ergonomics/4.4.0-opinionated-use-case-modes.md) - Done
 16. [`4.5.0` Faster Daily Loops](llm-chat-ergonomics/4.5.0-faster-daily-loops.md) - Done
+17. [`4.6.0` Git-Tracked Project Sources](llm-chat-ergonomics/4.6.0-git-tracked-project-sources.md) - Planned
+18. [`4.7.0` Project Source Diagnostics And Recovery](llm-chat-ergonomics/4.7.0-project-source-diagnostics-and-recovery.md) - Planned
+19. [`4.8.0` First-Class Chat Environment Selection](llm-chat-ergonomics/4.8.0-first-class-chat-environment-selection.md) - Planned
+20. [`4.9.0` Real-Repo Qualification Smokes](llm-chat-ergonomics/4.9.0-real-repo-qualification-smokes.md) - Planned
+21. [`5.0.0` Whole-Project Sandbox Development](llm-chat-ergonomics/5.0.0-whole-project-sandbox-development.md) - Planned
 
 Completed so far:
 
@@ -130,6 +143,14 @@ Completed so far:
   real `make smoke-daily-loop` verification path so the local machine warmup
   story is explicit before the chat host connects.
 
+Planned next:
+
+- [`4.6.0` Git-Tracked Project Sources](llm-chat-ergonomics/4.6.0-git-tracked-project-sources.md)
+- [`4.7.0` Project Source Diagnostics And Recovery](llm-chat-ergonomics/4.7.0-project-source-diagnostics-and-recovery.md)
+- [`4.8.0` First-Class Chat Environment Selection](llm-chat-ergonomics/4.8.0-first-class-chat-environment-selection.md)
+- [`4.9.0` Real-Repo Qualification Smokes](llm-chat-ergonomics/4.9.0-real-repo-qualification-smokes.md)
+- [`5.0.0` Whole-Project Sandbox Development](llm-chat-ergonomics/5.0.0-whole-project-sandbox-development.md)
+
 ## Expected Outcome
 
 After this roadmap, the product should still look like an agent workspace, not
@@ -155,3 +176,11 @@ The intended model-facing shape is:
 - 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
+- repo-root startup is robust even when the local checkout contains ignored,
+  generated, or unreadable files
+- chat-host users can choose the sandbox environment as part of the normal
+  connect/start path
+- the product has guest-backed qualification for real local repos, not only
+  shaped fixture scenarios
+- it becomes credible to tell a user they can develop a real project inside
+  sandboxes, not just evaluate or patch one