@botbotgo/agent-harness 0.0.196 → 0.0.198
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -23
- package/README.zh.md +12 -21
- package/dist/package-version.d.ts +1 -1
- package/dist/package-version.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -50,13 +50,17 @@ This repository is licensed under **Apache License 2.0**.
|
|
|
50
50
|
[LICENSE](./LICENSE)
|
|
51
51
|
|
|
52
52
|
Core runtime is open source, so you can inspect and run it freely.
|
|
53
|
-
Commercial services focus on
|
|
53
|
+
Commercial services focus on helping teams get to a production-ready handoff, including:
|
|
54
54
|
|
|
55
55
|
- Deployment and integration guidance for your environment
|
|
56
|
+
- Initial deployment setup and launch assistance
|
|
56
57
|
- Priority issue triage and troubleshooting
|
|
57
58
|
- Runtime governance, approval flow, and recovery hardening support
|
|
58
59
|
- Custom tools, connectors, and protocol integrations
|
|
59
|
-
-
|
|
60
|
+
- Operator runbooks and handoff guidance for the client team
|
|
61
|
+
|
|
62
|
+
Production operations, managed hosting, on-call coverage, and long-term run-the-system support are not included by default.
|
|
63
|
+
If a team wants us to take on that responsibility, we scope it separately based on environment complexity and SLA expectations.
|
|
60
64
|
|
|
61
65
|
If your team needs a scalable enterprise setup, please contact:
|
|
62
66
|
**[info@easynet.world](mailto:info@easynet.world)**.
|
|
@@ -184,35 +188,19 @@ The default rule is:
|
|
|
184
188
|
- if LangChain v1 or DeepAgents already has the feature, map it in YAML and adapt it internally
|
|
185
189
|
- do not add a new public runtime API unless the problem is truly runtime-owned
|
|
186
190
|
|
|
187
|
-
|
|
191
|
+
Start with these user-facing docs:
|
|
188
192
|
|
|
189
193
|
- `docs/development/index.html`
|
|
190
194
|
- `docs/development/getting-started.html`
|
|
191
|
-
- `docs/development/application-model.html`
|
|
192
|
-
- `docs/development/workspace-and-yaml.html`
|
|
193
|
-
- `docs/development/extensions.html`
|
|
194
|
-
- `docs/development/runtime-operations.html`
|
|
195
|
-
- `docs/development/testing-and-release.html`
|
|
196
195
|
- `docs/development/api-reference.html`
|
|
196
|
+
- `docs/development/protocol-surfaces.html`
|
|
197
197
|
- `docs/development/cookbook.html`
|
|
198
|
-
- `docs/upstream-feature-matrix.md`
|
|
199
|
-
- `docs/product-boundary.md`
|
|
200
|
-
- `docs/runtime-blueprint-assessment.md`
|
|
201
|
-
- `docs/policy-engine-scope.md`
|
|
202
|
-
- `docs/acp-support-plan.md`
|
|
203
|
-
- `docs/recovery-policy-matrix.md`
|
|
204
|
-
- `docs/operator-timeline.md`
|
|
205
198
|
- `docs/runtime-inspection-contract.md`
|
|
206
|
-
- `docs/queue-concurrency-inspection.md`
|
|
207
199
|
- `docs/tool-execution-policy.md`
|
|
208
|
-
- `docs/feature-checklist.md`
|
|
209
200
|
- `docs/long-term-memory.md`
|
|
210
|
-
- `docs/memory-runtime-design.md`
|
|
211
|
-
- `docs/memory-runtime-usage.md`
|
|
212
201
|
- `docs/memory-policy-reference.md`
|
|
213
|
-
|
|
214
|
-
-
|
|
215
|
-
- `docs/coding-agent-guide.md`
|
|
202
|
+
|
|
203
|
+
Maintainer notes and internal product-boundary discussions remain in the repository, but they are intentionally not part of the primary public reading path.
|
|
216
204
|
|
|
217
205
|
`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.
|
|
218
206
|
|
|
@@ -934,7 +922,7 @@ spec:
|
|
|
934
922
|
middleware: []
|
|
935
923
|
```
|
|
936
924
|
|
|
937
|
-
For backend-specific options, prefer the upstream concept directly inside `spec.config`.
|
|
925
|
+
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.
|
|
938
926
|
|
|
939
927
|
## Design Notes
|
|
940
928
|
|
package/README.zh.md
CHANGED
|
@@ -49,13 +49,17 @@
|
|
|
49
49
|
本仓库采用 **Apache License 2.0** 开源许可。[查看 LICENSE](./LICENSE)
|
|
50
50
|
|
|
51
51
|
核心运行时保持开源,方便你自由查看与试用。
|
|
52
|
-
|
|
52
|
+
商业服务聚焦“帮助团队完成生产落地与交接”的能力,包括:
|
|
53
53
|
|
|
54
54
|
- 你的环境中的部署与接入咨询
|
|
55
|
+
- 初期 deployment 搭建与上线协助
|
|
55
56
|
- 优先故障响应与问题排查
|
|
56
57
|
- 运行时治理、审批流和恢复能力加固支持
|
|
57
58
|
- 定制工具、连接器与协议接入开发
|
|
58
|
-
-
|
|
59
|
+
- 面向客户团队的操作手册与交接说明
|
|
60
|
+
|
|
61
|
+
正式生产运维、托管、值班响应和长期代运营不属于默认服务内容。
|
|
62
|
+
如果客户希望我们承担这部分责任,会根据环境复杂度和 SLA 要求单独评估与报价。
|
|
59
63
|
|
|
60
64
|
如果你需要企业级合作方案,请联系:**[info@easynet.world](mailto:info@easynet.world)**。
|
|
61
65
|
|
|
@@ -182,32 +186,19 @@ AI 让 agent 逻辑、工具调用和工作流代码更容易生成,真正更
|
|
|
182
186
|
- 若 LangChain v1 或 DeepAgents 已有能力,则在 YAML 中映射并在内部适配
|
|
183
187
|
- 除非问题确实属于运行时职责,否则不增加新的公共运行时 API
|
|
184
188
|
|
|
185
|
-
|
|
189
|
+
建议从这些面向用户的文档开始:
|
|
186
190
|
|
|
187
191
|
- `docs/development/index.html`
|
|
188
192
|
- `docs/development/getting-started.html`
|
|
189
|
-
- `docs/development/application-model.html`
|
|
190
|
-
- `docs/development/workspace-and-yaml.html`
|
|
191
|
-
- `docs/development/extensions.html`
|
|
192
|
-
- `docs/development/runtime-operations.html`
|
|
193
|
-
- `docs/development/testing-and-release.html`
|
|
194
193
|
- `docs/development/api-reference.html`
|
|
194
|
+
- `docs/development/protocol-surfaces.html`
|
|
195
195
|
- `docs/development/cookbook.html`
|
|
196
|
-
- `docs/upstream-feature-matrix.md`
|
|
197
|
-
- `docs/product-boundary.md`
|
|
198
|
-
- `docs/runtime-blueprint-assessment.md`
|
|
199
|
-
- `docs/policy-engine-scope.md`
|
|
200
|
-
- `docs/acp-support-plan.md`
|
|
201
|
-
- `docs/recovery-policy-matrix.md`
|
|
202
|
-
- `docs/operator-timeline.md`
|
|
203
196
|
- `docs/runtime-inspection-contract.md`
|
|
204
|
-
- `docs/queue-concurrency-inspection.md`
|
|
205
197
|
- `docs/tool-execution-policy.md`
|
|
206
|
-
- `docs/feature-checklist.md`
|
|
207
198
|
- `docs/long-term-memory.md`
|
|
208
|
-
- `docs/
|
|
209
|
-
|
|
210
|
-
|
|
199
|
+
- `docs/memory-policy-reference.md`
|
|
200
|
+
|
|
201
|
+
维护者笔记和产品边界讨论仍然保留在仓库里,但不会再作为公开阅读路径的一部分放在主要入口里。
|
|
211
202
|
|
|
212
203
|
当外部工具需要标准运行时边界时,`deepagents-acp` 是必须遵循的外部协议方向。`agent-harness` 应在该边界上严格契合 `deepagents-acp` 语义,同时继续把运行时生命周期、持久化、恢复与治理保留在 harness 内部。
|
|
213
204
|
|
|
@@ -891,7 +882,7 @@ spec:
|
|
|
891
882
|
middleware: []
|
|
892
883
|
```
|
|
893
884
|
|
|
894
|
-
后端相关选项优先直接写在 `spec.config`
|
|
885
|
+
后端相关选项优先直接写在 `spec.config` 中沿用上游概念。公开能力边界以开发者文档与 API 参考为准,不依赖维护者内部对比笔记。
|
|
895
886
|
|
|
896
887
|
## 设计说明
|
|
897
888
|
|
|
@@ -1 +1 @@
|
|
|
1
|
-
export declare const AGENT_HARNESS_VERSION = "0.0.
|
|
1
|
+
export declare const AGENT_HARNESS_VERSION = "0.0.197";
|
package/dist/package-version.js
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
export const AGENT_HARNESS_VERSION = "0.0.
|
|
1
|
+
export const AGENT_HARNESS_VERSION = "0.0.197";
|