53 lines
2 KiB
Markdown
53 lines
2 KiB
Markdown
# `5.0.0` Whole-Project Sandbox Development
|
|
|
|
Status: Planned
|
|
|
|
## Goal
|
|
|
|
Reach the point where it is credible to tell a user they can develop a real
|
|
project inside sandboxes, not just validate, inspect, or patch one.
|
|
|
|
## Public API Changes
|
|
|
|
No new generic VM breadth is required here. This milestone should consolidate
|
|
the earlier pieces into one believable full-project product story:
|
|
|
|
- robust project-aware startup
|
|
- explicit environment selection in the chat-host path
|
|
- summaries, reset, export, and service workflows that hold up during longer
|
|
work loops
|
|
- qualification targets that prove a nontrivial development cycle
|
|
|
|
## Implementation Boundaries
|
|
|
|
- keep the product centered on the chat-host workspace path rather than a broad
|
|
CLI or SDK platform story
|
|
- use the existing named modes and generic workspace path where they fit, but
|
|
teach one end-to-end full-project development walkthrough
|
|
- prioritize daily development credibility over adding new low-level sandbox
|
|
surfaces
|
|
|
|
## Non-Goals
|
|
|
|
- no attempt to become a generic remote dev environment platform
|
|
- no scheduler, queue, or CI matrix abstractions
|
|
- no claim that every possible project type is equally well supported
|
|
|
|
## Acceptance Scenarios
|
|
|
|
- the docs contain one end-to-end “develop a project in sandboxes” walkthrough
|
|
- that walkthrough covers dependency install, tests, patching, reruns, review,
|
|
and export, with app/service startup when relevant
|
|
- at least one guest-backed qualification target proves the story on a
|
|
nontrivial project
|
|
- the readiness docs can honestly say whole-project development is supported
|
|
with explicit caveats instead of hedged aspirational language
|
|
|
|
## Required Repo Updates
|
|
|
|
- README, install docs, integrations docs, use-case docs, and public contract
|
|
updated to include the whole-project development story
|
|
- at least one walkthrough asset or transcript added for the new end-to-end
|
|
path
|
|
- readiness and troubleshooting docs updated with the actual supported scope and
|
|
remaining caveats
|