@c4a/context-cli 0.6.1-beta.3 → 0.6.1-beta.5

package/README.md

@@ -57,6 +57,7 @@ the route; progressive loading does not shorten or discard them.
 ```bash
 # Create a standalone workspace.
 context init context
+# Use --language zh-CN when generated workspace and starter templates should be Chinese.
 cd context
 bun install
 
@@ -78,10 +79,21 @@ The workspace state is split across:
 
 - `src/` for project declarations and package templates.
 - `sources/` for source registries and captured evidence.
-- `unapproved/` for draft, rejected, or deprecated candidates.
-- `knowledge/` for approved knowledge.
+- `.tmp/context-runtime/lifecycle/` for ignored, CLI-managed draft candidates and
+  confirmed structure snapshots during an open lifecycle round.
+- `knowledge/` for approved Markdown, the closed `structure.yaml` projection,
+  and the minimal `decisions.json` rejected-candidate fingerprint map when one
+  exists.
 - `dist/` for generated package output.
-- `.tmp/context-runtime/` for ignored logs, previews, reports, locks, and caches.
+- `.tmp/context-runtime/` for other ignored logs, previews, reports, locks, and caches.
+
+The lifecycle and review runtime state is not user-editable and is removed by a
+successful `context close`. `knowledge/structure.yaml` is the durable approved
+structure projection. Its minimal `source_inputs` entries record only the
+source, collection, and source snapshot consumed by a closed prose target, so a
+clean workspace can distinguish completed and changed inputs after transient
+snapshots are removed. `knowledge/decisions.json` only preserves rejected
+candidate IDs and their fingerprints so unchanged candidates are not offered again.
 
 Do not repair lifecycle state by manually deleting or rewriting these
 directories. Use the command or next action returned by the CLI.
@@ -89,12 +101,11 @@ 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.
+KB packages use flat, package-relative OKF roots: `wikis/`, `guides/`,
+`rules/`, and `feats/`. The package name already identifies the surrounding
+`dist/<package-name>/` directory and is not repeated inside those roots. Older
+workspaces that still declare `distribution.knowledgeNamespace` remain
+loadable, but the legacy value no longer changes package paths.
 
 See the SDK manuals for the complete configuration and template contract:
 
@@ -138,6 +149,8 @@ context source add repo [YYYYMMDD] --module <module> --local <repo-or-subdir>
 context source add file [YYYYMMDD] --module <module> --local <file-or-folder>
 context source add lark [YYYYMMDD] --module <module> --url <lark-url>
 context source add batch [YYYYMMDD] --input <yaml-or-json>
+context source remove <source-id> --format json          # preview
+context source remove <source-id> --yes --format json    # apply after reference checks
 context source ensure [source]
 context source inspect [source]
 

package/README.zh-CN.md

@@ -40,7 +40,7 @@ Agent 把 `context status --format json` 返回的 `workflow.current` 作为当
 
 ```bash
 # 创建独立工作区
-context init context
+context init context --language zh-CN
 cd context
 bun install
 
@@ -61,19 +61,21 @@ node_modules/@c4a/context/docs/reference/package-templates.md
 
 - `src/`：项目声明和知识包模板。
 - `sources/`：来源登记和已经读取的证据。
-- `unapproved/`：草稿、拒绝或废弃的知识候选。
-- `knowledge/`：审核通过的知识。
+- `.tmp/context-runtime/lifecycle/`：一个开放生命周期轮次中的、被忽略且仅由 CLI 管理的草稿候选和已确认结构快照。
+- `knowledge/`：已批准的 Markdown、close 后的 `structure.yaml` 结构投影，以及存在时用于记录被拒候选 fingerprint 的精简 `decisions.json`。
 - `dist/`：构建生成的知识包。
-- `.tmp/context-runtime/`：忽略的日志、预览、报告、锁和缓存。
+- `.tmp/context-runtime/`：其他被忽略的日志、预览、报告、锁和缓存。
+
+生命周期和审核运行态不可由用户编辑，成功执行 `context close` 后会被自动清理。`knowledge/structure.yaml` 是持久的已批准结构投影，其中精简的 `source_inputs` 只记录已关闭 prose 目标消费的 source、collection 和来源快照，以便临时结构清理后仍能区分已完成输入与变化输入；`knowledge/decisions.json` 仅保留被拒候选的 ID 与 fingerprint，避免未变化的候选再次出现。
 
 不要通过手动删除或改写这些目录来修复流程状态，应使用 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 名称与它相互独立。
+`context build` 会把声明好的知识包写入 `dist/<package-name>/`。KB 包直接使用
+`wikis/`、`guides/`、`rules/` 和 `feats/` 作为包内 OKF 根目录，不再在这些目录下重复包名。
+旧工作区即使仍声明 `distribution.knowledgeNamespace` 也可以继续加载，但该兼容字段不再改变
+知识包输出路径。
 
 完整配置和模板约定参见 SDK 手册：
 
@@ -113,6 +115,8 @@ context source add repo [YYYYMMDD] --module <module> --local <repo-or-subdir>
 context source add file [YYYYMMDD] --module <module> --local <file-or-folder>
 context source add lark [YYYYMMDD] --module <module> --url <lark-url>
 context source add batch [YYYYMMDD] --input <yaml-or-json>
+context source remove <source-id> --format json          # 预览
+context source remove <source-id> --yes --format json    # 引用检查通过后执行
 context source ensure [source]
 context source inspect [source]