@c4a/context 0.7.13 → 0.7.14

package/docs/guides/knowledge-updates.md

@@ -194,6 +194,48 @@ coverage by mechanically placing every new page under an unrelated catch-all.
 Build reports missing bindings for the Agent to resolve; it does not classify
 content. Moving a menu entry does not change the article URL.
 
+### Preserve established navigation intent
+
+Before placing new knowledge, read the workspace's AGENTS.md, current
+`src/knowledge-map.yaml`, existing overview pages and relevant category/article
+bodies. Reuse any settled directory intent in the current plan. Establish what
+each affected category helps readers do and why adjacent categories are separate;
+do not infer this from labels alone. Read only affected branches and enough
+neighboring content to distinguish them, not the entire library on every update.
+If intent remains ambiguous, state the proposed interpretation in the plan.
+
+Prefer, in order: revise an existing article; add a page to a matching category;
+add a coherent child category; propose a top-level change only when existing
+categories cannot serve a distinct, lasting reader need. Do not create a top-level
+category merely because a source, repository, product, team or batch is new.
+For example, a new assistant's usage guide, frontend integration and runtime
+architecture can belong in existing usage, frontend and backend categories, with
+cross-links for the shared product. Keep them together only when the site's
+established organizing principle supports that choice.
+
+In the work-start report or current plan, briefly state the affected articles'
+intended placements and reused category intent. For proposed top-level additions,
+renames, removals or changes of purpose, show the before/after tree, why reuse is
+insufficient, affected existing pages and reading order. Present that change for
+human review before applying it. This uses the existing report feedback where
+available; do not add a new CLI state, schema field or routine per-article gate.
+Explicit user approval of that concrete structure is sufficient; do not ask again.
+General permission to write knowledge or organize batches is not approval to
+change the site's top-level organization. If the need emerges after report
+approval, update the same plan and ask about that structural change only; continue
+independent work within the approved organization.
+
+Before delivery, compare the resulting map with the approved plan: article
+placement matches its main reader task, titles match the bodies, sibling ordering
+is deliberate, and directories are neither empty nor accidental duplicates.
+Honor the workspace's chosen directory depth and homogeneous sibling convention;
+where it requires directory-only or article-only siblings, do not mix them.
+Use an "Other" group last only for genuinely useful residual content, not to
+avoid classification. Apply supported map adjustments through the current CLI
+flow, retaining article identities and URLs. Record lasting category intent
+briefly in the workspace AGENTS.md or existing organization guide; do not create
+a separate taxonomy ledger or put planning instructions in reader articles.
+
 ### Reader tasks, names and reading order
 
 Read the affected articles' bodies before changing their categories or titles.
@@ -251,8 +293,8 @@ change does not require a prose rewrite or file migration; changing its label do
 not silently rename the approved article. Needed title or content revisions use
 the existing revision and Review flow. Splits and merges use ordinary article
 tasks, link repair and any explicit retirement after replacement content is
-delivered. These are Agent editorial decisions, not new CLI checks or approval
-gates.
+delivered. These are Agent editorial decisions, not new CLI checks or routine per-article
+approval gates. Top-level changes follow the focused review described above.
 
 ## Edit one section or review part of a batch
 

package/docs/guides/package-outputs.md

@@ -480,3 +480,24 @@ Only approved selected content is exported. A map or article change invalidates
 both website and LLMS outputs; failure preserves the previous staged package.
 Standalone `llmsPackage()` uses the same map organization and supplies the full
 text and raw article files alongside its template-rendered `llms.txt` index.
+
+## Links to a deployed website
+
+After a website has been built and deployed, record its complete public root:
+
+```bash
+context package site-url <package-name> https://example.com/docs/
+```
+
+This command adds optional `site_url` to the existing `context.site-output/v1`
+map, in both the website and knowledge package. It normalizes a trailing slash,
+rejects credentials/query/fragment, and never contacts the URL. The address
+includes the deployment subpath; resolve `pages[].site_path` against it without
+adding `base` again. Rebuilds preserve the address from the previous website
+map and distribute the refreshed mapping with the package. Deleting dist also
+deletes this optional delivery metadata: record it again from the deployment
+result instead of guessing a hostname. No new workspace configuration is needed.
+
+The address is an access hint, not proof of publication or content freshness.
+Query Skills use it only to append related links in the final summary, with no
+network probes or version checks. Packages without the map work as before.

