@c4a/context 0.7.9 → 0.7.10-alpha.2

package/templates/package-templates/kb/skills/knowledge-query/SKILL.md

@@ -17,11 +17,9 @@ as evidence rather than relying on memory or frontmatter summaries.
    follow its links to a likely page.
 3. Read only the sections needed for the question. Use frontmatter to select
    scope, not to support factual claims.
-4. For relationship or impact questions, inspect
-   `context-build-inventory.json` `structure.edge_records` before reading the
-   endpoint pages.
-5. Answer only from reader-visible section content and source-backed edge
-   records. Cite the supporting page or section.
+4. For relationship or impact questions, read the relevant pages' explicit
+   explanations. Shared names, directory placement and links alone do not prove a relationship.
+5. Answer from reader-visible section content and cite the supporting page or section.
 6. If the package lacks evidence, report the gap and what was checked instead
    of inferring from nearby content.
 
@@ -29,7 +27,7 @@ as evidence rather than relying on memory or frontmatter summaries.
 
 | Root | Use |
 |---|---|
-| `{{wikisRoot}}/` | Structured entities and relationships from codeindex, business, and product knowledge. |
+| `{{wikisRoot}}/` | Code, business and product reference articles. |
 | `{{guidesRoot}}/` | Architecture, procedures, FAQs, decisions, incidents, and troubleshooting. |
 | `{{rulesRoot}}/` | Standards, constraints, acceptance criteria, and test scenarios. |
 | `{{featsRoot}}/` | Feature knowledge when selected into the package. |
@@ -45,7 +43,7 @@ was not selected into this package.
 | Named entity, API, domain, or action | Open the matching page or nearest group index. Show candidates if names are ambiguous. |
 | Architecture, procedure, FAQ, decision, or incident | Start from `{{guidesRoot}}/index.md`. |
 | Standard, constraint, acceptance, or test question | Start from `{{rulesRoot}}/index.md`. |
-| Relationship or impact | Inspect typed edges, then read both endpoint pages. |
+| Relationship or impact | Read the relevant explanations and state any coverage limits. |
 | Detail inside a known page | Read the relevant Markdown heading and its body. |
 | Coverage, gap, or inventory | Inspect the root indexes and `context-build-inventory.json`. |
 
@@ -59,16 +57,16 @@ Use each opened page or package artifact as an evidence card:
 | Frontmatter title, description, and tags | Navigation and scope selection only. |
 | Markdown headings | Locate and cite a section within its page. |
 | Reader-visible section body | Primary support for factual claims. |
-| `context-build-inventory.json` edge records | Typed relationship evidence. |
+| Exported source attribution | Locate the original material when available; read it before extending a claim. |
 | Root indexes and build inventory | Package scope and coverage evidence. |
 
 Do not infer a relationship from page co-occurrence. Published pages do not need
 production identifiers or source bookkeeping to be usable. Cite their readable
 paths and headings; do not search for missing technical metadata or ask users
-to supply it. Open the build inventory only for relationship or coverage questions,
+to supply it. Open the build inventory only for coverage questions,
 or when a maintainer needs to locate the original approved page via
-`dist_path` → `approved_path`. Original source attribution belongs to that
-workspace's `knowledge/`, not to the published page. If the original material is
+`dist_path` → `approved_path`. Source attribution is exported automatically from
+the workspace's fragment references. If the original material is
 not bundled, answer only from the visible approved content and state its limits.
 
 ## Search Fallback
@@ -91,9 +89,8 @@ by headings and bounded line ranges, then returns paths, line ranges, headings,
 and previews; it does not interpret meaning.
 
 Treat every hit as a lead and open its page and section before answering. For
-relationship or impact claims, use typed edges from
-`context-build-inventory.json`; BM25 scores and text co-occurrence are not
-relationship evidence.
+relationship or impact claims, cite the explanation that actually establishes
+the relationship; BM25 scores and text co-occurrence do not establish it.
 
 ## Citations And Gaps
 
@@ -102,7 +99,7 @@ Use compact citations tied to claims:
 ```text
 Page:         <claim> [<root>/path/page.md]
 Section:      <claim> [<root>/path/page.md, heading: <visible heading>]
-Relationship: <claim> [context-build-inventory.json#structure.edge_records edge:<type>]
+Relationship: <claim> [<root>/path/page.md, heading: <supporting explanation>]
 Coverage:     <claim> [context-build-inventory.json]
 ```
 
@@ -122,7 +119,7 @@ from memory, previous conversations, or source files outside the package.
 - The bundled OKF-compatible roots are the source of truth for this Skill.
 - The package contains approved knowledge selected by its Context workspace; it
   does not claim complete coverage of the underlying product or codebase.
-- Do not scan every page or edge when a narrower indexed scope answers the
+- Do not scan every page when a narrower indexed scope answers the
   request.
 
 Approved knowledge files: `{{knowledgeCount}}`

package/templates/package-templates.zh-CN/kb/skills/knowledge-query/SKILL.md

@@ -12,15 +12,15 @@ description: 查询 {{displayName}} 中经过审核、可追溯来源的知识
 1. 判断请求属于实体查找、解释、流程、规则、关系、细节还是覆盖检查。
 2. 从最相关的根索引开始，例如 `{{wikisRoot}}/index.md`，再沿链接进入具体页面。
 3. 只读取回答所需的章节；frontmatter 用来选择范围，不作为事实依据。
