@yugoo-design/dsh-design-skills-web-app 0.1.2 → 0.2.2

package/bundles/ai_agent_capabilities/locales/en-US.json

@@ -5,7 +5,7 @@
   "newAgent": "New Agent",
   "numberedAgent": "New Agent {index}",
   "empty": "Add an Agent and reference Skills and tools as needed.",
-  "guidance": "Define the Agent's job, then configure Skills and tools. Resources can be shared; saving does not install or run them.",
+  "guidance": "Check whether the Agent goals, responsibilities and tools fit together, and whether capabilities are missing or unnecessary. Saving here records the design; it does not install or run tools.",
   "name": "Name",
   "description": "Responsibility and goal",
   "functionRefs": "Related functions",

package/bundles/ai_agent_capabilities/locales/zh-CN.json

@@ -5,7 +5,7 @@
   "newAgent": "新 Agent",
   "numberedAgent": "新 Agent {index}",
   "empty": "添加一个 Agent，按需引用技能和工具。",
-  "guidance": "先明确 Agent 要做什么，再配置技能和工具；资源可复用，保存设计不会安装或执行。",
+  "guidance": "核对 Agent 的目标、能力分工和工具是否匹配，有无缺失或不必要的能力；这里保存的是设计，不会安装或执行工具。",
   "name": "名称",
   "description": "职责与目标",
   "functionRefs": "关联功能",

package/bundles/business_data/locales/en-US.json

@@ -2,7 +2,7 @@
   "bundleDescription": "- **Capability**: define the durable business things a Web App remembers, the information kept for each thing, user-visible states, and grounded associations or subtype inheritance between object types.\n- **Resolves**: S/T gaps where users must find, distinguish, update, or track lasting things but their meaning and information are unclear.\n- **Candidate when**: the product must remember the same business thing across actions or visits, or the user asks what information or custom fields to keep.\n- **Do not infer**: pages, actions, workflow steps, reports, filters, database tables, API payloads, and state-change behavior are not business things. Type relationships belong here; workflow transitions and instance provenance do not.\n- **Output**: a native `business_data` panel with ordered business things, information fields, optional states, and one relationship model shared by the form and canvas.",
   "objects": "Business objects", "object": "business object", "relations": "Object relationships", "relation": "relationship",
   "empty": "Add the first business object this product needs to remember and manage.",
-  "guidance": "Define the things, information and states the product remembers. The relationship canvas and forms edit the same design.",
+  "guidance": "Check that the things, fields and states the product needs to record are complete and that their relationships match reality. The relationship canvas and forms edit the same design.",
   "graphHint": "Cards represent object types; arrows point from source to target. Inheritance connects a subtype to its parent, not containment or instance provenance.",
   "parents": "Parent definitions", "parentHint": "Only local information is edited below. Shared information stays with its parent types.", "reverse": "Swap endpoints",
   "createSubtype": "Add subtype", "createSubtypeTitle": "Create a subtype",

package/bundles/business_data/locales/zh-CN.json

@@ -2,7 +2,7 @@
   "bundleDescription": "- **能力**：定义 Web App 持久记忆的业务事物、信息和用户可见状态，以及对象类型间有依据的关联与继承。\n- **解决**：用户需要查找、区分、更新或跟踪持久事物，但其含义和信息不明确时的 S/T 类缺口。\n- **适用时机**：产品需要跨操作或跨访问记住同一业务事物，或用户询问应保留哪些信息或自定义字段。\n- **不要推断**：页面、操作、流程步骤、报表、筛选器、数据库表、API 载荷和状态变化行为都不是业务事物；类型间关系属于本切片，流程转换和实例来源不属于。\n- **输出**：对象、信息、状态与关系共用 canonical 的原生表单/关系画布 `business_data` 面板。",
   "objects": "业务对象", "object": "业务对象", "relations": "对象关系", "relation": "关系",
   "empty": "添加产品需要长期保存和管理的第一个业务对象。",
-  "guidance": "定义产品需要记住的事物、信息和状态；关系画布与表单编辑同一份设计。",
+  "guidance": "核对产品需要记录的事物、字段和状态是否齐全，关系是否符合实际；关系画布与表单修改的是同一份设计。",
   "graphHint": "方框表示对象类型，箭头由起点指向终点。类型继承由子类型指向父类型，不表示包含或实例来源。",
   "parents": "沿用父类型的定义与信息", "parentHint": "下方仅维护本类型自己的信息；共享信息在父类型原处修改。", "reverse": "交换双方",
   "createSubtype": "添加子类型", "createSubtypeTitle": "创建子类型",

