@yugoo-design/dsh-design-studio-ui 0.1.2 → 0.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -4,7 +4,11 @@
4
4
  and Bundles, with Kits as the entry view. A host may additionally expose the
5
5
  Component Library capability. The established Studio layout has a compact
6
6
  breadcrumb/refresh bar above the workspace, with neutral typography, colors and
7
- control details. Shared authoring guidance is in the
7
+ control details. The narrow-screen menu and navigation drawer are anchored to
8
+ this workspace, including when a host places it beside or below a conversation;
9
+ they do not cover the host's header. The drawer fades within that boundary
10
+ throughout its opening transition. A closed drawer also hides its controls
11
+ from keyboard focus and the accessibility tree. Shared authoring guidance is in the
8
12
  [Panel UIUX standard](../../docs/panel-uiux-standard.md). Storage concepts such as
9
13
  Panel drafts must not add top-level navigation sections. The optional **Panel Component Library / 面板组件库**
10
14
  entry is a bottom sidebar utility, above the shared language switch, not another
@@ -17,6 +21,88 @@ retarget project pins. The installed catalog still comes only from the host.
17
21
  Public repository visibility and document synchronization must be verified before
18
22
  claiming that this external guide is available to anonymous users.
19
23
 
24
+ Catalogs and installed source remain read-only browsing surfaces. With the
25
+ `instances` capability, **Open / 打开** reads a local copy without host conversation
26
+ or mutation controls; **Copy / 复制** uses the existing S2 service to create an
27
+ independent copy and opens it for reading; **Edit / 编辑** explicitly enters local
28
+ copy authoring. A local copy can be copied again using its saved canonical source.
29
+ `instances.editCurrent` opens the same library identity for editing; Copy alone creates a new independent identity. Delete and less frequent
30
+ working-copy actions live in the shared right-hand overflow menu. Studio does not
31
+ expose an installed-package uninstall port; installed packages remain host-owned.
32
+ Hosts can supply `renderPreview` for saved-instance sample Panels, including
33
+ read-only **Open**, independently of the legacy Panel-draft `authoring` client.
34
+ The renderer receives the existing isolated preview and read-only context;
35
+ supplying it does not enter native authoring or grant a save capability.
36
+ Optional `instances.create` adds **New Kit / New Bundle**, creating a real blank S2
37
+ record before entering its editor. Empty definitions may still require content or
38
+ mounts before validation succeeds.
39
+
40
+ Kit and Bundle catalogs share the established header: a 300px search control on
41
+ the left, matched/total counts, and New on the right. The product breadcrumb already
42
+ names the section; the catalog does not repeat its heading. There is no local version picker or publication status. The existing leave guard protects unsaved edits.
43
+
44
+ Saved local Bundle cards show their Kit reference count. Select the count to
45
+ open the same mount management view used by installed Bundles, without opening
46
+ source editing. A Kit import can retain its mounted Bundle sources inside the
47
+ archive; mount management identifies these retained sources separately from
48
+ missing independent catalog entries. Single-file ZIP imports report an invalid
49
+ archive format before checking for required source files; ZIP resources inside
50
+ an imported source folder retain their original bytes.
51
+
52
+ Only new/edit object entries invoke `renderContent(content, context)`, inside the
53
+ Studio stage. The context supplies the object's `id`, create/edit `intent` and
54
+ `onDirtyChange` for unsent input. Editing retains product navigation, top bar,
55
+ object title, Back and full file tree. It hides the introduction sidebar; normal
56
+ reading can show the existing description. Introductions remain source-owned in
57
+ Mindset/SKILL metadata and existing locale resources: AI can propose the wording,
58
+ which people can revise and confirm through source editing.
59
+
60
+ A Kit editor has two tabs: **Source Files / 原始文件**, followed by
61
+ **Mount management / 挂载管理**, without a Panel preview or arbitrary
62
+ first-Bundle selection. Mount management uses the same Bundle cards as the catalog: only unmounted candidates on the
63
+ left in a narrow single column, mounted Bundles in the wider main area on the
64
+ right, with search only on the left. Card descriptions use the same Bundle
65
+ metadata and presentation as the catalog. Add/Remove
66
+ moves the card between columns and reports the unsaved added/removed counts; the editor's global Save uses the existing revision CAS.
67
+ Missing mounted sources remain visible and cannot be silently omitted from a save.
68
+ Preview diagnostics describe incomplete definitions without preventing source saves.
69
+ Save and Revert stay in the object's top-right header across source, preview and
70
+ mount views. The source toolbar switches between Edit and Diff against the saved
71
+ revision. AI proposals and manual corrections share the current source draft;
72
+ changing files or switching to Panel Preview does not discard it. Preview renders
73
+ the current files through the existing preparation service, including unsaved
74
+ `panel.yaml` and locale edits. Its sample data is not a separate save target.
75
+ Editing an AI proposal prepares a new digest for the exact files being saved.
76
+ Human and AI edits share ordinary source-save semantics; stale or
77
+ uncertain saves remain blocked until the existing read/reopen path verifies them.
78
+ The file workspace fills its content area using ordinary column dividers,
79
+ without another bordered card, rounded frame or exterior gutter.
80
+
81
+ The workbench's `renderSupplement` reports the canonical record/revision,
82
+ dirty/busy state, exact preview Bundle pin, entry intent and current relative
83
+ source file. The Preview workplane reports `panel.yaml` as `currentFile` when
84
+ that source exists, and uses the existing split: the same source editor/diff on
85
+ the left and live sample Panel on the right. Both views share drafts and the
86
+ object-level Save/Revert controls. Hosts use these as editing context,
87
+ retain revision and native-binding checks, and invalidate late asynchronous
88
+ results on exit or object switch. These hints grant no source or save authority.
89
+
90
+ The optional `proposalReplacement` supplement capability derives from the same
91
+ source, title and mount drafts and the existing candidate-save fence. A host can
92
+ replace a pristine proposal during one request, or offer an explicit choice that
93
+ uses the editor's ordinary discard confirmation. In-flight and unverified saves
94
+ block replacement. Same-revision refresh preserves the selected file and view;
95
+ human edits keep their current proposal until explicitly discarded.
96
+
97
+ Hosts may open an exact working copy through `initialInstance` (`id`,
98
+ `expectedRevision`, optional `bundle`). The standard `InstanceWorkbench` checks
99
+ that revision and pin before exposing source or preview; a Kit handoff without a
100
+ Bundle pin starts in source files and does not guess the first mount. This is a
101
+ one-time entry selection: later explicit saves and navigation use the existing
102
+ instance lifecycle. A host-supplied `renderInstanceWorkbench` receives the same
103
+ `initialSelection` and must preserve those checks. The host validates its native
104
+ binding separately; these props grant neither execution nor save authority.
105
+
20
106
  ## Locale and catalog copy
