@c4a/context-cli 0.6.3 → 0.6.5

package/README.md

@@ -112,8 +112,14 @@ KB packages use flat, package-relative OKF roots: `wikis/`, `guides/`,
 `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.
-Resources referenced by selected pages are copied to `others/assets/` inside
-the package, with links rewritten by the builder.
+New KB setup should offer Git raw resource delivery first. Build rewrites links
+to repository raw URLs; committing and publishing the resources remains the
+package author's responsibility. An explicit `urlPrefix` also works when the
+Context workspace itself is outside Git. Without Git or an explicit prefix,
+authors can bundle resources under `others/assets/` or explicitly omit them and
+retain unresolved references.
+Bundled delivery may configure `kbPackage().assets.optimize`; Context itself
+does not depend on an image processor.
 
 See the SDK manuals for the complete configuration and template contract:
 
@@ -141,6 +147,21 @@ implementation detail; Context users and plugins consume only
 Building a package completes the currently active approved state; it does not
 freeze the workspace. New sources can be added and processed later.
 
+With explicit current-conversation managed authority,
+`context run --managed --until blocked-or-complete` keeps one workspace-bound
+runtime for consecutive deterministic actions. Each action remains bound to
+the Route revision that selected it; after the action, Context reloads the
+project from disk and evaluates the graph again. Known local actions run in the
+same process, while source tools and other external effects remain isolated in
+child processes.
+
+The runtime scope owns only short-lived resources such as output capture,
+timers, child processes, and write locks, and releases them in reverse order.
+Knowledge, snapshots, decisions, and package output are durable state: they
+retain their existing revision checks, project write lock, atomic write, close,
+and verify contracts. No execution scope rolls back or substitutes those
+contracts, and the workspace file protocol is unchanged.
+
 ## Command Groups
 
 ```bash

package/README.zh-CN.md

@@ -81,7 +81,11 @@ node_modules/@c4a/context/docs/reference/package-templates.md
 `wikis/`、`guides/`、`rules/` 和 `feats/` 作为包内 OKF 根目录，不再在这些目录下重复包名。
 旧工作区即使仍声明 `distribution.knowledgeNamespace` 也可以继续加载，但该兼容字段不再改变
 知识包输出路径。
-选中页面引用的资源会复制到包内 `others/assets/`，相对链接由构建器自动改写。
+新建 KB 时优先选择 Git raw 资源分发：构建器将链接改写到仓库 raw 地址；资源的
+提交和发布由知识包作者负责。非 Git 工作区可以配置另一个资源仓库的显式 Raw
+前缀；没有可用 Git 或显式前缀时，可以选择随包复制到 `others/assets/`，或显式
+不输出资源并保留失效引用。随包模式可以安装 `sharp` 并通过
+`kbPackage().assets.optimize` 仅优化生成文件；Context 本身不依赖图片处理器。
 
 完整配置和模板约定参见 SDK 手册：
 
@@ -105,6 +109,16 @@ node_modules/@c4a/context/docs/reference/package-templates.md
 
 一次构建只完成当前已经确认的知识状态，并不会冻结工作区。后续还可以继续添加和处理新的来源。
 
+当前对话明确授予全托管权限后，
+`context run --managed --until blocked-or-complete` 会在同一个工作区运行时中连续执行
+确定性动作。每个动作仍绑定到选择它的 Route revision；动作完成后，Context 会重新从磁盘
+加载项目并再次求值工作图。已知的本地动作在同一进程中执行，来源工具和其他外部副作用仍
+隔离在子进程中。
+
+执行作用域只管理输出捕获、定时器、子进程和写锁等短生命周期资源，并按注册顺序的逆序释放。
+知识、快照、审核决定和知识包产物属于持久状态，继续使用原有的 revision 校验、项目写锁、
+原子写入、close 和 verify 契约。执行作用域不会回滚或替代这些契约，工作区文件协议也不改变。
+
 ## 命令分组
 
 ```bash