package/bundles/business_rules/locales/en-US.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "Select a rule and describe its conditions and deterministic outcome. Leave conditions empty when no restriction applies.",
+  "guidance": "Check which conditions lead to which result, looking for ambiguity, conflicts or omissions. Unconditional rules may leave the condition empty.",
   "bundleDescription": "- **Capability**: turn product decisions into independent rules that name relevant conditions or inputs and deterministic outcomes.\n- **Resolves**: S/T gaps where reasonable implementations could differ without a qualification, validation, calculation, threshold, automation, or exception.\n- **Candidate when**: an action, business thing, flow branch, price, limit, approval, or eligibility decision needs deterministic behavior.\n- **Do not infer**: ordinary step order, role permission, field definition, page layout, UI copy, and technical implementation are not automatically business rules.\n- **Output**: a native `business_rules` panel with an ordered list of editable rules.",
   "empty": "No business rules yet. Add one to explain when and how the product should respond.",
   "rules": "Business rules",

package/bundles/business_rules/locales/zh-CN.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "选择一条规则，写清适用条件和确定结果；没有条件限制时可留空。",
+  "guidance": "检查每条规则在什么条件下产生什么结果，是否有歧义、冲突或遗漏；无条件适用的规则可不填条件。",
   "bundleDescription": "- **能力**：把产品决策转化为独立规则，明确相关条件或输入以及确定性结果。\n- **解决**：缺少资格、校验、计算、阈值、自动化或异常定义会导致合理实现产生差异时的 S/T 类缺口。\n- **适用时机**：操作、业务事物、流程分支、价格、限制、审批或资格判断需要确定行为。\n- **不要推断**：普通步骤顺序、角色权限、字段定义、页面布局、UI 文案和技术实现并不自动属于业务规则。\n- **输出**：包含有序可编辑规则列表的原生 `business_rules` 面板。",
   "empty": "还没有业务规则。先添加一条，说明在什么情况下产品应该怎样处理。",
   "rules": "业务规则",

package/bundles/design_style/locales/en-US.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "Choose a palette and adjust settings. Save and regenerate the preview after structural or component-language changes.",
+  "guidance": "Judge whether the visual style fits the users and context, and whether text and actions are clear. Check the preview after adjustments; structural or component-language changes require regeneration after saving.",
   "bundleDescription": "- **Capability**: visual direction for a web/mobile product — palette, typography, component language, and one representative UI preview.\n- **Resolves**: S/T gaps in visual hierarchy, component language, and reviewable interface direction; visible feedback may also add U evidence.\n- **Candidate when**: the user explicitly asks for visual direction, one representative screen is the smallest useful way to settle a material product decision, or the user has explicitly requested high-fidelity pages and the project has no visual baseline.\n- **Do not infer**: website, page, or app alone does not make visual work mandatory; an explicit high-fidelity Page request is an output dependency rather than keyword inference.\n- **Output**: `design_style` panel, generated `DESIGN.md`, generated `tokens.css`, and one representative HTML preview.",
   "config.colors.primary": "Primary",
   "config.colors.primaryLight": "Primary light",

package/bundles/design_style/locales/zh-CN.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "选择配色并微调设置；结构和组件语言变更需保存后重新生成预览。",
+  "guidance": "对照目标用户和使用场景，判断视觉风格是否合适、文字和操作是否清晰；调整后查看预览，结构或组件语言变更需保存后重新生成。",
   "bundleDescription": "- **能力**：为 Web/移动产品确定视觉方向，包括色板、字体、组件语言和一个代表性 UI 预览。\n- **解决**：视觉层级、组件语言和可审阅界面方向中的 S/T 类缺口；可见反馈也可能补充 U 类证据。\n- **适用时机**：用户明确要求视觉方向、一个代表性页面是确定重要产品决策的最小有用方式，或已明确请求高保真页面但项目尚无视觉基线。\n- **不要推断**：仅仅提到网站、页面或应用，并不意味着必须进行视觉设计；明确请求高保真页面属于输出依赖，不是关键词推断。\n- **输出**：`design_style` 面板、生成的 `DESIGN.md`、`tokens.css` 和一个代表性 HTML 预览。",
   "config.colors.primary": "主色",
   "config.colors.primaryLight": "主色浅色",

package/bundles/flow_design/locales/en-US.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "Select a process to inspect responsibilities, branches and handoffs. Use diagram edit mode to change nodes or connections, then save.",
+  "guidance": "Follow the flow to check who owns each step, whether branch conditions are clear and how exceptions are handled. Adjust steps, connections or rules that do not fit.",
   "bundleDescription": "- **Capability**: product-process design — BPMN per material process with human/system responsibility, triggers, handoffs, and outcomes.\n- **Resolves**: S/T gaps by making established actors, product automation, ordered states, branches, triggers, and observable outcomes inspectable.\n- **Candidate when**: roles, approvals, handoffs, exceptions, or an explicitly material journey need an agreed process contract.\n- **Do not infer**: ordinary clicks or a vague product idea do not justify inventing actors, policy branches, or a BPMN diagram.\n- **Output**: `flow_design` panel — one BPMN per material product process; every diagram exposes what the system actually does.",
   "empty":"Process plans and diagrams appear here.", "processes":"Business flows", "process":"Process", "title":"Name", "description":"Description",
   "tier":"Value tier", "core":"Core", "business":"Business", "auxiliary":"Auxiliary", "type":"Flow structure", "linear":"Sequential", "approval":"Approval", "parallel":"Parallel", "event":"Event-driven",

