feat(pbs): resolve editorial chains and expose read-only external sources
Intrepid/Prometeu/Studio/pipeline/head Build started...
Test / Build skipped: 16, passed: 838
Intrepid/Prometeu/Studio/pipeline/pr-master This commit looks good

This commit is contained in:
2026-10-07 09:00:31 +01:00
parent d0737df0ac
commit 967b9ec598
38 changed files with 1856 additions and 42 deletions
+28
View File
@@ -153,3 +153,31 @@ The extension currently provides only the minimal LSP client bridge:
* receives LSP messages from the Java/LSP4J server
The Studio remains the source of trut
## Reading SDK/core and libraries
F12 opens bundled SDK/core and admitted dependency declarations as read-only
`prometeu-source:` documents. Hover, continued F12 and semantic highlighting work
inside them. Files in the editable project keep normal `file:` editing. A library
under `.workspace` is still external. SDK/core are never copied to an editorial
folder or cache. Formatting, rename and code actions cannot change external sources;
a proposal touching both project and dependency files is refused in full.
An open external document keeps its source revision. Disconnect leaves its text
visible, with queries unavailable until reconnection and revalidation. If the
source changed, navigate again from the project to obtain new text and positions.
The status bar indicates when an active external source is unavailable.
Compile with `npm run compile` before running the extension. Development acceptance
can launch an isolated real VS Code host against the test LSP classpath:
```sh
PROMETEU_VSCODE_DEV_TEST=1 ./gradlew :prometeu-lsp:prometeu-lsp-v1:test --tests '*ExternalSourceDevelopmentHostTest' --console=plain
```
Run that Gradle command from the repository root. Set `PROMETEU_VSCODE_EXECUTABLE`
when VS Code is not installed at the default macOS application path. The test covers
read-only typing, declaration ranges, hover/F12, highlighting, dependency sources
with Unicode/CRLF, reconnection and normal project editing. It does not validate a
packaged Studio distribution or installed JAR. Dependencies must already exist on
disk; dependency management remains a separate product task.