-4. 查询关系或影响范围时，先检查 `context-build-inventory.json` 中的 `structure.edge_records`，再读取两端页面。
-5. 结论只能来自可见章节正文和来源支持的边记录，并引用对应页面或章节。
+4. 查询关系或影响范围时，读取相关页面中的明确说明；同名、目录位置或链接本身不能证明关系。
+5. 结论来自可见章节正文，并引用对应页面或章节。
 6. 如果包内没有证据，明确报告缺口和已经检查的范围，不要根据邻近内容推断。
 
 ## 知识根目录
 
 | 根目录 | 用途 |
 |---|---|
-| `{{wikisRoot}}/` | 来自 codeindex、business、product 的结构化实体和关系。 |
+| `{{wikisRoot}}/` | 来自 codeindex、business、product 的代码、业务和产品说明。 |
 | `{{guidesRoot}}/` | 架构、流程、FAQ、决策、故障和排障说明。 |
 | `{{rulesRoot}}/` | 标准、约束、验收条件和测试场景。 |
 | `{{featsRoot}}/` | 被选择进入包内的功能知识。 |
@@ -35,7 +35,7 @@ description: 查询 {{displayName}} 中经过审核、可追溯来源的知识
 | 指定实体、API、领域或动作 | 打开匹配页面或最近的分组索引；有歧义时列出候选。 |
 | 架构、流程、FAQ、决策或故障 | 从 `{{guidesRoot}}/index.md` 开始。 |
 | 标准、约束、验收或测试 | 从 `{{rulesRoot}}/index.md` 开始。 |
-| 关系或影响范围 | 检查类型化边，再读取两端页面。 |
+| 关系或影响范围 | 阅读相关正文中的明确说明，并指出覆盖边界。 |
 | 已知页面中的细节 | 读取相关 Markdown 标题及其正文。 |
 | 覆盖范围或缺口 | 检查根索引和 `context-build-inventory.json`。 |
 
@@ -47,10 +47,10 @@ description: 查询 {{displayName}} 中经过审核、可追溯来源的知识
 | frontmatter 的标题、描述和标签 | 导航和范围选择。 |
 | Markdown 标题 | 定位和引用页面中的章节。 |
 | 读者可见的章节正文 | 事实结论的主要依据。 |
-| `context-build-inventory.json` 的边记录 | 类型化关系证据。 |
+| 导出的来源说明 | 原始材料可用时定位并阅读；不能只凭链接扩展结论。 |
 | 根索引和构建清单 | 包的范围和覆盖情况。 |
 
-不要根据页面同时出现来推断关系。发布页不需要生产标识或来源记账字段才能使用，直接引用可读路径和标题；不要寻找已经移除的技术元数据，也不要要求用户补齐。关系、覆盖问题，或维护者需要通过 `dist_path` → `approved_path` 定位原批准页时，才读取构建清单。原始来源归因留在生产工作区的 `knowledge/`，不要求写入发布页。原始材料未随包分发时，只根据已批准的可见正文回答并说明边界。
+不要根据页面同时出现来推断关系。直接引用可读路径和标题，不寻找已经移除的图谱字段，也不要求用户补齐。覆盖问题，或维护者需要通过 `dist_path` → `approved_path` 定位原批准页时，才读取构建清单。来源说明由工作区片段引用自动导出。原始材料未随包分发时，只根据已批准的可见正文回答并说明边界。
 
 ## 搜索兜底
 
@@ -62,7 +62,7 @@ node <当前 knowledge-query Skill 目录>/scripts/search.mjs --query '<关键
 
 脚本位于知识包目录内时会自动定位 `{{packageName}}`。如果包管理工具将本 Skill 复制到了其他位置，增加 `--root <包含 context-build-inventory.json 的包目录>`；也可以使用 `--base <多包集合根目录>`，按构建清单中的包名定位。它按 Markdown 标题和固定行块机械切分，返回路径、行号、标题和短预览，不判断内容语义。
 
-搜索命中只是线索。回答前必须打开命中的页面和章节；关系或影响范围仍以 `context-build-inventory.json` 的类型化边为准，不能用 BM25 分数或文本共现替代关系证据。
+搜索命中只是线索。回答前打开命中的页面和章节；关系或影响范围须引用实际说明该关系的正文，不能用 BM25 分数或文本共现代替。
 
 ## 引用与缺口
 
@@ -71,7 +71,7 @@ node <当前 knowledge-query Skill 目录>/scripts/search.mjs --query '<关键
 ```text
 页面：     <结论> [<root>/path/page.md]
 章节：     <结论> [<root>/path/page.md, 标题：<可见标题>]
-关系：     <结论> [context-build-inventory.json#structure.edge_records edge:<type>]
+关系：     <结论> [<root>/path/page.md, 标题：<明确说明该关系的章节>]
 覆盖：     <结论> [context-build-inventory.json]
 ```
 
@@ -89,7 +89,7 @@ node <当前 knowledge-query Skill 目录>/scripts/search.mjs --query '<关键
 
 - 包内兼容 OKF 的根目录是本 Skill 的事实来源。
 - 本包只包含 Context 工作区选择并批准的知识，不声明完整覆盖底层产品或代码库。
-- 已有更窄索引范围可以回答时，不要扫描所有页面或关系边。
+- 已有更窄索引范围可以回答时，不要扫描所有页面。
 
 已批准知识文件：`{{knowledgeCount}}`