feat(studio): improve compiler reliability and AI diagnostics
Test / Tests and coverage occurred while executing withChecks step.
Intrepid/Prometeu/Studio/pipeline/pr-master There was a failure building this commit

Preserve structured diagnostics, source attribution, phase outcomes and revision context through compiler, Studio, LSP, MCP and JavaFX. Add project service discovery and resilient VS Code reconnection.

Correct all eight reproduced PBS production failures in expression context, sibling executable bindings and nominal owner identity. Consolidate specs, lessons, immutable baseline evidence and the maintained source-to-guest qualification runner.

Validation: required Gradle gate recorded 724 tests, with 711 passed and 13 skipped. Full corpus passed 168 compilation observations and 108 guest runs (104 successes and four deliberate faults); supplemental controls passed 42 compilations and 16 guest runs. TypeScript compilation, two Node discovery tests and discussion validation passed.
This commit is contained in:
2026-11-10 12:36:25 +00:00
parent 38f201a9c9
commit ea1cc26fe3
1216 changed files with 168017 additions and 354 deletions
@@ -208,3 +208,26 @@ writes before retrying cleanup. Canceling that confirmation sends no consent.
Neither task release, Stop, reclaim nor a timeout implicitly permits discard.
Forced termination remains infrastructure failure with unknown publication
outcome; it MUST NOT manufacture a durable save result.
## Project LSP endpoint discovery
An open project's Studio LSP adapter MUST atomically publish `.studio/lsp.json`
after its loopback server starts. Schema version 1 contains `schemaVersion`,
`projectRoot` (canonical filesystem path), `sessionId` (fresh for each boot),
`processId`, `host` (`127.0.0.1`) and `port` (the actual OS-assigned port).
Publication failure MUST stop the newly started server. Shutdown MUST stop the
server and remove discovery only when its session identity still owns the file.
The file is transient, unversioned, carries no credential and MUST be independent
of automation grants. It does not change the public LSP configuration default.
The VS Code extension MUST default to discovering this file for exactly one local
workspace project, validate schema/root/process/host/port, and initialize against
that canonical workspace. It MUST NOT silently select one of several roots or
fall back to a fixed port. Absent or dead-process discovery means waiting for
Studio; malformed metadata MUST be reported without connecting. File creation,
replacement or deletion and workspace/configuration changes MUST restart discovery.
Retries MUST use capped exponential backoff (2–30 seconds), reset after connection,
and stop at extension shutdown. Connection state MUST be visible without recurring
error popups. Explicit manual mode MAY use configured host/port for other hosts.
The server's project binding validation remains authoritative.