# 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-05a-assets-workspace-foundation-and-service-state.md`](./PR-05a-assets-workspace-foundation-and-service-state.md)
2. [`PR-05b-asset-navigator-search-filters-and-selection.md`](./PR-05b-asset-navigator-search-filters-and-selection.md)
3. [`PR-05c-selected-asset-details-contract-and-preview.md`](./PR-05c-selected-asset-details-contract-and-preview.md)
4. [`PR-05d-assets-activity-progress-and-logs-integration.md`](./PR-05d-assets-activity-progress-and-logs-integration.md)
5. [`PR-05e-assets-staged-mutations-preview-and-apply.md`](./PR-05e-assets-staged-mutations-preview-and-apply.md)

Recommended execution order:

`PR-05a -> PR-05b -> PR-05c -> PR-05d -> PR-05e`