package/bundles/flow_design/locales/zh-CN.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "选择流程查看责任、分支和交接；进入图编辑模式后调整节点或连线，再保存。",
+  "guidance": "沿流程核对每一步由谁负责、分支条件是否清楚，以及异常如何处理；调整不合理的步骤、连线或规则。",
   "bundleDescription": "- **能力**：面向产品流程进行设计，为每个重要流程建立包含人员/系统职责、触发、交接和结果的 BPMN。\n- **解决**：让已确定的角色、产品自动化、状态顺序、分支、触发条件和可观察结果可审阅，从而补齐 S/T 类缺口。\n- **适用时机**：角色、审批、交接、异常或明确重要的用户旅程需要形成一致的流程约定。\n- **不要推断**：普通点击路径或模糊的产品想法，不足以凭空编造角色、策略分支或 BPMN 图。\n- **输出**：每个重要产品流程一张 BPMN 的 `flow_design` 面板，每张图都明确系统实际做什么。",
   "empty":"流程计划和流程图将在这里展示。", "processes":"业务流程", "process":"流程", "title":"名称", "description":"流程说明",
   "tier":"价值层级", "core":"核心流程", "business":"业务流程", "auxiliary":"辅助流程", "type":"流程结构", "linear":"顺序", "approval":"审批", "parallel":"并行", "event":"事件驱动",

package/bundles/function_modules/locales/en-US.json

@@ -6,8 +6,7 @@
   "source": "Origin", "ai": "AI proposal", "user": "User added", "reason": "Notes", "references": "Pinned sources",
   "situation": "Usage scenario", "behaviors": "Core behaviors", "behavior": "Behavior", "inputs": "Inputs", "input": "Input",
   "outputs": "Outcomes", "output": "Outcome", "limits": "Scope boundaries", "limit": "Boundary", "exceptions": "Exception handling", "exception": "Exception", "condition": "Condition", "response": "System response",
-  "guidance": "Browse functions by group and adjust descriptions or priorities. New function requests go to the main conversation for refinement.",
-  "applicationMindMap": "Application Functional Mind Map",
+  "guidance": "Check that the functions cover what users need to accomplish. Look for omissions, overlap or excess scope, and adjust descriptions and priorities.",
   "createRequest": "Please add the following function",
   "createSubmit": "Add with AI",
   "detailsAndEvidence": "Function details"

package/bundles/function_modules/locales/zh-CN.json

@@ -6,8 +6,7 @@
   "source": "来源", "ai": "AI 提出", "user": "用户添加", "reason": "备注", "references": "关联来源",
   "situation": "使用场景", "behaviors": "核心行为", "behavior": "行为", "inputs": "输入", "input": "输入",
   "outputs": "结果", "output": "结果", "limits": "范围边界", "limit": "边界", "exceptions": "异常处理", "exception": "异常情况", "condition": "发生条件", "response": "处理方式",
-  "guidance": "按分组浏览功能，调整说明和优先级；新增功能会交给主对话继续完善。",
-  "applicationMindMap": "应用功能脑图",
+  "guidance": "检查功能是否覆盖用户要完成的事情，有无遗漏、重复或超出范围；调整不准确的说明和优先级。",
   "createRequest": "请新增以下功能",
   "createSubmit": "AI 智能添加",
   "detailsAndEvidence": "功能详情"

package/bundles/function_modules/panel.yaml

@@ -72,7 +72,7 @@ ui:
   guidance: "$t:guidance"
   sidebar_icon: blocks
   id: function-board
-  title: $t:applicationMindMap
+  title: $t:functions
   source: functions
   board:
     request_create:

package/bundles/integration_design/locales/en-US.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "Describe the connection's purpose, then add verified information and usage instructions. Do not enter real secrets.",
+  "guidance": "Check what each external connection exchanges, why it is needed and what happens on failure. Add actual interface references, without entering real secrets.",
   "bundleDescription": "- **Capability**: design each product-relevant external connection as a complete new Plugin, with concise product-side notes.\n- **Resolves**: S/T gaps around which external capability the product needs, how the Agent accesses and uses it, and what the product does when the connection succeeds or fails.\n- **Candidate when**: a product behavior depends on an external API, webhook, SDK, MCP tool, third-party component, device, or team-operated system.\n- **Do not infer**: never invent vendor behavior, URL, credential, endpoint, or field-level API contract.\n- **Output**: `integration_design` panel — one editable Plugin-style connection record plus product-side remarks for every external capability.",
   "empty": "No integrations yet. Add connection instructions and product-side rules as needed.",
   "integrations": "System integrations",

