@botbotgo/agent-harness 0.0.195 → 0.0.197

package/README.md

@@ -184,35 +184,19 @@ The default rule is:
 - if LangChain v1 or DeepAgents already has the feature, map it in YAML and adapt it internally
 - do not add a new public runtime API unless the problem is truly runtime-owned
 
-Boundary documents live in:
+Start with these user-facing docs:
 
 - `docs/development/index.html`
 - `docs/development/getting-started.html`
-- `docs/development/application-model.html`
-- `docs/development/workspace-and-yaml.html`
-- `docs/development/extensions.html`
-- `docs/development/runtime-operations.html`
-- `docs/development/testing-and-release.html`
 - `docs/development/api-reference.html`
+- `docs/development/protocol-surfaces.html`
 - `docs/development/cookbook.html`
-- `docs/upstream-feature-matrix.md`
-- `docs/product-boundary.md`
-- `docs/runtime-blueprint-assessment.md`
-- `docs/policy-engine-scope.md`
-- `docs/acp-support-plan.md`
-- `docs/recovery-policy-matrix.md`
-- `docs/operator-timeline.md`
 - `docs/runtime-inspection-contract.md`
-- `docs/queue-concurrency-inspection.md`
 - `docs/tool-execution-policy.md`
-- `docs/feature-checklist.md`
 - `docs/long-term-memory.md`
-- `docs/memory-runtime-design.md`
-- `docs/memory-runtime-usage.md`
 - `docs/memory-policy-reference.md`
-- `docs/app-task-pattern.md`
-- `docs/model-layering.md`
-- `docs/coding-agent-guide.md`
+
+Maintainer notes and internal product-boundary discussions remain in the repository, but they are intentionally not part of the primary public reading path.
 
 `deepagents-acp` is the required external protocol direction when external tools need a standard runtime boundary. The harness should conform to `deepagents-acp` semantics at that boundary while keeping runtime lifecycle, persistence, recovery, and governance harness-owned.
 
@@ -660,6 +644,7 @@ Example workspaces:
 
 - `examples/hello-skill-app/` keeps the smallest local tool + skill workspace
 - `examples/runtime-flow-demo/` runs one real hosted-model request and exports a Mermaid flowchart from runtime plus upstream events
+- `examples/protocol-hello-world/` shows the same minimal direct agent wired to ACP, A2A, and AG-UI hello-world transport samples
 
 Workspace-local tool modules in `resources/tools/` should be exported with `tool({...})`.
 Any other local module shape is not supported, and unsupported shapes are rejected at load time.
@@ -933,7 +918,7 @@ spec:
     middleware: []
 ```
 
-For backend-specific options, prefer the upstream concept directly inside `spec.config`. Upstream feature coverage is tracked in [docs/upstream-feature-matrix.md](docs/upstream-feature-matrix.md).
+For backend-specific options, prefer the upstream concept directly inside `spec.config`. Keep the public runtime contract in the main developer docs and API reference rather than relying on maintainer-only comparison notes.
 
 ## Design Notes
 

package/README.zh.md

@@ -182,32 +182,19 @@ AI 让 agent 逻辑、工具调用和工作流代码更容易生成，真正更
 - 若 LangChain v1 或 DeepAgents 已有能力，则在 YAML 中映射并在内部适配
 - 除非问题确实属于运行时职责，否则不增加新的公共运行时 API
 
-边界说明见：
+建议从这些面向用户的文档开始：
 
 - `docs/development/index.html`
 - `docs/development/getting-started.html`
-- `docs/development/application-model.html`
-- `docs/development/workspace-and-yaml.html`
-- `docs/development/extensions.html`
-- `docs/development/runtime-operations.html`
-- `docs/development/testing-and-release.html`
 - `docs/development/api-reference.html`
+- `docs/development/protocol-surfaces.html`
 - `docs/development/cookbook.html`
-- `docs/upstream-feature-matrix.md`
-- `docs/product-boundary.md`
-- `docs/runtime-blueprint-assessment.md`
-- `docs/policy-engine-scope.md`
-- `docs/acp-support-plan.md`
-- `docs/recovery-policy-matrix.md`
-- `docs/operator-timeline.md`
 - `docs/runtime-inspection-contract.md`
-- `docs/queue-concurrency-inspection.md`
 - `docs/tool-execution-policy.md`
-- `docs/feature-checklist.md`
 - `docs/long-term-memory.md`
-- `docs/app-task-pattern.md`
-- `docs/model-layering.md`
-- `docs/coding-agent-guide.md`
+- `docs/memory-policy-reference.md`
+
+维护者笔记和产品边界讨论仍然保留在仓库里，但不会再作为公开阅读路径的一部分放在主要入口里。
 
 当外部工具需要标准运行时边界时，`deepagents-acp` 是必须遵循的外部协议方向。`agent-harness` 应在该边界上严格契合 `deepagents-acp` 语义，同时继续把运行时生命周期、持久化、恢复与治理保留在 harness 内部。
 
@@ -622,6 +609,7 @@ await stop(runtime);
 
 - `examples/hello-skill-app/` 保留最小的本地 tool + skill 工作区
 - `examples/runtime-flow-demo/` 会跑一次真实 hosted model 请求，并把 runtime 与 upstream events 导出为 Mermaid flowchart
+- `examples/protocol-hello-world/` 展示同一个最小 direct agent 的 ACP、A2A 与 AG-UI 三种 hello-world 传输示例
 
 `resources/tools/` 下的工作区本地工具模块应统一用 `tool({...})` 导出。
 不支持历史/兼容写法，任何不带该导出形式的工具模块都会在工作区加载时被拒绝。
@@ -890,7 +878,7 @@ spec:
     middleware: []
 ```
 
-后端相关选项优先直接写在 `spec.config` 中沿用上游概念。上游能力覆盖见 [docs/upstream-feature-matrix.md](docs/upstream-feature-matrix.md)。
+后端相关选项优先直接写在 `spec.config` 中沿用上游概念。公开能力边界以开发者文档与 API 参考为准，不依赖维护者内部对比笔记。
 
 ## 设计说明
 

package/dist/package-version.d.ts

@@ -1 +1 @@
-export declare const AGENT_HARNESS_VERSION = "0.0.194";
+export declare const AGENT_HARNESS_VERSION = "0.0.196";

package/dist/package-version.js

@@ -1 +1 @@
-export const AGENT_HARNESS_VERSION = "0.0.194";
+export const AGENT_HARNESS_VERSION = "0.0.196";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@botbotgo/agent-harness",
-  "version": "0.0.195",
+  "version": "0.0.197",
   "description": "Workspace runtime for multi-agent applications",
   "license": "MIT",
   "type": "module",