feat(studio): integrate project MCP setup and lifecycle
This commit is contained in:
@@ -84,3 +84,14 @@ Normative reminders:
|
||||
- the Studio backend is exposed through neutral API contracts shared by JavaFX and the local MCP adapter, without duplicated authority or orchestration;
|
||||
- Spring Boot remains the desktop composition root with the narrow DEC-0060 local MCP HTTP exception; Spring Modulith still verifies the JavaFX-free `p.studio.core` boundary;
|
||||
- `p.studio.Container`, `AppContainer`, and the mixed `prometeu-studio` module are not valid final architecture.
|
||||
|
||||
## Integrated MCP connection
|
||||
|
||||
DEC-0061 revises the baseline with Studio-owned `mcp --project` mode, grant-time
|
||||
project discovery, scoped HTTP credentials, one-time scaffold/preparation and a
|
||||
stable installation with bundled Java. Specs 8–11 define the lifecycle and
|
||||
transport boundaries; spec 1 defines project creation. PLN-0140 is complete;
|
||||
automated results and user-confirmed manual acceptance are consolidated in
|
||||
[LSN-0077](../../../discussion/lessons/DSC-0070-studio-persistent-mcp-connector/LSN-0077-integrated-mcp-stable-setup-and-ephemeral-access.md).
|
||||
The earlier HTTP evidence was not substituted for these gates. The embedded
|
||||
terminal remains separate.
|
||||
|
||||
Reference in New Issue
Block a user