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
+7 -4
View File
@@ -4,15 +4,18 @@ Owner: `studio`. Canonical source: `docs/specs/studio`.
This directory contains the normative Studio specification set.
## JavaFX 2 foundation
## Default JavaFX 2 frontend
[`13. JavaFX 2 Foundation Specification.md`](13.%20JavaFX%202%20Foundation%20Specification.md)
defines the independent `prometeu-studio-ui-javafx-2` foundation and minimal shell.
defines the `prometeu-studio-ui-javafx-2` foundation and reusable shell.
Its [module guide](../../../prometeu-studio-ui-javafx-2/README.md) documents execution,
component ownership, themes, locales, bundled fonts and verification. The previous
frontend remains available; specifications 1–4 describe its existing behavior and
frontend is retained for adapter qualification; specifications 1–4 describe its behavior and
do not impose its visual structure on the new implementation. Backend contracts
remain shared and unchanged.
remain shared. The normal/installed app uses the new chooser and Play frontend;
[`14. Integrated Play Specification.md`](14.%20Integrated%20Play%20Specification.md)
owns project flow, execution authority, transport/presentation, input, saves and
qualification boundaries.
## Purpose