@c4a/context-cli 0.6.1-beta.1 → 0.6.1-beta.2

package/README.md

@@ -10,6 +10,10 @@ The CLI is Node/Bun compatible and does not call an LLM. Mechanical work belongs
 to the CLI, semantic judgment belongs to the Agent, and important decisions
 belong to the user.
 
+Markdown parsing is structural only: source headings remain inside citeable
+evidence spans, while their meaning, grouping, and knowledge type are never
+inferred by the CLI.
+
 ## Install
 
 ```bash
@@ -41,9 +45,12 @@ For the shortest installed-package walkthrough, read
 | Explaining choices, editing `src/index.ts`, proposing structure, and generating candidates from evidence | Agent |
 | Source permission, classification, review decisions, and package-output choice | User |
 
-The Agent follows `context status` and CLI diagnostics rather than guessing the
-next command. It may execute safe mechanical steps, but it stops at human gates
-and external source-repository operations.
+The Agent treats `context status --format json` `workflow.current` as the
+current-step authority rather than guessing the next command. The default JSON
+view is compact: it contains the route, required resource locations, progress,
+counts, and aggregated diagnostics. Use `--view full` only for debugging. Long
+procedures and semantic rules remain complete Markdown resources selected by
+the route; progressive loading does not shorten or discard them.
 
 ## Create Or Continue A Workspace
 
@@ -79,10 +86,27 @@ The workspace state is split across:
 Do not repair lifecycle state by manually deleting or rewriting these
 directories. Use the command or next action returned by the CLI.
 
+## Package Output
+
+`context build` writes each declared package under `dist/<package-name>/`.
+Every KB package uses its package name as the default knowledge namespace, so
+its final OKF roots are shaped like
+`wikis/<package-name>/`, `guides/<package-name>/`,
+`rules/<package-name>/`, and `feats/<package-name>/`. A project may explicitly
+choose another safe single- or multi-segment namespace in `src/index.ts`;
+Skill names remain independent.
+
+See the SDK manuals for the complete configuration and template contract:
+
+- [Package outputs](../context/docs/guides/package-outputs.md)
+- [Package templates](../context/docs/reference/package-templates.md)
+
 ## Status-Driven Workflow
 
-The project workflow is declared in `src/index.ts` and routed by
-`context status`:
+The project workflow is declared in `src/index.ts` and routed by the bundled
+Context workflow graph behind `context status`. This graph is an internal CLI
+implementation detail; Context users and plugins consume only
+`workflow.current`, Context commands, and the selected resources:
 
 | Stage | CLI surface |
 |---|---|
@@ -141,8 +165,9 @@ configured `context.entry`.
 - Source registration and source-body reading are separate permissions.
 - Extraction scope and document classification are confirmed before candidate
   writes.
-- Review decisions come from the user. The Agent must not invent approval or
-  rejection payloads.
+- In ordinary mode, Review decisions come from the user and the Agent must not
+  invent payloads. Explicit current-conversation fully managed mode uses only
+  the atomic approval command returned by `workflow.current`.
 - Package output is chosen after approved knowledge exists; package templates
   are project configuration, not a second factual source.
 

package/README.zh-CN.md

@@ -6,6 +6,8 @@
 
 CLI 同时兼容 Node 和 Bun，本身不会调用 LLM。机械操作交给 CLI，语义判断交给 Agent，重要决策交给用户。
 
+CLI 对 Markdown 只做结构解析：源标题会保留在可引用的证据区间中，但标题的含义、分组方式和知识类型均不会由 CLI 推断。
+
 ## 安装
 
 ```bash
@@ -32,7 +34,7 @@ context plugin install
 | 解释选择、修改 `src/index.ts`、提出知识结构、基于证据生成候选 | Agent |
 | 来源授权、知识分类、审核决定和打包方式 | 用户 |
 
-Agent 会跟随 `context status` 和 CLI 返回的诊断，不会凭记忆猜下一条命令。安全的机械步骤可以自动执行，但遇到人工门禁和来源仓库外部操作时会停下来确认。
+Agent 把 `context status --format json` 返回的 `workflow.current` 作为当前步骤的权威协议，不会凭记忆猜下一条命令。默认 JSON 是紧凑视图，只包含当前路由、所需资源位置、进度、计数和聚合诊断；调试时才使用 `--view full`。长篇流程和语义规则仍以完整 Markdown 资源随包发布，由当前路由按需选择，渐进加载不会删减内容。
 
 ## 创建或继续工作区
 
@@ -66,9 +68,21 @@ node_modules/@c4a/context/docs/reference/package-templates.md
 
 不要通过手动删除或改写这些目录来修复流程状态，应使用 CLI 返回的命令或下一步操作。
 
+## 知识包输出
+
+`context build` 会把声明好的知识包写入 `dist/<package-name>/`。每个 KB 包默认使用包名作为知识 namespace，因此最终 OKF 根目录形如
+`wikis/<package-name>/`、`guides/<package-name>/`、
+`rules/<package-name>/` 和 `feats/<package-name>/`。项目可以在
+`src/index.ts` 中显式指定其他安全的单段或多段 namespace；Skill 名称与它相互独立。
+
+完整配置和模板约定参见 SDK 手册：
+
+- [知识包输出](../context/docs/guides/package-outputs.md)
+- [知识包模板](../context/docs/reference/package-templates.md)
+
 ## 状态驱动流程
 
-项目流程声明在 `src/index.ts` 中，由 `context status` 负责路由：
+项目流程声明在 `src/index.ts` 中，由 `context status` 背后的 Context 工作图负责路由。这张图是 CLI 内部实现；用户和插件只消费 `workflow.current`、Context 命令以及当前路由选中的资源：
 
 | 阶段 | CLI 入口 |
 |---|---|
@@ -122,7 +136,7 @@ context build
 - CLI 不会悄悄在来源仓库中执行 clone、checkout、reset、fetch、install、build 或脚本。
 - 登记来源和读取来源正文是两次独立授权。
 - 写入知识候选前，需要确认代码提取范围和文档分类。
-- 审核决定来自用户，Agent 不能自行编造批准或拒绝结果。
+- 普通模式下，审核决定来自用户，Agent 不能自行编造批准或拒绝结果；只有当前对话明确启用全托管时，才可执行 `workflow.current` 返回的原子批准命令。
 - 正式知识准备好后再选择打包方式；知识包模板是项目配置，不是第二份事实来源。
 
 CLI 返回的来源名称、阶段 ID、候选 ID、诊断和 `source_ref` 都是流程标识。`source_ref` 是不可拆解的证据引用，应原样复制，不能把它当作文件路径解析。