prometeu-studio/discussion/workflow/plans/PLN-0022-propagate-dec-0011-into-studio-vfs-and-lsp-specs.md

id	ticket	title	status	created	completed	tags
PLN-0022	studio-editor-write-wave-supported-non-frontend-files	Propagate DEC-0011 into Studio, VFS, and LSP specs	review	2026-03-31		studio lsp vfs specs frontend-boundary

Objective

Make the frontend read-only minimum LSP phase normative in the Studio/VFS spec corpus and establish the intended LSP contract shape before implementation.

Background

DEC-0011 introduces a dedicated phase:

• FE remains hard read-only,
• prometeu-lsp consumes VFS snapshots,
• the minimum feature set is diagnostics, symbols/outline, definition, and frontend highlight,
• non-frontend highlight may remain Studio-local,
• and the API should follow flat packaging similar to prometeu-packer-api.

Scope

Included

• propagate DEC-0011 into Studio and VFS specs
• introduce or update LSP-facing specification text
• document flat packaging and minimum LSP scope

Excluded

• code implementation
• frontend edit-right release
• completion

Execution Steps

Step 1 - Update Studio Editor and VFS Specifications

What: Add the new frontend semantic-read phase to the existing Studio/VFS spec set.

How: Amend the relevant specs so they explicitly state:

• FE remains hard read-only,
• LSP consumes VFS snapshots,
• non-frontend highlight remains local for now,
• frontend highlight comes from LSP semantics.

File(s):

• docs/specs/studio/5. Code Editor Workspace Specification.md
• docs/specs/studio/6. Project Document VFS Specification.md

Step 2 - Introduce an LSP-Focused Studio Specification

What: Create a normative home for the integrated LSP phase.

How: Add a Studio spec that defines:

• integrated prometeu-lsp role,
• read-only FE semantic phase,
• minimum capability set,
• flat packaging expectation,
• and explicit non-goals such as completion and frontend editing.

File(s):

• new docs/specs/studio/7. Integrated LSP Semantic Read Phase Specification.md
• docs/specs/studio/README.md

Test Requirements

Unit Tests

• none

Integration Tests

• none

Manual Verification

• verify no contradiction exists between DEC-0010 and DEC-0011 in the specs
• verify the new spec makes the minimum LSP scope and exclusions explicit

Acceptance Criteria

• the Studio spec set reflects the FE read-only minimum LSP phase
• frontend highlight ownership is clearly separated from Studio-local non-frontend highlight
• LSP flat packaging is stated normatively enough to guide implementation
• completion and frontend edit rights remain explicitly out of scope

Dependencies

• DEC-0011 accepted
• DEC-0010 stable enough to provide the underlying VFS/write boundary

Risks

• spec propagation may accidentally imply frontend editing
• lack of a dedicated LSP spec could bury too much behavior in editor/VFS docs
• packaging guidance may stay too vague if not stated explicitly