@c4a/context 0.7.5 → 0.7.9

package/sessionMetadata.d.ts

@@ -0,0 +1,49 @@
+import { z } from "zod";
+/** Associations are supplied by the caller, not proof of implementation or approval. */
+export declare const sessionChangeSchema: z.ZodEffects<z.ZodObject<{
+    repository: z.ZodOptional<z.ZodString>;
+    commit: z.ZodOptional<z.ZodString>;
+    mr: z.ZodOptional<z.ZodEffects<z.ZodString, string, string>>;
+}, "strict", z.ZodTypeAny, {
+    repository?: string | undefined;
+    commit?: string | undefined;
+    mr?: string | undefined;
+}, {
+    repository?: string | undefined;
+    commit?: string | undefined;
+    mr?: string | undefined;
+}>, {
+    repository?: string | undefined;
+    commit?: string | undefined;
+    mr?: string | undefined;
+}, {
+    repository?: string | undefined;
+    commit?: string | undefined;
+    mr?: string | undefined;
+}>;
+export declare const sessionChangesSchema: z.ZodArray<z.ZodEffects<z.ZodObject<{
+    repository: z.ZodOptional<z.ZodString>;
+    commit: z.ZodOptional<z.ZodString>;
+    mr: z.ZodOptional<z.ZodEffects<z.ZodString, string, string>>;
+}, "strict", z.ZodTypeAny, {
+    repository?: string | undefined;
+    commit?: string | undefined;
+    mr?: string | undefined;
+}, {
+    repository?: string | undefined;
+    commit?: string | undefined;
+    mr?: string | undefined;
+}>, {
+    repository?: string | undefined;
+    commit?: string | undefined;
+    mr?: string | undefined;
+}, {
+    repository?: string | undefined;
+    commit?: string | undefined;
+    mr?: string | undefined;
+}>, "many">;
+export type SessionChange = z.infer<typeof sessionChangeSchema>;
+export declare function readSessionChanges(markdown: string): SessionChange[] | undefined;
+/** Omitted changes preserve inline metadata. Explicit [] removes associations.
+ * Only the source header is serialized; the summary body is never rewritten. */
+export declare function writeSessionChanges(markdown: string, changes?: readonly SessionChange[]): string;

package/sources.d.ts

@@ -1,5 +1,6 @@
-export type SourceType = "repo" | "file" | "lark";
-export type DocumentSourceType = Extract<SourceType, "file" | "lark">;
+import { type ManagedDocumentSourceEntry, type ManagedDocumentSourceType } from "./managedSources.js";
+export type SourceType = "repo" | "file" | "lark" | "note" | "sessions";
+export type DocumentSourceType = Exclude<SourceType, "repo">;
 export declare const DEFAULT_REPO_SOURCES_REGISTRY_PATH = "sources/repo/index.yaml";
 export declare const DEFAULT_FILE_SOURCES_REGISTRY_PATH = "sources/file/index.yaml";
 export declare const DEFAULT_LARK_SOURCES_REGISTRY_PATH = "sources/lark/index.yaml";
@@ -60,7 +61,7 @@ export type SourceReference<TType extends SourceType = SourceType> = TypedSource
 export type RepoSourceReference = RegistrySourceReference | TypedSourceReference<"repo">;
 export type FileSourceReference = RegistrySourceReference | TypedSourceReference<"file">;
 export type LarkSourceReference = RegistrySourceReference | TypedSourceReference<"lark">;
