studio session persistent

This commit is contained in:
2026-04-04 06:57:33 +01:00
parent d1722b23a3
commit a824b2185f
24 changed files with 1612 additions and 26 deletions
@@ -79,6 +79,9 @@ Rules:
- the shell may construct and own project-session services that survive workspace focus changes;
- workspaces may consume those project-session services without inheriting their ownership;
- introducing a project-session service must not collapse shell and workspace responsibilities into one monolithic root.
- project-local Studio state under `.studio/` must be loaded through the project-session boundary rather than through shell-local ad hoc persistence;
- project-local setup required before workspace use must be available when the project session opens;
- shell-restorable state accepted by Studio must be restored when the project shell mounts and persisted when the project shell closes.
## Right Utility Panel
@@ -174,8 +174,16 @@ The first wave must not define:
- tab pinning,
- drag-and-drop tab reordering,
- grouped tabs,
- split editors,
- or cross-session tab restoration.
- split editors.
Project-session-owned cross-session tab restoration is accepted for the project-local Studio state wave.
Rules:
- persisted editor restoration state must come from the project-session-owned `.studio/` state store rather than from an editor-owned ad hoc file;
- accepted restoration scope in this wave is limited to open tabs and active tab;
- editor layout restoration accepted in this wave may include divider-driven editor sizing, `Project Navigator` expansion state, and dock-panel configuration such as `Outline` and `Helper` open/closed state plus their restored size;
- restoration must degrade safely when a previously open file is missing or unsupported.
## Access-Mode and Save Model
@@ -0,0 +1,85 @@
# Project-Local Studio State Specification
## Status
Active
## Applies To
- `prometeu-studio`
- Studio project-session persistence under `.studio/`
- project-local Studio setup and restoration state
## Purpose
Define the normative contract for the main project-local Studio state store.
## Authority and Precedence
This specification implements the accepted decision for project-local Studio state under `.studio/`.
It extends:
- [`1. Studio Shell and Workspace Layout Specification.md`](1.%20Studio%20Shell%20and%20Workspace%20Layout%20Specification.md)
- [`5. Code Editor Workspace Specification.md`](5.%20Code%20Editor%20Workspace%20Specification.md)
## Core Rules
1. The canonical root for project-local Studio persistence MUST be `.studio/` in the project root.
2. The main project-local Studio state store MUST be owned by `StudioProjectSession`, or by a service explicitly owned by `StudioProjectSession`.
3. The main store MUST start as a single file.
4. The main store MUST be versioned.
5. The main store MUST load when the project session opens.
6. Restorable shell and editor state accepted by this wave MUST restore when the project shell mounts.
7. The main store MUST save when the project shell or project session closes.
8. Missing, invalid, or schema-incompatible state MUST fall back to safe default values and MUST NOT block project open.
## Accepted Wave-1 Categories
The main store MUST include:
- `projectLocalSetup`
- `shellLayout`
- `openShellState`
- `editorRestoration`
Wave-1 accepted meaning is:
- `projectLocalSetup`: project-local Studio setup required to operate on the project, including runtime paths such as the Prometeu runtime path;
- `shellLayout`: restorable layout state already accepted by implementation, including divider positions and equivalent layout proportions for accepted workspaces such as `Assets` and `Code Editor`, `Project Navigator` expansion state, and editor dock-panel open/closed plus restored-size configuration;
- `openShellState`: which workspace or equivalent shell-owned project view was open;
- `editorRestoration`: open editor tabs and active tab.
## Explicit Exclusions
The main store MUST NOT include:
- project-local activity history;
- derived cache;
- transient hover-only or equivalent ephemeral UI state;
- heavy operational output;
- recomputable results that do not represent project-local setup or restoration state.
`Project-local activity` may still live under `.studio/`, but it is a separate persistence concern and not part of the main store defined here.
## Ownership Rules
- shell and workspace UI may consume the main store through project-session-owned contracts;
- shell and workspace UI must not define competing primary persistence files for accepted wave-1 categories;
- project-local setup may be consumed before a dedicated settings UI exists.
## Non-Goals
- defining persistence for project-local activity
- introducing a multi-file main store in this wave
- defining a settings editor UI for project-local setup
- persisting arbitrary transient workspace detail by convenience
## Exit Criteria
This specification is complete enough when:
- the `.studio/` boundary is unambiguous;
- accepted and excluded categories are explicit;
- load, restore, save, and fallback timing are explicit;
- and the ownership boundary with `StudioProjectSession` is normatively locked.
+3 -1
View File
@@ -57,6 +57,7 @@ The current Studio core corpus is:
5. [`5. Code Editor Workspace Specification.md`](5.%20Code%20Editor%20Workspace%20Specification.md)
6. [`6. Project Document VFS Specification.md`](6.%20Project%20Document%20VFS%20Specification.md)
7. [`7. Integrated LSP Semantic Read Phase Specification.md`](7.%20Integrated%20LSP%20Semantic%20Read%20Phase%20Specification.md)
8. [`8. Project-Local Studio State Specification.md`](8.%20Project-Local%20Studio%20State%20Specification.md)
## Reading Order
@@ -68,7 +69,8 @@ Recommended order:
4. assets workspace behavior;
5. project document VFS boundary;
6. code editor workspace behavior;
7. integrated LSP semantic-read behavior.
7. integrated LSP semantic-read behavior;
8. project-local Studio state behavior.
## Current Wave Notes