@yugoo-design/dsh-design-studio-ui 0.0.0-stage → 0.1.0-beta.1
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/LICENSE +202 -0
- package/NOTICE +18 -0
- package/README.md +220 -2
- package/THIRD_PARTY_NOTICES.md +35 -0
- package/lib/index.d.ts +632 -0
- package/lib/index.js +5961 -0
- package/licenses/dsh-distribution.json +67 -0
- package/package.json +36 -4
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/NOTICE
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
Yugoo-design
|
|
2
|
+
Copyright 2026 YugooDesign Team
|
|
3
|
+
|
|
4
|
+
Yugoo Design was initiated by Jianfeng Yang, who independently completed
|
|
5
|
+
its initial design and development. The project is maintained by
|
|
6
|
+
YugooDesign Team.
|
|
7
|
+
|
|
8
|
+
Except where otherwise identified, the original code and documentation in this
|
|
9
|
+
repository are licensed under the Apache License, Version 2.0. See LICENSE.
|
|
10
|
+
|
|
11
|
+
Third-party code, dependencies, vendored runtimes, and attributed materials
|
|
12
|
+
retain their own licenses and copyright notices. This notice does not relicense
|
|
13
|
+
those materials. See THIRD_PARTY_NOTICES.md and applicable component notices.
|
|
14
|
+
|
|
15
|
+
DSH distribution materials for this package: licenses/dsh-distribution.json.
|
|
16
|
+
It lists actual output hashes, selected original texts in this package, and external npm dependencies separately.
|
|
17
|
+
Existing third-party materials retain their individual terms.
|
|
18
|
+
Historical Companion/source observations are not claims of complete coverage for this DSH archive.
|
package/README.md
CHANGED
|
@@ -1,3 +1,221 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Shared Design Studio UI
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Studio accepts an explicit host `locale` (`zh` or `en`) with a document/browser
|
|
4
|
+
fallback. Bundle cards use the loader's existing bilingual title and display
|
|
5
|
+
description; IDs and raw source files remain unchanged. Search includes those
|
|
6
|
+
localized catalog fields without replacing the authoritative method description.
|
|
7
|
+
Kit, Bundle and editable-copy catalog cards share the same grid, 15px padding,
|
|
8
|
+
15px title and 12px description scale; differences in content do not introduce a
|
|
9
|
+
separate Kit size variant. Description excerpts stay bounded to three lines.
|
|
10
|
+
Kit cards and file sidebars use the loader-projected optional bilingual display
|
|
11
|
+
description from Mindset frontmatter, with the original description as fallback.
|
|
12
|
+
Bundle file sidebars reuse existing bilingual picker copy. A narrow, independently
|
|
13
|
+
scrollable right sidebar shows full copy; standard file purposes appear after the
|
|
14
|
+
filename in 12px secondary text. Exact standard relative paths are recognized by
|
|
15
|
+
one shared UI map; unknown files have no guessed purpose. No file bytes are edited
|
|
16
|
+
or translated by viewing or changing locale. English names/headings use Title Case,
|
|
17
|
+
actions and explanations use sentence case, following the shared
|
|
18
|
+
[Panel UIUX standard](../../docs/panel-uiux-standard.md); Chinese Kit is 设计套件.
|
|
19
|
+
The sidebar-footer Chinese/English switch is the single Studio language control; hosts
|
|
20
|
+
persist it via `onLocaleChange`. Trial requests snapshot the current Studio
|
|
21
|
+
language as `locale` (`zh-CN` or `en-US`); there is no trial-local selector.
|
|
22
|
+
Switching language never reruns or translates existing results.
|
|
23
|
+
User task text remains byte-exact; natural-language locale
|
|
24
|
+
inference is not implemented. Hosts must bind the result Panel to its recorded
|
|
25
|
+
trial locale rather than inheriting an unrelated browser-origin preference.
|
|
26
|
+
|
|
27
|
+
`MindsetInlineEditor` is an optional control embedded in the original Kit page.
|
|
28
|
+
It lazily creates/reopens a Kit working copy via the existing authoring client,
|
|
29
|
+
edits body segments without trimming, and preserves frontmatter and the unique
|
|
30
|
+
`design_skills` block byte-identically in folded read-only sections. Ambiguous
|
|
31
|
+
protection boundaries refuse editing; CAS failures retain pending input. Hosts
|
|
32
|
+
keep `installedSource` stable and adopt `onSource` into both raw/reading draft
|
|
33
|
+
views. Saved content is marked unpublished, not installed or published.
|
|
34
|
+
Optional `initialId` explicitly reopens a selected saved
|
|
35
|
+
record on mount; `onRecord` returns checked create/read/save receipts so the parent
|
|
36
|
+
can retain/select IDs on the original page. No latest-record heuristic is used.
|
|
37
|
+
Disposal invalidates late requests. `onDirtyChange` supplements the browser-unload guard
|
|
38
|
+
with the host's navigation/close guard. Focused source-plane checks:
|
|
39
|
+
`TSX_TSCONFIG_PATH=packages/studio-ui/tsconfig.json node --import tsx --test packages/studio-ui/tests/mindset-inline.test.mjs`.
|
|
40
|
+
These controller/SSR checks do not establish integrated browser or durable host
|
|
41
|
+
save/reopen acceptance.
|
|
42
|
+
|
|
43
|
+
The Kit files tab uses the same file explorer as Bundle and local-copy views.
|
|
44
|
+
Hosts expose optional `readKitFiles` / `readKitFile` ports for confined, exact-version
|
|
45
|
+
installed source reads; without them only the supplied Mindset is available.
|
|
46
|
+
The Companion adapter provides the full physical tree and bounded UTF-8 reads.
|
|
47
|
+
Raw Mindset includes the mount XML. Local Kit mounts are explicit checkboxes over
|
|
48
|
+
retained exact Bundle versions, saved through `updateMounts` with revision checks;
|
|
49
|
+
installed originals stay protected. Removal means deleting a recoverable local
|
|
50
|
+
copy, not uninstalling a Kit or Bundle. UI classes use the `ygd-studio` prefix;
|
|
51
|
+
package identities are unchanged. Studio loading locations share one indicator
|
|
52
|
+
with the KAG indeterminate sweep treatment (no fake completion percentage).
|
|
53
|
+
|
|
54
|
+
The title row owns the sole explicit trial entry. It checks the host connection,
|
|
55
|
+
then asks the native Agent to prepare a concrete input and execute it in the same
|
|
56
|
+
turn; merely mounting the UI never runs a Bundle. Preview uses left `panel.yaml`
|
|
57
|
+
and right sample Panel; trial uses the same split with left test input and right
|
|
58
|
+
actual isolated runtime Panel, not a modal or another mode toolbar.
|
|
59
|
+
A host may supply `panelUrl`
|
|
60
|
+
for its authenticated Panel-only presentation; otherwise the independent result
|
|
61
|
+
link remains available. Editing input does not execute anything: an
|
|
62
|
+
explicit rerun sends the exact edited text to a separate isolated trial. History
|
|
63
|
+
keeps the original input of each result. A waiting interaction may start another
|
|
64
|
+
round, but an uncertain or running sibling trial blocks reentry.
|
|
65
|
+
|
|
66
|
+
Hosts can supply `trials: StudioTrialClient` to enable a Bundle-local trial action,
|
|
67
|
+
including saved Panel draft revisions. The adapter owns immutable snapshots,
|
|
68
|
+
isolated projects, native dispatch, durable history and cleanup. This UI does not
|
|
69
|
+
start a model or write Design Files. Queue acceptance is not completion; missing
|
|
70
|
+
native evidence remains `unknown`. Stop failures leave the trial active, and only
|
|
71
|
+
verified terminal trials can be removed. Result links open the isolated runtime
|
|
72
|
+
Panel. The installed viewer and draft editor retain their existing behavior when
|
|
73
|
+
the capability is absent. The browser fixture under `tests/trial-browser.tsx`
|
|
74
|
+
tests presentation only and is not evidence of native execution.
|
|
75
|
+
The optional `checkConnection` port must return `available`, `unavailable` or
|
|
76
|
+
`unknown` from non-generating transport/session evidence. Absent, unknown or failed
|
|
77
|
+
checks do not launch a trial. API/thread reachability is not proof that a native
|
|
78
|
+
turn was consumed or completed; the existing trial evidence rules remain in force.
|
|
79
|
+
|
|
80
|
+
The trial's fixed bottom-right actions are “Undo edits” and “Demonstrate save”.
|
|
81
|
+
They demonstrate the Panel's saved UI state in the current browser only; they do
|
|
82
|
+
not publish design changes or send an Agent continuation. Undo returns to the
|
|
83
|
+
latest local demonstration baseline. Reload restores the actual generated result.
|
|
84
|
+
|
|
85
|
+
Optional authoring: hosts may supply `StudioAuthoring` to edit the left YAML in
|
|
86
|
+
the preview workplane. The first actual source change lazily creates a retained
|
|
87
|
+
Panel draft through the existing port, preserving text typed during creation.
|
|
88
|
+
Simply viewing installed content never creates a draft or changes the installed
|
|
89
|
+
Bundle. Subsequent source edits debounce the shared runtime preview, and save uses
|
|
90
|
+
the existing optimistic revision check. An unambiguous retained copy can be resumed
|
|
91
|
+
explicitly; a delayed recovery read cannot replace subsequently typed source.
|
|
92
|
+
Late or mismatched save receipts cannot switch another Bundle's trial source.
|
|
93
|
+
Trials of edited Panels use the saved
|
|
94
|
+
exact draft revision; unsaved source must be saved first. Native Panels without
|
|
95
|
+
`panel.yaml` explicitly explain that they have no editable YAML source.
|
|
96
|
+
`StudioPanelDraftController` rejects stale or mismatched preview replies. Hosts
|
|
97
|
+
render with sample-only ports; the shared UI imports no Panel implementation.
|
|
98
|
+
`onDraftDirtyChange` guards host closure and navigation. Confirmation locks a
|
|
99
|
+
local draft, not a published Kit; preview alone never starts execution.
|
|
100
|
+
|
|
101
|
+
`dsh-design-studio-ui` is the shared React Studio. Its sidebar contains Kits
|
|
102
|
+
and Bundles, with Kits as the entry view. A host may additionally expose the
|
|
103
|
+
accepted Component Library capability. A compact breadcrumb/refresh bar sits
|
|
104
|
+
above the workspace. The approved Studio demo supplies the layout and interaction
|
|
105
|
+
baseline; Yugoo supplies neutral typography, colors and control details. Storage
|
|
106
|
+
concepts such as Panel drafts must not add top-level navigation sections.
|
|
107
|
+
The optional **Panel Component Library / 面板组件库** entry is a bottom sidebar
|
|
108
|
+
utility, above the shared language switch, not another primary Kit/Bundle section.
|
|
109
|
+
|
|
110
|
+
The optional `componentLibrary: StudioComponentLibrary` adapter supplies the
|
|
111
|
+
actual same-build DSL catalog, display names, trusted synthetic examples and
|
|
112
|
+
the bundled `design-component` Skill. The UI does not register components or
|
|
113
|
+
import Core/Panel. The Companion adapter renders examples through the existing
|
|
114
|
+
`DslPanel`, using only confined fixture artifact reads and no data-write port.
|
|
115
|
+
Search, independent catalog scrolling, fixed read-only examples,
|
|
116
|
+
copyable full declarations and an extension prompt are available. Entries without
|
|
117
|
+
standalone examples remain visible with an honest limitation and a query for the
|
|
118
|
+
existing `design_list_panel_components` authoring tool. DSL availability and
|
|
119
|
+
generated-subset eligibility are distinct. All currently registered components
|
|
120
|
+
have populated examples; runtime-log examples explicitly use a finite synthetic
|
|
121
|
+
transcript and never read native Host logs. No host, model, project-save,
|
|
122
|
+
installation or publication port is granted by this view.
|
|
123
|
+
Preview containers distinguish compact inline examples, bounded navigation
|
|
124
|
+
examples and height-filling workspaces, while keeping the same renderer and
|
|
125
|
+
declarations. This is component documentation, not a draft editor or state-test
|
|
126
|
+
workbench: examples cannot modify their content, save, or create drafts. Viewing
|
|
127
|
+
interactions such as tabs, expansion and record navigation remain available.
|
|
128
|
+
An optional host `renderDirectory` port reuses the real shared Panel tree groups
|
|
129
|
+
and items; the host-neutral fallback uses expandable disclosure groups. Human-facing
|
|
130
|
+
catalog and preview titles use the selected locale; machine component identifiers
|
|
131
|
+
remain in Declaration and Usage, not a second apparent title.
|
|
132
|
+
Hosts may additionally supply `libraries` read-only metadata. A separate catalog
|
|
133
|
+
shows primary third-party UI libraries, package names, exact same-build resolved
|
|
134
|
+
versions and bilingual purposes. This is not an exhaustive transitive dependency
|
|
135
|
+
or license inventory, an update manager or a second DSL registration authority.
|
|
136
|
+
Companion derives version values from the same package metadata used by its
|
|
137
|
+
browser build; changing these entries never installs, upgrades or enables a component.
|
|
138
|
+
The self-contained Skill's single source is
|
|
139
|
+
`packages/companion/plugin/design-system/skills/design-component/SKILL.md`;
|
|
140
|
+
Companion embeds those exact bytes for copying and includes them in its existing
|
|
141
|
+
Codex, Claude Code and Qoder packaging slots. WorkBuddy packaging and installed
|
|
142
|
+
plugin activation are separate integration steps. Custom compiled components
|
|
143
|
+
require a development-source change and the existing registration/validation/UI
|
|
144
|
+
contract; this view is not a dynamic executable component marketplace.
|
|
145
|
+
|
|
146
|
+
Bundle pages put Source files first and Panel preview second. The recursive file
|
|
147
|
+
explorer displays actual source paths, including nested reference folders. Trial
|
|
148
|
+
execution is a Bundle-local action. Installed previews use the optional read-only
|
|
149
|
+
`previewInstalled` transport and the same runtime renderer. The installed host
|
|
150
|
+
loads Bundle-owned `reference/preview.json` before runtime initial values; the
|
|
151
|
+
preview displays the actual selected sample rather than an empty placeholder.
|
|
152
|
+
A missing sample is a diagnostic, not a fabricated populated Panel.
|
|
153
|
+
User-provided preview samples remain
|
|
154
|
+
isolated from project files. Request revisions and exact Kit/Bundle pins prevent
|
|
155
|
+
obsolete responses from replacing the current preview.
|
|
156
|
+
|
|
157
|
+
Mindset reading separates its body from frontmatter and the generated
|
|
158
|
+
`design_skills` section. The complete byte-exact file remains available in a
|
|
159
|
+
dialog; the reading projection never rewrites source. The contents list is
|
|
160
|
+
derived from rendered headings, so headings inside fenced examples do not create
|
|
161
|
+
incorrect navigation entries. Installed reads never mutate the original.
|
|
162
|
+
Hosts may supply the optional `instances` client for complete retained local copies.
|
|
163
|
+
Copy opens an independent editable file set; title-pencil renaming changes the
|
|
164
|
+
selected language's display name without changing source identities. The header places
|
|
165
|
+
an arrow-only Back action on the left and direct Copy/Delete actions on the right.
|
|
166
|
+
Deletion checks local references and retains recoverable
|
|
167
|
+
data. The existing Kits/Bundles lists include local copies, with no new navigation
|
|
168
|
+
area. Saves use optimistic revisions; preview compiles saved local bytes through
|
|
169
|
+
the existing renderer. Copies are unpublished and never retarget active sessions.
|
|
170
|
+
Hosts without this capability expose no inert mutation placeholders. Mount editing,
|
|
171
|
+
publication and native trial dispatch of complete local copies remain separate
|
|
172
|
+
capabilities, not implied by save or preview.
|
|
173
|
+
|
|
174
|
+
When Kit authoring is available, Mindset editing stays in the original document
|
|
175
|
+
page. Complete source is saved through the existing revision-checked draft API;
|
|
176
|
+
frontmatter and the generated mount block are preserved byte-for-byte. Saved
|
|
177
|
+
records can be selected explicitly after refresh, never by an implicit “latest”
|
|
178
|
+
lookup. Reading/full-file views show the selected saved draft, clearly unpublished;
|
|
179
|
+
the installed source remains the immutable editing base. Leaving dirty input
|
|
180
|
+
requires confirmation. This is not Kit publication or full Bundle-file editing.
|
|
181
|
+
|
|
182
|
+
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.
|
|
183
|
+
|
|
184
|
+
Styles are scoped to Studio: system CJK typography, purple `#7c5af6` brand accents
|
|
185
|
+
(hover `#6849d8`, active `#5032bc`), neutral `#272727` primary text,
|
|
186
|
+
`#6d6d6d` secondary text, light borders, 8px control radii, and compact search and
|
|
187
|
+
file rows. They do not import a Panel or Core theme. Markdown uses an
|
|
188
|
+
injection-safe subset renderer; raw Bundle files remain byte-exact.
|
|
189
|
+
All Studio page title regions share one compact baseline: a 32px content row
|
|
190
|
+
with 8px above and below (48px single-line height), 18px/24px medium-weight
|
|
191
|
+
headings, and 32px title icons and action buttons. Kit, Bundle, catalog and local
|
|
192
|
+
copy pages do not own competing vertical sizes. Optional catalog guidance sits
|
|
193
|
+
beside the title when space permits. Long titles, guidance and action rows may
|
|
194
|
+
wrap naturally on narrow screens; the header never clips them to a fixed height.
|
|
195
|
+
Pipe tables render with column headers, delimiter alignment, inline code and
|
|
196
|
+
emphasis. Escaped pipes stay in their cells; fenced examples remain code. Tables
|
|
197
|
+
use compact borders and a horizontal scroll container within the file viewer.
|
|
198
|
+
UI copy follows the host document/browser locale, but authored file content is never
|
|
199
|
+
translated or abbreviated in the document viewer.
|
|
200
|
+
|
|
201
|
+
### Content archives
|
|
202
|
+
|
|
203
|
+
Hosts may pass `contentClient` to expose **Content archives** in the existing
|
|
204
|
+
workspace toolbar; the sidebar remains Kits / Bundles. The archive workbench
|
|
205
|
+
accepts a file or pasted JSON, retains the import and displays its exact identity,
|
|
206
|
+
provenance and validation diagnostics. Import preparation does not create a
|
|
207
|
+
working copy. Explicit adoption retains validated content in the local content
|
|
208
|
+
library. Adopting a complete Kit additionally requires `kitAuthoring`; its receipt
|
|
209
|
+
opens the exact unconfirmed Kit working copy in the existing editor. A standalone
|
|
210
|
+
Bundle requires no Kit editor and opens its exact source workspace after the
|
|
211
|
+
catalog refresh. It is not implicitly mounted into a Kit or attached to a project.
|
|
212
|
+
The adoption receipt must preserve the import ID, exact content closure and inert
|
|
213
|
+
authority; a Bundle receipt must not contain a Kit draft. Adoption never overwrites
|
|
214
|
+
installed sources, retargets project pins, publishes or executes content.
|
|
215
|
+
|
|
216
|
+
Unprepared input participates in workspace navigation and browser-unload guards;
|
|
217
|
+
leaving the workbench invalidates late UI responses. Export uses the selected
|
|
218
|
+
installed Kit's exact version and user-supplied source/license declarations, and
|
|
219
|
+
downloads the returned archive bytes unchanged. Hosts without `contentClient`
|
|
220
|
+
retain the existing UI. The size check includes the JSON RPC wrapper and escaping
|
|
221
|
+
against Companion's 12 MiB request limit; it never truncates an archive.
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
# Third-party licensing inventory
|
|
2
|
+
|
|
3
|
+
Original Yugoo-design code and documentation are licensed under Apache-2.0,
|
|
4
|
+
except where otherwise identified. Third-party material retains its original
|
|
5
|
+
license. This inventory is a preparation record, not a complete release SBOM
|
|
6
|
+
or a substitute for license texts, source provision, or other obligations.
|
|
7
|
+
|
|
8
|
+
## Known components requiring release checks
|
|
9
|
+
|
|
10
|
+
| Component | License / location | Release requirement to verify |
|
|
11
|
+
| --- | --- | --- |
|
|
12
|
+
| Official Ladybug WASM dependency `@ladybugdb/wasm-core@0.21.1` | Package declares MIT; original text and public source locator in `third-party/native/ladybug-wasm-core-0.21.1/` | Current `packages/knowledge-ladybug` dependency route. Preserve Kùzu Inc./Ladybug Memory Inc. notices and verify actual release inclusion. The installed package has no separate third-party inventory or precise build-provenance file; embedded components and source/build correspondence remain unresolved. Package MIT is not a blanket license for the complete WASM. |
|
|
13
|
+
| Historical vendored Ladybug WASM runtime | MIT; `vendor/ladybug/runtime/LICENSE` | Separate legacy route: preserve its own copyright/license, provenance and patch if distributed. Do not use its patch/source evidence as the build provenance of the official npm dependency. Compiled-in component checks remain separate. |
|
|
14
|
+
| DSH code and reused utilities | MIT; `deepseek-harness/LICENSE` | Retain original notices; distinguish external host from copied/bundled utilities. |
|
|
15
|
+
| Pinned DSH JSON value utility (Core) | MIT; repository `packages/core/third-party/dsh-json/LICENSE`, Core package `third-party/dsh-json/LICENSE` | Preserve the original license and provenance README with the Core tarball; verify actual packed files. |
|
|
16
|
+
| ELK / elkjs | EPL-2.0 | Include license and corresponding source availability information; verify actual bundled version and modifications. |
|
|
17
|
+
| sharp | Apache-2.0 | Preserve applicable license and upstream notices. |
|
|
18
|
+
| Prebuilt sharp/libvips dependency bundle | Local `@img/sharp-libvips-*` package declares LGPL-3.0-or-later; contains multiple licenses | Inventory all bundled libraries per platform; provide required corresponding source/build materials and verify replacement/relinking conditions. libvips upstream alone is LGPL-2.1-or-later; do not confuse that with the distributed bundle's terms. |
|
|
19
|
+
| bpmn-js | bpmn.io License | Include original license/copyright; keep the required watermark visible and unchanged. |
|
|
20
|
+
| Design-style reference material and icon assets | Apache-2.0, MIT, ISC | Preserve the detailed notices in `packages/skills-web-app/skills/design_style/THIRD_PARTY_NOTICES.md`; verify required full license texts are distributed. |
|
|
21
|
+
|
|
22
|
+
## Scope exclusions
|
|
23
|
+
|
|
24
|
+
- `deepseek-harness/` and `vendor/ladybug/` are not relicensed by the root LICENSE.
|
|
25
|
+
- External packages keep their own licenses even when bundled into an output.
|
|
26
|
+
- Separately licensed Kit content and assets keep their explicit licenses.
|
|
27
|
+
- Downloaded model weights require their own version-specific license review;
|
|
28
|
+
the inference engine's license does not license the weights.
|
|
29
|
+
|
|
30
|
+
## Release work still pending
|
|
31
|
+
|
|
32
|
+
Generate a versioned inventory from actual tarballs and CLI plugin outputs,
|
|
33
|
+
include every required license/NOTICE, arrange corresponding source access for
|
|
34
|
+
applicable components, and verify Linux/Windows/macOS packaging separately.
|
|
35
|
+
See TODO.md. Do not label a release compliant based only on this inventory.
|