21
107
 
22
108
  Studio accepts an explicit host `locale` (`zh` or `en`) with a document/browser
@@ -45,33 +131,32 @@ trial locale rather than inheriting an unrelated browser-origin preference.
45
131
 
46
132
  ## Mindset editing and source files
47
133
 
48
- `MindsetInlineEditor` is an optional control embedded in the original Kit page.
49
- It lazily creates/reopens a Kit working copy via the existing authoring client,
50
- edits body segments without trimming, and preserves frontmatter and the unique
51
- `design_skills` block byte-identically in folded read-only sections. Ambiguous
52
- protection boundaries refuse editing; CAS failures retain pending input. Hosts
53
- keep `installedSource` stable and adopt `onSource` into both raw/reading draft
54
- views. Saved content is marked unpublished, not installed or published.
55
- Optional `initialId` explicitly reopens a selected saved
56
- record on mount; `onRecord` returns checked create/read/save receipts so the parent
57
- can retain/select IDs on the original page. No latest-record heuristic is used.
58
- Disposal invalidates late requests. `onDirtyChange` supplements the browser-unload guard
59
- with the host's navigation/close guard. Focused source-plane checks:
60
- `TSX_TSCONFIG_PATH=packages/studio-ui/tsconfig.json node --import tsx --test packages/studio-ui/tests/mindset-inline.test.mjs`.
61
- These controller/SSR checks do not establish integrated browser or durable host
62
- save/reopen acceptance.
134
+ Kit and Bundle content uses one instance editor. `editCurrent` opens a stable
135
+ library identity, internally materializing its source only on first edit; subsequent
136
+ edits return that same record. The UI replaces the installed card with this current
137
+ record rather than showing two copies. An explicit Copy creates an independent
138
+ identity and file set. Mindset, manifests and nested resources are ordinary source
139
+ files; there is no separate Mindset draft, recovery picker or confirmation lock.
63
140
 