-export type DocumentSourceReference = FileSourceReference | LarkSourceReference;
+export type DocumentSourceReference = FileSourceReference | LarkSourceReference | TypedSourceReference<ManagedDocumentSourceType>;
 export type SourceCollectionReference<TType extends SourceType = SourceType> = {
     kind: "source.collection";
     type: TType;
@@ -123,6 +124,8 @@ export type SourcesRegistry = {
     repos: readonly RepoSourceRegistryEntry[];
     files: readonly FileSourceRegistryEntry[];
     larks: readonly LarkSourceRegistryEntry[];
+    notes: readonly ManagedDocumentSourceEntry[];
+    sessions: readonly ManagedDocumentSourceEntry[];
 };
 export type LoadSourcesRegistryOptions = {
     rootDir?: string;
@@ -135,6 +138,9 @@ export type SourceDefinition = RepoSourceDefinition | FileSourceDefinition | Lar
 export type DocumentSourceDefinition = FileSourceDefinition | LarkSourceDefinition | DocumentSourceReference;
 export type RepoProjectSourceDefinition = RepoSourceDefinition | RepoSourceReference | SourceCollectionReference<"repo">;
 export type ProjectSourceDefinition = SourceDefinition | SourceCollectionReference;
+export declare function source(name: string, options: {
+    type: ManagedDocumentSourceType;
+}): TypedSourceReference<ManagedDocumentSourceType>;
 export declare function source(name: string): RegistrySourceReference;
 export declare function source(namespace: string, module: string): RepoSourceReference;
 export declare function source(namespace: string, module: string, options: {

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

@@ -46,7 +46,7 @@ was not selected into this package.
 | 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. |
-| Detail inside a known page | Read the relevant `context:section` block. |
+| 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`. |
 
 ## Evidence Contract
@@ -56,15 +56,20 @@ Use each opened page or package artifact as an evidence card:
 | Evidence | Valid use |
 |---|---|
 | Page path | Page identity and citation handle. |
-| Frontmatter title, description, stable node identity, and tags | Navigation and scope selection only. |
-| `context:section` id, kind, and `source_ref` | Section identity, citation, and source boundary. |
+| 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. |
 | Root indexes and build inventory | Package scope and coverage evidence. |
 
-Do not infer a relationship from page co-occurrence. If a `source_ref` points to
-source material that is not bundled, cite the approved section that reviewed it
-and do not expand beyond its visible content.
+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,
+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
+not bundled, answer only from the visible approved content and state its limits.
 
 ## Search Fallback
 
@@ -96,8 +101,7 @@ Use compact citations tied to claims:
 
 ```text
 Page:         <claim> [<root>/path/page.md]
-Section:      <claim> [<root>/path/page.md#section-id]
-Source-bound: <claim> [<root>/path/page.md#section-id, source_ref]
+Section:      <claim> [<root>/path/page.md, heading: <visible heading>]
 Relationship: <claim> [context-build-inventory.json#structure.edge_records edge:<type>]
 Coverage:     <claim> [context-build-inventory.json]
 ```
@@ -107,7 +111,7 @@ When evidence is missing, return:
 ```text
 Gap: this package does not contain evidence for <missing point>.
 Checked: <indexes, pages, or artifacts>.
-Next useful source: <source, page, or source_ref if known>.
+Next useful source: <source document or page if known>.
 ```
 
 Distinguish “not evidenced by this package” from “not true.” Do not fill gaps
@@ -123,7 +127,7 @@ from memory, previous conversations, or source files outside the package.
 
 Approved knowledge files: `{{knowledgeCount}}`
 
-## Template Author Recommendation
+{{!-- Template author guidance (not part of the published query Skill):
 
 This is a complete generic query Skill, but package authors should replace or
 edit it before publishing when the package has project-specific terminology,
@@ -131,3 +135,4 @@ common user intents, preferred entry pages, known limits, or task workflows.
 Update the description, routing table, and package-boundary guidance to match
 the actual package. If the generic behavior is intentionally sufficient,
 explicitly accept the unchanged default during Context package-template review.
+--}}

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

@@ -36,7 +36,7 @@ description: 查询 {{displayName}} 中经过审核、可追溯来源的知识
 | 架构、流程、FAQ、决策或故障 | 从 `{{guidesRoot}}/index.md` 开始。 |
 | 标准、约束、验收或测试 | 从 `{{rulesRoot}}/index.md` 开始。 |
 | 关系或影响范围 | 检查类型化边，再读取两端页面。 |
-| 已知页面中的细节 | 读取对应 `context:section`。 |
+| 已知页面中的细节 | 读取相关 Markdown 标题及其正文。 |
 | 覆盖范围或缺口 | 检查根索引和 `context-build-inventory.json`。 |
 
 ## 证据契约
@@ -44,13 +44,13 @@ description: 查询 {{displayName}} 中经过审核、可追溯来源的知识
 | 证据 | 可支持的内容 |
 |---|---|
 | 页面路径 | 页面身份和引用位置。 |
-| frontmatter 的标题、描述、稳定节点标识和标签 | 导航和范围选择。 |
-| `context:section` 的 id、kind、`source_ref` | 章节身份、引用位置和来源边界。 |
+| frontmatter 的标题、描述和标签 | 导航和范围选择。 |
+| Markdown 标题 | 定位和引用页面中的章节。 |
 | 读者可见的章节正文 | 事实结论的主要依据。 |
 | `context-build-inventory.json` 的边记录 | 类型化关系证据。 |
 | 根索引和构建清单 | 包的范围和覆盖情况。 |
 
-不要根据页面同时出现来推断关系。如果 `source_ref` 指向未随包分发的来源，只能引用已经过审核的可见章节，不能扩展到正文没有表达的内容。
+不要根据页面同时出现来推断关系。发布页不需要生产标识或来源记账字段才能使用，直接引用可读路径和标题；不要寻找已经移除的技术元数据，也不要要求用户补齐。关系、覆盖问题，或维护者需要通过 `dist_path` → `approved_path` 定位原批准页时，才读取构建清单。原始来源归因留在生产工作区的 `knowledge/`，不要求写入发布页。原始材料未随包分发时，只根据已批准的可见正文回答并说明边界。
 
 ## 搜索兜底
 
@@ -70,8 +70,7 @@ node <当前 knowledge-query Skill 目录>/scripts/search.mjs --query '<关键
 
 ```text
 页面：     <结论> [<root>/path/page.md]
-章节：     <结论> [<root>/path/page.md#section-id]
-来源绑定： <结论> [<root>/path/page.md#section-id, source_ref]
+章节：     <结论> [<root>/path/page.md, 标题：<可见标题>]
 关系：     <结论> [context-build-inventory.json#structure.edge_records edge:<type>]
 覆盖：     <结论> [context-build-inventory.json]
 ```
@@ -81,7 +80,7 @@ node <当前 knowledge-query Skill 目录>/scripts/search.mjs --query '<关键
 ```text
 缺口：本知识包没有包含 <缺失点> 的证据。
 已检查：<索引、页面或构建产物>。
-下一步来源：<已知时填写来源、页面或 source_ref>。
+下一步来源：<已知时填写来源文档或页面>。
 ```
 
 “本包没有证据”不等于“事实不成立”。禁止使用模型记忆、旧对话或包外源码填补缺口。
@@ -94,6 +93,7 @@ node <当前 knowledge-query Skill 目录>/scripts/search.mjs --query '<关键
 
 已批准知识文件：`{{knowledgeCount}}`
 
-## 模板作者建议
+{{!-- 模板作者建议（不进入分发的查询 Skill）：
 
 这是可直接工作的通用查询 Skill。正式发布前，如果知识包存在专用术语、常见用户意图、推荐入口、已知边界或固定任务流程，作者应修改 description、路由表和包边界说明；如果通用行为已经足够，应在 Context 的包模板 Review 中明确接受未修改模板。
+--}}