implements PLN-0005

This commit is contained in:
2026-03-27 17:01:40 +00:00
parent 124c6d078e
commit e0c57814e1
12 changed files with 143 additions and 10 deletions
@@ -71,6 +71,7 @@ The workspace must help the user understand:
- what the asset declares toward the runtime-facing contract;
- which operations are safe, staged, blocked, or destructive;
- whether the current view reflects healthy, stale, diverged, or reconciling packer state.
- what the canonical symbolic asset address is when Studio surfaces compile-facing identity.
The `Assets` workspace is also the first concrete consumer of the Studio event-driven workspace framework.
@@ -133,7 +134,8 @@ Rules:
- `Preload`
- The navigator must support textual search.
- Baseline search must cover at least:
- `asset_name`
- canonical asset address
- `asset_name` when still present as an editorial label
- asset root path
- path context
@@ -156,6 +158,7 @@ Rules:
- If an asset changes state while preserving identity, selection must remain attached to it.
- If the selected asset is removed from the navigator, selection must clear explicitly.
- Selection must never silently drift to another asset due to refresh ordering.
- If the selected asset keeps the same `asset_id` but its canonical address changes after a move or rename, Studio must preserve selection and refresh the visible address.
### Local Rendering Rules
@@ -206,7 +209,8 @@ Rules:
- `Summary` must always be present for a selected asset.
- `Summary` must show:
- `asset_name`
- canonical asset address
- `asset_name` when available as an editorial label
- registration status
- build participation
- `asset_id` when available
@@ -258,6 +262,16 @@ Rules:
- Sensitive actions must not look interchangeable with routine actions.
- `Relocate` must collect an explicit user-chosen destination root before the staged preview is generated.
- Automatic relocation targets are not sufficient Studio UX for `Relocate`.
## Namespace Collision Rule
Studio must respect the symbolic asset namespace contract used by compile-time authoring surfaces.
Rules:
- Studio must not allow creation of a new asset root whose canonical address would collide with an existing terminal asset or namespace prefix.
- Studio must not allow a terminal asset root to coexist with descendant asset roots that would require the same canonical path to act as both terminal and namespace.
- If a move or rename would create such a collision, Studio must block the action and surface the conflict explicitly.
- `Exclude From Build` and `Remove` must confirm in a modal review surface rather than an inline staged panel.
## Activity, Progress, and Logs Rules