package/bundles/integration_design/locales/zh-CN.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "先说明外部连接的目的，再补充真实资料和调用提示；不要填写真实密钥。",
+  "guidance": "核对每个外部连接要交换什么、为何需要，以及失败时如何处理；补充真实接口资料，不填写真实密钥。",
   "bundleDescription": "- **能力**：把每项与产品相关的外部连接设计成完整的新 Plugin，并附上简洁的产品侧说明。\n- **解决**：产品需要哪种外部能力、Agent 如何访问和使用它，以及连接成功或失败时产品如何处理等 S/T 类缺口。\n- **适用时机**：产品行为依赖外部 API、Webhook、SDK、MCP 工具、第三方组件、设备或团队运营的系统。\n- **不要推断**：绝不凭空编造供应商行为、URL、凭证、端点或字段级 API 约定。\n- **输出**：`integration_design` 面板，为每项外部能力提供一条可编辑的 Plugin 风格连接记录和产品侧备注。",
   "empty": "还没有系统集成。根据产品需要添加接入说明和业务规则。",
   "integrations": "系统集成",

package/bundles/notification_design/locales/en-US.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "Specify when to notify whom, through which channel, and the next action. The content preview does not send notifications.",
+  "guidance": "Check that the trigger, recipients and channel are appropriate and that the message helps them take the next action. Previewing content does not send a notification.",
   "bundleDescription": "- **Capability**: decide when an established business moment should proactively reach which people, through which human channel, with what useful message and next action.\n- **Resolves**: S/T gaps where a user could miss a material approval, deadline, exception, handoff, or completed result while not looking at the relevant page.\n- **Candidate when**: an established flow contains waiting, handoff, deadline, exception, or material status change and somebody must know or act without already being on that page.\n- **Do not infer**: every state change needs a notification; page feedback, dashboards, reports, exports, audit history, machine webhooks, and final marketing copy belong elsewhere.\n- **Output**: `notification_design` panel — an ordered, editable set of proactive notification moments.",
   "empty": "Add a notification: when it appears, who receives it, which channel is used and what it says.",
   "notifications": "Notifications",

package/bundles/notification_design/locales/zh-CN.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "写清何时通知谁、通过什么渠道以及下一步行动；内容预览不会发送通知。",
+  "guidance": "核对触发时机、接收人和渠道是否合适，信息能否帮助对方采取下一步行动；内容预览不会发送通知。",
   "bundleDescription": "- **能力**：确定已经建立的业务时刻应在何时、通过哪种人工渠道、向哪些人主动发送什么有用信息和下一步操作。\n- **解决**：用户未停留在相关页面时可能错过重要审批、截止日期、异常、交接或完成结果的 S/T 类缺口。\n- **适用时机**：已建立的流程包含等待、交接、截止、异常或重要状态变化，且有人必须及时知晓或行动。\n- **不要推断**：并非每次状态变化都需要通知；页面反馈、仪表盘、报表、导出、审计历史、机器 Webhook 和最终营销文案不属于这里。\n- **输出**：包含一组有序、可编辑的主动通知时刻的 `notification_design` 面板。",
   "empty": "添加一个通知时刻，说明何时、向谁、通过什么渠道传达什么信息。",
   "notifications": "通知时刻",

package/bundles/page_design/locales/en-US.json

@@ -29,6 +29,6 @@
   "hotspotLabel": "Source hotspot label",
   "members": "Pages in group",
   "map": "Page map",
-  "guidance": "Select a page to preview it or a connection to edit navigation. Map positions and groups organize the map only.",
+  "guidance": "Walk through the user task and check that page content, actions and navigation form a coherent path without gaps or dead ends. Map positions and groups only organize the view.",
   "shared": "Shared specification"
 }

package/bundles/page_design/locales/zh-CN.json

@@ -29,6 +29,6 @@
   "hotspotLabel": "源热点说明",
   "members": "分区内页面",
   "map": "页面地图",
-  "guidance": "选择页面看预览，选择连线改跳转；地图位置和分区只影响地图组织。",
+  "guidance": "从用户要完成的任务出发，检查页面内容、操作和跳转是否连贯，有没有遗漏或死路；地图位置和分区只影响组织方式。",
   "shared": "公共规格"
 }

package/bundles/quality_acceptance/locales/en-US.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "Describe the acceptance scenario and an observable passing result. Add a verification method only when unclear; test code is not required.",
+  "guidance": "Check whether each acceptance item has a clear situation and an observable passing result. Add a checking method only when it is unclear; test code is not required.",
   "bundleDescription": "- **Capability**: define the small set of observable requirements that tell users and the delivery team when established product behavior and material quality are good enough to accept.\n- **Resolves**: T gaps where an important function, rule, flow, page, or integration has no concrete passing result, or a material quality expectation remains vague.\n- **Candidate when**: the user asks for acceptance criteria, quality requirements, non-functional requirements, or a clear definition of done for product behavior.\n- **Do not infer**: business rules, missing product behavior, test code, release governance, project plans, risk registers, or a generic enterprise NFR checklist do not belong here.\n- **Output**: `quality_acceptance` panel — one editable ordered list of acceptance requirements.",
   "empty": "Add an acceptance requirement: describe the situation and the outcome that counts as success.",
   "requirements": "Acceptance requirements",

