@huaweidevtools/aishell-dsh-brand 0.0.10 → 0.0.11

package/lib/client.js

@@ -306,6 +306,14 @@ const SUGGESTIONS = [
 		titleKey: "suggestion.billing.title",
 		glossKey: "suggestion.billing.gloss",
 		promptKey: "suggestion.billing.prompt"
+	},
+	{
+		id: "security",
+		icon: "security",
+		hue: { tile: "var(--dsw-static-red-400)" },
+		titleKey: "suggestion.security.title",
+		glossKey: "suggestion.security.gloss",
+		promptKey: "suggestion.security.prompt"
 	}
 ];
 
@@ -379,6 +387,25 @@ function CostIcon() {
 		/* @__PURE__ */ (0, react_jsx_runtime.jsx)(Stroke, { d: "M9.5 12.2h3.2" })
 	] });
 }
+/**
+* A shield with a check: the security review.
+*
+* A shield is the one shape in this set that carries "protection" on its own,
+* and the check inside it reads as an inspection that came back — which is
+* the tool's actual job (it reports what it found, not that all is well).
+*
+* Chosen over a magnifier, which was the other candidate: a magnifier and the
+* already-shipped cost glyph both reduce to "a rounded outline with a small
+* mark inside" at 17px, and magnifiers are the generic stand-in for any
+* lookup. The shield keeps this glyph's silhouette distinct from the others.
+*
+* The check's elbow sits at x=11.2 and its tail rises to the shield's inner
+* edge; both strokes stay inside the outline so nothing breaks the closed
+* silhouette the shape rules ask for.
+*/
+function SecurityIcon() {
+	return /* @__PURE__ */ (0, react_jsx_runtime.jsxs)(react_jsx_runtime.Fragment, { children: [/* @__PURE__ */ (0, react_jsx_runtime.jsx)(Stroke, { d: "M12 3 4.8 5.9v5.3c0 4.3 2.9 8.3 7.2 9.9 4.3-1.6 7.2-5.6 7.2-9.9V5.9z" }), /* @__PURE__ */ (0, react_jsx_runtime.jsx)(Stroke, { d: "m8.9 12.1 2.3 2.3 4.4-4.4" })] });
+}
 /** Resolve one icon key to its glyph. */
 function SuggestionIconArt({ icon, size = 20 }) {
 	return /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("svg", {
@@ -391,7 +418,8 @@ function SuggestionIconArt({ icon, size = 20 }) {
 			icon === "cloud" && /* @__PURE__ */ (0, react_jsx_runtime.jsx)(InventoryIcon, {}),
 			icon === "deploy" && /* @__PURE__ */ (0, react_jsx_runtime.jsx)(DeployIcon, {}),
 			icon === "architecture" && /* @__PURE__ */ (0, react_jsx_runtime.jsx)(ArchitectureIcon, {}),
-			icon === "cost" && /* @__PURE__ */ (0, react_jsx_runtime.jsx)(CostIcon, {})
+			icon === "cost" && /* @__PURE__ */ (0, react_jsx_runtime.jsx)(CostIcon, {}),
+			icon === "security" && /* @__PURE__ */ (0, react_jsx_runtime.jsx)(SecurityIcon, {})
 		]
 	});
 }
