complete Studio core and JavaFX boundary migration
Intrepid/Prometeu/Studio/pipeline/pr-master Build started...
JaCoCo Coverage #### Project Overview No changes detected, that affect the code coverage. * Line Coverage: 64.01% (20482/31999) * Branch Coverage: 54.22% (8240/15196) * Lines of Code: 31999 * Cyclomatic Complexity: 13164 #### Quality Gates Summary Output truncated.
Test / Build skipped: 15, passed: 715
Intrepid/Prometeu/Studio/pipeline/head This commit looks good

This commit is contained in:
2026-09-25 11:28:18 +01:00
parent 10f1b3f87c
commit a0a5050d5e
461 changed files with 9319 additions and 7205 deletions
@@ -60,10 +60,24 @@ When the packer is embedded inside another host such as Studio, the host must bo
Rules:
- the embedded packer runtime must receive a typed event bus reference from the host when shared host visibility is part of the integration contract;
- the embedded packer runtime must receive a typed event sink or adapter from the host when shared host visibility is part of the integration contract;
- that reference is the baseline path for packer publish/subscribe integration in the embedded host;
- the embedded packer runtime must not quietly create a disconnected parallel event system when host integration expects shared operational visibility;
- in Studio, this shared typed event bus reference is owned by the Studio `Container`.
- in Studio, bootstrap, shutdown, and event adaptation are owned by the `prometeu-app` composition root;
- the embedded integration must not use `p.studio.Container`, Spring context lookup, or another static service locator.
### Studio Dependency Rule
The dependency direction is always Studio to Packer.
Rules:
- Studio Core may consume stable public contracts from `prometeu-packer-api` directly;
- a Studio-owned gateway is required only when an integration is concrete, static, infrastructure-oriented, unstable, excessively broad, or leaks provider lifecycle details;
- such a gateway must expose only the capabilities required by its consuming Studio module;
- gateway implementations and Packer bootstrap belong in `prometeu-app` or another explicit infrastructure adapter;
- the JavaFX adapter must consume neutral Studio API contracts and must not call Packer directly;
- Packer must not depend on `p.studio` and must not publish Studio UI events as part of its domain contract.
Baseline core services: