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
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:
@@ -25,6 +25,9 @@ Runtime-side reading semantics for `assets.pa` are defined upstream in `../runti
|
||||
5. A future shipper is a consumer of packer artifacts, not a co-author of the asset contract.
|
||||
6. Runtime reading semantics are not redefined by the packer.
|
||||
7. The packer must stop at artifact publication, not cartridge assembly.
|
||||
8. The packer's Java package root is `p.packer`; it must not be moved under `p.studio` or treated as a Studio subdomain.
|
||||
9. The packer must remain independently consumable by Studio, command-line tooling, build tooling, and future automation adapters.
|
||||
10. No Packer module may depend on `p.studio`, Studio UI, or Studio application modules.
|
||||
|
||||
## Packer-Owned Artifacts
|
||||
|
||||
@@ -57,6 +60,18 @@ Rules:
|
||||
- shipper-specific workflow detail is deferred;
|
||||
- published artifact names and meanings must remain documented and stable enough for later consumption.
|
||||
|
||||
## Studio Consumption Boundary
|
||||
|
||||
Studio is a consumer of Packer capabilities, not the owner of Packer semantics.
|
||||
|
||||
Rules:
|
||||
|
||||
- Studio should consume a stable, neutral, use-case-oriented public Packer API directly;
|
||||
- Studio must not add a gateway that merely mirrors an already suitable public Packer API;
|
||||
- when only concrete, static, infrastructure-oriented, unstable, or excessively broad integration is available, the Studio consumer may define a narrow consumer-owned gateway;
|
||||
- implementations of Studio-owned gateways must stay outside Packer and outside the Studio Core functional contract;
|
||||
- Studio projections and orchestration must not duplicate Packer validation, packing, diagnostic, concurrency, or artifact semantics.
|
||||
|
||||
## Non-Goals
|
||||
|
||||
- cartridge assembly flow
|
||||
|
||||
+16
-2
@@ -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:
|
||||
|
||||
|
||||
@@ -52,6 +52,10 @@ Specs should normally be fed by:
|
||||
|
||||
If a spec edit would require guessing an unresolved design choice, stop and surface the missing decision first.
|
||||
|
||||
## Integration Boundary
|
||||
|
||||
The Packer package root is `p.packer`, and Packer remains autonomous from Studio. Studio consumes stable public Packer APIs directly and introduces a narrow consumer-owned gateway only for concrete, static, unstable, or infrastructure-specific integration. Packer never depends on `p.studio`.
|
||||
|
||||
## Current Corpus
|
||||
|
||||
The current packer core corpus is:
|
||||
|
||||
Reference in New Issue
Block a user