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
+33 -11
View File
@@ -7,7 +7,8 @@ This extension does **not** start the language server itself. It connects to the
```text
VS Code Extension
-> vscode-languageclient
-> TCP 127.0.0.1:7775
-> project-local .studio/lsp.json
-> TCP 127.0.0.1:<project-port>
-> Prometeu Studio Java/LSP4J
```
@@ -18,11 +19,10 @@ VS Code Extension
* VS Code
* Prometeu Studio running with the embedded LSP server enabled
The Studio LSP server must be listening on:
```text
127.0.0.1:7775
```
Open the same project in Studio and in the Extension Development Host. Studio
publishes its OS-assigned loopback LSP port in `.studio/lsp.json`. Discovery is
automatic and independent of an automation grant. Rebuild/restart older Studio
versions first: they do not publish this file.
## Install dependencies
@@ -80,10 +80,9 @@ View -> Output -> Prometeu LSP
```text
Prometeu VS Code extension activated.
Connecting to Prometeu Studio LSP at 127.0.0.1:7775...
Connecting to 127.0.0.1:<project-port>
TCP connection established with Prometeu Studio.
Prometeu Studio LSP client started.
[Info] Hello from Prometeu Studio LSP
Connected to Studio at 127.0.0.1:<project-port>
```
## Run commands manually
@@ -131,16 +130,39 @@ With Prometeu Studio running, opening `.pbs` or `.barrel` files should activate
## Configuration
Default settings:
Automatic discovery is the default:
```json
{
"prometeu.studio.connectionMode": "auto"
}
```
Open exactly one local project folder (the folder containing `prometeu.json`).
The extension validates the canonical project root, schema, loopback endpoint and
Studio process. It watches discovery changes and reconnects after a Studio
restart. Missing discovery means “Waiting for Studio” in the status bar; retries
increase from 2 seconds to at most 30 seconds without repeated error dialogs.
Click the status item to retry immediately. Transient discovery is not versioned.
For a separately hosted LSP or an older Studio, explicitly select manual mode:
```json
{
"prometeu.studio.connectionMode": "manual",
"prometeu.studio.host": "127.0.0.1",
"prometeu.studio.port": 7775
}
```
These can be changed in VS Code settings if needed.
Host/port settings apply only in manual mode. Changing connection settings restarts
the client. Automatic discovery never falls back to the fixed port.
Run discovery regressions after compiling:
```sh
node --test out/test/discovery.js
```
## Current status