@botbotgo/agent-harness 0.0.95 → 0.0.97

package/README.md

@@ -82,7 +82,7 @@ Recommended orchestration shape for long-running flows:
 
 - let callers select the host agent explicitly whenever possible
 - use `backend: deepagent` when you want high-level execution semantics with minimal application wiring
-- use `backend: langgraph` when approvals, recovery, and long-running orchestration need application-owned workflow control
+- keep `backend: langchain-v1` for lighter direct-response or explicitly chosen V1 agent shapes
 
 ## Why This Exists
 
@@ -130,8 +130,6 @@ your-workspace/
       backends.yaml
       tools.yaml
       mcp.yaml
-    workflows/
-      langgraph-workflows.yaml
     agents/
       direct.yaml
       orchestra.yaml
@@ -376,7 +374,6 @@ Core workspace files:
 - `config/catalogs/backends.yaml`
 - `config/catalogs/tools.yaml`
 - `config/catalogs/mcp.yaml`
-- `config/workflows/langgraph-workflows.yaml`
 - `config/agents/direct.yaml`
 - `config/agents/orchestra.yaml`
 - `resources/tools/`
@@ -394,7 +391,6 @@ There are three main configuration layers:
 ### Backend Guidance
 
 At the moment, the most stable path for complex production-style runs is `backend: deepagent`.
-`backend: langgraph` now exists as an explicit adapter boundary for LangGraph-shaped runtime entry design, but it still reuses the current LangChain-style runnable path internally rather than exposing a fully custom graph DSL.
 
 Current temporary limits on the `backend: langchain-v1` path are:
 
@@ -405,117 +401,8 @@ Current temporary limits on the `backend: langchain-v1` path are:
 Practical guidance:
 
 - use `backend: deepagent` for approvals, resume, multi-agent orchestration, rich memory flows, and heavier tool chains
-- use `backend: langgraph` when you want the agent to bind to a built-in preset or an explicit LangGraph workflow resource in config
 - keep `backend: langchain-v1` for lighter direct-response or explicitly chosen V1 agent shapes while this upstream behavior settles
 
-Minimal Kubernetes-style LangGraph example:
-
-```yaml
-apiVersion: agent-harness/v1alpha1
-kind: LangGraphWorkflows
-spec:
-  - id: default
-    entryNode: planner
-    nodes:
-      - id: planner
-        kind: llm
-        role: planner
-      - id: executor
-        kind: agent
-    edges:
-      - from: planner
-        to: executor
-```
-
-```yaml
-apiVersion: agent-harness/v1alpha1
-kind: Agent
-metadata:
-  name: graph-entry
-spec:
-  runtime:
-    runRoot: ./.agent
-  execution:
-    backend: langgraph
-    modelRef: model/default
-    config:
-      preset: review-loop
-```
-
-Built-in LangGraph presets currently supported:
-
-- `react`
-- `prompt-chaining`
-- `routing`
-- `parallelization`
-- `plan-execute`
-- `review-loop`
-- `evaluator-optimizer`
-- `approval-gate`
-- `handoff`
-- `orchestrator-workers`
-
-The repository also checks in matching YAML workflow resources for these patterns in
-`config/workflows/langgraph-workflows.yaml`, so applications can reference them directly with
-`workflow.ref: langgraph-workflow/<pattern-id>`.
-
-For agent-driven presets such as `routing`, `parallelization`, `handoff`, and `orchestrator-workers`, also set:
-
-```yaml
-config:
-  preset: handoff
-  agent: researcher
-```
-
-LangGraph also supports profile-first entry config for common application shapes:
-
-- `coding-runtime`
-- `personal-assistant`
-- `research-runtime`
-- `approval-review-runtime`
-- `claw-style-assistant`
-- `chat-operator`
-- `copilot-sidecar`
-- `task-delegation-hub`
-
-```yaml
-config:
-  profile: copilot-sidecar
-  with:
-    coderAgent: repo-coder-lite
-```
-
-These presets are harness-owned workflow templates built on top of the LangGraph backend. They are not LangGraph-native node kinds or edge conditions.
-
-Current workflow primitive node kinds:
-
-- `llm`
-- `agent`
-- `tool`
-- `approval`
-- `condition`
-
-Only these primitive node kinds are supported in workflow YAML. Role-shaped names such as `planner`, `reviewer`,
-`replanner`, `specialist`, `executor`, and `finalizer` are not part of the final DSL.
-
-Use an explicit workflow ref when an application wants full graph control:
-
-```yaml
-apiVersion: agent-harness/v1alpha1
-kind: Agent
-metadata:
-  name: graph-entry
-spec:
-  runtime:
-    runRoot: ./.agent
-  execution:
-    backend: langgraph
-    modelRef: model/default
-    config:
-      workflow:
-        ref: langgraph-workflow/default
-```
-
 ### `config/runtime/workspace.yaml`
 
 Use this file for workspace-wide runtime policy.