@@ -499,7 +527,7 @@ function ringStep(pos, delta, n) {
 *
 * ## Why the strip advances on its own
 *
-* The strip shows three of four cards, so a card is always off screen and a
+* The strip shows three of five cards, so cards are always off screen and a
 * reader who never touches the arrows never learns it exists. Rotation is what
 * makes the set self-evident. The cost is that content moves without being
 * asked to, which is why every reason to stop is collected here rather than
@@ -1226,10 +1254,13 @@ const zh = {
 	"suggestion.deploy.prompt": "我要部署一个轻量级 Web 应用，请对比几种可行的部署方案，说明各自的适用规模、月度成本量级和运维复杂度，并给出你的推荐及理由。",
 	"suggestion.enterprise.title": "企业上云",
 	"suggestion.enterprise.gloss": "多账号、网络分区与权限边界的整体设计",
-	"suggestion.enterprise.prompt": "请为我规划一套云上 Landing Zone 架构，覆盖账号组织结构、网络分区、权限边界与审计要求，并说明各部分的设计取舍。",
+	"suggestion.enterprise.prompt": "一家 200 人的电商公司要把业务迁到华为云，需要满足等保三级。现状是开发、测试、生产共用一套 VPC，没有做网络隔离。请设计改造方案：账号怎么划分，VPC 和子网如何切分，安全组规则怎么定，以及迁移的先后顺序和每一步的风险。",
 	"suggestion.billing.title": "账单分析",
 	"suggestion.billing.gloss": "分析上个月的云资源支出",
-	"suggestion.billing.prompt": "请分析我上个月的云资源支出构成，找出占比最高的几项服务，指出其中可以优化或降配的部分，并估算调整后能节省多少。"
+	"suggestion.billing.prompt": "请分析我上个月的云资源支出构成，找出占比最高的几项服务，指出其中可以优化或降配的部分，并估算调整后能节省多少。",
+	"suggestion.security.title": "安全审查",
+	"suggestion.security.gloss": "检查云资源是否存在安全问题",
+	"suggestion.security.prompt": "请检查我的华为云资源是否存在安全问题，重点看安全组规则、端口暴露、存储权限和密钥管理，指出高危项并给出修复建议。"
 };
 /** English dictionary. Complete against {@link zh}; also the terminal fallback. */
 const en = {
@@ -1243,10 +1274,13 @@ const en = {
 	"suggestion.deploy.prompt": "I want to deploy a lightweight web application. Compare a few viable deployment options, covering the scale each one suits, its order-of-magnitude monthly cost, and its operational complexity, then recommend one and explain why.",
 	"suggestion.enterprise.title": "Landing zone",
 	"suggestion.enterprise.gloss": "Multi-account structure, network and permission boundaries",
-	"suggestion.enterprise.prompt": "Design a cloud landing zone for my organisation, covering the account structure, network partitions, permission boundaries and audit requirements, and explain the trade-offs behind each part.",
+	"suggestion.enterprise.prompt": "A 200-person e-commerce company is migrating to Huawei Cloud and must meet Level 3 of China's Multi-Level Protection Scheme (等保三级). Today development, test and production share a single VPC with no network isolation. Design the migration: how to split the accounts, how to divide the VPC and subnets, what the security group rules should be, and the order to migrate in with the risk at each step.",
 	"suggestion.billing.title": "Billing analysis",
 	"suggestion.billing.gloss": "Break down last month's cloud spend",
-	"suggestion.billing.prompt": "Analyse my cloud spend for last month, identify the services that account for the largest share, point out what could be optimised or downsized, and estimate how much that would save."
+	"suggestion.billing.prompt": "Analyse my cloud spend for last month, identify the services that account for the largest share, point out what could be optimised or downsized, and estimate how much that would save.",
+	"suggestion.security.title": "Security review",
+	"suggestion.security.gloss": "Check the cloud resources for security problems",
+	"suggestion.security.prompt": "Check my Huawei Cloud resources for security problems, looking in particular at security group rules, exposed ports, storage permissions and key management. Point out anything high-risk and suggest how to fix it."
 };
 
 //#endregion

package/lib/types/client/SuggestionCards.d.ts

@@ -77,7 +77,7 @@
  *
  * ## Auto-rotation
  *
- * The strip shows three of four cards, so the fourth would otherwise be
+ * The strip shows three of five cards, so two would otherwise be
  * invisible to anyone who does not touch the arrows. It advances one card
  * every {@link AUTOPLAY_INTERVAL_MS}, pausing on hover, on keyboard focus, in
  * a background tab, and under `prefers-reduced-motion`. The policy itself

package/lib/types/client/autoplay.d.ts

@@ -7,7 +7,7 @@
  *
  * ## Why the strip advances on its own
  *
- * The strip shows three of four cards, so a card is always off screen and a
+ * The strip shows three of five cards, so cards are always off screen and a
  * reader who never touches the arrows never learns it exists. Rotation is what
  * makes the set self-evident. The cost is that content moves without being
  * asked to, which is why every reason to stop is collected here rather than

package/lib/types/client/locales.d.ts

@@ -34,10 +34,13 @@ export declare const zh: {
     readonly 'suggestion.deploy.prompt': "我要部署一个轻量级 Web 应用，请对比几种可行的部署方案，说明各自的适用规模、月度成本量级和运维复杂度，并给出你的推荐及理由。";
     readonly 'suggestion.enterprise.title': "企业上云";
     readonly 'suggestion.enterprise.gloss': "多账号、网络分区与权限边界的整体设计";
-    readonly 'suggestion.enterprise.prompt': "请为我规划一套云上 Landing Zone 架构，覆盖账号组织结构、网络分区、权限边界与审计要求，并说明各部分的设计取舍。";
+    readonly 'suggestion.enterprise.prompt': "一家 200 人的电商公司要把业务迁到华为云，需要满足等保三级。现状是开发、测试、生产共用一套 VPC，没有做网络隔离。请设计改造方案：账号怎么划分，VPC 和子网如何切分，安全组规则怎么定，以及迁移的先后顺序和每一步的风险。";
     readonly 'suggestion.billing.title': "账单分析";
     readonly 'suggestion.billing.gloss': "分析上个月的云资源支出";
     readonly 'suggestion.billing.prompt': "请分析我上个月的云资源支出构成，找出占比最高的几项服务，指出其中可以优化或降配的部分，并估算调整后能节省多少。";
+    readonly 'suggestion.security.title': "安全审查";
+    readonly 'suggestion.security.gloss': "检查云资源是否存在安全问题";
+    readonly 'suggestion.security.prompt': "请检查我的华为云资源是否存在安全问题，重点看安全组规则、端口暴露、存储权限和密钥管理，指出高危项并给出修复建议。";
 };
 /** English dictionary. Complete against {@link zh}; also the terminal fallback. */
 export declare const en: {
@@ -55,6 +58,9 @@ export declare const en: {
     readonly 'suggestion.billing.title': "Billing analysis";
     readonly 'suggestion.billing.gloss': "Break down last month's cloud spend";
     readonly 'suggestion.billing.prompt': string;
+    readonly 'suggestion.security.title': "Security review";
+    readonly 'suggestion.security.gloss': "Check the cloud resources for security problems";
+    readonly 'suggestion.security.prompt': string;
 };
 /** Every key, derived from the zh dictionary (the source of truth). */
 export type AishellBrandLocaleKey = keyof typeof zh;

package/lib/types/client/suggestion-icons.d.ts

@@ -1,7 +1,7 @@
 /**
  * Inline SVG artwork for the suggestion cards.
  *
- * Inline rather than an icon dependency: the strip draws four shapes, and a
+ * Inline rather than an icon dependency: the strip draws five shapes, and a
  * dependency would add a package, a version to track, and a bundle face to
  * keep in step with the host.
  *
@@ -13,13 +13,13 @@
  *
  * The first draft drew "deploy" as a box with an arrow leaving it — which
  * reads as SHARE or export, the one meaning this card must not carry. A
- * glyph in a row of four is read at a glance and out of context, so each one
+ * glyph in a row is read at a glance and out of context, so each one
  * has to be recognisable on its own:
  *
  *   - nothing may resemble the share glyph (box + outward arrow) or the
  *     external-link glyph (box + arrow through a corner);
  *   - every shape is closed and filled-ish in silhouette, because outlines
- *     at 20px in a row of four blur into each other;
+ *     at 20px in a row blur into each other;
  *   - no glyph carries more than three strokes, so they stay distinguishable
  *     at the size they are actually drawn.
  *

package/lib/types/client/suggestions.d.ts

@@ -26,7 +26,7 @@
  *
  * Three cards share one row, which at the default column leaves roughly 150px
  * per title — about seven CJK glyphs, or noticeably more Latin ones. Measured
- * against the shipped set: every title fits at 560px and above, and all four
+ * against the shipped set: every title fits at 560px and above, and all five
  * clip below ~460px. Keep them within a couple of characters of each other —
  * the longest one is otherwise the only card that ever shows an ellipsis,
  * which reads as a bug rather than as a long name.
@@ -54,13 +54,13 @@ export interface Suggestion {
     readonly promptKey: AishellBrandLocaleKey;
 }
 /** The icon set this strip can draw. Keys are local to this plugin. */
-export type SuggestionIcon = 'cloud' | 'deploy' | 'architecture' | 'cost';
+export type SuggestionIcon = 'cloud' | 'deploy' | 'architecture' | 'cost' | 'security';
 /**
  * The tile colour for one card, as the shell's own token names.
  *
  * ## Why each card carries its own hue
  *
- * The first version drew every icon in one accent, on the reasoning that four
+ * The first version drew every icon in one accent, on the reasoning that five
  * hues beside the brand mark would read as noise. That was a guess, and the
  * shell contradicts it: `FileTypeIcon` gives every item in a row its own hue
  * (`code` blue, `excel` green, `folder` amber, `image` violet), which is the
@@ -83,15 +83,17 @@ export type SuggestionIcon = 'cloud' | 'deploy' | 'architecture' | 'cost';
  * artwork. The same value is reused here rather than inventing a second one,
  * and it is the only literal colour in this plugin.
  *
- * The four were picked to clear three bars at once, in both themes:
+ * The five were picked to clear three bars at once, in both themes:
  *
  *   - glyph on its tile >= 4.5 — measured 5.42 at worst (violet);
  *   - tile against the card >= 1.6 — measured 2.05 at worst;
  *   - worst pairwise colour distance >= 30 (CIE76 dE) — measured 38.7.
  *
- * The last bar is the one that matters for "four colours, not one blur": an
+ * The last bar is the one that matters for "five colours, not one blur": an
  * obvious-looking pick like blue + violet measures only 17.5 apart, which is
- * why this is measured rather than eyeballed.
+ * why this is measured rather than eyeballed. Adding the fifth hue did not
+ * move either floor — red's nearest neighbour is amber at 42.9, and the
+ * tightest pair is still blue vs violet.
  */
 export interface SuggestionHue {
     /**

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@huaweidevtools/aishell-dsh-brand",
   "description": "AI Shell brand reskin for DSH web — replaces sidebar and hero brand marks with AI Shell SVG",
-  "version": "0.0.10",
+  "version": "0.0.11",
   "publishConfig": {
     "access": "public"
   },