feat(studio): ship JavaFX 2 Play and delegate integration tooling
Test / Tests and coverage occurred while executing withChecks step.
Intrepid/Prometeu/Studio/pipeline/head There was a failure building this commit

Launch the JavaFX 2 project shell on Java 25 with an interactive viewport,
managed Play lifecycle and project mutation guards. Preserve headless/MCP and
save compatibility, and qualify exact runtime executable bundles.
Separate unit JaCoCo gates from opt-in integration suites and use the internal
Pong fixture for the headless visual pilot.
Move maintenance and native conformance tools into tooling; retain the VS Code
extension and update current navigation links.

Validation: tooling make verify passed, including 1064 Studio unit tests,
JaCoCo thresholds and 22 headless integration tests.
This commit is contained in:
2026-11-19 17:32:03 +00:00
parent 1e17fc4d67
commit 71fb80efc3
163 changed files with 5929 additions and 4950 deletions
+71 -8
View File
@@ -11,7 +11,8 @@ The root project is a monorepo with these main areas:
- `prometeu-app`: Spring Boot non-web composition, concrete adapters, packaging, and JavaFX entry point (`p.studio.app.StudioLauncher`).
- `prometeu-studio-api`: toolkit-neutral Studio contracts and operation surfaces.
- `prometeu-studio-core`: JavaFX-free project, session, assets, shipper, runtime, and execution services.
- `prometeu-studio-ui-javafx`: the current human-facing JavaFX adapter.
- `prometeu-studio-ui-javafx-2`: the default human-facing frontend and presentation foundation.
- `prometeu-studio-ui-javafx`: retained previous adapter and compatibility qualification surfaces.
- `prometeu-packer`: embedded packer APIs and implementation used by Studio.
- `prometeu-compiler`: compiler core, build pipeline, frontend APIs, and the PBS frontend.
- `prometeu-infra`: shared infrastructure used across modules.
@@ -25,17 +26,30 @@ the enclosing [Prometeu Engineering workspace](../README.md) using
## Current Product Shape
The Studio shell currently organizes the product around four workspaces:
The normal and installed application opens the new project chooser. Open an existing
project, choose a qualified runtime installation, then use Play, Pause, Resume and
Stop. Close the project before opening another. A save-capable game requires an
existing development save image or an explicitly disposable session.
- Assets
- Debug
- DEV (external-agent authorization and observation)
- Shipper
Play prepares compiler/assets into the cartridge directory and starts an owned
native runtime process whose frames appear inside Studio. Zoom is x1/x2/x4 in
logical pixels with scrolling. Minimizing or switching applications pauses;
returning requires manual Resume. Closing stops the game, subject to save protection.
Play does not create a PMC or a distributable build.
At runtime, the app boots an embedded packer, restores project-local Studio state, and opens the Studio launcher window. Project creation currently scaffolds a Prometeu workspace with `prometeu.json`, `src/`, `assets/`, `build/`, `cartridge/`, `.workspace/`, and local Studio metadata.
This first frontend slice does not mount editors, Assets/DEV/Shipper workspaces,
AI prompts/configuration or breakpoint debugging. Their existing service contracts,
headless runtime and MCP adapters remain separately tested. The previous DEV guide
below describes retained adapter behavior, not controls available in the new UI.
See the [integrated Play contract](docs/specs/studio/14.%20Integrated%20Play%20Specification.md).
## External Coding Agents (MCP)
The following authorization workflow belongs to the previous DEV adapter. The new
Play UI does not yet expose a grant/configuration surface. This omission does not
change the deterministic headless protocol, task authority, MCP tool schemas or
installed stdio connector; their process and adapter qualification gates remain.
Studio includes its own `mcp --project <absolute-root>` mode. Configure the native
client once; project grants and desktop restarts no longer require copying ports
or tokens. The initial integration targets Codex on macOS.
@@ -219,7 +233,7 @@ follow-ups are consolidated in [LSN-0076](discussion/lessons/DSC-0068-studio-hea
## Requirements
- JDK 21 or newer recommended for local development
- JDK 25 for local compilation/tests and the bundled product runtime (Gradle 9.3.1)
- Gradle wrapper (`./gradlew`) included in the repository
- A desktop environment capable of running JavaFX
@@ -237,12 +251,61 @@ Run the desktop application:
./gradlew :prometeu-app:run
```
The new UI is the default. `:prometeu-studio-ui-javafx-2:run` and `:gallery` remain
separate foundation demonstrations, without a backend or a project.
Opt-in integrated Play qualification (desktop/installed native runtime required):
```sh
./gradlew :prometeu-app:studioPlayProcessTest -PstudioRuntimeInstall=/absolute/runtime-install
./gradlew :prometeu-app:studioPlayDesktopTest -PstudioRuntimeInstall=/absolute/runtime-install
```
Add `-PstudioPlayStress=true` for the 30-second presentation/FX-delay/20-cycle gate.
The headless visual evidence pilot uses a disposable copy of `test-projects/pong`.
Integration fixtures belong to this repository; no external port checkout is
required. A runtime's three executable identities must match a distributed
capacity profile; rebuilding a native binary does not automatically requalify it.
Build the native umbrella distribution with `../runtime/scripts/local-dist.sh`.
It packages `prometeu`, `prometeu-runtime` (desktop/Studio Play) and
`prometeu-headless` (deterministic automation). Select the extracted
`../runtime/dist-staging/stable/prometeu-cli-<target>` directory in Studio.
An unchanged dispatcher can belong to several releases: Studio selects a profile
only when all three executable hashes match the same qualified bundle.
After changing a native binary, qualify the actual installation before building
or launching Studio with its updated catalog:
```sh
make -C ../tooling venv
../tooling/.venv/bin/python ../tooling/scripts/qualify.py \
--studio . \
--runtime ../runtime/dist-staging/stable/prometeu-cli-aarch64-apple-darwin
```
This command executes the native glyph/scene 16/17 boundary test afresh, verifies
the evidence and executable identities, then publishes an exact capacity profile
under `prometeu-app/src/main/resources/asset-capacity`. Review/include those
resources when distributing Studio. It neither builds a replacement runtime nor
relaxes the execution guard. A failed qualification publishes no catalog entry.
The native build stays independent of the JVM; qualification is an explicit
consumer verification step, separate from pressing Play.
Run the test suite:
```bash
./gradlew test
```
`test` runs unit tests and excludes JUnit `@Tag("integration")`. Integration
includes process/network/desktop qualification and real application or provider
composition, including fixture subprocesses. Existing integration suites remain
in this repository; `../tooling` prepares their environment and orchestrates
selected integration commands and builds. They are currently excluded from the
runtime and Studio pipelines; the opt-in commands above are separate checks.
Consolidated JaCoCo uses only the unit `test.exec` files.
Generate the aggregated coverage report:
```bash