package/README.zh.md

@@ -82,7 +82,7 @@
 
 - 尽量由调用方显式指定要运行的 host agent
 - 想用高层执行语义、少写应用编排时，优先选择 `backend: deepagent`
-- 当 approvals、recovery 与长链路 orchestration 需要由应用自己控制时，使用 `backend: langgraph`
+- 轻量 direct-response 或明确需要 V1 agent 语义时，使用 `backend: langchain-v1`
 
 ## 为何需要它
 
@@ -130,8 +130,6 @@ your-workspace/
       backends.yaml
       tools.yaml
       mcp.yaml
-    workflows/
-      langgraph-workflows.yaml
     agents/
       direct.yaml
       orchestra.yaml
@@ -376,7 +374,6 @@ await stop(runtime);
 - `config/catalogs/backends.yaml`
 - `config/catalogs/tools.yaml`
 - `config/catalogs/mcp.yaml`
-- `config/workflows/langgraph-workflows.yaml`
 - `config/agents/direct.yaml`
 - `config/agents/orchestra.yaml`
 - `resources/tools/`
@@ -394,7 +391,6 @@ await stop(runtime);
 ### Backend 选择建议
 
 当前对于复杂、生产化风格的运行链路，最稳定的路径仍然是 `backend: deepagent`。
-现在也支持 `backend: langgraph` 作为显式的 LangGraph 风格 adapter 边界；不过内部实现当前仍复用现有 LangChain runnable 路径，还不是完整自定义 graph DSL。
 
 目前 `backend: langchain-v1` 这条路径的暂时限制是：
 
@@ -405,73 +401,8 @@ await stop(runtime);
 实际建议：
 
 - approvals、resume、多 agent orchestration、复杂 memory 流、重工具链，优先使用 `backend: deepagent`
-- 如果你想让 agent 在配置层显式绑定到一个 LangGraph workflow 资源，使用 `backend: langgraph`
 - `backend: langchain-v1` 先保留给轻量 direct-response 场景，或明确需要 V1 agent 语义的工作区
 
-最小的 Kubernetes 风格 LangGraph 示例：
-
-```yaml
-apiVersion: agent-harness/v1alpha1
-kind: LangGraphWorkflows
-spec:
-  - id: default
-    entryNode: planner
-    nodes:
-      - id: planner
-        kind: llm
-        role: planner
-      - id: executor
-        kind: agent
-    edges:
-      - from: planner
-        to: executor
-```
-
-当前建议优先使用的 workflow primitive node kinds：
-
-- `llm`
-- `agent`
-- `tool`
-- `approval`
-- `condition`
-
-最终版 workflow YAML 只支持这些 primitive node kinds。`planner`、`reviewer`、`replanner`、`specialist`、
-`executor`、`finalizer` 这类角色型名字不属于最终 DSL。
-
-LangGraph 也支持面向常见应用入口的 profile-first 配置：
-
-- `coding-runtime`
-- `personal-assistant`
-- `research-runtime`
-- `approval-review-runtime`
-- `claw-style-assistant`
-- `chat-operator`
-- `copilot-sidecar`
-- `task-delegation-hub`
-
-```yaml
-config:
-  profile: copilot-sidecar
-  with:
-    coderAgent: repo-coder-lite
-```
-
-```yaml
-apiVersion: agent-harness/v1alpha1
-kind: Agent
-metadata:
-  name: graph-entry
-spec:
-  runtime:
-    runRoot: ./.agent
-  execution:
-    backend: langgraph
-    modelRef: model/default
-    config:
-      workflow:
-        ref: langgraph-workflow/default
-```
-
 ### `config/runtime/workspace.yaml`
 
 用于工作区范围的运行时策略。

