# Studio Pull Requests

This directory contains executable plans for Studio work.

## Purpose

A Studio pull-request or plan artifact packages a decision into an implementable sequence.

Use it to:

- separate shell work from workspace work,
- describe service and event-lane integration steps,
- define acceptance criteria for UI behavior,
- make validation and regression risks explicit before code changes.

## Expected Format

A Studio plan should usually include:

1. Briefing
2. Objective
3. Dependencies
4. Scope
5. Non-Goals
6. Execution Method
7. Acceptance Criteria
8. Validation
9. Affected Artifacts

## Writing Rules

- Organize by execution sequence, not by brainstorming.
- Keep visual design, interaction behavior, and service integration clearly separated.
- State what the user should be able to do after the change lands.
- Tie the plan back to Studio specs and decisions explicitly.

## Current Queue

The current Studio execution queue is:

1. [`PR-01-studio-event-bus-foundation.md`](./PR-01-studio-event-bus-foundation.md)
2. [`PR-02-studio-shell-components-wave-1.md`](./PR-02-studio-shell-components-wave-1.md)
3. [`PR-03-project-launcher-and-project-entry-shell.md`](./PR-03-project-launcher-and-project-entry-shell.md)
4. [`PR-04a-project-launcher-window-lifecycle.md`](./PR-04a-project-launcher-window-lifecycle.md)
5. [`PR-04b-new-project-wizard.md`](./PR-04b-new-project-wizard.md)