64
141
  The Kit files tab uses the same file explorer as Bundle and local-copy views.
65
142
  Hosts expose optional `readKitFiles` / `readKitFile` ports for confined, exact-version
66
143
  installed source reads; without them only the supplied Mindset is available.
67
144
  The Companion adapter provides the full physical tree and bounded UTF-8 reads.
68
- Raw Mindset includes the mount XML. Local Kit mounts are explicit checkboxes over
69
- retained exact Bundle versions, saved through `updateMounts` with revision checks;
70
- installed originals stay protected. Removal means deleting a recoverable local
71
- copy, not uninstalling a Kit or Bundle. UI classes use the `ygd-studio` prefix;
145
+ Raw Mindset includes the mount XML. Local Kit mount management presents available
146
+ and mounted Bundle cards by stable identity, saved through `updateMounts`
147
+ with revision checks. Mounted local Bundles use their current saved content;
148
+ project-owned copies are unaffected by library changes. Removal moves the local
149
+ copy to the system Trash, without uninstalling installed content. UI classes use the `ygd-studio` prefix;
72
150
  package identities are unchanged. Studio loading locations share one indicator
73
151
  with the KAG indeterminate sweep treatment (no fake completion percentage).
74
152
 
153
+ The shared working-copy editor's **Refresh working copy / 刷新副本** action reads
154
+ the current saved revision, including changes made through the Host conversation.
155
+ It uses the existing discard confirmation for local source edits. Host conversation
156
+ input remains owned by its surrounding workbench; refreshing source does not send
157
+ that input. A Kit's existing mounted-Bundle preview selection is also available
158
+ to the Host supplement, so authoring uses the same view context.
159
+
75
160
  ## Bundle trials
76
161
 
77
162
  The title row owns the sole explicit trial entry. It checks the host connection,
@@ -87,7 +172,7 @@ keeps the original input of each result. A waiting interaction may start another
87
172
  round, but an uncertain or running sibling trial blocks reentry.
88
173
 
89
174
  Hosts can supply `trials: StudioTrialClient` to enable a Bundle-local trial action,
90
- including saved Panel draft revisions. The adapter owns immutable snapshots,
175
+ using the current saved source files. The adapter owns immutable snapshots,
91
176
  isolated projects, native dispatch, durable history and cleanup. This UI does not
92
177
  start a model or write Design Files. Queue acceptance is not completion; missing
93
178
  native evidence remains `unknown`. Stop failures leave the trial active, and only
@@ -107,32 +192,50 @@ latest local demonstration baseline. Reload restores the actual generated result
107
192
 
108
193
  ## Panel authoring and shared controls
109
194
 
