131 lines
4.5 KiB
Markdown
131 lines
4.5 KiB
Markdown
---
|
|
id: PLN-0012
|
|
ticket: studio-code-editor-workspace-foundations
|
|
title: Propagate DEC-0008 into Studio shell and workspace specs
|
|
status: done
|
|
created: 2026-03-30
|
|
completed: 2026-03-30
|
|
tags:
|
|
- studio
|
|
- editor
|
|
- specs
|
|
- read-only
|
|
---
|
|
|
|
## Objective
|
|
|
|
Propagate DEC-0008 into the normative Studio spec surface so the read-only first wave of the `Code Editor` workspace is explicit before or alongside implementation.
|
|
|
|
## Background
|
|
|
|
DEC-0008 locks the first `Code Editor` wave as a read-only editorial foundation with:
|
|
|
|
- `Project Navigator` over the full project,
|
|
- reserved `Outline` region,
|
|
- responsive tab strip with overflow,
|
|
- read-only file opening,
|
|
- passive helper region,
|
|
- passive status bar,
|
|
- manual refresh only,
|
|
- and explicit deferral of save/dirty/LSP/semantic behavior.
|
|
|
|
The current Studio spec corpus defines shell-level workspace presence and shared UI foundations, but it does not yet define the concrete contract of the `Code Editor` workspace itself.
|
|
|
|
## Scope
|
|
|
|
### Included
|
|
- Add a dedicated `Code Editor` workspace specification to the Studio spec corpus.
|
|
- Update Studio spec navigation so the new chapter is discoverable.
|
|
- Align shell/foundations references so DEC-0008 terminology is consistent with existing Studio norms.
|
|
|
|
### Excluded
|
|
- Java implementation changes in `prometeu-studio`.
|
|
- LSP or semantic-provider contract design.
|
|
- Editable-mode design, save behavior, or conflict-resolution policy.
|
|
|
|
## Execution Steps
|
|
|
|
### Step 1 - Add a dedicated Code Editor workspace specification
|
|
|
|
**What:**
|
|
Create a new Studio spec chapter that normatively defines the read-only `Code Editor` workspace baseline from DEC-0008.
|
|
|
|
**How:**
|
|
Add a new chapter under `docs/specs/studio/` covering:
|
|
1. workspace layout,
|
|
2. `Project Navigator` ownership and full-project visibility,
|
|
3. reserved `Outline` region,
|
|
4. responsive tabs with overflow,
|
|
5. read-only file opening,
|
|
6. unsupported-file modal behavior,
|
|
7. passive helper region,
|
|
8. passive status bar fields,
|
|
9. manual refresh,
|
|
10. and deferred scope for save/LSP/semantic features.
|
|
|
|
**File(s):**
|
|
- `docs/specs/studio/5. Code Editor Workspace Specification.md`
|
|
|
|
### Step 2 - Update Studio spec navigation and cross-references
|
|
|
|
**What:**
|
|
Make the new spec reachable from the Studio spec index and aligned with the current corpus order.
|
|
|
|
**How:**
|
|
Update the Studio README reading order and current-corpus list to include the new chapter.
|
|
Add or adjust cross-references where shell/foundations specs should point to workspace-local ownership rather than implying global responsibility.
|
|
|
|
**File(s):**
|
|
- `docs/specs/studio/README.md`
|
|
- `docs/specs/studio/1. Studio Shell and Workspace Layout Specification.md`
|
|
- `docs/specs/studio/2. Studio UI Foundations Specification.md`
|
|
|
|
### Step 3 - Align terminology and deferred-scope language
|
|
|
|
**What:**
|
|
Ensure the spec corpus consistently uses DEC-0008 language for the first editor wave.
|
|
|
|
**How:**
|
|
Normalize references to:
|
|
1. read-only first wave,
|
|
2. passive helper and `Outline` placeholder,
|
|
3. manual refresh,
|
|
4. and explicit deferral of semantic/LSP features and save/write behavior.
|
|
|
|
**File(s):**
|
|
- `docs/specs/studio/5. Code Editor Workspace Specification.md`
|
|
- `docs/specs/studio/1. Studio Shell and Workspace Layout Specification.md`
|
|
- `docs/specs/studio/2. Studio UI Foundations Specification.md`
|
|
|
|
## Test Requirements
|
|
|
|
### Unit Tests
|
|
|
|
- No Java unit tests are required for this editorial plan.
|
|
|
|
### Integration Tests
|
|
|
|
- No runtime integration tests are required for this editorial plan.
|
|
|
|
### Manual Verification
|
|
|
|
- Verify the new spec chapter is listed in `docs/specs/studio/README.md`.
|
|
- Verify the new chapter matches DEC-0008 exactly on read-only scope, manual refresh, and deferred LSP/save behavior.
|
|
- Verify shell/foundations wording does not contradict workspace-local ownership defined by the new chapter.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- [ ] The Studio spec corpus contains a dedicated `Code Editor` workspace specification.
|
|
- [ ] The spec explicitly states that the first wave is read-only and excludes save/dirty/LSP/semantic behavior.
|
|
- [ ] The spec defines the baseline layout: navigator, reserved outline region, responsive tabs, editor body, passive helper, passive status bar.
|
|
- [ ] Studio spec navigation and cross-references are updated to make the new chapter discoverable and consistent.
|
|
|
|
## Dependencies
|
|
|
|
- DEC-0008 accepted content.
|
|
|
|
## Risks
|
|
|
|
- A too-light writeup could leave implementation inventing behavior that DEC-0008 already closed.
|
|
- Over-editing shell/foundations docs could blur shell-owned versus workspace-owned responsibilities.
|