package/docs/reference/indexer-provider-protocol.md

@@ -351,8 +351,10 @@ visible-Skill claim nor the Route report authorizes Bundle materialization.
 ## Contract overlay validation
 
 `validate-indexer-contract-overlays` recomputes the complete data-only overlay
-against the exact CLI base and operator contracts. Invalid DSL, executable
-fields, identity redefinition, threshold weakening, digest drift or a partial
+against the current CLI base and operator contracts. Contract versions must match;
+historical base/operator digests are provenance, not compatibility pins. Parser
+release changes and unrelated profile changes do not require rebinding. Invalid DSL, executable
+fields, identity redefinition, threshold weakening, invalid payload integrity or a partial
 Provider identity fails validation. The selected Provider Bundle integrity is
 an exact input, not a self-reported trust assertion.
 

package/index.js

@@ -23838,11 +23838,11 @@ function validateIndexerContractOverlay(input) {
   if (indexerContractOverlayDigest(overlayPayload) !== overlay.overlay_digest) {
     throw new TypeError("contract overlay digest does not match its canonical payload");
   }
-  if (overlay.extends.version !== base.version || overlay.extends.contract_digest !== base.contract_digest) {
-    throw new TypeError("contract overlay is bound to another base contract");
+  if (overlay.extends.version !== base.version) {
+    throw new TypeError("contract overlay requires another base contract version");
   }
-  if (overlay.operator_contract_version !== operators.version || overlay.operator_contract_digest !== operators.contract_digest) {
-    throw new TypeError("contract overlay is bound to another operator contract");
+  if (overlay.operator_contract_version !== operators.version) {
+    throw new TypeError("contract overlay requires another operator contract version");
   }
   const baseProfile = profileById(base, overlay.extends.profile);
   const effectiveProfile = mergeOverlayProfile(baseProfile, overlay);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c4a/context",
-  "version": "0.7.13",
+  "version": "0.7.14",
   "type": "module",
   "description": "Declarative SDK for Context knowledge sources, workflows, review, and package outputs",
   "license": "MIT",

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

@@ -133,3 +133,20 @@ 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.
 --}}
+
+## Website links in the final summary
+
+After answering from the pages actually read, optionally append one or more
+related document links in the final summary. Read `context-site-map.json` from
+the selected package (or its sibling website output in a workspace). Match the
+read page to `pages[].package_path` or `approved_path`; use its `title` and resolve
+`site_path` relative to `site_url`. The URL already includes the deployment base
+path: do not prepend `base` again. Only cite matched articles, deduplicate links,
+and do not invent section anchors.
+
+This is a local formatting step, not retrieval or validation. Do not probe URLs,
+make HTTP/HEAD requests, open a browser, inspect a deployment platform, or check
+remote versions to add links. Never build, publish or update metadata for this
+purpose. If the map, URL or matching page is absent or malformed, keep the local
+citation and continue silently. A configured URL does not prove that the site
+contains the current local revision; do not claim online verification.

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

@@ -97,3 +97,16 @@ node <当前 knowledge-query Skill 目录>/scripts/search.mjs --query '<关键
 
 这是可直接工作的通用查询 Skill。正式发布前，如果知识包存在专用术语、常见用户意图、推荐入口、已知边界或固定任务流程，作者应修改 description、路由表和包边界说明；如果通用行为已经足够，应在 Context 的包模板 Review 中明确接受未修改模板。
 --}}
+
+## 总结中的网站文档链接
+
+完成正文检索和回答后，仅在最终总结中按需附上一篇或多篇实际读取过的相关文档链接。
+从当前知识包读取 `context-site-map.json`，按命中文章的包内路径匹配
+`pages[].package_path`，使用 `title` 作链接文字，将 `site_path` 相对
+`site_url` 拼接。`site_url` 已包含站点子路径，不再重复拼接 `base`。
+同一文章只列一次，不凭标题推测页面地址或章节锚点。
+
+这是本地引用格式化，不是检索前置步骤：不要为地址发起 HTTP/HEAD 请求、打开浏览器、
+查询部署平台或远端版本，也不触发构建、发布或元数据修改。映射、地址或匹配项缺失、
+格式不正确时沿用本地引用即可，不阻塞回答，不要求用户补配置。
+记录的链接不证明线上内容与本地版本一致，不声称已验证网站。