fix: route AgentRun bridge from runners

This commit is contained in:
AgentRun Codex
2026-06-11 01:57:17 +00:00
parent 23e2a6e3e2
commit 0d0b3e21f3
5 changed files with 217 additions and 6 deletions
+17
View File
@@ -85,6 +85,21 @@ assertCondition(
"AgentRun control-plane status must degrade empty runtime JSON snippets instead of failing the whole status probe",
);
assertCondition(
agentRunSource.includes('type AgentRunBridgeCaptureBackend = "local-backend-core-broker" | "remote-frontend-websocket"')
&& agentRunSource.includes('reason: "runner-environment"')
&& agentRunSource.includes('degradedReason: "capture-backend-unavailable"')
&& agentRunSource.includes('"agentrun-cli-returned-failure"')
&& agentRunSource.includes('failureKind: "bridge-execution-environment"')
&& agentRunSource.includes('key === "nextActions"'),
"AgentRun CLI bridge must use the remote frontend backend in runner/no-Docker environments and classify bridge failures separately",
);
assertCondition(
!agentRunSource.includes('degradedReason: "agentrun-cli-bridge-failed"'),
"AgentRun CLI bridge must not collapse official AgentRun failures into bridge failures",
);
console.log(JSON.stringify({
ok: true,
checks: [
@@ -96,5 +111,7 @@ console.log(JSON.stringify({
"AgentRun command help presents heredoc/stdin before reusable file fallbacks",
"global help indexes AgentRun v0.1 entrypoints",
"AgentRun control-plane status degrades empty runtime JSON snippets",
"AgentRun CLI bridge selects remote frontend backend in runner/no-Docker environments",
"AgentRun CLI bridge keeps AgentRun failures distinct from bridge failures",
],
}));