110
- Optional authoring: hosts may supply `StudioAuthoring` to edit the left YAML in
111
- the preview workplane. The first actual source change lazily creates a retained
112
- Panel draft through the existing port, preserving text typed during creation.
113
- Simply viewing installed content never creates a draft or changes the installed
114
- Bundle. Subsequent source edits debounce the shared runtime preview, and save uses
115
- the existing optimistic revision check. An unambiguous retained copy can be resumed
116
- explicitly; a delayed recovery read cannot replace subsequently typed source.
117
- Late or mismatched save receipts cannot switch another Bundle's trial source.
118
- Trials of edited Panels use the saved
119
- exact draft revision; unsaved source must be saved first. Native Panels without
120
- `panel.yaml` explicitly explain that they have no editable YAML source.
121
- `StudioPanelDraftController` rejects stale or mismatched preview replies. Hosts
122
- render with sample-only ports; the shared UI imports no Panel implementation.
123
- `onDraftDirtyChange` guards host closure and navigation. Confirmation locks a
124
- local draft, not a published Kit; preview alone never starts execution.
125
-
126
- The optional host-neutral `renderSelect: StudioSelectRenderer` port supplies the
127
- shared choice control for Bundle/Kit versions, Mindset working-copy recovery and
128
- the two Kit preview Bundle selectors. DSH's standalone browser page and Companion
129
- inject the existing Panel control; Studio UI imports only the local port types.
130
- Hosts without the port retain a controlled native select. Values, empty choices,
131
- unknown stored values and disabled options remain caller-owned. Studio supplies
132
- its compact 32px trigger geometry and semantic token bridge; the shared popup
133
- keeps keyboard/focus handling and carries its own styles. Recovery menus stay
134
- inside an open native dialog's top layer. This changes presentation only, not
135
- working-copy, preview, CAS or save operations.
195
+ Hosts pass an already prepared S1 `{request, candidate}` through
196
+ `InstanceWorkbench.sourceChanges`. The current workbench and complete source tree
197
+ stay mounted. A proposal opens its changed file in **Source Files**, where exact
198
+ inline additions, removals and context show the pending source. Unchanged files
199
+ remain readable in that tree; new files appear beside the existing source. The
200
+ existing **Panel Preview** is a read-only sample view of the same candidate.
201
+ There is no separate review page or review-entry button.
202
+
203
+ The shared candidate state captures the full replacements once, rechecks the
204
+ working-copy revision and saves only through the supplied `saveChanges` port with
205
+ the digest of the exact proposed files. Saving remains explicit. Success updates that same
206
+ copy and its new saved revision in place, so the existing export action reads
207
+ the saved source. A proposal arriving during human edits waits without reloading
208
+ or replacing them. A stale base cannot save; an uncertain save receipt disables
209
+ resubmission and export until the existing refresh/reopen path verifies the copy.
210
+ A failed reopen leaves that uncertainty intact. Late receipts cannot switch the
211
+ selected copy or candidate.
212
+
213
+ Operation failures use contextual `StudioFeedback` cards with recovery actions.
214
+ `StudioEmptyState` separately displays missing content in the affected region,
215
+ centered with a warning icon and the missing file or sample; valid no-Panel content
216
+ uses its neutral `info` tone. Neither state opens a modal automatically.
217
+ Blocked explicit saves use the shared `StudioErrorDialog`. Its
218
+ controlled props are `open`, `onClose`, `title`, optional `message`, `details` and
219
+ `actions`, and `locale`. Details expand inside the dialog; file navigation and
220
+ recovery actions close it without taking focus away from their destination.
221
+ Escape and ordinary dismissal restore the trigger's focus. `StudioFeedback`
222
+ opens technical details in this dialog on request; explicit `autoOpen: true`
223
+ is reserved for blocking action results and opens once per stable `feedbackId`.
224
+ Success remains nonblocking.
225
+ Hosts provide real recovery actions and keep repair in the existing conversation.
226
+
227
+ The editor toolbar contains actions without inline error explanations. Incomplete
228
+ source can be saved; preview errors remain in the affected preview region. Human
229
+ and AI source changes use the same save mode. Busy, stale or uncertain writes
230
+ remain protected, and filename format errors stay beside the input. A missing
231
+ preview renderer does not prevent saving files. Native Agent completion, source
232
+ save, preview success and runtime consumption are distinct facts.
233
+
234
+ `StudioAuthoring` supplies only installed sample preview and the shared runtime
235
+ renderer. All editing uses `StudioInstanceClient`; the old Panel/Kit draft editors,
236
+ confirmation/fork workflows and standalone review page are removed. `renderSelect`
237
+ remains the optional shared control adapter for ordinary supported choices. It
238
+ must preserve caller-owned values, unknown stored choices, focus and popup styles.
136
239
 
137
240
  ## Component library
138
241
 
@@ -172,7 +275,7 @@ plugin activation are separate integration steps. Custom compiled components
172
275
  require a development-source change and the existing registration/validation/UI
173
276
  contract; this view is not a dynamic executable component marketplace.
174
277
 
175
- ## Source browsing and retained copies
278
+ ## Source browsing and current content
176
279
 
177
280
  Bundle pages put Source files first and Panel preview second. The recursive file
178
281
  explorer displays actual source paths, including nested reference folders. Trial