package/dist/api.d.ts

@@ -1,7 +1,7 @@
 import type { ApprovalRecord, CancelOptions, RunRecord, RunOptions, RunSummary, ResumeOptions, RuntimeHealthSnapshot, RuntimeAdapterOptions, ThreadSummary, ThreadRecord, WorkspaceLoadOptions } from "./contracts/types.js";
 import { AgentHarnessRuntime } from "./runtime/harness.js";
-import type { InventoryAgentRecord, InventorySkillRecord } from "./runtime/inventory.js";
-import type { RequirementAssessmentOptions } from "./runtime/skill-requirements.js";
+import type { InventoryAgentRecord, InventorySkillRecord } from "./runtime/harness/system/inventory.js";
+import type { RequirementAssessmentOptions } from "./runtime/harness/system/skill-requirements.js";
 import type { ToolMcpServerOptions } from "./mcp.js";
 export { AgentHarnessRuntime } from "./runtime/harness.js";
 type CreateAgentHarnessOptions = {
@@ -14,7 +14,7 @@ type CreateAgentHarnessOptions = {
 };
 export declare function createAgentHarness(): Promise<AgentHarnessRuntime>;
 export declare function createAgentHarness(workspaceRoot: string, options?: CreateAgentHarnessOptions): Promise<AgentHarnessRuntime>;
-export declare function run(runtime: AgentHarnessRuntime, options: RunOptions): Promise<import("./contracts/types.js").RunResult>;
+export declare function run(runtime: AgentHarnessRuntime, options: RunOptions): Promise<import("./contracts/runtime.js").RunResult>;
 export declare function subscribe(runtime: AgentHarnessRuntime, listener: Parameters<AgentHarnessRuntime["subscribe"]>[0]): () => void;
 export declare function listThreads(runtime: AgentHarnessRuntime, filter?: Parameters<AgentHarnessRuntime["listThreads"]>[0]): Promise<ThreadSummary[]>;
 export declare function listRuns(runtime: AgentHarnessRuntime, filter?: Parameters<AgentHarnessRuntime["listRuns"]>[0]): Promise<RunSummary[]>;
@@ -29,8 +29,8 @@ export declare function describeInventory(runtime: AgentHarnessRuntime, options?
     workspaceRoot: string;
     agents: InventoryAgentRecord[];
 };
-export declare function resolveApproval(runtime: AgentHarnessRuntime, options: ResumeOptions): Promise<import("./contracts/types.js").RunResult>;
-export declare function cancelRun(runtime: AgentHarnessRuntime, options: CancelOptions): Promise<import("./contracts/types.js").RunResult>;
+export declare function resolveApproval(runtime: AgentHarnessRuntime, options: ResumeOptions): Promise<import("./contracts/runtime.js").RunResult>;
+export declare function cancelRun(runtime: AgentHarnessRuntime, options: CancelOptions): Promise<import("./contracts/runtime.js").RunResult>;
 export declare function stop(runtime: AgentHarnessRuntime): Promise<void>;
 export declare function createToolMcpServer(runtime: AgentHarnessRuntime, options: ToolMcpServerOptions): Promise<import("@modelcontextprotocol/sdk/server/mcp.js").McpServer>;
 export declare function serveToolsOverStdio(runtime: AgentHarnessRuntime, options: ToolMcpServerOptions): Promise<import("@modelcontextprotocol/sdk/server/mcp.js").McpServer>;