This commit is contained in:
2026-04-15 07:22:33 +01:00
parent d9f857b9bf
commit 9dbc88ce35
6 changed files with 0 additions and 1025 deletions
@@ -1,137 +0,0 @@
---
id: PLN-0049
ticket: studio-scene-workspace
title: Propagate DEC-0026 into Scene Workspace and Assets specs
status: abandoned
created: 2026-04-14
completed:
tags:
- studio
- specs
- scene
- workspace
- assets
---
## Objective
Turn `DEC-0026` into normative Studio specifications so execution can proceed against stable written contracts for `Scene Workspace`, `Assets`, and shell integration.
## Background
`DEC-0026` locks the ownership boundary between `Scene Workspace` and `Assets`, the wave-1 tilemap scope, the explicit scene-to-asset binding rule, and the rule that `Assets` may create `SCENE` assets but must not author scenes.
The repository already has shell and assets workspace specifications but does not yet have a dedicated `Scene Workspace` specification.
## Scope
### Included
- Add a new `Scene Workspace` specification under `docs/specs/studio`.
- Propagate the ownership boundary into `docs/specs/studio/1. Studio Shell and Workspace Layout Specification.md`.
- Propagate the `Assets` limitation and handoff rules into `docs/specs/studio/4. Assets Workspace Specification.md`.
- Record the wave-1 UI composition, save model, binding contract, and non-goals in normative English.
### Excluded
- Java implementation.
- Serialization format design beyond what `DEC-0026` already locks.
- Packer publication rules.
## Execution Steps
### Step 1 - Add the Scene Workspace specification
**What:**
Create a dedicated normative spec for `Scene Workspace`.
**How:**
Author a new Studio spec document that captures:
- workspace purpose and authority;
- scene-first navigation;
- explicit distinction between scene artifact and linked `SCENE` asset;
- wave-1 `Tilemap` layout;
- save rules;
- tileset selection rules;
- tool-scope inclusions and exclusions;
- explicit exclusions for camera/lights/AABB and advanced paint tools.
**File(s):**
- `docs/specs/studio/9. Scene Workspace Specification.md` or the next appropriate numbered spec file.
### Step 2 - Propagate shell-level workspace presence
**What:**
Update the shell spec so `Scene Workspace` is a baseline Studio workspace.
**How:**
Amend the shell workspace set and topology language to include `Scene Workspace` as a first-class shell workspace, while keeping workspace-local detail delegated to the new workspace spec.
**File(s):**
- `docs/specs/studio/1. Studio Shell and Workspace Layout Specification.md`
### Step 3 - Propagate the Assets boundary
**What:**
Update the `Assets` workspace spec so it can create a `SCENE` asset without absorbing scene-authoring responsibility.
**How:**
Add explicit normative language that:
- `Assets` may create a `SCENE` asset;
- `Assets` must delegate subsequent scene authoring to `Scene Workspace`;
- `Assets` must not expose map-painting or scene-editor interactions;
- contextual handoff into `Scene Workspace` is supported.
**File(s):**
- `docs/specs/studio/4. Assets Workspace Specification.md`
### Step 4 - Align accepted project-local state implications
**What:**
Clarify whether `Scene Workspace` introduces accepted project-local restoration categories in this wave.
**How:**
Inspect the current `Project-Local Studio State` scope and either:
- explicitly keep scene restoration out of wave 1; or
- add only the minimum accepted shell layout/restoration state required by `DEC-0026`.
The update must not invent persistence categories that the decision does not support.
**File(s):**
- `docs/specs/studio/8. Project-Local Studio State Specification.md`
## Test Requirements
### Unit Tests
- None required for spec-only changes.
### Integration Tests
- None required for spec-only changes.
### Manual Verification
- Confirm each `DEC-0026` normative rule appears in at least one Studio spec.
- Confirm no spec text gives `Assets` ownership over scene editing.
- Confirm the new `Scene Workspace` spec remains limited to wave-1 `Tilemap`.
## Acceptance Criteria
- [ ] A dedicated `Scene Workspace` specification exists in `docs/specs/studio`.
- [ ] Shell specs name `Scene Workspace` as a first-class workspace.
- [ ] `Assets` specs explicitly allow `SCENE` asset creation but forbid scene editing.
- [ ] The spec set clearly distinguishes scene artifact save from asset-management flow.
- [ ] The written specs are sufficient for implementation planning without reopening `DEC-0026`.
## Dependencies
- `DEC-0026-studio-scene-workspace.md`
## Risks
- Misplacing binding or save semantics into the wrong spec would blur workspace ownership.
- Adding too much persistence detail at the spec stage could outrun the accepted decision.
- Reusing `Assets` wording too heavily could accidentally reintroduce asset-first ownership into the scene editor.
## Abandonment
Abandoned on 2026-04-15 because the parent decision `DEC-0026` was explicitly abandoned by the user.
@@ -1,126 +0,0 @@
---
id: PLN-0050
ticket: studio-scene-workspace
title: Build Scene Workspace shell and project-state foundations
status: abandoned
created: 2026-04-14
completed:
tags:
- studio
- workspace
- shell
- project-state
- scene
---
## Objective
Establish the shell, workspace registration, and project-state foundations required to mount `Scene Workspace` as a first-class Studio workspace.
## Background
`DEC-0026` requires `Scene Workspace` to exist as its own shell workspace and to own scene-authoring detail locally. The current shell and project-state code already support `Assets`, `Code Editor`, `Debug`, and `Shipper`, but no scene workspace entry exists yet.
## Scope
### Included
- Add a `Scene Workspace` entry to the Studio shell workspace model.
- Mount a first implementation composition root for `Scene Workspace`.
- Extend project-local layout/state only where needed for accepted shell behavior.
- Keep workspace-local operational state out of shell-global ownership.
### Excluded
- Full tilemap editor interactions.
- Asset creation workflows.
- Scene serialization and save internals.
## Execution Steps
### Step 1 - Extend workspace identifiers and shell selection
**What:**
Add `Scene Workspace` to the workspace identity model and shell-selection flow.
**How:**
Update the workspace enum/identifier, shell selection logic, and main window wiring so the shell can mount and switch to `Scene Workspace` like other first-class workspaces.
**File(s):**
- `prometeu-studio/src/main/java/p/studio/workspaces/WorkspaceId.java`
- `prometeu-studio/src/main/java/p/studio/window/MainView.java`
- `prometeu-studio/src/main/java/p/studio/workspaces/WorkspaceHost.java`
### Step 2 - Add a Scene Workspace composition root
**What:**
Create the initial workspace class and composition surface for `Scene Workspace`.
**How:**
Introduce a new workspace package with a composition root that follows the Studio event-driven workspace framework and can initially host the wave-1 layout regions.
**File(s):**
- `prometeu-studio/src/main/java/p/studio/workspaces/scene/SceneWorkspace.java`
- supporting classes under `prometeu-studio/src/main/java/p/studio/workspaces/scene/`
### Step 3 - Wire workspace lifecycle and activity integration
**What:**
Ensure the new workspace participates correctly in the shared workspace lifecycle model.
**How:**
Use existing workspace lifecycle helpers and add any minimal shell-activity mapping needed for workspace open or scene-open events, without leaking scene-local detail into the shell.
**File(s):**
- `prometeu-studio/src/main/java/p/studio/workspaces/StudioWorkspaceLifecycleSupport.java`
- `prometeu-studio/src/main/java/p/studio/controls/shell/StudioActivityEventMapper.java` if needed
### Step 4 - Extend project-local shell state only as required
**What:**
Support accepted shell/layout restoration for `Scene Workspace` if the implementation needs persisted split/divider state in wave 1.
**How:**
Introduce the smallest project-local state additions necessary for shell restoration and workspace layout proportions. Do not persist scene-editor document state here unless a separate accepted rule exists.
**File(s):**
- `prometeu-studio/src/main/java/p/studio/projectstate/ProjectLocalStudioState.java`
- `prometeu-studio/src/main/java/p/studio/projectstate/ProjectLocalStudioStateService.java`
- related tests under `prometeu-studio/src/test/java/p/studio/projectstate/`
## Test Requirements
### Unit Tests
- Workspace id / shell restoration tests for the new workspace entry.
- Project-local state normalization tests if new layout state is added.
### Integration Tests
- Main-view or shell-focused tests that verify `Scene Workspace` can mount and become the active workspace.
### Manual Verification
- Open a project and confirm `Scene Workspace` appears as a shell workspace.
- Switch between `Assets`, `Scene Workspace`, and `Code Editor` without losing shell stability.
- Reopen the project and confirm accepted shell layout restoration still behaves safely.
## Acceptance Criteria
- [ ] `Scene Workspace` is a selectable shell workspace.
- [ ] The workspace mounts through the standard workspace host path.
- [ ] No scene-local editing detail is pushed into shell-global state.
- [ ] Any new project-local state is limited to accepted shell/workspace restoration concerns.
## Dependencies
- `DEC-0026-studio-scene-workspace.md`
- `PLN-0049-scene-workspace-spec-and-boundary-propagation.md`
## Risks
- Overloading shell state with scene-editor detail would violate the workspace boundary.
- Introducing restoration for unaccepted categories would outrun the decision.
- Wiring shortcuts through `MainView` without a clean package boundary would make later tilemap work harder.
## Abandonment
Abandoned on 2026-04-15 because the parent decision `DEC-0026` was explicitly abandoned by the user.
@@ -1,135 +0,0 @@
---
id: PLN-0051
ticket: studio-scene-workspace
title: Build scene artifact identity, save flow, and Assets handoff contract
status: abandoned
created: 2026-04-14
completed:
tags:
- studio
- scene
- asset
- binding
- save
---
## Objective
Implement the Studio-local data contract that gives scenes a stable authoring identity, supports save for the intermediate scene artifact, and allows explicit handoff between `Scene Workspace` and `Assets`.
## Background
`DEC-0026` requires a stable scene artifact identity, a save-oriented scene-authoring lifecycle, and an explicit binding between scene artifact and `SCENE` asset that does not rely primarily on path inference.
## Scope
### Included
- Define and implement the scene artifact model used by `Scene Workspace`.
- Add Studio-local binding metadata between scene artifact and `SCENE` asset.
- Implement scene save/load for the intermediate authoring artifact.
- Add `Assets` handoff behavior after `SCENE` asset creation.
### Excluded
- Final packer publication logic.
- Advanced editing tools.
- Future aspect tabs.
## Execution Steps
### Step 1 - Define the scene artifact DTO and persistence boundary
**What:**
Create a Studio-owned scene artifact model with stable identity and wave-1 tilemap data.
**How:**
Add DTOs and persistence helpers that capture:
- scene identity;
- linked `SCENE` asset identity when present;
- four layers;
- per-layer dimensions;
- per-layer tileset reference;
- tile presence and editable tile data.
Keep the format explicitly intermediate and Studio-owned.
**File(s):**
- new files under `prometeu-studio/src/main/java/p/studio/workspaces/scene/model/`
- new files under `prometeu-studio/src/main/java/p/studio/workspaces/scene/persistence/`
### Step 2 - Implement save/load for the scene artifact
**What:**
Make `Scene Workspace` able to save and reopen the intermediate scene artifact.
**How:**
Build a dedicated repository/service for reading and writing scene artifacts using the chosen Studio-local format and metadata contract. Ensure identity survives rename/relocation independently of path.
**File(s):**
- new persistence/service classes under `prometeu-studio/src/main/java/p/studio/workspaces/scene/`
- tests under `prometeu-studio/src/test/java/p/studio/workspaces/scene/`
### Step 3 - Implement explicit scene-to-asset binding
**What:**
Introduce the explicit binding required by the decision.
**How:**
Store a stable scene artifact id and the linked `SCENE` asset reference in Studio metadata or equivalent explicit state. Avoid primary reliance on path inference. Make the binding readable from both `Scene Workspace` and `Assets`.
**File(s):**
- scene metadata / persistence files under `prometeu-studio/src/main/java/p/studio/workspaces/scene/`
- `prometeu-studio/src/main/java/p/studio/projectstate/` only if the accepted metadata home belongs there
### Step 4 - Add Assets-to-Scene handoff behavior
**What:**
Allow `Assets` to create a `SCENE` asset and then hand off authoring to `Scene Workspace`.
**How:**
Extend the asset-creation flow with the minimal family support needed for `SCENE`, then trigger explicit open/handoff into `Scene Workspace` without embedding editor controls into `Assets`.
**File(s):**
- `prometeu-studio/src/main/java/p/studio/workspaces/assets/wizards/AddAssetWizard.java`
- `prometeu-studio/src/main/java/p/studio/workspaces/assets/AssetWorkspace.java`
- new event/message classes under `prometeu-studio/src/main/java/p/studio/workspaces/assets/messages/events/` and/or `workspaces/scene/messages/`
## Test Requirements
### Unit Tests
- Scene artifact serialization/deserialization tests.
- Binding-identity stability tests across rename-like path changes.
- Asset handoff event tests.
### Integration Tests
- End-to-end test: create `SCENE` asset, hand off to `Scene Workspace`, save scene artifact, reopen and preserve binding.
### Manual Verification
- Create a scene from `Scene Workspace` and verify a linked `SCENE` asset exists.
- Create a `SCENE` asset from `Assets` and verify the UI hands off to `Scene Workspace`.
- Rename or relocate the scene artifact and verify semantic linkage still resolves.
## Acceptance Criteria
- [ ] The scene authoring artifact has a stable identity independent of raw path.
- [ ] `Scene Workspace` can save and reopen the intermediate scene artifact.
- [ ] The binding between scene artifact and `SCENE` asset is explicit and stable.
- [ ] `Assets` can create a `SCENE` asset and hand off authoring without embedding scene editing.
## Dependencies
- `DEC-0026-studio-scene-workspace.md`
- `PLN-0049-scene-workspace-spec-and-boundary-propagation.md`
- `PLN-0050-scene-workspace-shell-and-project-state-foundations.md`
## Risks
- Choosing the wrong metadata home could make binding brittle or leak scene ownership into the wrong layer.
- Reusing asset-oriented DTOs for scene authoring could erase the boundary that the decision just locked.
- Save/load work can sprawl if the intermediate format is not kept intentionally narrow for wave 1.
## Abandonment
Abandoned on 2026-04-15 because the parent decision `DEC-0026` was explicitly abandoned by the user.
@@ -1,151 +0,0 @@
---
id: PLN-0052
ticket: studio-scene-workspace
title: Implement Scene Workspace wave-1 tilemap editor
status: abandoned
created: 2026-04-14
completed:
tags:
- studio
- scene
- workspace
- tilemap
- ui
---
## Objective
Implement the wave-1 `Tilemap` experience for `Scene Workspace` according to `DEC-0026`.
## Background
The accepted decision limits wave 1 to one visible tab, `Tilemap`, with four layers, independent layer dimensions, explicit tile presence semantics, scene-first navigation, and basic editing tools only.
## Scope
### Included
- Left scene navigator.
- Top tab strip with only `Tilemap` visible.
- Central tilemap editing canvas.
- Right-side tilemap details and tile palette regions.
- Four-layer editing model with visibility and focus.
- Basic painting, erasing, and tile selection.
### Excluded
- Camera boundaries.
- Lights.
- AABB authoring.
- Placeholder tabs for unsupported aspects.
- Advanced editing tools such as bucket fill, marquee, flood fill, or lock semantics.
## Execution Steps
### Step 1 - Build the workspace projection model
**What:**
Create projection/view-state types for the scene navigator, active scene, active layer, tile palette, and tilemap details.
**How:**
Follow the event-driven workspace framework already used by other Studio workspaces. Keep projection boundaries local so navigator, details, and palette can update without whole-workspace redraw.
**File(s):**
- new projection and message classes under `prometeu-studio/src/main/java/p/studio/workspaces/scene/`
### Step 2 - Build the left navigator and scene selection flow
**What:**
Render a scene-first navigator that lists authoring scenes, not assets.
**How:**
Introduce a custom navigator control inspired by `Assets` patterns but scoped to scene identity, with linked asset context rendered only as secondary status.
**File(s):**
- new controls under `prometeu-studio/src/main/java/p/studio/workspaces/scene/list/`
- `prometeu-studio/src/main/java/p/studio/workspaces/scene/SceneWorkspace.java`
### Step 3 - Build the wave-1 Tilemap layout
**What:**
Implement the single visible tab and its three-region body.
**How:**
Compose:
- central tilemap canvas;
- right upper details panel;
- right lower tile palette;
- layer controls for visibility and focus.
Do not expose unsupported tabs.
**File(s):**
- `prometeu-studio/src/main/java/p/studio/workspaces/scene/SceneWorkspace.java`
- new controls under `prometeu-studio/src/main/java/p/studio/workspaces/scene/tilemap/`
### Step 4 - Implement tile selection and painting
**What:**
Support the basic editing interactions required by the decision.
**How:**
Implement tile selection from the palette, paint on the active layer, erase by clearing explicit tile presence, and preserve valid `glyph_id = 0` semantics.
**File(s):**
- tilemap interaction classes under `prometeu-studio/src/main/java/p/studio/workspaces/scene/tilemap/`
- scene model classes under `prometeu-studio/src/main/java/p/studio/workspaces/scene/model/`
### Step 5 - Implement tileset resolution and layer detail rendering
**What:**
Resolve glyph-bank-backed tileset data for the active scene/layer and show dimensions/details in the side panel.
**How:**
Consume the scene-owned tileset choice, render available tiles and palette choices, and expose active layer dimensions and relevant properties without handing ownership to `Assets`.
**File(s):**
- scene workspace service/projection classes
- tile palette and detail controls under `prometeu-studio/src/main/java/p/studio/workspaces/scene/tilemap/`
## Test Requirements
### Unit Tests
- Projection-state tests for active scene, layer visibility, and focus.
- Tile painting tests that preserve explicit presence semantics.
- Palette-selection tests that keep `glyph_id = 0` valid.
### Integration Tests
- UI-oriented tests for scene selection, tile selection, paint, erase, and save-triggered refresh.
### Manual Verification
- Open `Scene Workspace`, create/open a scene, and confirm the navigator is scene-first.
- Paint and erase on different layers with independent dimensions.
- Verify layer visibility/focus changes do not corrupt scene data.
- Verify only the `Tilemap` tab is visible in wave 1.
## Acceptance Criteria
- [ ] `Scene Workspace` renders a scene-first navigator.
- [ ] Wave 1 exposes only the `Tilemap` tab.
- [ ] The editor supports four layers with independent dimensions.
- [ ] Painting and erasing respect explicit tile presence semantics.
- [ ] Layer visibility and focus work in the tilemap editor.
- [ ] Tile palette and details panels reflect the active scene/layer context.
## Dependencies
- `DEC-0026-studio-scene-workspace.md`
- `PLN-0049-scene-workspace-spec-and-boundary-propagation.md`
- `PLN-0050-scene-workspace-shell-and-project-state-foundations.md`
- `PLN-0051-scene-artifact-and-assets-handoff-contract.md`
## Risks
- Overbuilding the first UI pass could quietly introduce unsupported aspect tabs or tools.
- Canvas interaction code can become monolithic if projection boundaries are not enforced early.
- Tileset rendering may drift toward asset-first ownership if scene-owned selection is not kept explicit.
## Abandonment
Abandoned on 2026-04-15 because the parent decision `DEC-0026` was explicitly abandoned by the user.