feat(studio): integrate project MCP setup and lifecycle
This commit is contained in:
@@ -142,3 +142,23 @@ This specification is complete enough when:
|
||||
- workspace and shell responsibilities are clearly separated;
|
||||
- the shell-level expectations for workspace architecture are explicit;
|
||||
- the baseline Studio frame is stable enough for implementation planning.
|
||||
|
||||
## Project Assistant Preparation (DEC-0061)
|
||||
|
||||
Project creation MUST scaffold neutral agent-integration intent in
|
||||
`.studio/setup.json` and invoke the same preparation port used by existing
|
||||
projects in DEV. Application infrastructure resolves installed Studio and client
|
||||
configuration; the wizard/Core MUST NOT serialize provider TOML or launch an
|
||||
agent. Failed preparation leaves a usable project with actionable incomplete
|
||||
readiness in DEV, never a false ready claim. Runtime/editor settings and unrelated
|
||||
client configuration MUST survive. Preparation grants no project control.
|
||||
|
||||
### Automatic preparation when opening a project
|
||||
|
||||
Opening a project MUST prepare its enabled MCP integration using the same neutral
|
||||
port as scaffold and DEV retry. Desktop composition MUST start the shared loopback
|
||||
server before project sessions become available; no external command or separate
|
||||
per-project desktop Run is required. Explicitly disabled integration MUST remain
|
||||
disabled. Preparation failure MUST remain visible in DEV readiness without blocking
|
||||
project use. Opening MUST NOT publish credentials or grant/acquire agent control.
|
||||
The coding client continues to own its configured stdio process and initial trust.
|
||||
|
||||
Reference in New Issue
Block a user