Release Notes
These notes summarize recent product releases by what readers and Agents notice. The complete history is in the Context CHANGELOG and the Agent Graph CHANGELOG. The site's own Changelog entry in the More menu is different: it lists the versions of this documentation, not product releases.
To upgrade Context, run the same two commands as a first installation — npm install -g @c4a/context-cli@latest and context plugin install — and restart the Agent session; see Installation. An active knowledge workspace needs no migration step: the next context status returns a fresh Route for the upgraded CLI, and workflow read receipts are kept when a task resumes.
Context 0.7.62 (2026-10-13)
- An approved article that a More menu item targets no longer needs a knowledge map entry: package builds, knowledge map adjustments and structure approval accept it, and review reports no longer list it as unplaced.
- The repository README and the contributing, support and development guides link to this documentation site and describe the Context ecosystem.
Context 0.7.61 (2026-10-12)
Knowledge websites
- The reader's saved light or dark choice is applied from the first paint, so pages no longer flash the system scheme while loading.
- A reader language that leaves homepage fields unset inherits the site's own homepage title, slogan, description and actions instead of falling back to defaults.
- Unknown addresses show a centred 404 page in the reader's language with a link back home.
- Diagrams render in a single frame in both offline Review and websites; edge labels are smaller and centred on their edge, and subgraph titles no longer touch the border.
Planning
- Broad version updates compare the cited repository files by Git object ID before reading content and fetch partial-clone objects in one batch, avoiding long stalls.
Context 0.7.60 (2026-10-08)
Multilingual websites
site.localespublishes one website in several languages. Translations live undertranslations/<tag>/, remember which approved version they were written from, and show a notice when stale or missing.context translate status|prepare|submit|skipvalidates sections, code blocks and links; translation is a workspace Route step before the version is recorded, and it counts toward package freshness with a newtranslationchangelog trigger.
Site navigation
site.nav,site.moreandsite.socialLinksadd top links, More menu items and social icons. A More menu item may target an approved article kept outside the knowledge map — as this page is — and root-relative paths can link to sibling applications on the same domain.
See Multilingual Sites and Documentation Sites.
Context 0.7.50 (2026-10-03)
Same-repository content
- Register a repository's own documentation and authored Skills without copying their bodies into knowledge, with safe relative symlink entrances; see Same-Repository Docs.
- The evidence plugin and local or remote queries understand these references, including incomplete symlink-index coverage.
Evidence and builds
- Evidence keeps historical repository paths and commits, detects relocated document regions, and notices changes anywhere in a Skill directory.
- Optional repository entrance pages, original-source links, localized navigation and offline build fallbacks.
- Invalid registrations stay advisory with repair guidance, and invalid build inputs are rejected without replacing the previous output.
Context 0.7.40 – 0.7.43 (2026-09-29 to 2026-10-01)
These releases made remote code evidence part of normal querying:
- 0.7.40 — queries can use optional read-only remote code evidence at the recorded repository baselines before retrieving unavailable local sources, preserving fixed commits, returned line ranges, partial batch results and permission boundaries.
- 0.7.42 — approved knowledge and recorded code evidence can be read remotely without a checkout. The CLI bundles a read-only repository Wasm plugin that attaches section evidence and commit-specific source URLs, installed with
context evidence installor at workspace initialization. - 0.7.43 — the plugin moves to ABI 2 and attaches compact references to individual read items without replacing their content; remote query guidance follows bounded default reads, file-only search and per-file match limits.
Local and offline retrieval keep working throughout. See Reading Code Evidence Remotely.
Context 0.7.35 – 0.7.36 (2026-09-22)
- Planning for large projects. The
context-planSkill researches a project or a broad source update, hands one stage at a time to production, and recovers from a Git-backed plan. A stage is recommended at thirty documents and capped at fifty, with one newly researched repository per stage; broad discovery needs scope confirmation, and more than five hundred documents needs a person. See Planning Large Projects. - Delegated review. A task can delegate plan and article review while human review stays the default and authorization boundaries are kept; see Managed Mode and Review Policy.
- Document capture. Online document snapshots can be fetched without a workspace and imported later; directory discovery is resumable, and registrations are staged with checkpoints, status, replay and cancellation.
- Review reports list unplaced articles with navigation recovery guidance.
Releases before 0.7.35 are listed in the full CHANGELOG.
Agent Graph
0.3.1 (2026-10-13) raises the compatibility.agentGraph range in the scaffold, templates and examples to ^0.3.0, documents the 0.3.0 Resource protocol migration, and links the repository guides to this site.
0.3.0 (2026-08-31) is a breaking release for Provider authors. The Resource v1/v2 split is replaced by three independent v1 protocols — file, Graph-action and Host-action resources and their locations — and the former agent-graph.resource.v1, .v2, agent-graph.resource-location.v1 and .v2 identifiers are removed. The Host Action input, output and recovery interface is unchanged, but each materialization authority is now explicit in serialized Routes and SDK types. Follow Migration to rename the protocols in an existing Provider.
The 0.2 line built the contract that 0.3.0 renamed:
| Release | Main addition |
|---|---|
| 0.2.7 | Host-materialized resources with versioned input and output schemas and pre-dispatch Provider validation |
| 0.2.6 | Gate-owned delegated execution policies |
| 0.2.5 | Lifecycle-aware evidence as ordinary revision-bound Facts |
| 0.2.3 | Resource read receipts for the current conversation |
| 0.2.1 – 0.2.2 | Gate resolution and read-only Gate inspection Actions |
| 0.2.0 | Fact-grounded routing contracts and catalog-backed reason codes |
0.1.0 (2026-07-22) published the first specification, SDK, CLI, schemas, templates and examples. For what these terms mean, see Core Model.
发布说明
这里按读者和 Agent 能感知到的变化,汇总近期的产品版本。完整历史见 Context CHANGELOG 和 Agent Graph CHANGELOG。“更多”菜单里本站自己的 Changelog 是另一回事:它列出的是这套文档的版本,而不是产品版本。
升级 Context 时,运行与首次安装相同的两条命令——npm install -g @c4a/context-cli@latest 和 context plugin install——然后重启 Agent 会话;参见安装。进行中的知识工作区不需要迁移步骤:下一次 context status 会为升级后的 CLI 返回新的 Route,任务恢复时也会保留工作流的读取回执。
Context 0.7.62(2026-10-13)
- 被“更多”菜单项指向的已批准文章不再需要出现在知识地图中:知识包构建、知识地图调整和结构批准都接受这类文章,审核报告也不再把它们列为未放置。
- 仓库 README 以及贡献、支持和开发指南都链接到本文档站点,并介绍 Context 生态。
Context 0.7.61(2026-10-12)
知识站点
- 读者保存的浅色或深色选择从首次绘制起生效,页面加载时不再先闪现系统配色。
- 某个读者语言未设置的首页字段,会沿用站点自身首页的标题、标语、描述和操作按钮,而不是回退到默认值。
- 访问不存在的地址时,显示居中的 404 页面,使用读者的语言,并提供返回首页的链接。
- 图表在离线审核和站点中都一次渲染完成;连线标签字号更小、居中压在所标注的连线上,子图标题不再贴住边框。
规划
- 大范围版本更新时,先按 Git 对象 ID 比较被引用的仓库文件再读取内容,并在部分克隆中一次性批量拉取对象,避免长时间卡顿。
Context 0.7.60(2026-10-08)
多语言站点
site.locales让一个站点以多种语言发布。译文存放在translations/<tag>/下,记录它译自哪个已批准版本,过期或缺失时显示提示。context translate status|prepare|submit|skip会校验章节、代码块和链接;翻译是记录版本之前的一个知识工作区 Route 步骤,并计入知识包的新鲜度,同时新增translationChangelog 触发项。
站点导航
site.nav、site.more和site.socialLinks用于添加顶部链接、“更多”菜单条目和社交图标。“更多”菜单条目可以指向放在知识地图之外的已批准文章——本页就是这样——以根目录开头的路径还可以链接到同一域名下的兄弟应用。
Context 0.7.50(2026-10-03)
同仓库内容
- 登记仓库自身的文档和自编 Skill,不把正文复制进知识,并维护安全的相对符号链接入口;参见同仓库文档。
- 证据插件以及本地或远程查询都能识别这类引用,包括符号链接索引覆盖不完整的情况。
证据与构建
- 证据保留历史上的仓库路径和提交,能发现文档区域的位置移动,也能察觉 Skill 目录中任意位置的变化。
- 可选的仓库入口页、原始来源链接、本地化导航和离线构建回退。
- 无效的登记只作为提示并给出修复指引;无效的构建输入会被拒绝,且不会替换上一次的输出。
Context 0.7.40 – 0.7.43(2026-09-29 至 2026-10-01)
这几个版本让远程代码证据成为日常查询的一部分:
- 0.7.40——查询在获取本地不可用的来源之前,可以先在记录的仓库基线上使用可选的只读远程代码证据,同时保留固定提交、返回的行范围、部分批量结果和权限边界。
- 0.7.42——无需检出仓库即可远程读取已批准的知识和记录的代码证据。CLI 内置一个只读的仓库 Wasm 插件,为读取结果附上章节证据和指向具体提交的源码 URL,通过
context evidence install或在初始化知识工作区时安装。 - 0.7.43——插件升级到 ABI 2,为每个读取项附上紧凑的引用而不替换其内容;远程查询指引改为遵循有界的默认读取、仅文件搜索和按文件的匹配上限。
本地和离线检索始终可用。参见远程读取代码证据。
Context 0.7.35 – 0.7.36(2026-09-22)
- 大型项目规划。
context-planSkill 负责调研项目或大范围的来源更新,每次把一个阶段交给生产,并依靠 Git 中的计划恢复进度。建议每个阶段三十篇文档、最多五十篇,每个阶段只新调研一个仓库;大范围发现需要确认范围,超过五百篇文档需要人工介入。参见规划大型项目。 - 委托审核。 任务可以委托计划审核和文章审核,同时人工审核仍是默认方式,授权边界保持不变;参见托管模式与审核策略。
- 文档采集。 在线文档快照可以脱离知识工作区先抓取、之后再导入;目录发现可以断点续跑,登记以暂存方式进行,支持检查点、状态查询、重放和取消。
- 审核报告会列出未放入导航的文章,并给出导航恢复指引。
0.7.35 之前的版本见完整的 CHANGELOG。
Agent Graph
**0.3.1(2026-10-13)**把脚手架、模板和示例中的 compatibility.agentGraph 范围提高到 ^0.3.0,补充了 0.3.0 Resource 协议的迁移说明,并让仓库中的各指南链接到本站。
**0.3.0(2026-08-31)**对 Provider 作者是一个不兼容版本。原来的 Resource v1/v2 划分被三个相互独立的 v1 协议取代——文件、Graph-action 和 Host-action 三类资源及其位置——原有的 agent-graph.resource.v1、.v2、agent-graph.resource-location.v1 和 .v2 标识被移除。Host Action 的输入、输出和恢复接口不变,但每种物化授权现在都在序列化的 Route 和 SDK 类型中明确写出。按版本迁移重命名现有 Provider 中的协议。
0.2 系列构建了 0.3.0 所重命名的契约:
| 版本 | 主要新增 |
|---|---|
| 0.2.7 | 由宿主物化的资源,带版本化的输入输出 schema,以及调度前的 Provider 校验 |
| 0.2.6 | 由 Gate 持有的委托执行策略 |
| 0.2.5 | 把感知生命周期的证据作为普通的、绑定修订号的 Facts |
| 0.2.3 | 当前会话中的资源读取回执 |
| 0.2.1 – 0.2.2 | Gate 解决动作和只读的 Gate 检查动作 |
| 0.2.0 | 基于 Facts 的路由契约和由目录支撑的原因码 |
0.1.0(2026-07-22)发布了最初的规范、SDK、CLI、schema、模板和示例。这些术语的含义见核心模型。