package/bundles/quality_acceptance/locales/zh-CN.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "写清验收情境和可观察的通过结果；检查方法不明显时再补充，不必写测试代码。",
+  "guidance": "检查每项验收是否有明确情境和可观察的通过结果，能否据此判断做对了；检查方法不明显时再补充，无需编写测试代码。",
   "bundleDescription": "- **能力**：定义一小组可观察的要求，让用户和交付团队判断既定产品行为及重要质量是否足以验收。\n- **解决**：重要功能、规则、流程、页面或集成缺少具体通过结果，或重要质量期望仍模糊时的 T 类缺口。\n- **适用时机**：用户要求验收标准、质量要求、非功能要求，或产品行为清晰的完成定义。\n- **不要推断**：业务规则、缺失的产品行为、测试代码、发布治理、项目计划、风险登记表或泛化的企业 NFR 清单不属于这里。\n- **输出**：包含有序验收要求列表的可编辑 `quality_acceptance` 面板。",
   "empty": "添加一项验收要求，说明在什么情况下，出现什么结果才算通过。",
   "requirements": "验收要求",

package/bundles/research/SKILL.md

@@ -41,7 +41,11 @@ working copy. They never use host filesystem or shell access.
 
 - **Plan.** Maintain the complete plan state in `research/research.json`: rounds
   with directions (`title` + `research_points`) and deterministic direct
-  artifact paths for new work. The Producer updates its working copy and calls
+  artifact paths for new work. Preserve explicit source limits, allowed source
+  types, product scope and exclusions in the affected direction's existing
+  `research_points`, alongside its questions, so the saved plan retains the
+  complete brief across confirmation, delegation and serial takeover. Do not
+  invent a limit when the user supplied none. The Producer updates its working copy and calls
   `design_publish({action:"handoff"})` to enter the independently configured gate,
   and the runtime presents `开始调研` / `Start Research`; the user may revise
   the plan before starting it.
@@ -149,6 +153,34 @@ the current product or requested exploration. Express this in the existing
 `research_points`, not extra plan fields. Broad landscape research can discover
 useful questions; it need not pretend the user has already chosen a solution.
 
+### Honor the user's evidence bounds
+
+The user's source limit is an acceptance condition for the requested output,
+separate from the Host's tool/time/token budget. Carry the complete current
+constraint into every Worker brief. Before serial research or taking over a
+failed Worker, reread the saved direction and apply the same constraint; a failed
+attempt does not permit a larger source set or broader product scope.
+
+For a limit on report sources, count distinct cited document URLs across the
+findings and its `信息来源` section, not domains, repeated citations or search
+result counts. For example, “at most two first-party sources per direction”
+permits at most two distinct first-party document URLs in that direction's
+findings and matching `source_urls`. It does not mean two websites with unlimited
+pages, nor two new sources in addition to retained ones. A limit on pages opened
+or tool calls instead applies before retrieval; follow the user's actual wording.
+
+Before integrating a Worker receipt or publishing serial findings, inspect the
+landed report against the current direction's questions and bounds. If it exceeds
+the source limit, keep the strongest permitted evidence and revise or qualify
+every claim that depended on a removed source. Update inline links, the source
+list and `source_urls` together; trimming only JSON or the bibliography does not
+repair an over-budget report. Regenerate the affected round conclusion from the
+accepted findings without adding external sources. If the permitted evidence
+cannot support the requested answer, keep that limitation explicit rather than
+silently adding a source. Report the actual per-direction source counts and any
+unmet bound in the handoff. Ordinary Bundle validation does not mechanically
+interpret these free-text constraints; passing it never waives this review.
+
 Apply the same evidence standard to every statement, including headings,
 table cells, chart labels and recommendation reasons:
 - An observation says only what the source establishes, within its context.
@@ -399,7 +431,8 @@ For each direction:
 1. Cover every `research_points` bullet from more than one useful search angle.
    Stop when credible retrieved evidence supports a useful answer, or when the
    Host's configured tool/time/token budget is exhausted. The Host owns those
-   limits; this Skill Body does not promise a fixed number of search or fetch
+   runtime limits; the user's evidence/output bounds still apply to both Worker
+   and serial execution. This Skill Body does not promise a fixed number of search or fetch
    calls. If important evidence remains missing at the configured boundary,
    leave the gap explicit instead of extending the run indefinitely.
 2. Open the most authoritative hits with `web_fetch` when available — search
