@huaweidevtools/aishell-dsh-huaweicloud-docs 0.0.0-stage → 0.0.1-beta.3

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 ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined in Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is derived from (or based upon) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2026 Huawei Cloud AI Shell
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
200
+ implied. See the License for the specific language governing
201
+ permissions and limitations under the License.
package/README.md CHANGED
@@ -1,3 +1,64 @@
1
- # Temporary Holding Version
1
+ # @huaweidevtools/aishell-dsh-huaweicloud-docs
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ Tells DSH's model where to read Huawei Cloud product documentation. One system-prompt section; no tools, no browser half, no other dependency.
4
+
5
+ ## What it injects
6
+
7
+ ```
8
+ Huawei Cloud product documentation — for what a product is, what it supports,
9
+ its quotas and limits, or its billing model — is indexed at
10
+ https://support.huaweicloud.com/llms.txt
11
+
12
+ That index lists every Huawei Cloud product by category, each entry naming the
13
+ product's own llms.txt. Read it to find the product, then read that product's
14
+ file for the detail. Do not answer questions about a product's capabilities or
15
+ limits from memory; they change between releases, and the documentation is the
16
+ authority.
17
+ ```
18
+
19
+ ## Why only a pointer
20
+
21
+ The index itself is ~35 KB of product names — real value, but a per-turn cost of roughly 9k tokens, of which any one task needs a single entry. So the section carries the pointer, and the model fetches the index — and then the one product under it — with the web-fetch tool it already has. That is the shape `llms.txt` exists for.
22
+
23
+ The URL answers: `https://support.huaweicloud.com/llms.txt` returns the index as `text/plain` (~35 KB), and each product entry links to that product's own file — ECS, for one, resolves to ~500 KB of real documentation. `web_fetch`'s User-Agent is `deepseek-harness/0.0.1 (+https://github.com/deepseek-ai)`.
24
+
25
+ That User-Agent is not something the model can set. `web_fetch` exposes no header parameter — the value is a plugin `Config` field (`userAgent`) defaulting to the constant above. So any instruction to fetch with a particular browser User-Agent is unactionable for the model, and this package issues none.
26
+
27
+ ## Where it sits in the prompt
28
+
29
+ Early — immediately after the deployment persona prefix, ahead of every policy and tool section. Background knowledge is worth having before the model starts planning, rather than discovering it once it reaches the tool list.
30
+
31
+ Measured against the real `SystemPrompt` service, the assembled prompt reads:
32
+
33
+ ```
34
+ harness:identity -1000
35
+ deployment:persona-prefix 0
36
+ aishell:huaweicloud-docs 100 ← this plugin
37
+ plan:policy 500
38
+ tool:* 1000+
39
+ deployment:persona-suffix 10200
40
+ ```
41
+
42
+ So it lands inside the persona envelope (the prefix opens at `0`, the suffix closes at `10200`) and before every policy and tool slot. The position is a number (`HUAWEICLOUD_DOCS_ORDER = 100`) rather than one of the framework's named slots, because its placement table is closed: `PromptSectionOrderName` is `keyof` a fixed constant, so a `HUAWEICLOUD_DOCS` name has nowhere to go. The table leaves the gap between `0` and `500` empty, and `100` sits inside it.
43
+
44
+ A section rather than a runtime context because the URL never changes. `context()` is for facts that flip — the read-only policy uses it for exactly that reason — and a constant belongs in a section.
45
+
46
+ ## Install
47
+
48
+ ```sh
49
+ # On its own.
50
+ dsh plugin --profile <name> add @huaweidevtools/aishell-dsh-huaweicloud-docs
51
+
52
+ # Or with the rest of the aishell plugin set.
53
+ dsh plugin --profile <name> add @huaweidevtools/aishell-dsh-base
54
+ ```
55
+
56
+ ## What it does NOT touch
57
+
58
+ - No tools. The model uses its existing web-fetch tool; this plugin adds none.
59
+ - No credentials, no network calls of its own.
60
+ - No browser half — nothing to render.
61
+
62
+ ## License
63
+
64
+ Apache License 2.0.
@@ -0,0 +1,10 @@
1
+ # aishell-huaweicloud-docs bundle patch: inserts the documentation pointer.
2
+ # Install standalone: `dsh plugin --profile <name> add @huaweidevtools/aishell-dsh-huaweicloud-docs`
3
+ #
4
+ # The single row mounts a host-only plugin: it registers one system-prompt
5
+ # section naming the Huawei Cloud documentation index. It has no browser half
6
+ # and no tools — the model reads the index with the ordinary web-fetch tool it
7
+ # already has.
8
+ - insert:
9
+ - id: aishell-huaweicloud-docs
10
+ name: '@huaweidevtools/aishell-dsh-huaweicloud-docs'
package/lib/index.js ADDED
@@ -0,0 +1,68 @@
1
+ //#region src/index.ts
2
+ /**
3
+ * Position of the documentation pointer in the assembled prompt.
4
+ *
5
+ * A number, not a name, because the framework's placement table is closed:
6
+ * `PromptSectionOrderName` is `keyof` a fixed constant, and
7
+ * `getSectionOrder('HUAWEICLOUD_DOCS')` would return `undefined` — there is no
8
+ * slot for product-domain background. Every shipped plugin reads a name from
9
+ * that table, so this is the one place this package departs from them.
10
+ *
11
+ * The table's own entries leave the gap between the persona prefix (0) and the
12
+ * first policy (500) empty, and 100 sits inside it. Note that "ahead of the
13
+ * persona" would be wrong as well as worse: the persona opens at 0, so the only
14
+ * order that precedes it is a negative one — before `harness:identity` at
15
+ * -1000, i.e. before the prompt has said what it is. 100 puts this after the
16
+ * persona and before anything the model is asked to reason about.
17
+ */
18
+ const HUAWEICLOUD_DOCS_ORDER = 100;
19
+ /** Name this contribution registers under; unique across the assembled prompt. */
20
+ const DOCS_SECTION_NAME = "aishell:huaweicloud-docs";
21
+ /** The Huawei Cloud documentation index. */
22
+ const DOCS_INDEX_URL = "https://support.huaweicloud.com/llms.txt";
23
+ /**
24
+ * What the model reads.
25
+ *
26
+ * The last sentence is the load-bearing one: a model asked about a product's
27
+ * quotas or billing will otherwise answer from memory, and those numbers move
28
+ * between releases. Naming the authority is what makes the pointer worth
29
+ * carrying.
30
+ */
31
+ const DOCS_POINTER = `Huawei Cloud product documentation — for what a product is, what it supports, its quotas and limits, or its billing model — is indexed at ${DOCS_INDEX_URL}
32
+
33
+ That index lists every Huawei Cloud product by category, each entry naming the product's own llms.txt. Read it to find the product, then read that product's file for the detail. Do not answer questions about a product's capabilities or limits from memory; they change between releases, and the documentation is the authority.`;
34
+ /**
35
+ * Register the documentation pointer.
36
+ *
37
+ * Deferred behind `ctx.inject` rather than declared in this plugin's own
38
+ * `inject`: the pointer is an enhancement, and a deployment without the system
39
+ * prompt should lose the pointer rather than fail to mount.
40
+ *
41
+ * @param ctx - host context.
42
+ */
43
+ function registerDocsPointer(ctx) {
44
+ ctx.inject(["systemPrompt"], (scope) => {
45
+ scope.systemPrompt.section({
46
+ name: DOCS_SECTION_NAME,
47
+ order: HUAWEICLOUD_DOCS_ORDER,
48
+ interpolate: false,
49
+ text: DOCS_POINTER
50
+ });
51
+ });
52
+ }
53
+ const name = "aishell-huaweicloud-docs";
54
+ /**
55
+ * No required services.
56
+ *
57
+ * The one dependency is taken through `ctx.inject` inside
58
+ * {@link registerDocsPointer}, so a deployment without a system prompt loses
59
+ * the pointer instead of the whole entry failing to activate.
60
+ */
61
+ const inject = [];
62
+ function apply(ctx) {
63
+ registerDocsPointer(ctx);
64
+ }
65
+
66
+ //#endregion
67
+ export { DOCS_INDEX_URL, DOCS_POINTER, DOCS_SECTION_NAME, HUAWEICLOUD_DOCS_ORDER, apply, inject, name, registerDocsPointer };
68
+ //# sourceMappingURL=index.js.map
@@ -0,0 +1,86 @@
1
+ /**
2
+ * Huawei Cloud product-documentation pointer for DSH.
3
+ *
4
+ * ## What this injects, and why it is only a pointer
5
+ *
6
+ * One fact: where to read Huawei Cloud's product documentation. The index at
7
+ * `llms.txt` is ~35 KB of product names — real value, but a per-turn cost of
8
+ * roughly 9k tokens, of which a given task needs one entry. So the plugin
9
+ * carries the pointer and lets the model fetch the index (and then the one
10
+ * product under it) with the web-fetch tool it already has. That is the shape
11
+ * `llms.txt` is designed for.
12
+ *
13
+ * ## Why a prompt section and not a runtime context
14
+ *
15
+ * The URL never changes, so this is static knowledge rather than session state.
16
+ * `systemPrompt.section()` is the registration for text that is always present;
17
+ * `context()` is for facts that flip (the read-only policy uses it for that
18
+ * reason — it appears and disappears with the mode). A section is re-rendered
19
+ * on every assembly either way; the difference is that a context snapshot is
20
+ * only committed when its text changes.
21
+ *
22
+ * ## Where it sits in the prompt
23
+ *
24
+ * Early: immediately after the deployment persona prefix, ahead of every policy
25
+ * and tool section. Background knowledge is worth reading before the model
26
+ * starts planning — it should know where to look things up, not discover it
27
+ * once it has reached the tool list.
28
+ *
29
+ * Measured, not asserted — mounting this plugin against the real `SystemPrompt`
30
+ * service renders, in order: `harness:identity`, the persona prefix, this
31
+ * section, then the policy and tool slots, then the persona suffix.
32
+ *
33
+ * @module @huaweidevtools/aishell-dsh-huaweicloud-docs
34
+ */
35
+ import type { Context } from '@deepseek-ai/cordis';
36
+ /**
37
+ * Position of the documentation pointer in the assembled prompt.
38
+ *
39
+ * A number, not a name, because the framework's placement table is closed:
40
+ * `PromptSectionOrderName` is `keyof` a fixed constant, and
41
+ * `getSectionOrder('HUAWEICLOUD_DOCS')` would return `undefined` — there is no
42
+ * slot for product-domain background. Every shipped plugin reads a name from
43
+ * that table, so this is the one place this package departs from them.
44
+ *
45
+ * The table's own entries leave the gap between the persona prefix (0) and the
46
+ * first policy (500) empty, and 100 sits inside it. Note that "ahead of the
47
+ * persona" would be wrong as well as worse: the persona opens at 0, so the only
48
+ * order that precedes it is a negative one — before `harness:identity` at
49
+ * -1000, i.e. before the prompt has said what it is. 100 puts this after the
50
+ * persona and before anything the model is asked to reason about.
51
+ */
52
+ export declare const HUAWEICLOUD_DOCS_ORDER = 100;
53
+ /** Name this contribution registers under; unique across the assembled prompt. */
54
+ export declare const DOCS_SECTION_NAME = "aishell:huaweicloud-docs";
55
+ /** The Huawei Cloud documentation index. */
56
+ export declare const DOCS_INDEX_URL = "https://support.huaweicloud.com/llms.txt";
57
+ /**
58
+ * What the model reads.
59
+ *
60
+ * The last sentence is the load-bearing one: a model asked about a product's
61
+ * quotas or billing will otherwise answer from memory, and those numbers move
62
+ * between releases. Naming the authority is what makes the pointer worth
63
+ * carrying.
64
+ */
65
+ export declare const DOCS_POINTER = "Huawei Cloud product documentation \u2014 for what a product is, what it supports, its quotas and limits, or its billing model \u2014 is indexed at https://support.huaweicloud.com/llms.txt\n\nThat index lists every Huawei Cloud product by category, each entry naming the product's own llms.txt. Read it to find the product, then read that product's file for the detail. Do not answer questions about a product's capabilities or limits from memory; they change between releases, and the documentation is the authority.";
66
+ /**
67
+ * Register the documentation pointer.
68
+ *
69
+ * Deferred behind `ctx.inject` rather than declared in this plugin's own
70
+ * `inject`: the pointer is an enhancement, and a deployment without the system
71
+ * prompt should lose the pointer rather than fail to mount.
72
+ *
73
+ * @param ctx - host context.
74
+ */
75
+ export declare function registerDocsPointer(ctx: Context): void;
76
+ export declare const name = "aishell-huaweicloud-docs";
77
+ /**
78
+ * No required services.
79
+ *
80
+ * The one dependency is taken through `ctx.inject` inside
81
+ * {@link registerDocsPointer}, so a deployment without a system prompt loses
82
+ * the pointer instead of the whole entry failing to activate.
83
+ */
84
+ export declare const inject: readonly string[];
85
+ export declare function apply(ctx: Context): void;
86
+ //# sourceMappingURL=index.d.ts.map
package/package.json CHANGED
@@ -1,6 +1,46 @@
1
1
  {
2
2
  "name": "@huaweidevtools/aishell-dsh-huaweicloud-docs",
3
- "version": "0.0.0-stage",
4
- "stub": true,
5
- "description": "Temporary package placeholder for staged publishing"
3
+ "description": "Points DSH's model at Huawei Cloud's product documentation index (support.huaweicloud.com/llms.txt)",
4
+ "version": "0.0.1-beta.3",
5
+ "publishConfig": {
6
+ "access": "public"
7
+ },
8
+ "repository": {
9
+ "type": "git",
10
+ "url": "git+https://github.com/yusheng-g/aishell-dsh-plugins.git",
11
+ "directory": "packages/aishell-huaweicloud-docs"
12
+ },
13
+ "type": "module",
14
+ "main": "lib/index.js",
15
+ "types": "lib/types/index.d.ts",
16
+ "exports": {
17
+ ".": {
18
+ "types": "./lib/types/index.d.ts",
19
+ "default": "./lib/index.js"
20
+ }
21
+ },
22
+ "files": [
23
+ "lib/index.js",
24
+ "lib/types/**/*.d.ts",
25
+ "cordis.patch.yml"
26
+ ],
27
+ "license": "Apache-2.0",
28
+ "peerDependencies": {
29
+ "@deepseek-ai/cordis": "^4.0.4",
30
+ "@deepseek-ai/dsh-system-prompt": "0.2.0-rc.1 || 0.2.1-rc.1 || 0.2.1-rc.2 || 0.2.1"
31
+ },
32
+ "devDependencies": {
33
+ "@deepseek-ai/cordis": "^4.0.4",
34
+ "@deepseek-ai/dsh-system-prompt": "0.2.0-rc.1 || 0.2.1-rc.1 || 0.2.1-rc.2 || 0.2.1",
35
+ "tsdown": "^0.10.0",
36
+ "typescript": "^5.7.0"
37
+ },
38
+ "dsh": {
39
+ "bundle": {
40
+ "patch": "./cordis.patch.yml"
41
+ }
42
+ },
43
+ "scripts": {
44
+ "build:bundle": "tsdown"
45
+ }
6
46
  }