connect DEV to live MCP configuration and verify tool conformance

This commit is contained in:
2026-09-29 10:36:50 +01:00
parent 20bbbd26bd
commit 9592c9b274
16 changed files with 417 additions and 18 deletions
@@ -62,6 +62,35 @@ and [tools](https://modelcontextprotocol.io/specification/2025-06-18/server/tool
contracts. Optional SSE, server-initiated requests, sampling, prompts, resource
subscriptions and list-change notifications are not advertised.
### 1.1 DEV Connection Assistance
DEV displays the current endpoint without credentials and provides **Copy MCP
configuration** for an open project. The neutral `AgentConnectionGuide` supplies
availability and a deliberate clipboard export; JavaFX MUST NOT depend on the
HTTP server or keep credentials in labels, diagnostics, project state or history.
Connection lifecycle changes refresh availability. A closed project or stopped
server cannot export a descriptor. Unloading DEV only unsubscribes presentation
listeners; it does not stop the endpoint or revoke project authority.
The copied text is a provider-neutral JSON descriptor with `transport` set to
`streamable-http`, the live `url`, `headers.Authorization`, canonical `projectRoot`
and `instructions`. It is not a promise of a drop-in configuration format for
every external client. The developer maps URL/header fields to that client's MCP
configuration; a provider-specific wizard remains out of scope. The secret is
materialized only for explicit copying and MUST NOT be written to versioned files
or logs. Clipboard success/failure feedback MUST NOT repeat credential-bearing
content or raw exceptions. The clipboard itself is a deliberate secret export.
Copied instructions and MCP initialization guidance direct the client to discover
actual tools, read project context and applicable language/SDK/library references,
wait for human grant before acquisition, edit saved files within project scope,
validate with LSP/build, recover operation receipts by clientRequestId and release
explicitly. Missing language support is a reported limitation, not a PBS fallback.
They also explain that SDK/external libraries are read-only, revocation cannot
stop external file writes, copying grants no authority, and a Studio restart
requires fresh endpoint/token configuration. No provider or model is required
to test this guidance and the MCP service contract.
## 2. Identity and Admission
All tool inputs require `projectRoot`: an absolute filesystem root resolving to
@@ -405,6 +434,9 @@ and `studio_language_query`, plus control acquire/release, build start and opera
get/cancel as of step 20 (eight tools). Headless handlers are implemented and
tested against the neutral port, but are advertised only when a real
`HeadlessGateway` is composed in the integration phase. No fake runtime is shipped.
DEV configuration-copy stays unavailable until step 21. Passing this transport
gate is not the phase 3 or final external-agent acceptance gate. API/Core and
DEV configuration-copy is connected as of step 21. The automated HTTP conformance
gate exercises all 17 tool contracts using real project knowledge/LSP and test-only
build/runtime ports; a separate HTTP test uses the real compiler/packer. This
completes MCP-phase conformance, not real-process or external-agent acceptance.
API/Core and
JavaFX MUST NOT import MCP/HTTP implementations; architecture tests enforce it.