prometeu-studio/discussion/workflow/plans/PLN-0064-normative-test-and-lesson-cleanup-for-editor-stack-removal.md

id	ticket	title	status	created	completed	tags
PLN-0064	studio-editor-workspace-cleanup	Normative Test and Lesson Cleanup for Editor Stack Removal	done	2026-05-05	2026-05-05	studio editor cleanup docs tests lessons

Objective

Remove or revise the normative documentation, tests, lessons, and user-facing resources that describe the embedded editor stack as a current Studio surface.

Background

DEC-0031 treats the editor stack removal as both code cleanup and normative cleanup. The repository currently contains active specs, README entries, i18n resources, and lessons that define Code Editor, prometeu-vfs, and the integrated semantic-read phase as active architecture.

Scope

Included

• Remove or rewrite Studio specs dedicated to the embedded editor stack.
• Update the Studio specs index and README.
• Remove or archive editor/LSP/VFS-specific tests that are no longer valid.
• Reclassify legacy lessons and references so they are not presented as active guidance.
• Remove user-facing i18n strings that only existed for the editor stack.

Excluded

• Implementation of shell/session/module cleanup itself.
• Future specs for the replacement backend or replacement external-editor strategy.

Execution Steps

Step 1 - Clean normative Studio specs

What: Remove or replace specs that define the embedded editor stack as active architecture. How: Delete or explicitly retire the Code Editor, Project Document VFS, and Integrated LSP Semantic Read Phase specs, then rewrite any remaining Studio README/index material so it no longer points to dead architecture. File(s): docs/specs/studio/5. Code Editor Workspace Specification.md, docs/specs/studio/6. Project Document VFS Specification.md, docs/specs/studio/7. Integrated LSP Semantic Read Phase Specification.md, docs/specs/studio/README.md.

Step 2 - Clean user-facing resources and shell references

What: Remove editor-specific strings, labels, and messages that no longer correspond to product surfaces. How: Delete workspace.code and codeEditor.* message keys and any equivalent theme or resource references still tied to removed editor UI. File(s): prometeu-studio/src/main/resources/i18n/messages.properties, any directly related theme or resource files.

Step 3 - Clean tests and update surviving expectations

What: Remove tests whose sole purpose was validating the editor stack and update remaining tests to stop expecting that stack. How: Delete or rewrite tests for editor workspace behavior, legacy LSP, legacy VFS, session expectations, and any shell assertions that still require the editor workspace. File(s): prometeu-studio/src/test/java/p/studio/projectsessions/**, editor-related tests, prometeu-lsp/**/test/**, prometeu-vfs/**/test/**, any shell-level tests affected by workspace removal.

Step 4 - Reclassify lessons and historical references

What: Ensure discussion lessons remain historically useful without being mistaken for current architecture. How: Review the lessons and references tied to editor/VFS/LSP waves and either archive them, mark them as legacy, or update index/readme material so they are not treated as active operational guidance. File(s): affected files under discussion/lessons/DSC-0010*, DSC-0012*, DSC-0013*, DSC-0014*, DSC-0016*, DSC-0017*, DSC-0020*, DSC-0021*, plus any summary/index surfaces that present them.

Test Requirements

Unit Tests

• Ensure no surviving test suite still references removed editor stack types or message keys.
• Add assertions where needed that remaining shell/resource state is internally consistent.

Integration Tests

• Validate the Studio docs/spec tree remains internally linked after removal or retirement of the editor specs.
• Validate the build/test graph no longer includes editor-stack-only suites.

Manual Verification

• Read the Studio spec README and confirm it no longer advertises the removed stack as active.
• Inspect project lessons/readme surfaces and confirm editor-stack lessons are clearly historical or retired.
• Launch the application and confirm no missing i18n keys or dead UI labels remain.

Acceptance Criteria

• Studio specs no longer define the embedded editor stack as an active surface.
• Studio README/index material no longer points to removed editor/VFS/LSP architecture as current.
• Editor-specific i18n keys are removed or no longer consumed.
• Obsolete tests are removed or rewritten.
• Historical lessons are clearly demoted from active operational guidance.

Dependencies

• DEC-0031 accepted and normatively locked.
• Sufficient implementation progress that the codebase no longer depends on the removed specs/resources/tests.

Risks

• Removing normative docs too early may temporarily leave the repo without clear current guidance.
• Historical lessons may still be valuable; deleting them outright could lose context that should instead be reclassified.
• Partial cleanup can leave broken links or missing i18n keys that only appear at runtime.