@@ -410,8 +443,9 @@ For each direction:
    writes and repairs that exact path; the Producer reads the file, checks the
    receipt, and updates the direction state.
 
-When delegating a direction, include this bounded-evidence policy, all of that
-direction's `research_points`, and the complete findings contract below in the
+When delegating a direction, include this bounded-evidence policy, the user's
+explicit source/scope constraints, all of that direction's `research_points`,
+and the complete findings contract below in the
 Worker prompt. Search depth must not depend on whether the Producer performs the
 direction itself or delegates it.
 

package/bundles/research/locales/en-US.json

@@ -1,3 +1,3 @@
 {
-  "guidance": "Select a round or research direction to inspect findings and sources. If there is no plan, describe the question in the main conversation.",
+  "guidance": "Check whether the findings answer your question, then whether the key sources support them. Point out weak evidence or directions that need further investigation.",
   "bundleDescription": "- **Capability**: external information gathering — market context, competitor analysis, business background, reference targets (\"what is X\").\n- **Resolves**: U gaps caused by uncertain external facts, reference products, domain conventions, regulations, or current landscape.\n- **Candidate when**: reliable external evidence would materially change a product decision and a confident answer would otherwise require guessing.\n- **Do not infer**: a named product, an unfamiliar word, or a request for a bounded draft does not by itself require a research round. Analysis explicitly requested as input to a later imitation/build does require research.\n- **Output**: `research` panel — sourced findings, their design implications and evidence limits, persisted to design state.","title":"Research","empty":"No research plan yet. Describe the external question to investigate in the conversation."}

package/bundles/research/locales/zh-CN.json

@@ -1,3 +1,3 @@
 {
-  "guidance": "选择轮次或调研方向查看发现和来源；还没有计划时，在主对话说明要核查的问题。",
+  "guidance": "先看结论是否回答了你的问题，再核对关键来源能否支持它；指出证据不足或需要继续调查的方向。",
   "bundleDescription": "- **能力**：收集外部信息，包括市场背景、竞品分析、业务背景和参考对象（“X 是什么”）。\n- **解决**：由不确定的外部事实、参考产品、领域惯例、法规或当前市场格局造成的 U 类缺口。\n- **适用时机**：可靠的外部证据会实质影响产品决策，而直接给出确定答案将依赖猜测。\n- **不要推断**：仅仅出现产品名、生词或要求范围明确的草案，并不需要启动调研；明确要求为后续仿制或构建提供分析时则需要调研。\n- **输出**：包含有来源的发现、设计启示和证据局限并持久化到设计状态的 `research` 面板。","title":"调研分析","empty":"暂无调研计划。请在对话中描述需要核查的外部问题。"}

package/bundles/research/reference/artifact-contract.md

