compose real headless runtime with task build and lifecycle

This commit is contained in:
2026-09-29 11:27:42 +01:00
parent bc76f08bbd
commit 379420e7a9
10 changed files with 272 additions and 27 deletions
@@ -293,6 +293,15 @@ from that session and are enforced without clamping. Shutdown detaches only afte
managed cleanup finishes. Runtime process supervision and protocol mapping belong
to the application gateway delivered in step 22, not to MCP or the test doubles.
Reset leaves the attached process unbooted, marks the previous capture stale and
retains its build association. A subsequent explicit `studio_headless_boot` with
that same current buildId reboots the known cartridge within the session. Boot
without reset while a runtime is attached is rejected as busy. Reset does not
change task authority or implicitly start execution. Rebuilding ends and detaches
that process, invalidates previous buildIds and requires a fresh explicit boot.
Synchronous headless failures finish their worker before returning the error,
so a corrective call cannot race the failed worker's admission lock.
Task-local operation/build records are discarded after worker termination on
return, revocation or project closure. Cleanup failures never restore authority;
the records are still discarded after managed work stops. Neither connection
@@ -429,14 +438,17 @@ authentication, Origin, endpoint/method/version handling, tool dispatch, malform
or oversized input, closure, restart and old-token rejection. Provider doubles
exist only in tests. Composition starts/closes transport with Studio.
The production registry composes `studio_project_context`, `studio_reference_read`
and `studio_language_query`, plus control acquire/release, build start and operation
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.
The production registry composes all 17 tools as of step 23, including headless
handlers bound to the actual `HeadlessProcessGateway`. Missing project runtime
configuration fails at boot with `RUNTIME_UNAVAILABLE`; tool discovery does not
grant authority or launch a process. No fake runtime is shipped.
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.
completes MCP-phase conformance. The packaged-runtime gate additionally exercises
actual app composition, project LSP, compiler/packer, saved edits, explicit
reset/reboot, build identity invalidation and corrective loops after compile
errors/guest faults. Full HTTP/visual and external-agent acceptance remain
subsequent integration gates, not implied by this service-composition gate.
API/Core and
JavaFX MUST NOT import MCP/HTTP implementations; architecture tests enforce it.