@@ -185,32 +288,41 @@ User-provided preview samples remain
185
288
  isolated from project files. Request revisions and exact Kit/Bundle pins prevent
186
289
  obsolete responses from replacing the current preview.
187
290
 
188
- Mindset reading separates its body from frontmatter and the generated
189
- `design_skills` section. The complete byte-exact file remains available in a
190
- dialog; the reading projection never rewrites source. The contents list is
191
- derived from rendered headings, so headings inside fenced examples do not create
192
- incorrect navigation entries. Installed reads never mutate the original.
291
+ Mindset reading preserves the complete source alongside its Markdown projection.
292
+ Reading files never creates an editable record.
193
293
  Hosts may supply the optional `instances` client for complete retained local copies.
294
+ An optional `renderInstanceWorkbench(props)` presentation port can render an
295
+ existing instance inside the same Studio navigation. It receives the complete
296
+ `InstanceWorkbenchProps`, including the original client, ID, locale, preview and
297
+ back/change/dirty callbacks. The instance ID keys its lifetime; a nullish return
298
+ keeps the standard workbench. This presentation port grants no additional catalog,
299
+ save, execution or publication capability. Hosts that omit it retain the existing
300
+ source editor. Catalog counts and empty states include visible local copies using
301
+ the same search filter as their cards.
302
+ When a host combines unsent conversation input with the editor's dirty signal,
303
+ it may report `onDirtyChange(navigationDirty, { sourceDirty })`, retaining the
304
+ shared editor's canonical dirty signal as `sourceDirty`. Export uses that source
305
+ signal; navigation protects both. Unsent input stays in place after exporting the
306
+ saved revision. Boolean-only callbacks retain their existing behavior, and the
307
+ editor still blocks export during unsaved source changes or uncertain saves.
194
308
  Copy opens an independent editable file set; title-pencil renaming changes the
195
309
  selected language's display name without changing source identities. The header places
196
- an arrow-only Back action on the left and direct Copy/Delete actions on the right.
197
- Deletion checks local references and retains recoverable
198
- data. The existing Kits/Bundles lists include local copies, with no new navigation
310
+ an arrow-only Back action on the left and copy/edit actions on the right, with
311
+ export and the red **Move to Trash** action in the shared overflow menu.
312
+ Removal checks local references and moves the working-copy record to the system
313
+ Trash. Its confirmation identifies that destination; success appears only after
314
+ the operation succeeds. Users restore through the operating system or import
315
+ again. The existing Kits/Bundles lists include local copies, with no new navigation
199
316
  area. Saves use optimistic revisions; preview compiles saved local bytes through
200
- the existing renderer. Copies are unpublished and never retarget active sessions.
201
- Hosts without this capability expose no inert mutation placeholders. Mount editing,
202
- publication and native trial dispatch of complete local copies remain separate
203
- capabilities, not implied by save or preview.
317
+ the existing renderer. Saved content is usable without publication. Existing projects retain their own definition trees.
318
+ Hosts without an editing capability expose no inert mutation placeholders. Native runtime consumption still needs its own verification; preview success does not prove it.
204
319
 
205
- When Kit authoring is available, Mindset editing stays in the original document
206
- page. Complete source is saved through the existing revision-checked draft API;
207
- frontmatter and the generated mount block are preserved byte-for-byte. Saved
208
- records can be selected explicitly after refresh, never by an implicit “latest”
209
- lookup. Reading/full-file views show the selected saved draft, clearly unpublished;
210
- the installed source remains the immutable editing base. Leaving dirty input
211
- requires confirmation. This is not Kit publication or full Bundle-file editing.
212
-
213
- The package renders installed Kits, searchable Bundles, Kit workspaces and byte-exact read-only Bundle source files. Resource inventories belong in the file explorer, not a paragraph beneath the Kit cards. File viewing uses one toolbar, a scrollable document body and a compact byte-count/status footer; Markdown metadata is folded without removing it from the raw source. Schema and validation files use that same viewer without additional compiled-summary blocks. A Bundle workspace overlays its original section and returns without a re-read. Kit selection carries the exact `name@version` pin; divergent identities and obsolete asynchronous responses cannot replace the current workspace. Without the explicit authoring capability there are no draft controls. With it, edits are kept in a separate draft rather than changing installed content. All data comes from server views; the UI hardcodes no Kit, Bundle or version and imports no Agent Host, Design Core, G/R/A or filesystem API.
320
+ The package renders searchable Kits and Bundles, current content editors and
321
+ byte-exact file views. Resource inventories belong in the file explorer, not a
322
+ paragraph below cards. One toolbar, scrollable body and byte-count/status footer
323
+ serve every source file. Metadata may be folded for reading without changing raw
324
+ source. All data comes from host ports; the UI hardcodes no Kit or Bundle and
325
+ imports no host runtime, Core implementation or filesystem authority.
214
326
 