@@ -8,6 +8,37 @@ Canonical state: `research/research.json`. Findings: `research/{round_id}/{direc
 
 Use `artifact_kind: "research_direction"`, round-scoped `artifact_id: "{round_id}/{direction_id}"` and the exact findings file for delegation or serial focus. Conclusion focus uses `research_conclusion`, round ID and the exact conclusion file. Each author writes/repairs its artifact; the Producer reads findings for actual synthesis, updates the corresponding refs and sources, then validates and publishes the integrated round. A reference is accepted only after the file exists. There is no separate research script; use the ordinary Bundle validation.
 
+## User bounds and evidence acceptance
+
+For authorized research or revision, preserve explicit source limits, allowed
+source types, product scope and exclusions in the affected direction's existing
+`research_points`. They accompany the questions in every Worker brief and remain
+binding when the Producer takes over a failed Worker. Host runtime budgets do
+not relax those output constraints, and no source limit is implied when none was
+requested.
+
+A report-source cap counts distinct cited document URLs, including inline
+citations and the `信息来源` list; repeated use of one URL counts once, while two
+pages on one site count as two sources. The final source list and `source_urls`
+must match the report's used sources. A retrieved search-result list is not the
+report's accepted source set. If a figure uses a separate asset URL, retain its
+link to the cited source document rather than treating an unexplained asset as
+new evidence. An explicit limit on pages opened or tool calls applies to retrieval
+instead; follow the user's stated unit and scope.
+
+The Producer checks these bounds against the actual findings before acceptance
+and again before publication, for both delegated and serial output. Repair an
+excess by revising claims and links together; never hide extra evidence by only
+shortening the bibliography or JSON. A conclusion cites only sources retained in
+accepted findings. If the bounded evidence is insufficient, explain the gap
+without silently exceeding the cap. Report actual per-direction source counts
+and unmet constraints. The existing schema and declared rules do not infer a
+numeric limit from free text, so structural validation is not proof of compliance.
+
+Restoring existing research preserves its observed sources and provenance;
+report an apparent historical mismatch instead of deleting evidence to satisfy
+a newly requested limit without an authorized revision.
+
 ## Findings Markdown
 
 User-facing report, not a raw JSON payload:

package/bundles/research/reference/preview.json

@@ -8,7 +8,7 @@
         "D-PREVIEW-001": {
           "direction_id": "D-PREVIEW-001",
           "title": "从保存到再次阅读的使用场景",
-          "research_points": ["了解材料难以再次找到的典型情境。", "比较按标题查找与按主题整理的使用边界。"],
+          "research_points": ["了解材料难以再次找到的典型情境。", "比较按标题查找与按主题整理的使用边界。", "合成约束示例：本方向报告最多引用 2 个不同的一手来源文档；不足之处明确说明。"],
           "findings_file": null
         },
         "D-PREVIEW-002": {

package/bundles/research/skill.yaml

@@ -2,7 +2,7 @@
 
 # Stable internal id; must equal this directory name.
 name: research
-version: "1.0"
+version: "1.1"
 
 # Optional candidate hint, not automatic execution or a unique provider binding.
 review_support: [reflection]

package/bundles/research/validation.yaml

@@ -3,6 +3,9 @@
 # declared below. Citation provenance and report quality are reviewed by the
 # executing Agent against SKILL.md, not by a separate citation/report driver
 # declared in this Bundle. A successful validation is not proof of grounding.
+# Explicit per-direction source/scope bounds in research_points are also
+# Agent-reviewed against the actual report; these rules do not infer numeric
+# source limits from free text. Passing them does not waive the user's bounds.
 #
 # Contract summary:
 # - Every accepted direction has a direct `findings_file` and non-empty file.

package/bundles/role_access/locales/en-US.json

@@ -35,7 +35,7 @@
   "parentRole": "Source role",
   "inheritanceReason": "Evidence for inheritance (optional)",
   "addChildRole": "Add child role",
-  "guidance": "Roles are flat by default. Set a source role only for evidenced permission reuse. Each role has at most one parent and keeps its own assignment rule.",
+  "guidance": "Check what each role can do and which data it can access, looking for excessive or missing permissions. Set one source role only when reuse is needed; grants remain independent.",
   "graphHint": "Connect the child to its source role. Return to details for local permissions and read-only inherited sources.",
   "inheritanceHelp": "Inherited permissions retain their original applicability, confirmation and identity verification. Role assignment and conflict precedence are not inherited."
 }

package/bundles/role_access/locales/zh-CN.json

@@ -35,7 +35,7 @@
   "parentRole": "来源角色",
   "inheritanceReason": "继承依据（可选）",
   "addChildRole": "添加子角色",
-  "guidance": "角色默认平级；只有明确需要复用权限时才设置来源角色。每个角色最多一个来源，授予规则仍独立。",
+  "guidance": "检查各角色能做什么、作用于哪些数据，是否存在权限过多或遗漏；仅在确需复用时指定一个来源角色，授予规则仍独立。",
   "graphHint": "从子角色连向来源角色；返回详情查看本角色权限及只读的继承来源。",
   "inheritanceHelp": "继承权限保留原适用条件与确认、身份验证要求；不会继承角色授予规则，也不自动决定冲突优先级。"
 }

package/bundles/smart_questions/locales/en-US.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "Answer the current round. Explain uncertainty or leave an answer empty; previous rounds are read-only.",
+  "guidance": "Check whether the questions reflect your intent, then answer or correct them. Explain uncertainty or leave it open; earlier rounds remain available to review.",
   "bundleDescription": "- **Capability**: maintain coherent product background and evolving context through editable questions and answers.\n- **Resolves**: understanding of users, needs, value, scenarios and boundaries, plus relevant context not owned by another design facet.\n- **Candidate when**: exploring requirements, reconstructing product background, revising existing understanding or clarifying context necessary for the current result; not a technical inventory or fixed questionnaire.\n- **Do not infer**: a short request, low score, or missing detail alone does not authorize questioning when a useful draft or grounded default is what the user requested.\n- **Output**: `smart_questions` panel — editable question cards with rendered options and answers.",
   "configuration": "Application Development Configuration",
   "empty": "There are no questions to answer.",

package/bundles/smart_questions/locales/zh-CN.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "回答当前轮次的问题，不确定时可说明或留空；历史轮次只供回看。",
+  "guidance": "确认问题中的理解是否符合你的意图，再回答或纠正；不确定的地方可以说明或留空，历史轮次可回看。",
   "bundleDescription": "- **能力**：持续维护连贯的产品背景与关键上下文，并在需要时通过可编辑问题向用户取证。\n- **解决**：产品为谁、在何种场景解决什么问题、带来什么价值及其边界；补充其他设计维度不适合承载但影响整体理解的上下文。\n- **适用时机**：探索需求、重建产品背景、修订已有理解或澄清当前结果的关键缺口；不是技术盘点或固定问卷。\n- **不要推断**：需求简短、清晰度分数较低或细节缺失，并不意味着可以提问；用户需要可用草案或有依据的默认值时应直接推进。\n- **输出**：可编辑问题卡、选项和答案组成的 `smart_questions` 面板。",
   "configuration": "应用开发配置",
   "empty": "当前没有待回答的问题。",

package/bundles/web_app_prd_assembly/locales/en-US.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "Browse the PRD by chapter and use source labels to return to the design. Request generation or revision in the main conversation.",
+  "guidance": "Check that the PRD reflects the agreed scope and key decisions. Follow source labels back to the original design when something is wrong, or request a revision in the conversation.",
   "bundleDescription": "- **Capability**: generate or update one development-ready Web App PRD from current design evidence and user material.\n- **Resolves**: the delivery gap where product, design, engineering, test, and operations still lack one shared implementation-ready specification.\n- **Candidate when**: the user asks to generate, export, update, or inspect a complete PRD.\n- **Do not infer**: PRD assembly is an on-demand delivery action, not a required design gate and not permission to mutate owner Bundles.\n- **Output**: one stable canonical `prd.html`; Git retains history.",
   "contents": "Contents", "empty": "No PRD yet. Ask in the conversation to generate or revise the complete PRD.",
   "pending": "Pending confirmation", "legend": "Purple rail: temporary completion to keep the PRD coherent; not yet confirmed by the user",

package/bundles/web_app_prd_assembly/locales/zh-CN.json

@@ -1,5 +1,5 @@
 {
-  "guidance": "按目录查看 PRD，并通过来源标签返回原设计；生成或修订请在主对话提出。",
+  "guidance": "核对 PRD 是否准确表达已确认的范围和关键决策；发现偏差时通过来源标签回到原设计，或在对话中提出修订。",
   "bundleDescription": "- **能力**：从当前设计证据和用户材料生成或修改一份可直接用于研发的完整 Web App PRD。\n- **解决**：产品仍缺少一份各交付角色都能直接理解、审阅和实施的统一需求文档。\n- **适用时机**：用户要求生成、导出、修改或查看完整 PRD。\n- **不要推断**：PRD 整合是按需交付动作，不是必经设计关卡，也不允许修改证据所属 Bundle。\n- **输出**：唯一稳定的 canonical `prd.html`；Git 保留历史修订。",
   "contents": "文档目录", "empty": "暂无 PRD。可以在对话中要求生成或修订完整 PRD。",
   "pending": "待确认", "legend": "紫色左轨：为保持 PRD 结构完整而临时补全，尚待用户确认",

package/bundles/whiteboard/locales/en-US.json

@@ -1,3 +1,3 @@
 {
-  "guidance": "Select or add a topic and express ideas with text, shapes and connectors. Save after editing.",
+  "guidance": "Check whether the ideas and relationships in the drawing are clear. Add text, shapes or connections where something is missing; create another topic when the questions are distinct.",
   "bundleDescription": "Draw and revise topic-based diagrams together using text, shapes and connectors; explore ideas without replacing formal flows or page designs.","empty":"Create a topic to start drawing together.","boards":"Whiteboards","board":"Topic","id":"ID","title":"Topic title","file":"Scene file","new":"New topic"}

package/bundles/whiteboard/locales/zh-CN.json

@@ -1,3 +1,3 @@
 {
-  "guidance": "选择或新增主题，用文字、图形和连线表达想法；编辑后保存。",
+  "guidance": "检查图中的想法和关系是否表达清楚，用文字、图形或连线补上遗漏；需要区分不同问题时可新增主题。",
   "bundleDescription": "按主题共同绘制和修改文字、图形与连线；用于开放探索，不替代业务流程或页面设计的正式产物。","empty":"新建一个主题，开始共同绘制。","boards":"自由白板","board":"主题","id":"标识","title":"主题名称","file":"场景文件","new":"新主题"}

package/kits/web_app/kit.yaml

@@ -14,7 +14,7 @@ mounts:
   # Research markets, competitors and domain context, with sources and design implications.
   - bindingKey: research
     name: research
-    version: "1.0"
+    version: "1.1"
 
   # 功能模块：将产品目标与使用场景展开为可逐项推敲的功能卡片。
   # Turn product goals and scenarios into function cards that can be reviewed individually.

package/kits/web_app/mindset.md

@@ -1,6 +1,6 @@
 ---
 name: web_app
-version: "1.1"
+version: "1.2"
 description: >
   Calibration guidance for design choices in general web applications, SaaS,
   and enterprise products. It ranks genuine alternatives; it never chooses a

package/package.json

@@ -5,7 +5,7 @@
     "directory": "packages/skills-web-app"
   },
   "name": "@yugoo-design/dsh-design-skills-web-app",
-  "version": "0.1.2",
+  "version": "0.2.2",
   "license": "Apache-2.0",
   "type": "module",
   "description": "Self-contained web_app Design Kit: Mindset, Bundle manifests, references, and ordinary Agent-facing scripts.",