Files
prometeu-studio/docs/specs/studio
bquarkz 675ffe5f2a
Test / Tests and coverage occurred while executing withChecks step.
Intrepid/Prometeu/Studio/pipeline/head There was a failure building this commit
feat(studio): restore project selection and loading flow
Restore the project launcher, creation wizard and loading shield with UI2
components. Coordinate real opening phases, a one-second minimum, pending
session cleanup and per-project window geometry while retaining the Play slice.

Keep global presentation controls in the project window, make the launcher
frame resize with its window and prevent root run from chaining the foundation
demo after the product exits. Update desktop/installed probes and documentation.

Register the existing native bundle after capacity qualification, without
changing native binaries or bypassing the execution guard.

Validated with unit, desktop, native Play, headless, save, MCP and installed
connector gates. Human-tested and accepted under WRK-0018.
2026-11-21 00:16:54 +00:00
..

Studio Specs

Owner: studio. Canonical source: docs/specs/studio.

This directory contains the normative Studio specification set.

Default JavaFX 2 frontend

13. JavaFX 2 Foundation Specification.md defines the prometeu-studio-ui-javafx-2 foundation and reusable shell. Its module guide documents execution, component ownership, themes, locales, bundled fonts and verification. The previous 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. The normal/installed app uses the new chooser and Play frontend; 14. Integrated Play Specification.md owns project flow, execution authority, transport/presentation, input, saves and qualification boundaries.

Purpose

Specs define the official Studio contract.

They exist to stabilize:

  • the application shell,
  • workspace responsibilities,
  • interaction flows,
  • service and event integration expectations,
  • UX behavior that implementation should preserve.

Expected Format

The exact structure may vary by document, but a Studio spec should usually contain:

  1. Title
  2. Status
  3. Scope or Applies To
  4. Purpose
  5. Authority and Precedence
  6. Normative Inputs
  7. Core Rules
  8. Non-Goals
  9. Exit Criteria

Writing Rules

  • Write in normative language.
  • Integrate only decisions that have already been closed.
  • Keep design exploration and option analysis out of the spec body.
  • Preserve clear boundaries between shell, workspace, and integration specs.

Upstream Rule

Specs should normally be fed by:

  1. agendas that frame the open Studio topic,
  2. decisions that close the product or interaction choice,
  3. plans that define propagation,
  4. then spec integration.

If a spec edit would require guessing unresolved UI behavior, stop and surface the missing decision first.

Current Corpus

The current Studio core corpus is:

  1. 1. Studio Shell and Workspace Layout Specification.md
  2. 2. Studio UI Foundations Specification.md
  3. 3. Studio Components Module Specification.md
  4. 4. Assets Workspace Specification.md
  5. 8. Project-Local Studio State Specification.md
  6. 9. Studio Core and Adapter Architecture Specification.md
  7. 10. DEV and Automation Specification.md
  8. 11. MCP Tools and Project Knowledge Contract.md

Reading Order

Recommended order:

  1. shell and workspace layout;
  2. shared UI foundations;
  3. components module policy;
  4. assets workspace behavior;
  5. project-local Studio state behavior;
  6. Studio Core, adapter, composition, and external integration boundaries;
  7. DEV authority, document handoff, automation operations/captures and phased integration gates;
  8. MCP transport/tool schemas and project/language knowledge contracts.

Current Wave Notes

The embedded Studio code-editor stack was removed by DEC-0031.

Normative reminders:

  • the accepted Studio workspace corpus is Assets, Debug, Shipper, and DEV; the DEV implementation follows DEC-0060's phased delivery;
  • project-local Studio session state remains normative and is owned by StudioProjectSession;
  • DEC-0060 authorizes an external coding agent using native file tools and the existing project LSP through MCP; it does not reinstate the embedded editor or authorize a replacement language-service architecture;
  • the Studio backend is exposed through neutral API contracts shared by JavaFX and the local MCP adapter, without duplicated authority or orchestration;
  • Spring Boot remains the desktop composition root with the narrow DEC-0060 local MCP HTTP exception; Spring Modulith still verifies the JavaFX-free p.studio.core boundary;
  • p.studio.Container, AppContainer, and the mixed prometeu-studio module are not valid final architecture.

Integrated MCP connection

DEC-0061 revises the baseline with Studio-owned mcp --project mode, grant-time project discovery, scoped HTTP credentials, one-time scaffold/preparation and a stable installation with bundled Java. Specs 8–11 define the lifecycle and transport boundaries; spec 1 defines project creation. PLN-0140 is complete; automated results and user-confirmed manual acceptance are consolidated in LSN-0077. The earlier HTTP evidence was not substituted for these gates. The embedded terminal remains separate.

See the specification guide for compiler, language and provider boundaries.