215
327
  ## Layout and typography
216
328
 
@@ -231,24 +343,83 @@ use compact borders and a horizontal scroll container within the file viewer.
231
343
  UI copy follows the host document/browser locale, but authored file content is never
232
344
  translated or abbreviated in the document viewer.
233
345
 
234
- ## Content archives
235
-
236
- Hosts may pass `contentClient` to expose **Content archives** in the existing
237
- workspace toolbar; the sidebar remains Kits / Bundles. The archive workbench
238
- accepts a file or pasted JSON, retains the import and displays its exact identity,
239
- provenance and validation diagnostics. Import preparation does not create a
240
- working copy. Explicit adoption retains validated content in the local content
241
- library. Adopting a complete Kit additionally requires `kitAuthoring`; its receipt
242
- opens the exact unconfirmed Kit working copy in the existing editor. A standalone
243
- Bundle requires no Kit editor and opens its exact source workspace after the
244
- catalog refresh. It is not implicitly mounted into a Kit or attached to a project.
245
- The adoption receipt must preserve the import ID, exact content closure and inert
246
- authority; a Bundle receipt must not contain a Kit draft. Adoption never overwrites
247
- installed sources, retargets project pins, publishes or executes content.
248
-
249
- Unprepared input participates in workspace navigation and browser-unload guards;
250
- leaving the workbench invalidates late UI responses. Export uses the selected
251
- installed Kit's exact version and user-supplied source/license declarations, and
252
- downloads the returned archive bytes unchanged. Hosts without `contentClient`
253
- retain the existing UI. The size check includes the JSON RPC wrapper and escaping
254
- against Companion's 12 MiB request limit; it never truncates an archive.
346
+ ## Import and export
347
+
348
+ Hosts provide `instances.importSources` for the **Import / 导入** action beside
349
+ **New** in each catalog. Bundle import accepts a ZIP, folder or bare `SKILL.md`;
350
+ Kit import accepts a ZIP or folder containing `mindset.md` and `kit.yaml`.
351
+ A folder can be selected from the adjacent import menu. Archive manifests remain
352
+ supported, but ordinary source ZIPs do not need a manifest.
353
+ Import preserves the complete selected Skill directory, including nested
354
+ `references/`, `assets/`, `scripts/` and other resources with their original paths
355
+ and bytes. `SKILL.md` identifies the Skill; it is not a whitelist of its contents.
356
+ Saving and exporting an incomplete copy retains these resources too.
357
+
358
+ Import creates a local working copy. Missing Bundle files are listed in a simple
359
+ completion dialog: **Not now** keeps the copy with an **Incomplete** card warning;
360
+ **Complete with AI** opens its editor and prefills the host conversation with the
361
+ missing items. The user sends the request and reviews the ordinary source diff,
362
+ preview and save. The source file tree also offers **New file** for manual additions;
363
+ new paths share the existing unsaved changes, diff, global save and revert.
364
+ No new model client is used. Kit issues can be corrected in
365
+ its existing source/mount editor. The warning reflects current saved sources.
366
+ Name collisions get distinct local names rather than overwriting content.
367
+
368
+ `contentClient.export` downloads a ZIP directly from the object's overflow menu
369
+ or saved-copy action. There is no source/license form, export modal or licensing
370
+ check. The download preserves source files and readable Unicode titles, without
371
+ internal revision/version suffixes. Export uses the exact saved revision; pending source
372
+ edits retain the existing save/discard behavior. Imported incomplete copies may
373
+ also be exported. Installed content and project pins are unchanged.
374
+
375
+ Import success refreshes the current catalog. Failure to refresh after import
376
+ retries the read, never the import write. File selection cancellation is inert;
377
+ existing transport limits report errors without truncating sources.
378
+
379
+ ## Host contribution beside a working copy
380
+
381
+ `ConversationMessage` and `ConversationActivity` provide the same message and
382
+ collapsible tool-record presentation for Companion and Studio. Hosts supply actual
383
+ public messages, tool names and observed outcomes; these components own no model
384
+ client, transcript store or execution state. Running work uses the shared circular
385
+ indicator and the composer Stop action, without an estimated progress bar. Polling
386
+ preserves a user-collapsed tool group; terminal work stops animating.
387
+
388
+ `InstanceWorkbench` is available as a component value as well as a props type.
389
+ Its optional `renderSupplement({ record, dirty, busy })` renders host controls
390
+ after the existing header. This callback must stay pure; its `dirty` projection
391
+ includes source and title edits. The shared editor keeps source state and save
392
+ behavior. Host containers supply the existing Studio shell and styles, preserve
393
+ pending edits across asynchronous results, and supply `sourceChanges` for
394
+ in-place prepared source changes and explicit save.
395
+
396
+ Hosts composing a persistent conversation beside the content may use
397
+ `embedded` on the workbench to render a section inside their existing main.
398
+ A full Studio retains its original conversation beside the content; a host
399
+ embedding only the content keeps its own conversation and does not read or add a
400
+ second one. A single exact native proposal enters the current source workbench
401
+ directly. Pending proposals preserve the current human edits; replacing one uses the ordinary discard decision and never saves implicitly.
402
+ `InstanceWorkbench.initialView` selects `files` (the unchanged default) or
403
+ `preview` on opening. A Bundle without `panel.yaml` opens its source files even
404
+ when the host requests preview. These presentation options grant no new execution or save
405
+ capability. The shared authoring layout keeps conversation and content scrolling
406
+ separately and places the input below the conversation; a narrow viewport stacks
407
+ both regions. Request history shown by a host must identify its actual scope,
408
+ rather than imply a durable native transcript.
409
+
410
+
411
+ ### Portable import and export
412
+
413
+ Export downloads a `.zip` file containing the original sources and assets under
414
+ `content/` plus `studio-manifest.json` with the exact version, provenance and
415
+ integrity metadata. Import accepts this ZIP or a previously exported JSON envelope
416
+ through the stateless `readArchive` integrity parser, then `instances.importSources`.
417
+ There is no retained import record or separate adoption step. Missing, unexpected or damaged
418
+ files produce a recoverable error; importing never silently repairs a package.
419
+ The existing expanded-content and HTTP request limits still apply. Export checks
420
+ the same import request budget before downloading, so oversized content is
421
+ reported without discarding or truncating source files.
422
+
423
+ An import that succeeds remains successful if refreshing the catalog fails. The
424
+ notice offers a read-only refresh retry without repeating the import. Downloading
425
+ initiates the browser save operation; it does not prove the user saved to disk.
@@ -33,3 +33,29 @@ Generate a versioned inventory from actual tarballs and CLI plugin outputs,
33
33
  include every required license/NOTICE, arrange corresponding source access for
34
34
  applicable components, and verify Linux/Windows/macOS packaging separately.
35
35
  See TODO.md. Do not label a release compliant based only on this inventory.
36
+
37
+ ## fflate 0.8.3
38
+
39
+ Studio uses the unmodified fflate ZIP codec. Upstream: https://github.com/101arrowz/fflate.
40
+
41
+ MIT License
42
+
43
+ Copyright (c) 2026 Arjun Barrett
44
+
45
+ Permission is hereby granted, free of charge, to any person obtaining a copy
46
+ of this software and associated documentation files (the "Software"), to deal
47
+ in the Software without restriction, including without limitation the rights
48
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
49
+ copies of the Software, and to permit persons to whom the Software is
50
+ furnished to do so, subject to the following conditions:
51
+
52
+ The above copyright notice and this permission notice shall be included in all
53
+ copies or substantial portions of the Software.
54
+
55
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
56
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
57
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
58
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
59
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
60
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
61
+ SOFTWARE.