prometeu-studio/docs/studio/pull-requests

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
2. PR-05b-asset-navigator-search-filters-and-selection.md
3. PR-05c-selected-asset-details-contract-and-preview.md
4. PR-05d-assets-activity-progress-and-logs-integration.md
5. PR-05e-assets-staged-mutations-preview-and-apply.md
6. PR-07a-assets-event-topology-and-lifecycle-foundation.md
7. PR-07b-asset-navigator-and-row-subscriptions.md
8. PR-07c-asset-details-and-form-lifecycle.md
9. PR-07d-asset-mutation-and-structural-sync-orchestration.md
10. PR-07e-assets-refactor-cleanup-and-regression-coverage.md
11. PR-08-assets-workspace-panel-package-boundaries-and-local-subscriptions.md
12. PR-06-project-scoped-studio-state-and-activity-persistence.md

The PR-07 family is a corrective refactor pass for the current Assets implementation. It exists to replace the refresh-heavy direction with lifecycle-managed, event-driven ownership. It also establishes the intended Studio-wide workspace framework, with Assets as the first consumer and proof point.

PR-08 is the package-topology and subscription-ownership follow-up for that same direction. It enforces list/details package boundaries and requires every panel to consume the workspace bus directly.

Recommended execution order:

PR-05a -> PR-05b -> PR-05c -> PR-05d -> PR-05e -> PR-07a -> PR-07b -> PR-07c -> PR-07d -> PR-07e -> PR-08 -> PR-06

Next planned family for Bank Composition:

13. PR-10a-bank-composition-details-dto-projection.md
14. PR-10b-bank-composition-base-components.md
15. PR-10c-bank-composition-section-shell-and-form-session-integration.md
16. PR-10d-bank-composition-family-policies-and-section-coordinator.md
17. PR-10e-bank-composition-workspacebus-events-and-local-orchestration.md
18. PR-10f-bank-composition-apply-through-packer-and-snapshot-refresh.md