@huaweidevtools/aishell-dsh-deploy 0.0.26 → 0.0.28

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/lib/index.js CHANGED
@@ -1691,7 +1691,7 @@ function withAnchoredPaths(args, ctx) {
1691
1691
  * written by earlier releases carry it — so it is kept even though there is no
1692
1692
  * server.
1693
1693
  */
1694
- const SERVER_VERSION = "aishell-deploy 0.0.26";
1694
+ const SERVER_VERSION = "aishell-deploy 0.0.28";
1695
1695
 
1696
1696
  //#endregion
1697
1697
  //#region src/deployment-state.ts
@@ -10290,15 +10290,19 @@ const PERMISSION_CONTEXT_NAME = "aishell:permission-policy";
10290
10290
  /**
10291
10291
  * What the model reads while mutations are refused.
10292
10292
  *
10293
- * Three paragraphs, each doing one job: the state and its scope, the route
10294
- * the gate does not cover, and the way of working that keeps a read-only
10295
- * session useful.
10293
+ * Each paragraph does one job: the state, the boundary of what it governs, the
10294
+ * route the gate does not cover, what sits outside the switch, and the way of
10295
+ * working that keeps a read-only session useful.
10296
10296
  */
10297
- const READ_ONLY_POLICY = `Current HuaweiCloud permission mode: read-only — nothing in the HuaweiCloud account is to change, by any route, including resources reachable directly.
10297
+ const READ_ONLY_POLICY = `Current HuaweiCloud permission mode: read-only — nothing in this HuaweiCloud account is to change.
10298
10298
 
10299
- An EIP, a tunnel, or an internal address that answers is still the same account. Reads over such a path are fine; state changes are not. Reaching a resource by a route the permission check does not cover does not make the change allowed — do not use one to do what a refusal declined.
10299
+ This switch governs this account and nothing else. It is not a sandbox and not a global read-only posture.
10300
10300
 
10301
- Local work is unaffected: files and local processes are yours. Treat the session as review work — carry the investigation through and produce the complete change (plan, exact commands, cost or impact), stating what would be applied. Ask for read-write only when a specific operation is blocked.`;
10301
+ An EIP, a tunnel, or an internal address that answers a request is still this account reached another way. Reads over such a path are fine; changes to the account are not. Reaching an account resource by a route the permission check does not cover does not make the change allowed — do not use one to do what a refusal declined.
10302
+
10303
+ Everything outside this account is untouched and stays open: local files and processes, containers, other cloud accounts, any other service. Work there as you normally would.
10304
+
10305
+ Treat the session as review work for the HuaweiCloud part — carry the investigation through and produce the complete change (plan, exact commands, cost or impact), stating what would be applied. Ask for read-write only when a specific operation on the account is blocked.`;
10302
10306
  /**
10303
10307
  * The text this context contributes for one mode.
10304
10308
  *
@@ -20,11 +20,14 @@
20
20
  * refusal cannot be talked around.
21
21
  *
22
22
  * This text therefore does not restate the gate's rules. It covers what the
23
- * gate cannot: the way of working. A read-only session is a review session, and
24
- * the model should carry the work through rather than decline it. The
25
- * over-refusal it guards against is the default failure of a prompt-side
26
- * constraint: a model that reads "read-only" as "I may not touch anything",
27
- * stops early, and leaves the user with less than they asked for.
23
+ * gate cannot: where the boundary lies and the way of working inside it. A
24
+ * read-only session is a review session on the account, and the model should
25
+ * carry that work through rather than decline it.
26
+ *
27
+ * The boundary is named because a restriction stated alone is read as a blanket
28
+ * ban. The switch governs one account; work outside it — local files,
29
+ * containers, another cloud — is not something this text or the gate reaches,
30
+ * and the text says so, the way a refusal names what remains available.
28
31
  *
29
32
  * ## The gap this text cannot close
30
33
  *
@@ -46,11 +49,11 @@ export declare const PERMISSION_CONTEXT_NAME = "aishell:permission-policy";
46
49
  /**
47
50
  * What the model reads while mutations are refused.
48
51
  *
49
- * Three paragraphs, each doing one job: the state and its scope, the route
50
- * the gate does not cover, and the way of working that keeps a read-only
51
- * session useful.
52
+ * Each paragraph does one job: the state, the boundary of what it governs, the
53
+ * route the gate does not cover, what sits outside the switch, and the way of
54
+ * working that keeps a read-only session useful.
52
55
  */
53
- export declare const READ_ONLY_POLICY = "Current HuaweiCloud permission mode: read-only \u2014 nothing in the HuaweiCloud account is to change, by any route, including resources reachable directly.\n\nAn EIP, a tunnel, or an internal address that answers is still the same account. Reads over such a path are fine; state changes are not. Reaching a resource by a route the permission check does not cover does not make the change allowed \u2014 do not use one to do what a refusal declined.\n\nLocal work is unaffected: files and local processes are yours. Treat the session as review work \u2014 carry the investigation through and produce the complete change (plan, exact commands, cost or impact), stating what would be applied. Ask for read-write only when a specific operation is blocked.";
56
+ export declare const READ_ONLY_POLICY = "Current HuaweiCloud permission mode: read-only \u2014 nothing in this HuaweiCloud account is to change.\n\nThis switch governs this account and nothing else. It is not a sandbox and not a global read-only posture.\n\nAn EIP, a tunnel, or an internal address that answers a request is still this account reached another way. Reads over such a path are fine; changes to the account are not. Reaching an account resource by a route the permission check does not cover does not make the change allowed \u2014 do not use one to do what a refusal declined.\n\nEverything outside this account is untouched and stays open: local files and processes, containers, other cloud accounts, any other service. Work there as you normally would.\n\nTreat the session as review work for the HuaweiCloud part \u2014 carry the investigation through and produce the complete change (plan, exact commands, cost or impact), stating what would be applied. Ask for read-write only when a specific operation on the account is blocked.";
54
57
  /**
55
58
  * The text this context contributes for one mode.
56
59
  *
@@ -18,5 +18,5 @@
18
18
  * written by earlier releases carry it — so it is kept even though there is no
19
19
  * server.
20
20
  */
21
- export declare const SERVER_VERSION = "aishell-deploy 0.0.26";
21
+ export declare const SERVER_VERSION = "aishell-deploy 0.0.28";
22
22
  //# sourceMappingURL=version.d.ts.map
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@huaweidevtools/aishell-dsh-deploy",
3
3
  "description": "Huawei Cloud infrastructure tools for DSH — Terraform, OpenAPI, resource inventory, cost estimates",
4
- "version": "0.0.26",
4
+ "version": "0.0.28",
5
5
  "publishConfig": {
6
6
  "access": "public"
7
7
  },
@@ -31,7 +31,7 @@
31
31
  "hcl2-parser": "^1.0.3",
32
32
  "jsonpath-plus": "^10.4.0",
33
33
  "zod": "^4.2.0",
34
- "@huaweidevtools/aishell-dsh-credentials-store": "0.0.26"
34
+ "@huaweidevtools/aishell-dsh-credentials-store": "0.0.28"
35
35
  },
36
36
  "peerDependencies": {
37
37
  "@deepseek-ai/cordis": "^4.1.0",